![]() 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. Updated the Setting Up MailMate instructions for the new preferences in MailMate 1.1.2. Improved compatibility with Mac OS X 10.7 (Lion). This has been confirmed by a user ( Torsten Grust) in the context of MailMate/SpamSieve. Made various changes to improve SpamSieve’s filtering accuracy. ![]() 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. It’s quick and easy to control SpamSieve from within Apple Mail (Mail.app), Airmail, Entourage, MailMate, Mailsmith, Outlook, Postbox 5, PowerMail, and more. Works with IMAP, Exchange, and POP mail accounts. Killing the appleeventsd daemon fixes the problem temporarily ( Antonin Hildebrand discovered this fact). SpamSieve gives you back your inbox, using powerful Bayesian spam filtering to provide amazing accuracy that’s constantly improving.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.The problem is related to the OS X 10.8.2 update. Microsoft Outlook > Tools > Junk E-Mail Protectionouble-click on the SpamSieve application icon to open the program.This is what is currently “known” about the problem: You can read about Brian’s findings here. But a much better understanding of the problem and a better workaround came about when Michael was contacted by Brian Webster. In short, Michael Tsai (SpamSieve developer) joined the discussion and we found a workaround involving a different approach to the AppleScript communication between MailMate and SpamSieve. The time line of an investigation of this problem can be seen in this ticket. You can find and kill it in the Activity Monitor or you can paste the following in a Terminal window (requires a password): You can also temporarily fix the problem by killing a process named appleeventsd. If you have a Mac App Store license then you cannot update to a test version. ![]() If you think you have this problem with MailMate/SpamSieve then you should fetch the current test version of MailMate by holding down ⌥ when clicking “Check Now” in the Software Update preferences pane of MailMate (note that, in general, test versions are not always stable versions of MailMate and they may include incomplete features). See further below for more technical details and a bit of insight into the detective work some times needed in the software development process. Each request sent by MailMate to SpamSieve hangs for 2 minutes before failing with a timeout error. ![]() The problem turns out to be that the AppleScript communication between MailMate and SpamSieve breaks down. Since Apple released the 10.8.2 update for Mountain Lion I have received several reports about MailMate being slow and unable to detect spam. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |