• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 259
  • Last Modified:

slow incoming emails

if the emails came 1 or 2 days later, do you check with your ISP or the source ISP- from the header, is it possible to deduct what is the problem?
2 Solutions
Alan HardistyCo-OwnerCommented:
Analysing the headers is the only way to check why the emails are delayed.  They will provide the dates / times for all servers between the sender and you and pinpoint where the delay occurred.

If you would like to past a header into http://www.mxtoolbox.com/EmailHeaders.aspx - that should analyze them happily for you.

You then just need to interpret the output to see where the delay is.

Post a header if you need help.

Be aware that the MXtool to trace through the Received headers has problems:

- If a spammer/phisher inserts bogus Received headers, this tool will trace through them giving you a false source for the message hence potentially invalid timestamping.  With internal routing within e-mail services, it isn't always easy to spot where the forged Received header(s) got inserted.

- It does not unbias the day for the timezone.  A Received header with a datestamp of "Tue, 15 Feb 2011 17:54:44 -0800" as the source followed by the next Received header with a datestamp of "Wed, 16 Feb 2011 01:54:44 +0000 (UTC)" get unbiased to UTC so both show for 01:54:44 UTC but they forget to change the day.  So it will look like the e-mail got delivered at the same time but a day later.  The e-mail that got transferred in less than a second shows it got sent on Tues and received on Wed which is not the case.

It's still a useful tool as long as you realize the day of the week may be wrong in what it reports.  You should be able to trace through the Received headers while unbiasing the timezones in each to figure out how long it takes between hops to deliver the message.  Headers get prepended to a message with each hop through a mail server, so you read the Received headers from bottom to top.  The topmost Received header is the one prepended by your receiving mail server.  The bottommost Received header is the one prepended by the sender's mail server.

E-mails should transfer within a few seconds unless an underpowered e-mail service was involved that, say, batched up their e-mails to send out every hour, or so.  A delay of a day or two would probably mean one of the mail servers was down, unresponsive, or unreachable (routing problems with slow/unresponsive hosts between the source and destination mail servers).  When tracing the Received header from bottom to top in the headers, the first large jump in delivery time is probably the major cause of delay.  Just be careful to note the timezones in the datestamps since some mail servers bias against UTC while others use their local timezone.  Also remember that the timezone reported by the mail server is for itself and not that of the sender when they chose to compose the e-mail (which is shown in the Date header).  For example, someone in the midwest USA with timezone -0600 using Hotmail's servers in the -0800 timezone will have Hotmail's timezone in the Received header and the sender's timezone in the Date header.  The Received headers are added by the mail servers.  The Date header is part of the *data* defined by the sender's e-mail client (it is part of the message composed by the e-mail client and sent during the DATA command).

You could post the headers of the problematic e-mail here for us to analyze.  Munge or star out any sensitive info, like usernames in e-mail address but leave the domains intact.  You want to hide the e-mail account, not the e-mail service provider which isn't a secret.  Make sure to check all headers for usernames as several may contain them, like From, To, Cc, Received, Reply-To, Sender, etc.  You could just show the Received headers and only their time and date values to let us trace through them but I suspect you could do that yourself.
anushahannaAuthor Commented:
thanks for the nice resource to check it out.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now