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. 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. 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 |