SpamSieve 3.1.3b1 Public Beta

[Michael_Tsai]

Here’s a new beta version of SpamSieve. The changes are:

• Made various changes to improve SpamSieve’s filtering accuracy.
• The new MailMaven e-mail client from SmallCubed is now in public beta, and it includes built-in support for SpamSieve. The SpamSieve manual now includes sections for Setting Up MailMaven and Checking the MailMaven Setup, and these are linked from the Settings ‣ Other Clients window.
• SpamSieve is better at detecting whether a server junk filter classified a message as spam (for display in the Log and Corpus windows).
• Clicking a notification to open the message in SpamSieve’s Log window now works when SpamSieve isn’t already running.
• When using the Show number of new good messages in Dock option with the Apple Mail extension and the Check inboxes for new messages not sent to Mail extension option, the number shown in the Dock icon is now accurate even if the same message had been processed twice.
• Improved the efficiency of updating the rule hits statistics, reading settings, and various database operations.
• Improved the following sections of the manual:
  • Show Dock icon
  • Show number of new good messages in Dock
  • Turning Off New Outlook
  • Turning Off the Fastmail Spam Filter
  • Why are Apple Mail inbox messages not being processed?
• Improved the handling of AppleScript errors if you train a message when Apple Mail is overloaded.
• Worked around a bug where Apple Mail would ask the extension to filter messages that were drafts.
• Made further changes to prevent SpamSieve from triggering local network privacy prompts.
• SpamSieve will now report an error if it looks like filtering is being impacted by the Mac’s clock being wrong.
• Fixed a bug where search fields weren’t appropriately cleared when clearing a search.
• Fixed a bug where the training toolbar buttons were enabled in the Words tab of the Corpus window.
• Changes to the esoteric preferences from Terminal now take effect right away.

If you have not installed a beta version of SpamSieve before, first click here to enter the beta key. Thereafter, you can just launch SpamSieve or choose Software Update from the SpamSieve menu to auto-install the beta. SpamSieve will also notify you about future betas automatically. You can click here to stop receiving in-app notifications of beta versions.

[Austin_Baze]

Thanks for frequent updates, enhancements and fixes. Just installed. One question (not unique to SpamSieve): Is it hard to code the password entry requirement to complete installation to use the TouchID on my Mac Studio (keyboard) instead of a typed password?
Some apps do, some don’t, some Apple modifications do and even some of those don’t. I would love all requests for password verification to use the biometric when available. Just curious.

[Michael_Tsai]

@Austin_Baze

Is it hard to code the password entry requirement to complete installation to use the TouchID on my Mac Studio (keyboard) instead of a typed password?

I don’t think the API we’re using supports biometrics at all. However, it may be that authentication is not actually needed for updating SpamSieve on your Mac. You can click here to tell SpamSieve not to ask for this permission or click here to go back to the default.

[Austin_Baze]

Thanks for that. Just updated Sequoia and Apple itself is not using its own API that supports its own biometrics. I would say it’s something around 60/40 in Apple directed upgrades that require verification which actually use built-in biometrics that (I assume) Apple has access to.

[ddauerbach (David Auerbach)]

I’ve been meaning to thank you for supporting MailMaven and doing it so seamlessly. I’ve been using MailMaven for months now (and liking it, though it is still a beta) and had to do almost exactly nothing to get to work with SpamSeive. Moreover, SpamSieve support is built in to it, so menubar not needed–just drag the offending (or non-offending, as the case may be) message to where it belongs.

[Michael_Tsai]

@ddauerbach

Moreover, SpamSieve support is built in to it, so menubar not needed–just drag the offending (or non-offending, as the case may be) message to where it belongs.

At least in my testing, moving messages in MailMaven, e.g. dragging them into or out of Junk, does not train SpamSieve. You would need to use the menu commands or buttons. Are you seeing otherwise in the Log window?

[ddauerbach (David Auerbach)]

I’m an idiot.
At some time, when I first learned the MailMaven had built in support, I somehow end up assuming that draggingand dropping did the job. AND, because I had been training SpamSieve for years on Mail, any glitches with doing that just didn’t catch my eye. Confirmation bias. But, I suppose I can consciously test it.

[ddauerbach (David Auerbach)]

This is amusing: The latest beta from MailMaven adds the feature I thought it had. Moving messages to (or from) junk trains SpamSieve!
I was prescient.