Random internal and external outlook emails coming back undeliverable when replied to.
Some of our email users are getting a undeliverable message:
Your message did not reach some or all of the intended recipients.
Subject: RE: dress for the wedding
The following recipient(s) cannot be reached:
LastName, FirstName on 2/28/2011 2:57 PM
The e-mail address could not be found. Perhaps the recipient moved to a different e-mail organization, or there was a mistake in the address. Check the address and try again.
<exchange.domain.org #5.1.0>
This happens when a user REPLIES to an email. If they create a new email to the recipient it will arrive correctly. Every once in a while the replies will work as well but it is rare. I have not found any pattern between the users experiencing this problem. Some of the users are using Outlook 2003, others using Outlook 2007. This is going through our Exchange server 2003 and the problem started about a week ago and seems to be slowly coming up on more users. Another note is that once they get the failed delivery notice that email address is pulled from the auto fill in outlook.
Your message did not reach some or all of the intended recipients.
Subject: RE: dress for the wedding
The following recipient(s) cannot be reached:
LastName, FirstName on 2/28/2011 2:57 PM
The e-mail address could not be found. Perhaps the recipient moved to a different e-mail organization, or there was a mistake in the address. Check the address and try again.
<exchange.domain.org #5.1.0>
This happens when a user REPLIES to an email. If they create a new email to the recipient it will arrive correctly. Every once in a while the replies will work as well but it is rare. I have not found any pattern between the users experiencing this problem. Some of the users are using Outlook 2003, others using Outlook 2007. This is going through our Exchange server 2003 and the problem started about a week ago and seems to be slowly coming up on more users. Another note is that once they get the failed delivery notice that email address is pulled from the auto fill in outlook.
this is an issue with forwarders. when they hit the reply button the translation of email address is not correct. this is an issue on the other email system.
Is this a reply to a new email or a reply to an old email?
Does this happen for all replies to all users both internal and external?
Does this happen for all replies to all users both internal and external?
ASKER
It happens when they reply to a new email. They can pull emails from before this issue started, with the same failing recipients, and it will reply successfully. It is not just external emails either. Replying to some internal emails fail as well, so they copy and paste the reply into a new email and it will get to the user. 99% of the replies fail for these users. They will have a moment where maybe three of them work then it goes back to failing on all internal and external replies.
Can you please post the header of an email that fails when being replied to.
It sounds like the sending server are using .local as their email address not .com or .net etc.
I can hide domain specifics for security purposes, but it would be good to see the entire header unadulterated.
Alan
It sounds like the sending server are using .local as their email address not .com or .net etc.
I can hide domain specifics for security purposes, but it would be good to see the entire header unadulterated.
Alan
ASKER
Microsoft Mail Internet Headers Version 2.0
From: postmaster@domain1.org
To: tbarnes@domain1.org
Date: Mon, 28 Feb 2011 14:51:29 -0600
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-statu
boundary="9B095B5ADSN=_01C
X-DSNContext: 335a7efd - 2430 - 00000002 - 80070003
Message-ID: <bpH71yEXU00000038@exchang
X-Content-Failure: 0x80070003
Subject: Delivery Status Notification (Failure)
--9B095B5ADSN=_01CBD54B47E
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01CBD54B47E
Content-Type: message/delivery-status
--9B095B5ADSN=_01CBD54B47E
Content-Type: text/rfc822-headers
--9B095B5ADSN=_01CBD54B47E
From: postmaster@domain1.org
To: tbarnes@domain1.org
Date: Mon, 28 Feb 2011 14:51:29 -0600
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-statu
boundary="9B095B5ADSN=_01C
X-DSNContext: 335a7efd - 2430 - 00000002 - 80070003
Message-ID: <bpH71yEXU00000038@exchang
X-Content-Failure: 0x80070003
Subject: Delivery Status Notification (Failure)
--9B095B5ADSN=_01CBD54B47E
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01CBD54B47E
Content-Type: message/delivery-status
--9B095B5ADSN=_01CBD54B47E
Content-Type: text/rfc822-headers
--9B095B5ADSN=_01CBD54B47E
That's the NDR message - could you please post the email header from the remote domain that you / your user is replying to and the reply fails.
The original message from the remote domain should show their return address. If it ends .local - there is your problem - well, their problem.
The original message from the remote domain should show their return address. If it ends .local - there is your problem - well, their problem.
ASKER
Microsoft Mail Internet Headers Version 2.0
Received: from sv4-mta-53a.emailfiltering
Fri, 25 Feb 2011 15:09:54 -0600
X-CTCH-RefID: str=0001.0A020208.4D681AA0
Received: from 216.65.194.164 ([216.65.194.164])
by sv4-mta-53a.emailfiltering
for tbarnes@domain1.org;221748
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:messag
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----_=_NextPart_
type="multipart/alternativ
Subject: RE: dress for the wedding
Date: Fri, 25 Feb 2011 15:09:46 -0600
Message-ID: <6B3F3FD9A4786E4B854807074
In-Reply-To: <B092047AA94C7C4687E99156C
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: dress for the wedding
Thread-Index: AcvVH+GBWmDxVmd5TwCLBg27G1
References: <6B3F3FD9A4786E4B854807074
From: "Teresia Slaughter" <TSlaughter@domain2.ORG>
To: "Mandy George" <MGeorge@mydomain.com>,
"Barnes, Tionna" <tbarnes@otherdomain1.org>
Return-Path: TSlaughter@domain2.ORG
X-OriginalArrivalTime: 25 Feb 2011 21:09:54.0176 (UTC) FILETIME=[59319800:01CBD53
X-TM-AS-Product-Ver: SMEX-7.0.0.1584-6.5.1024-1
X-TM-AS-Result: No--19.322600-4.000000-31
------_=_NextPart_001_01CB
Content-Type: multipart/alternative;
boundary="----_=_NextPart_
------_=_NextPart_002_01CB
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding:
------_=_NextPart_002_01CB
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding:
------_=_NextPart_002_01CB
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image001.jpg"
Content-Transfer-Encoding:
Content-ID: <image001.jpg@01CBD4FE.07D
Content-Description: image001.jpg
Content-Location: image001.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image002.jpg"
Content-Transfer-Encoding:
Content-ID: <image002.jpg@01CBD4FE.07D
Content-Description: image002.jpg
Content-Location: image002.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image003.jpg"
Content-Transfer-Encoding:
Content-ID: <image003.jpg@01CBD4FE.07D
Content-Description: image003.jpg
Content-Location: image003.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image004.jpg"
Content-Transfer-Encoding:
Content-ID: <image004.jpg@01CBD4FE.07D
Content-Description: image004.jpg
Content-Location: image004.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image005.jpg"
Content-Transfer-Encoding:
Content-ID: <image005.jpg@01CBD4FE.07D
Content-Description: image005.jpg
Content-Location: image005.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image006.jpg"
Content-Transfer-Encoding:
Content-ID: <image006.jpg@01CBD4FE.07D
Content-Description: image006.jpg
Content-Location: image006.jpg
------_=_NextPart_001_01CB
Received: from sv4-mta-53a.emailfiltering
Fri, 25 Feb 2011 15:09:54 -0600
X-CTCH-RefID: str=0001.0A020208.4D681AA0
Received: from 216.65.194.164 ([216.65.194.164])
by sv4-mta-53a.emailfiltering
for tbarnes@domain1.org;221748
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:messag
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----_=_NextPart_
type="multipart/alternativ
Subject: RE: dress for the wedding
Date: Fri, 25 Feb 2011 15:09:46 -0600
Message-ID: <6B3F3FD9A4786E4B854807074
In-Reply-To: <B092047AA94C7C4687E99156C
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
Thread-Topic: dress for the wedding
Thread-Index: AcvVH+GBWmDxVmd5TwCLBg27G1
References: <6B3F3FD9A4786E4B854807074
From: "Teresia Slaughter" <TSlaughter@domain2.ORG>
To: "Mandy George" <MGeorge@mydomain.com>,
"Barnes, Tionna" <tbarnes@otherdomain1.org>
Return-Path: TSlaughter@domain2.ORG
X-OriginalArrivalTime: 25 Feb 2011 21:09:54.0176 (UTC) FILETIME=[59319800:01CBD53
X-TM-AS-Product-Ver: SMEX-7.0.0.1584-6.5.1024-1
X-TM-AS-Result: No--19.322600-4.000000-31
------_=_NextPart_001_01CB
Content-Type: multipart/alternative;
boundary="----_=_NextPart_
------_=_NextPart_002_01CB
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding:
------_=_NextPart_002_01CB
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding:
------_=_NextPart_002_01CB
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image001.jpg"
Content-Transfer-Encoding:
Content-ID: <image001.jpg@01CBD4FE.07D
Content-Description: image001.jpg
Content-Location: image001.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image002.jpg"
Content-Transfer-Encoding:
Content-ID: <image002.jpg@01CBD4FE.07D
Content-Description: image002.jpg
Content-Location: image002.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image003.jpg"
Content-Transfer-Encoding:
Content-ID: <image003.jpg@01CBD4FE.07D
Content-Description: image003.jpg
Content-Location: image003.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image004.jpg"
Content-Transfer-Encoding:
Content-ID: <image004.jpg@01CBD4FE.07D
Content-Description: image004.jpg
Content-Location: image004.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image005.jpg"
Content-Transfer-Encoding:
Content-ID: <image005.jpg@01CBD4FE.07D
Content-Description: image005.jpg
Content-Location: image005.jpg
------_=_NextPart_001_01CB
Content-Type: image/jpeg;
name="image006.jpg"
Content-Transfer-Encoding:
Content-ID: <image006.jpg@01CBD4FE.07D
Content-Description: image006.jpg
Content-Location: image006.jpg
------_=_NextPart_001_01CB
ASKER
Another thing I have discovered testing with one user is once I took them out of cached exchanged mode all their new email replies started working. The emails that already failed still failed but the new replies after that worked.
The sending address / return address seems to be okay (TSlaughter@remotedomain.O
Interesting that non-cached Exchange mode seems to resolve the issue.
Can you create a new Outlook profile for a problem user and see if the problem happens again when replying to an existing email.
Interesting that non-cached Exchange mode seems to resolve the issue.
Can you create a new Outlook profile for a problem user and see if the problem happens again when replying to an existing email.
ASKER
Yes that is the correct address.
I will be able to make the user here a new mailbox and have them test it out tomorrow. I will post the results.
I will be able to make the user here a new mailbox and have them test it out tomorrow. I will post the results.
ASKER
After further testing we discovered that when journaling is enabled on our mailbox store this problem happens. Today it was causing this on almost every user in our domain. Disabled journaling and the problem stops. Now to figure out why that is.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.