So if you're going to be using SpamSieve, keep a collection of spam in a separate folder for training before you begin. The instructions suggest fishing these out of your trash, but the problem is that if your spam is in the trash it's almost certainly mixed in with a lot of good messages and now you have to manually tease them apart. DON'T DO THIS! The training process requires about 600 representative spam messages. The messages will be colored in gray and moved to the Junk mailbox. The instructions say to delete the messages in your current spam folder before setting up SpamSieve. To train SpamSieve with spam messages, select one or more of them in Mail and then choose SpamSieve - Train as Spam from the Message menu. I do have one complaint: the instructions for the initial training process are a little unclear, and in one place downright misleading. My spam problem is (I almost dare not say this for fear of tempting fate) effectively solved. New installations of SpamSieve will use the Junk mailbox by default, and the manual has been rewritten with this new setup in mind. I've had one false positive during the training process, and the false negatives have rapidly dwindled to 1-2 a day. I've only been using (which is to say training) it for three days, but the situation is already dramatically better than it was before. I was a little skeptical that it would work much better than Apple's built-in filter, but there's a 30-day free trial so I didn't have much to lose. I was about to throw up my hands in despair and set up a second mail server for Microsoft users, when I decided instead to try SpamSieve. Issues: When I use the Message > Train as Spam function, Mail DOES NOT MOVE THE MESSAGE TO THE SPAM FILTER. One man's spam is another man's hot deal of the week from his favorite on-line vendor, and the training process can get really annoying if it's not integrated into the client. Added the new SpamSieve rule per Help 3.1 Eliminated all previous Rules except Not in my address book, which I unchecked Dragged the SpamSieve rule to the top of the list. I could have installed a content-based spam filter on the server, but the problem is that spam is personal. I have clients using this server who use outlook, so I had to disable the FQDN requirement. As far as I have been able to determine, it is not possible to configure Microsoft Outlook on Windows to send an FQDN. Unfortunately, it works a little too well. This will prevent many botnet machines from connecting because they tend to not be configured to send a FQDN. One of the ways an SMTP server can cut down on spam is to require clients to connect with a fully qualified domain name (FQDN). I've recently started running my own mail server, so I started tweaking the settings to try to cut down on the processed breakfast meat, and discovered that Microsoft Outlook has a serious bug (what a surprise). I get a ton of spam, and it was starting to overwhelm the filter built in to the OS X mail client.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |