![]() ![]() Note that I am still not able to reproduce the problem myself which means that feedback on the solutions above is still appreciated. Thanks to everyone who helped track down this problem. This has been confirmed by a user ( Torsten Grust) in the context of MailMate/SpamSieve. It also indicates that triggering this problem involves relaunching the target application (in order to give it a new process id). Spamsieve 2.9.46b1 not working with Monterey Beta 9. Beta fixed the problem with training as bad, but only for a day. The above indicates that the problem is likely to be some kind of stale cache used by appleeventsd for mapping bundle ids and 4-letter application signatures to process ids. Training not working on POP mail account. Killing the appleeventsd daemon fixes the problem temporarily ( Antonin Hildebrand discovered this fact). If for instance I reset the Spamsieve conditions by running the 'spam setup assistant' from the prefs, and ask successively for the three conditions that lead to the 'usual' setup ('not in previous, etc.), all new spam jumps right in my incoming folder and I can perfectly see SpamSieve is not activated (it is not even launched if it doesn't run).NSAppleScript and osascript are not affected by the problem. SpamSieve uses blacklists and whitelists to help determine what's spam and what's not, but it also uses Bayesian filtering, in which the software learns. ![]() This is what is used for the workaround in MailMate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |