Worked around an issue that could prevent some Apple Mail messages from being filtered through SpamSieve if SpamSieve had not yet launched and the Mac was overloaded, e.g. (If you weren’t seeing this problem or have no disabled accounts, it’s not necessary to update the plug-in.) This fix is available for all new installations and for older ones if you choose Install Apple Mail Plug-In from the SpamSieve menu. Worked around an AppleScript bug in Apple Mail on macOS 10.15 that could result in messages trained as good being moved to the inbox of an account that’s disabled, making it look like the messages disappeared. The latest information about Catalina is available here. SpamSieve 2.9.38 (and also 2.9.37) are compatible with macOS 10.15, however a small number of customers are seeing issues with the Catalina version of Apple Mail. This is a free update that includes the following changes: It does not need access to your mail account login and does not transmit your mail data anywhere. SpamSieve running on your Mac can keep the spam off your iPhone/iPad, and you can even train SpamSieve from your iOS device. It’s quick and easy to control SpamSieve from within Apple Mail, Airmail, Entourage, MailMate, Mailsmith, Outlook, Postbox 5, PowerMail, and more. SpamSieve learns and adapts to your mail, so it’s able to block nearly all the junk-without putting good messages in the spam mailbox. SpamSieve gives you back your inbox, using Bayesian spam filtering to provide amazing accuracy that’s constantly improving. Save time by adding powerful spam filtering to the e-mail client on your Mac. Version 2.9.38 of SpamSieve is now available. The bottom line is that if the drone scripts seem not to work for you, there is a chance that there is an issue with your box rather than with spamsieve and the drone scripts.The following was posted on the SpamSieve blog: I have been tempted to reinstall the dual G5 machine completely to see if this fixes the problem, but simply haven’t had the time. Same compiled scripts, no changes from the G5 box. I moved everything over to a mostly unused first-gen mini that was sitting around, and all works flawlessly. The scripts in the “drone” publication also fail to work correctly on my dual G5 machine. A force-quit and restart of mail.app fixes everything until the next time it fails, again without any notice.Īnecdotally, I have a at least one friend who has had similar issues with mail.app on his dual G5 machine. Unfortunately, the only way you can tell that mail.app has failed is to check things by hand. Alas, a simple check using another box or web interface proves this to be incorrect. I have noticed an issue with mail.app on the G5 box where mail.app crashes gracelessly – that is to say, when you ask it to check for new mail (either automagically or explicitly using the dropdown menu for same) mail.app will tell you blithely that there’s nothing new waiting to come down. For the record, there were problems before spamsieve, and unsurprisingly, they didn’t go away while I was playing with spamsieve. I have noticed problems with mail.app on my dual G5 2.3 box. Mail.app (IMAP) on a dual G5 drone problems and a brute-force fix I suspect that something could be cobbled together using a variation of the “drone” approach to make this process cleaner. While this approach lacks elegance, it gets the job done and serves to provide me with a usable inbox on those occasions when I don’t have access to any of my own machines and have to use the web interface to check my mail. When I’m scanning through the IMAP spam folders and find something which has been misclassified as spam I flag it and then tell SpamSieve that it is good next time I’m using the guilty machine so it doesn’t do it again. What matters for me is training the specific machine which occasionally marks something good as spam. Someday when it is possible to merge the corpuses (corpii?) I’ll do it, but in the interim it doesn’t really matter. When I look at my IMAP folders, I see something like this:įor purposes of training SpamSieve that a given piece of spam has leaked through to my inbox, I don’t really care which machine gets the lesson. I got around the question of “how do you know which machine and filterset marked a given piece of mail as spam so you can train it” by telling each of the machines to put spam in a dedicated folder on the server. The third is my notebook, which is running only part of the time. One faces the intarweb and routes my household, and the other is a “communal” box in our living area. Two of the machines are almost always running. I have been running SpamSieve on three different boxes for several months with good results, and without using the “ drone” approach (which incidentally looks interesting.) SpamSieve on multiple machines with IMAP - a workable approach
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |