Strategically Preventing Mail Delivery Failure

It's been estimated that the percentage of email on the internet breaks down to 90% and only 10% legitimate email. As our global dependency on email increases each year, counter measures are being taken by companies to block out as much junk as possible.

Major ISPs are starting to perform reverse DNS checks, and others are even starting to use SPF (a form of email authentication technology) to verify that mail is originating from the source that is authorized for that domain.

Avoiding Blacklists

<blacklist overview blurb>

MXToolbox has a really nice blacklist check, which will go out and scan all major blackblists and report in an intuitive layout if your server is/is not on the list.

http://www.mxtoolbox.com/blacklists.aspx

Enter the IP address of your mail server to confirm that you haven't magically landed on a spam blacklist, or ended up there due to a network machine that got infected by a virus.

Reverse DNS

This is becoming more of a mandatory item if you want to host your own mail server. Most ISP will require you to have a reverse DNS record before they will accept email from you, otherwise your messages will get dropped.

A reverse DNS record is just as it states: it does the opposite of regular DNS, which takes a name and matches it to an IP address, by checking the DNS record of the IP address. This is not something you will have control to change easily, and MUST be done with your ISP, since they are in control of information on your IP address.

There are 2 pieces of the puzzle that must exist:

Once your reverse DNS record has been request and is in place, test it!

From your mail server, go to http://www.init7.com/ip-address-test.php. This will check your IP address, and give you your actual host name.

Creating an SPF record

<spf overview blurb>

Here is a sample SPF string I use for zones on our Windows DNS server. Since most DNS servers do not support the "SPF" record type as of yet, enter this string as a "TXT" record

v=spf1 a:<reverse DNS> mx:<domain name> ip4:<main server IP>/<subnet mask in slash notation> ~all

Here's a break down on what information you need to fill in:

Here is a great page to test your new SPF record:

http://www.kitterman.com/spf/validate.html