This document assumes you are troubleshooting a problem with an existing mail server and a working mail client. You might use this info to troubleshoot a problem sending or recieving messages to or from a particular sender or recipient, for example.
Whether you are troubleshooting the problem yourself or asking a support person to troubleshoot the problem for you, the same information is needed.
First, you need the original error message (NDR or non-delivery report) that came back from the sender's mail server. It's important that you have the original error message because it will have all of the message headers that are absolutely necessary to troubleshoot any problem.
Second, if you are having a technician help troubleshoot, you must forward the original error message to the technician as an attachment in order to preserve the headers. Please read that statement carefully because it is very precisely worded.
Third, for in-depth troubleshooting, you will need access to the mail server log files as well. Furthermore, you will need to know the time zones of the e-mail messaging participants in order to correlate the log entries and error messages.
Zimbra Web Client → (select message) → Forward
Then:
Options → Include Original As Attachment
Gmail → (open the message) → More (ellipse) → Download Message
Then:
Compose (new message) → Attach File (previously downloaded .eml
file)
There is a keyboard shortcut you can use. Just select the message you want to forward and press Ctrl+Alt+F.
Otherwise, to forward a message as an attachment, select the message then in the Respond group, click More and then click Forward as Attachment.
In the modern, spam-infested world, mail system administrators go to great lengths to filter junk mail from their user's Inboxes. One of the tools mail system administrators use are 'blacklists' or 'blocklists'.
These lists, and there are many of them, are checked in a programmatic way by mail servers each time they receive a message. If the sending mail server is on blocklist, the receiving server may refuse the message.
Blocklists can be based on many different criteria, such as DNS or IP address ranges or even the country of origin.
As you can imagine there is tremendous room for errors and problems!
You first need to know the IP address of your mail server. You can get that from the message headers or by querying the domain name system (DNS).
To query DNS, use dig
or nslookup
. On Windows PCs, just use nslookup
.
First, query the domain for mail exchanger (MX) records:
dig yourdomain.tld mx
which yields something like this line from the Answer Section:
yourdomain.tld. 3600 IN MX 10 mailserver.yourdomain.tld.
which indicates the mail server is named “mailserver.yourdomain.tld”.
Now you need to determine the IP address of this server. Again we use 'dig':
dig mailserver.yourdomain.tld
which results in a line like this from the Answer Section:
mailserver.yourdomain.tld. 3405 IN A xxx.xxx.xxx.xxx
You can then use that IP address to check for blacklistings. Here are some convenient web sites that allow you to check various blacklists:
http://whatismyipaddress.com/blacklist-check
http://www.mxtoolbox.com/blacklists.aspx
Sometimes we see problems that “just shouldn't be”…problems where a message is refused without any obvious cause. These situations almost always involve “big” mail services such as Cox, AOL, AT&T, Earthlink, etc…services that are big enough to be “bullies”.
No one wants to hear this, but to be perfectly honest, the solution may simply be to not use the “big” e-mail service provider in favor of one that actually 'cares'.
Yes, I realize you will probably have a hard time convincing your messaging partner that they should dump that 'big' service provider, but the recommendation stands none the less. You might just tell the recipient that the problem is on their end and ask them for an alternate e-mail address.
See also Multiple Copies of E-Mails