Solved

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

Posted on 2010-09-20
2
710 Views
Last Modified: 2012-05-10
Hello,

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 <<user@domain.com>>
9/16/2010 5:51 PM   SMTP Store Driver: Message Delivered Locally to Store to <<user@domain.com>>>
9/18/2010 6:00 PM    SMTP: Non-Delivered Report (NDR) Generated

<<user@domain.com>> 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,

Mark



0
Comment
Question by:mbudman
2 Comments
 
LVL 23

Expert Comment

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

Accepted Solution

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

http://support.microsoft.com/kb/938650

0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Resolve DNS query failed errors for Exchange
"Migrate" an SMTP relay receive connector to a new server using info from an old server.
In this video we show how to create a User Mailbox 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 Recipients >> Mailb…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

762 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

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now