|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
21 Oct 2013, 12:53 PM | #1 |
Junior Member
Join Date: Oct 2013
Posts: 3
|
Delayed messages
Is anyone else having a problem with delayed messages? Today I've seen messages come in anywhere from four to eleven hours after they were sent. This is not happening consistently with all messages, but a large number of them.
In nearly ten years of using Fastmail, I can't recall this problem before. |
23 Oct 2013, 03:38 AM | #2 |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,926
|
No, I saw nothing odd on October 20. Look at the full headers of those messages using More > Show Raw Message. You need to invert the sign of the timezone offset and add the number to the local time to get the GMT time of each header so you can compare them. So:
20 Oct 2013 23:44:22 -0400 is 27:44:22, or 03:44:22 on Oct 21. 21 Oct 2013 15:57:03 -0400 is 19:57:03 on Oct 21. New header are added at the top, so you have to read the headers backwards. Near the end of the headers you normally will find Date, From, and To headers. That's the date/time the message was sent by the composing agent. Looking up at headers from later times, you will see the delay at each transfer. The first transfer to a Fastmail server will be the header where the message is received by mx*.messagingengine.com (where * is a small integer. So the receiving server could be mx1.messagingengine.com or mx2.messagingengine.com. If the messages came through a forwarding service, that is most likely the source of the delay. In some cases you may see greylisting delays due to a suspicious sending server (such as from spam) causing the messagingengine.com Fastmail receiving server to delay the message for an hour or so. The longer delays you describe are not normal, and probably indicate some problem with the sender or a forwarding service or a problem with your particular Fastmail account. I assume the messages were directly sent in some manner (or forwarded directly) to your Fastmail account, and that you are looking at them via webmail. If you got them via POP links or you are using an email client, there may be other reasons for what you are seeing. Bill |
8 Nov 2013, 10:28 PM | #3 |
Essential Contributor
Join Date: Feb 2007
Posts: 249
|
I've also been experiencing delays in receipt of email when using fastmail's webmail.
Here are all received headers from one delayed message. Although the headers indicate the message was slightly delayed in getting to fastmail on November 7, it didn't show up in the webmail inbox until the morning of November 8. So it seems as if the delays are happening at fastmail. How should I proceed? Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by sloti30d5p1 (Cyrus git2.5+0-git-fastmail-9457) with LMTPA; Thu, 07 Nov 2013 16:58:24 -0500 Received: from mx4 ([10.202.2.203]) by compute1.internal (LMTPProxy); Thu, 07 Nov 2013 16:58:24 -0500 Received: from mx.rcn.com (mx.rcn.com [69.168.97.77]) by mx4.messagingengine.com (Postfix) with ESMTP id 4EBEC3C0EF3 for <xxx@fastmail.xxx>; Thu, 7 Nov 2013 16:58:24 -0500 (EST) Received-SPF: neutral (mx01.rcn.cmh.synacor.com: 65.54.190.140 is neither permitted nor denied by domain of ymail.com) Received: from [65.54.190.140] ([65.54.190.140:30587] helo=bay0-omc3-s2.bay0.hotmail.com) by mx.rcn.com (envelope-from <xxx@ymail.com>) (ecelerity 2.2.3.49 r(42060/42061)) with ESMTP id 71/4D-16975-EFC0C725; Thu, 07 Nov 2013 16:58:23 -0500 Received: from BAY406-EAS184 ([65.54.190.189]) by bay0-omc3-s2.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 7 Nov 2013 13:58:23 -0800 Thanks. Ellen |
9 Nov 2013, 05:17 AM | #4 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,926
|
Quote:
Bill |
|
9 Nov 2013, 06:01 AM | #5 |
Essential Contributor
Join Date: Feb 2007
Posts: 249
|
Thanks Bill. This is starting to make sense to me. I wasn't correcting for time zone differences. Since I will in the future, please tell me if I understand this.
If I understand things correctly, the top received line indicates it was delivered to the inbox on 11/7 at 16:58:24, which if I am following your instructions about inverting the offset is five hours later (which would be 9:58 p.m. EST)? Then why does the first Date: line (not in the expanded headers, but the one that is displayed in "normal" header view) show 7 Nov 2013 4:48 PM? That's ten minutes earlier than the top received line (assuming my calculations are correct). Also, what is X-OriginalArrivalTime? That one has an even later timestamp: 07 Nov 2013 21:58:23.0196. Thanks again for your help. Ellen Ellen |
10 Nov 2013, 06:10 AM | #6 | |
Intergalactic Postmaster
Join Date: May 2004
Location: Irving, Texas
Posts: 8,926
|
More details from the headers
Quote:
Bill |
|
15 Nov 2013, 09:55 AM | #7 |
Essential Contributor
Join Date: Feb 2007
Posts: 249
|
Thank you so much for taking the time to write this clear explanation. I appreciate it.
Ellen Last edited by ellentk : 15 Nov 2013 at 09:56 AM. Reason: Left out a word |
Thread Tools | |
|
|