With both Apple Mail and Outlook, the number of false positives, i.e., good emails that go to the JunkMail folder, is very high, requiring constant monitoring of the JunkMail box a somewhat self-defeating exercise time-wise. The resident filter in Apple Mail is completely incompetent (as was the one in Outlook previously) it learns very poorly and continues to deliver the same crap from the same addresses into my Inbox. I’ve been suffering a literal spam invasion, getting somewhere around 2000 a day from my four email accounts. Note that I am still not able to reproduce the problem myself which means that feedback on the solutions above is still appreciated.I installed a fully functional trial version of SpamSieve on the recommendation of my friend Leisureguy a couple of weeks ago. 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). 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. Killing the appleeventsd daemon fixes the problem temporarily ( Antonin Hildebrand discovered this fact).NSAppleScript and osascript are not affected by the problem.This is what is used for the workaround in MailMate. Using typeKernelProcessID for the target type still works (thanks goes to Brian Webster for this crucial fact).The problem is related to the use of the AESendMessage/AESend functions used with typeApplicationBundleID or typeApplSignature for the target type.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |