SpamSieve 3.0.5

SpamSieve 3.0.5 is a free update for those who have already purchased the SpamSieve 3.0 upgrade. If you’re using SpamSieve 2 and haven’t upgraded yet, the easiest way is to first let SpamSieve install the new version. At launch, it will show the Purchase window, and you can click the Check Upgrade Options button to get the upgrade discount without having to enter your old serial number.

Normally, SpamSieve will automatically offer to update you to the new version. There are also instructions for updating on this page. SpamSieve 3.0.5 is compatible with macOS 10.13 (High Sierra) through macOS 15 (Sequoia) and is recommended for all customers using those versions of macOS. Older versions are also available for macOS 10.12 (Sierra) and earlier.

The changes in this version are:

Apple Mail
  • Preliminary testing shows that SpamSieve is compatible with macOS 15 Sequoia Developer Beta 2. Further updates may be required when Apple updates Mail in a subsequent Sequoia beta.
  • Worked around some problems where Mail could temporarily hang during spam filtering if the network connection was very slow or when encountering a macOS bug where Mail redownloads messages that have already been downloaded. If SpamSieve detects that Mail is slow reading a message, it will postpone filtering for a while to give it time to finish downloading everything. It can also help to go to Mail ‣ Settings ‣ Accounts ‣ Account Information and set Download Attachments to All for each account. This will encourage Mail to fully download messages right away.
  • The Filter Now button in Settings ‣ Apple Mail ‣ Filtering can now be used to manually filter the Mail inboxes, even when automatic filtering is disabled or postponed.
  • Worked around an issue where sometimes filtering in Mail didn’t work because Mail was so bogged down that it couldn’t read the inboxes for SpamSieve in a timely manner.
  • The mailbox outline for Filter spam messages in other mailboxes now recognizes the lowercase spam and junk names as being for mailboxes that should not be filtered.
  • Fixed a bug where SpamSieve would try to repair files related to Mail plug-ins when running on macOS 14, which doesn’t support plug-ins.
  • Fixed a bug where updating certain settings could cause a spurious error to be logged if you were not using the Mail plug-in.
  • Improved the error reporting to track down a Mail AppleScript issue when finding new messages to filter.
Microsoft Outlook
  • The Settings ‣ Outlook ‣ Setup window clarifies that, when using Enable spam filtering for Inbox, the non-spam messages left in the inbox are marked with the Good category after SpamSieve has processed them.
  • Fixed a bug where the notification score slider was too narrow on macOS 10.13.
  • Modernized the editable text fields to use shaded bezels instead of solid lines.
  • Secondary label text throughout the user interface now uses the modern gray coloring.
  • Due to a macOS bug, clicking the SpamSieve menu bar icon does not show the menu when the Mac has multiple displays, a window on the secondary display is full screen, and you are clicking the menu bar icon on that display. You can work around this by accessing the SpamSieve commands in another way (e.g. via the keyboard shortcuts or the menu bar icon on the main display) or by unchecking Show Dock icon in the settings.
  • Fixed a bug where the application icon in the Dock or Command-Tab switcher could appear pixellated when it was badged to show that SpamSieve was in the process of filtering or training a message.
  • SpamSieve now disables automatic filtering for Apple Mail and Outlook when the Mac is not connected to the Internet, to avoid hangs that could occur when trying to read messages that can’t be downloaded from the server.
  • The Open in External Viewer command now works in the Corpus and Log windows when the table view has a selected message but doesn’t have keyboard focus.
  • Improved the error reporting when a database can’t be accessed because the disk is full.
  • Worked around a problem where SpamSieve could crash if Core Data’s conflict resolution failed because the database file was damaged.
  • Made various updates for macOS 15, Xcode 16, and Swift 6.