9/14/2023 0 Comments Spamsieve crashing 2019![]() ![]() For information about previous releases of SpamSieve, please see the version history. Older versions are available for older operating systems. ![]() SpamSieve 2.9.31 works with macOS 10.7 through 10.13 and requires an e-mail client. Fixed a crash reporter bug that could prevent some information from being logged.Diagnostic reports now include more information about localizations and SpamSieve helper processes.The Apple Mail - Discard Spam script is better able to work around Mail slowness that could leave spam messages stranded in the trash.Worked around a bug in macOS 10.13 that could cause an internal error at launch when resolving an alias.chezpaul (chezpaul) December 4, 2019, 7:32am 1. New SpamSieve 2.9.11 crashes mac, cant do anything. Automatically Deleting Old Spam Messages Last night she got a message asking to update spamsieve to the latest version I’ve used spam sieve forever now.Improved the following sections of the manual:.The Outlook sections of the manual have been renamed to Setting Up Outlook 365 and Setting Up Outlook 2011 for clarity.Postbox 6 no longer supports plug-ins, so we recommend continuing to use Postbox 5 for the time being or using the Apple Mail drone setup in the background. Updated the Requirements and Setting Up Postbox sections of the manual.Outlook - Filter Mailboxes now checks for new inbox messages every 1 minute by default (instead of 5), is more efficient, and is able to filter inboxes with localized names that were previously ignored.Fixed a database bug that could cause SpamSieve to crash when processing a particular type of spam message containing garbage Unicode characters in the subject.Made various changes to improve SpamSieve’s filtering accuracy.This is a free update that includes the following changes: Version 2.9.31 of SpamSieve is now available. Is there any way I can restore Spam Sieve without Mail tossing its cookies like this? SpamSieve has served me well–maybe I just will leave the Corpus alone next time.The following was posted on the SpamSieve blog: ![]() ![]() Previously, I just ignored the hint and let it grow and grow. Note that this is the first time since I installed SpamSieve on my system that I actually followed the hint and reset the Corpus. I think that pretty much points a very damning finger at the SpamSieve mailbundle!!! As soon as I did that and restarted Mail without doing anything else (no more restarts, no switching off haxies, etc.), Mail not only stopped crashing, it continues to stay up as of now. So, in desperation, what I did was go into /Library/Mail/Bundles and moved SpamSieve.mailbundle into /Library/Mail/Bundles (Disabled). And the Mail crash log was very explicit about which thread had caused the crash: the one with the hundreds of SpamSieve lines. Where xxx was some number between 60 and 100. Each time, in the Mail.crash logs, the crashed thread had hundreds of lines (up to 496 of them) of the form: And it crashed after staying up for maybe 30 seconds. I followed your instructions and restarted my Mac. Nope, didn’t work but something else did which confirmed my suspicions There’s actually a lot more (goes up to line 496 that’s identical to line 37 above). And then Apple Mail crashed and wouldn’t start without crashing so I’m in the middle of an Envelope Index rebuild right now by doing the reimport method. I used the “Train as good” plugin and surprisingly, the email didn’t get moved to my Inbox like it normally did. Then I noticed that one legitimate email was in the Spam folder. I reset SpamSieve’s corpus today just to cut the bloat and retrain SpamSieve. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |