Trouble receiving mail? Installing a new mail server? Need to make sure all your email servers are accessible?
Experienced network managers have long plodded through DNS queries, making sure that MX records matched A records which matched IP addresses. Then they checked SMTP ports to make sure the servers were open for business…
This can be a fairly time-consuming and error-prone process, especially if you or your email vendor, sport 11 mail servers, like IBM… Or two MX records that point to 15 hosts, like 3com.com… Or five MX records pointing to 18 IP addresses, some of which are only for outbound email, like sun.com.
Email service can even be a challenge for single-server shops. All too often, less experienced administrators either call their consultant, switch suppliers, or tell their users, “That’s the way it is. Get used to it.”
That’s why the builder of email firewall trimMail Inbox (our sponsor) produced Mail Server Profiler, its free web-based tool.
Simply type in the domain name you want to check. Mail Server Profiler tracks down all its mail servers and checks their SMTP ports to tell you which servers are listening for mail, and which servers are not.
Then Mail Server Profiler produces a profile of your mail server setup, along with insights into possible sources of any mail delivery problems.
“We have used Mail Server Profiler internally to help customers solve mail problems for a long time,” said trimMail Tech Support Manager Aaron Gillette, “But now, we hope we’ve polished it up enough for end-users. Mail Server Profiler should help anybody sort out mail delivery problems, no matter what their skill level is, or how many mail servers they have.”
Mail Server Profiler Beta is offered as a free service at Email Battles. All users are welcome to work with it. All comments will be considered, as the developers work to extend Mail Server Profiler’s functions and usability.
Email Battles Backgrounder:

8 comments
Comments feed for this article
April 6th, 2006 at 8:42 am
sand al wood
Hello,
I would like to see the distance between each IP address.
Thank you
April 6th, 2006 at 9:37 am
Millhouse
Not sure what MX Profile means. Numbers seem all over the chart. Any more info available?
April 6th, 2006 at 10:23 am
Editor
When setting up your MX records for mail servers in DNS, you can set a different preference level for each host.
Example: The MX priority for mailserverA = 10. The MX priority for mailserverB = 20. Senders will (ideally) try to deliver to mailserverA first. If that doesn’t work, they will try mailserverB. However, many senders ignore your MX priorities entirely.
If both MX priorities are equal, senders will more-or-less randomly pick one.
April 6th, 2006 at 11:54 am
T Payne
just 1 MX+ 1 IP for the whitehouse: mailhub-wh2.whitehouse.gov -> 63.161.169.140
2 MX + 2 IPs for Republican National Committee (rnc.org):
mailscan1.smartechcorp.net -> 64.203.97.101
mailscan2.smartechcorp.net -> 64.203.98.245
2 MX + 6 IPs for the Democratic National Committee (dnc.org):
inbound.mailwise.com -> 216.75.199.57, 216.75.199.60, 216.75.199.71
smtpbackup.mailwise.com -> 216.75.199.57, 216.75.199.60, 216.75.199.71
These politicians can’t agree on anything!
April 6th, 2006 at 2:46 pm
Tomasz Nidecki
I would suggest, that you tool checks for the existence of two absolutely required e-mail addresses at the mail server that handles the domain: postmaster and abuse (see rfc-ignorant.org). I found many mail servers administrators to be unaware of this requirement.
April 7th, 2006 at 11:18 am
BJ Gillette
@Tomasz. Excellent insight! It’s on the list.
April 10th, 2006 at 11:00 am
erick
As long as the tool is already connecting to the SMTP port, how about capturing HELO/EHLO output? That could be very helpful for admins, for instance for verifying whether or not a host offers STARTTLS, etc.
April 10th, 2006 at 12:32 pm
BJ Gillette
Hi Erick.
(Shhh. You read our minds;)
Thanks for your excellent insight.