![]() ![]() I’ll keep an eye on the logs and report back. OK, I just set up the script rule and disabled the regular SpamSieve rule (and reactivated the Remote Training and Server Junk Mailbox SpamSieve rules). ![]() This suggests to me that the script rule will probably work for you, since it moves messages in the same way as the drone. The Catalina bug with disabled accounts ( #3 here) only applied to manually training messages as good. OS X’s imaging subsystems and leading to crashes. 124 if you find that corrupt files are confusing Mac. Attached is the Crash Log which has many references to SpamSieve. I have tried to solve this by deleted about 3500 messages out of In boxes as well as 2000 that were in SpamSieve, I have also done a systems reinstall, nothing seems to help. And then you could easily review all the gray messages in the inbox (by clicking on the expanded flag icon) to delete the spam. 123 the contents of attached images and PDF files to help detect whether a message is spammy. Mail rules doen’t seem to be applying the rules to all the messages, also Mail keeps crashing. with the gray flag) instead of moving them. Or, you could make the SpamSieve rule flag the messages (e.g. One potential workaround is to use a script rule instead of a Move Messages rule. It’s one reason I don’t recommend that people update to Catalina. Fortunately, this only seems to happen for a fraction of a percent of users, but obviously it’s quite serious for that group. Unfortunately, one of the Mail bugs we’ve seen with Catalina is that rules that move messages (both regular and SpamSieve) sometimes delete the messages instead. What type of mail account are you using? Do you have the SpamSieve rule set to move messages to a mailbox on the mail server or under “On My Mac”? For information about previous releases of SpamSieve, please see the version history.I updated to version 2.9.38, but I’m still seeing messages automatically marked as spam disappearing completely-I can see them in the log, but they do not appear in my spam folder. Older versions are available for older operating systems. The problem seems to occur when checking one of my gmail accounts - it doesn’t happen if I remove SpamSieve. SpamSieve 2.9.31 works with macOS 10.7 through 10.13 and requires an e-mail client. Hello - Since upgrading to Yosemite, I’ve had sporadic problems with Mail crashing when it checks all my accounts on opening. 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.In any case, 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. ![]() It’s easiest if you update to SpamSieve 2.9.21 before updating to El Capitan.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |