I’m testing SpamSieve and I would like to disable spam capabilities on Microsoft servicies (no problem in Google til the moment).
The instructions are in section 7.6.9 on SpamSieve documentation. But they don’t apply for my setup since I have Microsoft 365 instead of outlook.com. Hence, I following these other instructions (which seems to be the same place for the instructions provided by SpamSieve in first place):
Things are not working as expected. Spam mails go to the main inbox as expected but if I classify them as spam, they are moved to the junk folder and most times, later, the mail trained as spam goes back again to the inbox.
I presumen that the problem maybe on the SpamSieve side (or the problem is more complex than expected). Today, I have three spam mails, I used them to train SpamSieve, they were moved to the junk folder and the behaviour was that only the most recent one (latest to arrive) was moved back to the inbox folder. Let me know if further information is required.
Which mail client app (Apple Mail, Outlook, etc.) are you trying to use with SpamSieve?
SpamSieve doesn’t move messages out of Junk, and you’ve set up your own flow that does move messages out of Junk, so most likely that’s the source of the problem. Maybe it is getting confused about whether or not the messages are new. Does the problem go away if you turn off the Power Automate flow?
Ultimately, it’s a Microsoft problem if their spam filter is misbehaving and can’t be turned off. However, we do have a way in Apple Mail where you can set up SpamSieve to rescue good messages that were incorrectly caught by a server filter.
I miss important information, I’m using Apple Mail.
I assume that SpamSieve doesn’t move messages of Junk but I would say that the point is how SpamSieve move the messages to the Junk.
If I turn off Power Automate everything works as expected BUT some mails are classified as SPAM by server side which is quite annoying (that is the reason of testing SpamSieve).
I will check the script that you mention but my first impression is that will make the workflow “weird”. I would like to know if this option is recommended and usually used.
It is becoming more common because a lot of people now have server filters that they can’t control. This feature will eventually be built directly into the app so that you don’t need to set up a script.
I’m obtaining the following message from SpamSieve app:
SpamSieve has deactivated its Apple Mail rules.
macOS 14 Sonoma removes support for Mail plug-ins, so SpamSieve has deactivated its rules that depend on the plug-in so that they don’t move good messages to the Junk mailbox without consulting SpamSieve. SpamSieve now uses a Mail extension, which does not require any rules.
If you are also using SpamSieve on another Mac with an earlier version of macOS, you can leave the rules inactive on this Mac and active on that Mac. Otherwise, click “Uninstall Plug-In…,” SpamSieve will remove the rules on this Mac, and iCloud will then remove them from your other Macs.
This happens each time I open Mail.app. I can manually active the rule. Is there any way to check if an e-mail comes from Junk folder? Just to check in some moment if the manually activated rule works as expected (while the Mail.app is not completely closed), although it will not happen frequently (false-positive should not happen frequently).
Like the error says, after updating to macOS Sonoma, you should either leave the rule inactive or delete it. For more information, please see this page.
Sorry, If I’m not very smart but the last link to make SpamSieve to process unread messages in other folders does not apply to junk/spam folders since are not eligible. The rule that is giving the error message is related to the apple script to rescue good messages that it was recommended previously. The instructions say as follows:
Go to Mail’s Preferences window and create a new rule at the top of the list (above the SpamSieve rule, if present) called Rescue Good Messages SpamSieve.
The rule conditions should say Every Message.
The rule actions should say Run AppleScript […]Apple Mail - Rescue Good Messages.scpt. First, choose Run AppleScript from the pop-up menu; then select the Apple Mail - Rescue Good Messages.scpt file (using either the pop-up menu or the Choose… button).
Probably I’m wrong but, could it be that these instructions would be designed for the plug-in based install instead of the extension based install?
The error message about the rule is because of a rule called SpamSieve (or some variant starting with that), which was only used with the old plug-in setup from before macOS Sonoma. The rule for rescuing messages out of Junk should be called Rescue Good Messages SpamSieve and therefore shouldn’t trigger the error. This rule works with both the plug-in and extension setups.
Thanks, I changed the name, sorry for the disturbance. I didn’t thought that it would be a problem. After changing the name of the rule and restarting Mail.app, no problems so far.