pklein22
asked on
HELP!!!! Emails arriving 24 hours after they were sent and in some cases, customers receiving ndr's.
Still pretty new to supporting email:
Two part question:
How do I find out why we are receiving some emails anywhere from 8 hours to 24 hours after they were sent? I have a copy of one of the email headers below:
Microsoft Mail Internet Headers Version 2.0
Received: from sears.com (hofsecimgw1.sears.com [198.179.148.4]) by dgntexch.nsamedia.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id XRPL9D93; Wed, 24 Nov 2004 20:51:27 -0600
Received: from ([166.76.89.65]) by hofsecimgw1.sears.com with ESMTP id KP-NTG56.37237762; Tue, 23 Nov 2004 08:46:09 -0600
content-class: urn:content-classes:messag
Subject: Re: Mart Stores - Flighting
MIME-Version: 1.0
Content-Type: application/ms-tnef;
name="winmail.dat"
Date: Tue, 23 Nov 2004 08:37:15 -0600
Content-Transfer-Encoding:
Message-ID: <OFCB9B8D29.C9BC201C-ON862
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <OFCB9B8D29.C9BC201C-ON862
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Thread-Topic: Mart Stores - Flighting
Thread-Index: AcTSmaizTZj+up2qRGutMfe63x
From: <rander3@sears.com>
To: <jeriser@sears.com>
Cc: <cathy.petritz@nsamedia.co
<jkrueg4@sears.com>,
<lynn.kubiak@nsamedia.com>
How do I determine why some, not all, emails are being retruned as undeliverable to the people who are trying to send to us? An expamle of the header from one of those is below:
Reporting-MTA: dns; usdmzsvpsmtpct1.kmart.com
Final-Recipient: rfc822;maryanne.volk@nsame
Diagnostic-Code: smtp; 454 5.7.3 Client was not authenticated.
Remote-MTA: dns; mail2.nsamedia.com
Action: failed
Status: 4.0.0
Final-Recipient: rfc822;amy.godfrey@nsamedi
Diagnostic-Code: smtp; 454 5.7.3 Client was not authenticated.
Remote-MTA: dns; mail2.nsamedia.com
Action: failed
Status: 4.0.0
Two part question:
How do I find out why we are receiving some emails anywhere from 8 hours to 24 hours after they were sent? I have a copy of one of the email headers below:
Microsoft Mail Internet Headers Version 2.0
Received: from sears.com (hofsecimgw1.sears.com [198.179.148.4]) by dgntexch.nsamedia.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id XRPL9D93; Wed, 24 Nov 2004 20:51:27 -0600
Received: from ([166.76.89.65]) by hofsecimgw1.sears.com with ESMTP id KP-NTG56.37237762; Tue, 23 Nov 2004 08:46:09 -0600
content-class: urn:content-classes:messag
Subject: Re: Mart Stores - Flighting
MIME-Version: 1.0
Content-Type: application/ms-tnef;
name="winmail.dat"
Date: Tue, 23 Nov 2004 08:37:15 -0600
Content-Transfer-Encoding:
Message-ID: <OFCB9B8D29.C9BC201C-ON862
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: <OFCB9B8D29.C9BC201C-ON862
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Thread-Topic: Mart Stores - Flighting
Thread-Index: AcTSmaizTZj+up2qRGutMfe63x
From: <rander3@sears.com>
To: <jeriser@sears.com>
Cc: <cathy.petritz@nsamedia.co
<jkrueg4@sears.com>,
<lynn.kubiak@nsamedia.com>
How do I determine why some, not all, emails are being retruned as undeliverable to the people who are trying to send to us? An expamle of the header from one of those is below:
Reporting-MTA: dns; usdmzsvpsmtpct1.kmart.com
Final-Recipient: rfc822;maryanne.volk@nsame
Diagnostic-Code: smtp; 454 5.7.3 Client was not authenticated.
Remote-MTA: dns; mail2.nsamedia.com
Action: failed
Status: 4.0.0
Final-Recipient: rfc822;amy.godfrey@nsamedi
Diagnostic-Code: smtp; 454 5.7.3 Client was not authenticated.
Remote-MTA: dns; mail2.nsamedia.com
Action: failed
Status: 4.0.0
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You are welcome and thank you for the points
As far as the second question goes, I would definitely not worry as the headers show that it was only passed to your server a short while before delivery. That is something that you would have no control over and it can happen for any number of reasons
Good luck with the support!
As far as the second question goes, I would definitely not worry as the headers show that it was only passed to your server a short while before delivery. That is something that you would have no control over and it can happen for any number of reasons
Good luck with the support!
ASKER