[MlMt] Recreating an old workflow in MailMate[Mailing Lists]

[Zvi Biener]

Just one more note.

I noticed that sometimes my inbox rules do not get automatically 
applied. I can’t figure out the conditions, although I’m pretty 
certain that a sufficient (but not necessary) condition is that another 
email program (say, on my phone) has retrived the messages before MM 
has. It doesn’t make much sense to me, but there it is. And, again, 
this isn’t necessary.

The solution is easy, just run the rules (there is a key shortcut), move 
away from the inbox, and then back to the inbox. (MM will not 
‘disappear’ the messages from under you, it waits until you revisit 
the mailbox). You can make a keybinding for this, which makes it very 
quick.

I would be interested to know if anyone else has seen this behavior with 
rules, and if you can tell under what conditions it happens.

Zvi



  A flaw to the first system below that the second system didn’t have: 
when a message arrives in the Inbox, sometimes the rules

On 9 Dec 2022, at 11:28, Zvi Biener wrote:

> This is my solution. Honestly, I implemented this two days ago, so I 
> can’t tell you how flawlessly it works, but it has worked ok for 48 
> hours.
>
> 1. I have several smart mailboxes defined for mailinglists. Each smart 
> mailbox uses conditions like “From:”, “To:”, and 
> “Subject:” depending on how the mailing list works. (As Henry 
> says, not all mailig lists play nice with the appropriate headers, so 
> this is the only way to get around that, as far as I know).
>
> 2. I have a rule in my inbox that says: if <message-ID> is in 
> <smart-mailbox> <message-ID>, then archive the message.
>
> So when a message arrives, the smart mailbox should match it, and then 
> the rule should move it out of the inbox. It will still show as unread 
> in the smart mailbox.
>
> Previously, I had a converse of this system:
>
> 1. A rule on the inbox that matched various “From:”, “To:”, 
> and “Subject:” fields, then tagged the message with the keyword 
> “ListServ” and archived it.
>
> 2. A smart mailbox that matched the keyword “ListServ”.
>
> Zvi
>
> On 9 Dec 2022, at 11:07, Henry Seiden wrote:
>
>> Zac,
>>
>> I think you mean Inbox in MM terminology. But yes, I agree that mail 
>> stays where it is, same philosophy as all source mail locations in 
>> MM.
>>
>> As to the other point about the decision to treat Mailing List items, 
>> it’s all about the header info in MM. The categorization as to 
>> whether an item is a mailing list item, depends on the header 
>> characterization of the item itself. So if the header is categorized 
>> (by the sender) as a mailing list item as that it will appear in the 
>> MM defined category. If you disagree with that philosophy, then you 
>> are free to establish your own conditions/rules as to what is 
>> categorized and make a set of smart mailboxes of your own.
>>
>> Respectfully,
>>
>> Henry Seiden
>> - -
>> Techworks Pro Co.
>> E: info<at>techworkspro<dot>com
>> W: http://techworkspro.com
>>
>> On 9 Dec 2022, at 10:44, Zac Belado wrote:
>>
>>> Typically what I used to do with a mailing list was have a folder 
>>> that I moved messages to when a mailing list message came in. Now I 
>>> know that MailMate has its own Mailing Lists dropdown but I have two 
>>> problems with it
>>>
>>> 1.  It creates lists for anything that it thinks is a mailing list 
>>> including a series of receipts I have from an electronics store I 
>>> shop at
>>> 2.  It doesn’t remove the message from the mailbox when it 
>>> arrives._______________________________________________
>> mailmate mailing list
>> mailmate at lists.freron.com
>> https://lists.freron.com/listinfo/mailmate
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freron.com/pipermail/mailmate/attachments/20221209/30134f27/attachment.htm>