If you are a pair.com customer and you use the e-mail provided with their web hosting accounts, you should make sure you are taking advantage of their new antispam/junkmail filtering. My experience is that it really works. If it isn’t working for you then either they haven’t convereted your server yet, or something is wrong.
If your server has been converted but your junk mail hasn’t fallen off dramatically, here are a few tips:
# First off, you might need to wait a couple of days after they upgrade your server. They use DNS changes to make sure your mail goes to one of their “mailwash” servers before it arrives at the server that hosts your mailbox. This DNS change can take a couple of days to propagate. Until it does, Greylisting, which cuts down a lot of spam, won’t work.
# If the number of spam mails you receive doesn’t taper off login and make sure Greylisting is enabled.
# Also make sure that you have junkmail filtering enabled for your mailbox and any mail recipies that end up in your mailbox.
# Check the headers of some of the spaml to see if your mail is being delivered to a mailwash server before it gets to the server with your mailbox. If it isn’t you’ll probably see a line like this in the headers:
"X-Greylisting: 18.104.22.168/24 is whitelisted." which probably means that the MX records for your domain are still pointing to the server hosting your mailbox. This can happen if you have custom DNS enabled on pair, or if you are using someone else to host DNS for your domain, like pairnic, godaddy, or network solutions. The solution is to figure out your mailwash server. It should be obvious from looking over the headers, the name will be “mailwashXX.pair.com” where XX is a one or two digit number (thanks for clarifying, Luke). Once you’ve figured out your mailwash server you should update your DNS so that it is the highest priority mail exchanger.
Please post other tips in the comments.
In my experience, greylisting has cut spam off dead. The only spam I’ve received in the past few days looks like it was sent using my old MX record that hasn’t expired from cache. As a result, I haven’t even bothered exploring the other antispam features.