Undeliverable Calendar Appointments

I have a Microsoft Exchange 2003 SP2 server. The clients are running Outlook 2007. One user is experiencing occasional undeliverable messages only when updating or canceling calendar appointments. Below is an example of an appointment that was canceled and two users with gmail.com emails were invited to. The first one goes through but the second Quits and ends up undeliverable. Any thoughts?

2010-03-18 15:30:28 209.85.222.69 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 220+mx.google.com+ESMTP+1si746836pzk.74 0 0 39 0 62 SMTP - - - -
2010-03-18 15:30:28 209.85.222.69 OutboundConnectionCommand SMTPSVC1 MAPEX01 - 25 EHLO - email.mydomain.org 0 0 4 0 62 SMTP - - - -
2010-03-18 15:30:28 209.85.222.69 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 250-mx.google.com+at+your+service,+[MYIP] 0 0 49 0 937 SMTP - - - -
2010-03-18 15:30:28 209.85.222.69 OutboundConnectionCommand SMTPSVC1 MAPEX01 - 25 MAIL - FROM:<david.****@mydomain.org>+SIZE=4151 0 0 4 0 937 SMTP - - - -
2010-03-18 15:30:28 209.85.222.69 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 250+2.1.0+OK+1si746836pzk.74 0 0 28 0 1000 SMTP - - - -
2010-03-18 15:30:28 209.85.222.69 OutboundConnectionCommand SMTPSVC1 MAPEX01 - 25 RCPT - TO:<surya****@gmail.com> 0 0 4 0 1000 SMTP - - - -
2010-03-18 15:30:29 209.85.222.69 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 250+2.1.5+OK+1si746836pzk.74 0 0 28 0 1078 SMTP - - - -
2010-03-18 15:30:29 209.85.222.69 OutboundConnectionCommand SMTPSVC1 MAPEX01 - 25 DATA - - 0 0 4 0 1078 SMTP - - - -
2010-03-18 15:30:29 209.85.222.69 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 354++Go+ahead+1si746836pzk.74 0 0 29 0 1140 SMTP - - - -
2010-03-18 15:30:33 209.85.222.69 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 250+2.0.0+OK+1268926341+1si746836pzk.74 0 0 39 0 5484 SMTP - - - -
2010-03-18 15:30:33 209.85.222.69 OutboundConnectionCommand SMTPSVC1 MAPEX01 - 25 QUIT - - 0 0 4 0 5500 SMTP - - - -
2010-03-18 15:30:33 209.85.222.69 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 221+2.0.0+closing+connection+1si746836pzk.74 0 0 44 0 5547 SMTP - - - -
2010-03-18 15:30:33 209.85.222.43 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 220+mx.google.com+ESMTP+9si166167pzk.61 0 0 39 0 63 SMTP - - - -
2010-03-18 15:30:33 209.85.222.43 OutboundConnectionCommand SMTPSVC1 MAPEX01 - 25 EHLO - email.mydomain.org 0 0 4 0 63 SMTP - - - -
2010-03-18 15:30:33 209.85.222.43 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 250-mx.google.com+at+your+service,+[MyIP] 0 0 49 0 141 SMTP - - - -
2010-03-18 15:30:33 209.85.222.43 OutboundConnectionCommand SMTPSVC1 MAPEX01 - 25 QUIT - - 0 0 4 0 141 SMTP - - - -
2010-03-18 15:30:33 209.85.222.43 OutboundConnectionResponse SMTPSVC1 MAPEX01 - 25 - - 221+2.0.0+closing+connection+9si166167pzk.61 0 0 44 0 203 SMTP - - - -

ShareTechAsked:
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.

Vishal BreedProgram ManagerCommented:
Possible for you to share copy of NDR (non deliverable report/receipt)?
0
ShareTechAuthor Commented:
NDR to match the SMTP logs above:

Your message

  To:      christophermhaley+AEA-gmail.com
  Subject: Canceled: Brunch with Surya/David

did not reach the following recipient(s):

christophermhaley+AEA-gmail.com on Fri, 19 Mar 2010 10:30:48 -0500
    Could not deliver the message in the time limit specified.  Please
retry or contact your administrator.
    +ADw-email.mnaidsproject.org +ACM-4.4.7+AD4-
0
Vishal BreedProgram ManagerCommented:
Reference: http://support.microsoft.com/kb/284204

Possible Cause: The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred. This NDR may also indicate that a message header limit has been reached on a remote server or that some other protocol timeout occurred during communication with the remote server.

Troubleshooting: This code typically indicates an issue on the receiving server. Verify the validity of the recipient address, and verify that the receiving server is configured to receive messages correctly. You may have to reduce the number of recipients in the header of the message for the host that you are receiving this NDR from. If you resend the message, it is placed in the queue again. If the receiving server is on line, the message is delivered.

Suggestion: Run ExBPA (Exchange Best Practice Analyzer) Tool which will can your current configuration and might suggest you some changes. As far as the error is concerned, there is no problem from your end.
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
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.