A user creates a meeting request, sends it to company employees as well as people outside the firm. The meeting request goes through ok. For some reason or another, the meeting needs to be changed so the user modifies the meeting request and sends the changed request out to the invitees. The change meeting request causes an NDR for people outside the firm. Thanks for any assistance, this is happening more frequently in our organization and I have not had any luck finding a solution.
Exchange 2003 sp2, Outlook 2007, XP, Server 2003
Software/Hardware used:
Exchange 2003 sp2, Outlook 2007, XP, Server 2003
ASKED:
September 17, 2009 8:27 PM
UPDATED:
October 5, 2009 5:03 PM
Here is the NDR info:
Subject: Undeliverable: Delivery Status Notification (Failure)
Your message did not reach some or all of the intended recipients.
Subject: Dinner-Garfield
The following recipient(s) cannot be reached:
123@123456789.com on 9/16/2009 8:18 AM
Could not deliver the message in the time limit specified. Please retry or contact your administrator.
<mail.123.com #4.4.7>
Do you use a third party email filtering vendor such as Message Labs? Are you filtering outgoing mail? Are the NDR’s from just organizations which use Exchange or is it not specific to Exchange organizations? Is it true for ALL external emails or just some?
We do have a third party email gateway which is AT&T our ISP, they scan email coming in only. We do not filter outgoing email. I do not know if the outside organizations use Exchange or not, I had thought of that too. The original calendar request goes out fine to these organizations, its just the changed calendar request that receives the NDR. It does not happen for all outgoing calendar changes at least not to ALL organizations. I believe it does happen to the same organizations consistantly.
thanks for the help.
I seem to recall this same issue happening to us and it turned out to be a version mismatch of Exchange. They did not have SP2 installed on their Exchange 2003 version if I remember correctly. This SHOULDN’T cause a problem, but I am very sure this turned out to BE the problem. So see if you can find out from the “problem” organizations if they are running Exchange and what version.
There is a hotfix for this issue.
http://support.microsoft.com/kb/938650/en-us
thanks for the help.
Good, you found the issue. I was sure it had something to do with the version, and I remember that patch now that you posted it. Sorry I did not recall it for you.