![]() ![]() Spam, or electronic junk mail, has been clogging email boxes for years now, and it’s only getting worse. If you use email, you know what we’re talking about. ![]() Email was so close to attaining electronic communications utopia! Unfortunately, it never made it, and it never will, because the spammers went and ruined everything. It allows people to send free messages that can be accessed instantly, it allows people to create electronic communication archives, and it breathes new life into the age-old tradition of letter writing. Note that I am still not able to reproduce the problem myself which means that feedback on the solutions above is still appreciated.AirPort Apple Apps Backups Developer Education Email Hardware Internet iPad iPhone Mac Music Network Photos Security TV Weekend WonkĮmail is almost the perfect communications method. 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.The problem is related to the OS X 10.8.2 update.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 |