SpamSieve score calculation for existing mails

That sounds like a great solution and would perfectly fit my needs (both actions, actually :) )!

Running 'Evaluate' or 'Recompute Score' on selected messages only makes perfect sense, I'd only like to ask for a 'separator' in the context menu to indicate that Junk/Not Junk and the extra operations are different beasts.

Hi Benny, I've checked the 'Recompute Score', and it did what I wanted, but I might have been a bit too optimistic when marking ~4000 Mails, so SpamSieve was busy for a minute, but MailMate needed ~30 minutes to recover to become responsive again. Is there any post-SpamSieve action involved now that could stall MailMate or was this still the SpamSieve 'Recomputation'?

Each email is sent (in full) to SpamSieve using AppleScript. This is going to be slow for a large number of messages. The only possible improvement is to do it in a separate thread, but this won't be high on my list for now.

Another reason for MailMate stalling seems to be when a few thousand messages are selected (or when I go back to a folder where all messages are selected). I can live with that and the feature above works fine. One minor thing though, there is no SpamSieve score anymore for messages that are marked as Junk/NotJunk, but this field can not be shown, so there's simply an empty SpamSieve score. Still, I tested both new context menu options and they behave well.

Thanks a lot - now MailMate can be used as a fine-granular tool to train SpamSieve and I can also clean my messy mailboxes from all that never treated Spam :)

I didn't understand the “minor thing”? Does MailMate delete the SpamSieve score when you mark something Junk or Not Junk?

As soon as I mark a mail as Junk or NotJunk the SpamSieve score disappears in the column. I guess because it's then a clear '100%' decision, but this is a bit of a mystery to me.

Or let's phrase it differently: The score is a probability, where I could understand if one argues that as soon as it's used for training, it's definite and a probability cannot be attributed. But personally I think the score could be helpful even for training mails.

I then thought that maybe there's a Junk State field (for mails marked as Junk/NotJunk) that is toggled instead when the score goes away, but I can't find a column header for this.

Ah, I had forgotten about that. Yes, it's cleared because it's essentially overridden by the user.

You can map tags to the $Junk, $NotJunk IMAP keywords and then enable the Tags column. A more “raw” approach is to enable the “Raw Flags” column (which I ought to rename IMAP Keywords).

Hm, the $Junk keyword seems to work as a tag with an Emoji, but the $NotJunk for some reason not (though visible as a raw keyword) ...

I actually reran the 'Recompute Score' on my Junk mailbox and found out that many mails get a rather low SpamSieve score when re-evaluated (not 100% as I thought). So I tend to think the SpamSieve score should remain to be able to correct SpamSieve.

Hi Benny, after some further thinking and looking at my mailboxes, I believe that the SpamSieve score should remain also for mails that have been user-marked, especially since the raw flags contain the Junk/JotJunk marking.

The $NotJunk as emoji seems to work now, but I can't find out why it didn't before.

Btw., is there any distinction between Junk/NotJunk triggered by the user or by SpamSieve?

Thanks again for your prompt addition of the aforementioned feature - still very helpful! :)