Exchange Mail Deilvered but NDR Sent to Sender

I have a few users (in separate storage groups) that have been receiving email with no issue.  However the sender has been reporting NDRs for the delivered messages.  I am running Exchange 2003 with a single front-end box and an active/passive clustered back-end array.  The issue seems to have resolved itself with a reboot of the front-end exchange server but without any idea what may be causing this I don't want to close the book on this incident.

There are no errors in the System, Application logs and the message tracking center log shows a 'normal' path for message delivery with no mention of NDR.


An example NDR:
Your message

     To: [mime_recipient]
     Subject: MFC workshop agenda
     Sent:           Wed Apr 07 02:47:14 2010


did not reach the following recipient(s):
 lmt@XXXXXXXXX on Wed Apr 07 02:47:14 2010

     The e-mail account does not exist at the organization this message
was sent to.  Check the e-mail address, or contact the recipient
directly to find out the correct address.
     <Front-End Exchange Server #5.1.1>
Reporting-MTA: dns; Front-End Exchange Server

Final-Recipient: RFC822;  lmt@XXXXXXXXX
Action: failed
Status: 5.1.1
X-Supplementary-Info: Front-End Exchange Server
X-Display-Name: lmt@XXXXXXXXX


The user does exist, the destination name is correct and the user receives the email.  Why is there an NDR sent?
jbongardAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

thabashCommented:

Possible Cause:
1- The e-mail account does not exist at the organization the message was sent to. This issue may occur if there was a problem when users were moved between sites. For example, if a former Administrative_Group_1 user moves to Administrative_Group_2 and then replies to an old e-mail message, or if the user does not re-create his or her Outlook profile, an old Administrative Group style LegDN address will be used, and an NDR is generated.

2- The message was sent to obsolete personal address book entries.

3- The categorizer rejected delivery because you configured your SMTP contact with see comment SMTP RFC821 characters.

Troubleshooting:
 Verify the recipient address and resend the message. Verify that the recipient address is formatted correctly and that the categorizer was able to correctly resolve the recipient.


The error can also occur if the recipient does not have an account on the server.  In some cases, you may find that the particular recipient once had a mailbox on the destination server, but that the mailbox has been moved to another server within the domain.  When that happens, the sender’s Outlook recipient cache may still contain the recipient’s previous information. When that happens, it is necessary to remove the recipient's address from the senders Outlook recipient cache before the sender retransmits the message.
0
jbongardAuthor Commented:
thabash:

1) The recipient's account does exist and the send to address is one of the email addresses listed in AD.
2) The sender is external to our organization and the send-to address is correct.  The email is a new message (not a reply from previous string) and the user's mailbox has not moved from the current store in a significant amount of time.
3) The categorizer did NOT reject the message.  The message was delivered to the user's mailbox as per Message Tracking Center and the user received the sent mail item.
0
thabashCommented:
perform an nslookup *from* your exchange server for the MX records of
receipit  domainname(example carolina.rr.com) be sure u get back the following results?

carolina.rr.com MX preference = 10, mail exchanger = hrndva-01.mgw.rr.com
carolina.rr.com MX preference = 10, mail exchanger = hrndva-02.mgw.rr.com
carolina.rr.com MX preference = 10, mail exchanger = orngca-01.mgw.rr.com
carolina.rr.com MX preference = 10, mail exchanger = orngca-02.mgw.rr.com
carolina.rr.com MX preference = 10, mail exchanger = clmboh-01.mgw.rr.com
carolina.rr.com MX preference = 10, mail exchanger = clmboh-02.mgw.rr.com\

0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

michaelgoldsmithCommented:
I wonder if you are getting the NDR back from a forwarding address, like a blackberry device.
0
jbongardAuthor Commented:
I was able to solve the issue.  My spam filter GFI MailEssentials was issuing NDR reports for the emails based on SPF settings but still allowing the email through to the recipient.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
thabashCommented:
Its from the GFI mail
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Protocols

From novice to tech pro — start learning today.