No announcement yet.

mail delay - uncertain of how to read header

  • Filter
  • Time
  • Show
Clear All
new posts

  • mail delay - uncertain of how to read header

    user was having problems sending email to a certain domain, so I had them send email with Receive and Read receipts.

    it appears the person at the other company replied to the email monday at 1:30 pm, but we didnt receive the receipt until 11:30 am tuesday morning.
    so I look at the header of the email that we finally received, but I am having trouble wrapping my head around the times on this header.

    I thought you were supposed to read these from the bottom up, but the bottom time is 15:35 UTC on the 29th, then goes to 13:55 on the 28th, to 14:01 on the 29th, then 11:35 on the 29th (when we received it).

    how can I decipher this? just trying to verify if the issue was on our end on theirs (I really hope theirs)

    here is the header:
    Microsoft Mail Internet Headers Version 2.0
    Received: from ([xxx.xx.xx.xx]) by Mycompaniesemailserver with Microsoft SMTPSVC(6.0.3790.1830);
    Wed, 29 Jul 2009 11:35:49 -0400
    Received: from int-smtp-1 by - Websense Email Security (6.1.1); Tue
    , 28 Jul 2009 14:00:56 -0400
    MIME-Version: 1.0
    Content-Type: multipart/report;
    Subject: Read: Test
    Date: Tue, 28 Jul 2009 13:55:45 -0400
    Message-ID: <[email protected]>
    From: "joe cool" <>
    To: "Mycompany, myuser" <[email protected]>
    X-WatchGuard-IPS: message checked
    X-WatchGuard-AntiVirus: part scanned. clean action=allow
    X-OriginalArrivalTime: 29 Jul 2009 15:35:49.0390 (UTC) FILETIME=[3FA1FAE0:01CA1062]

    Content-Type: text/plain;
    Content-Transfer-Encoding: quoted-printable
    X-WatchGuard-AntiVirus: part scanned. clean action=allow

    Content-Type: message/disposition-notification
    Content-Transfer-Encoding: 7bit
    X-WatchGuard-AntiVirus: part scanned. clean action=allow

    ing to make heads or tails of the headers, can

  • #2
    Re: mail delay - uncertain of how to read header

    You do read them up, but the only lines you are interested in are those about the actual transfer.
    The delay appears to have occurred in the transfer from their smart host to your server. There could be any number of reasons for that, you would have to look in your MSTP logs (if enabled) to see if previous connections were attempted and then failed for some reason.

    Simon Butler
    Exchange MVP

    More Exchange Content:
    Exchange Resources List:
    In the UK? Hire me:

    Sembee is a registered trademark, used here with permission.