![]() Why do good messages keep going to the Junk or Spam mailbox? Separate Spam Mailboxes for Each Account Fixed a bug where certain Unicode character sequences in a message’s address list could cause SpamSieve to hang when matching against a rule list Worked around a macOS bug that could prevent a rules file written on macOS 12 on an M1 Mac from being properly read on macOS 10.15 It also now helps you figure out if Outlook Filter Mailboxes doesn’t have Automation access to control SpamSieve. Updated the Outlook Filter Mailboxes helper app to work around a problem where macOS 12.3 would report an error at launch. However, if you don’t see the SpamSieve commands in Apple Mail’s Message menu, be sure to choose Install Apple Mail Plug-In from the SpamSieve menu and to enable the plug-in. SpamSieve 2.9.49 should automatically update the installed version of its Apple Mail plug-in, and the plug-in should stay enabled. We recommend updating SpamSieve before updating macOS. Added support for Apple Mail on the forthcoming macOS 12.5 and macOS 13 Ventura. Reduced the size of the app by removing a helper tool that was only necessary for Apple Mail on macOS 10.7, which is no longer supported SpamSieve is better at handling damaged rules files Fixed a bug that in rare cases could prevent SpamSieve from detecting that two copies of the Apple Mail plug-in were loaded at the same time Fixed a bug where SpamSieve could incorrectly report that another copy of the Apple Mail plug-in was installed in the wrong place, when that copy might be necessary for another macOS user account on a different volume Made a change to prevent potential problems setting up the Message menu in Apple Mail on future versions of macOS 13 Ventura Fixed an issue where, on macOS 12.5, sometimes SpamSieve would disable its Apple Mail rules because it looked like Mail hadn’t loaded the plug-in, but actually Mail was just slow to launch Fixed an issue where, on macOS 12.5, sometimes Mail would move e-mails received immediately after launch to the Junk mailbox without asking SpamSieve whether they were spam Why do good messages move to the wrong inbox when trained in Apple Mail? Why are messages marked as spam in Apple Mail but not moved? What can I do if my Spam or Junk mailbox in Apple Mail disappeared? ![]() How should I configure the junk filter on my mail server? Improved the following sections of the manual: SpamSieve now requires macOS 10.13 (High Sierra) or later ![]() Added a workaround to the Apple Mail - Remote Training script for some users whose messages were not being moved out of the TrainGood mailbox The Apple Mail - Remote Training script now skips accounts that are disabled in Mail to avoid spurious errors ![]() ![]() The Apple Mail - Rescue Good Messages script now has an option to remove colored flags that were added by the server junk filter, as these can make spam messages show up in Mail’s special mailboxes even after they’ve been deleted Improved the erro reporting when the Apple Mail plug-in cannot be installed due to a file permissions problem. If training a message doesn’t work due to an AppleScript failure, the error message now explains how you may be able to fix this by removing problematic legacy component files from your Mac Improved the diagnostic report on macOS 13 Renamed Preferences to Settings for macOS 13 When using Apple Mail, SpamSieve installs a launch agent, and this now shows up as SpamSieve rather than as C-Command Software in System Settings ‣ General ‣ Login Items ‣ Allow in the Background on macOS 13 Made various changes to improve SpamSieve’s filtering accuracy ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |