[MlMt] Keybindings and IMAP flags?

[Bill Cole]

On 27 Sep 2018, at 16:07 (-0400), Randall Meadows wrote:

> So, I'm trying to learn and embrace key bindings.  I have a series of 
> commands to TrainSpam in conjunction with SpamSieve::
>
> "s" = {
> 	"#1" = ( "markAsJunk:", "setTag:", "\\SEEN", "moveToMailbox:", 
> "<<path to spam mailbox>>");
> 	"#2" = ( "markAsJunk:", "setTag:", "\\SEEN", "moveToMailbox:", 
> "<<path to spam mailbox>>");
> 	...
>
> which works just fine, apparently.  I've tried to do something similar 
> with TrainGood, but MM complains about an invalid flag or something.  
> What's the proper way to do this:
>
> "g" = {
> 	"#1" = ( "markAsNotJunk:", "setTag:", "\\UNSEEN", "moveToMailbox:", 
> "<<path to good mailbox>>");

'\Seen' is a standard IMAP keyword (as indicated by the leading '\') 
which is either set or not set to denote whether the message has been 
seen or not, i.e. read or unread. The MailMate selector to unset a 
keyword or a MailMate tag (which is mapped to an IMAP keyword) is 
'removeTag:'. Keywords are case-insensitive.

'\UNSEEN' is NOT a standard IMAP keyword, and I would expect most IMAP 
servers to to reject any attempt to create it, since that leading '\' is 
meaningful in the protocol.

Since read/unread state is logically a pure binary, having distinct 
'\Seen' and '\Unseen' keywords isn't just unnecessary, it would lead to 
4 possible states: read, unread, neither read nor unread, and both read 
and unread. Absent quantum computing, these would be 2 states too many.



-- 
Bill Cole
bill at scconsult.com or billcole at apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole