Exchange 2003 server - problem sending calendar updates to external email addresses

Posted on 2010-09-20
Last Modified: 2012-05-10

We are currently running Exchange 2003 server. We have a front end server and back server (both Exchange 2003 server, same patches and service packs installed). The Exchange servers are applications servers and not Domain Controllers.

All outgoing email (smtp) is to be passed to front end server and then to the specific recipients.

This works fine except for one instance:

When making a change to a calendar appointment, such as time or date, The user gets a NDR 48 hours later.

I did message tracking, and their are two entries for the same email calendar update that sent out (even though only one message was sent).

The first one, which is successful, contacts the backend exchange server, which transfers it to the front end server,  which then makes the delivery. What is interesting here is the sender is list as his email address.

The second message, only lists the backend server (no reference to front end server) and then generates an NDR 48 hours later. Here, the sender is listed as his full name as it appears in active directory.

Tracing the second message shows the followong:

9/16/2010 5:51 PM   SMTP store Driver: Message submitted from Store
9/16/2010 5:51 PM   SMTP: Message Submitted to Advanced Queuing
9/16/2010 5:51 PM   SMTP: Started Message Submission to Advanced Queue
9/16/2010 5:51 PM   SMTP: Message Submitted to Categorizer
9/16/2010 5:51 PM   SMTP: Message Categorized and Queued for Routing
9/16/2010 5:51 PM   SMTP: Message Categorized and Queued for Routing
9/16/2010 5:51 PM   SMTP: Message queued for Local delivery
9/16/2010 5:51 PM   SMTP: Message Routed and Queued for Remote Delivery
9/16/2010 5:51 PM   SMTP: message delivered locally to <<>>
9/16/2010 5:51 PM   SMTP Store Driver: Message Delivered Locally to Store to <<>>>
9/18/2010 6:00 PM    SMTP: Non-Delivered Report (NDR) Generated

<<>> is to be replaced by actual user.

This only happens with Calendar meeting updates.

It seems like something is not configured correctly. does anyone have any ideas?

Thanks in advanced,


Question by:mbudman
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 23

Expert Comment

by:Stacy Spear
ID: 33771499
Looks like its trying to send that remote message to a local user.

Accepted Solution

mbudman earned 0 total points
ID: 33914234
I finally found the solution. This is in regards to microsoft kb 938650:


Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data‚Ķ
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question