Receiving Delivery Status Notification when sending updated calendar entries

Having an issue where sending out updates to calendar entries to external users results in delivery status notification delay/failure messages.

The initial calendar invite will go out fine, but if you go to edit it and send an update, that is when you receive the DSN message.

Exchange is 2003SP2 running on Win2k3
End users are using outlook 2007
gtelnetAsked:
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.

Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
This is a known issue between Exchange 2003 and Exchange 2007.

The fix:
http://support.microsoft.com/kb/938650
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
So you don't miss it in the article like I first did.    You need to install the hotfix and then mod the registry:

Hotfix request (very top of the article):
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=938650&kbln=en-us
0
friekedCommented:
Thanks.... I actually found that hotfix and applied it a couple weeks ago but this seems to happen for ALL external users, not just E2k7.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

gtelnetAuthor Commented:
Oops, previous comment was me on my other account...
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
You applied the hotfix and modified the registry and rebooted?

So far I have done this about six or so times...actually one last night and have to check the results today.   But they are all successfully in resolving.  
0
Rick FeeMessaging Engineer - Disaster Recovery EngineerCommented:
I would check the registry again to ensure you didn't put a extra space.    Or just delete the key you entered and set it back up and maybe reinstall the hotfix.

I will check to see if this was the fix for last night.    Odd that this does not work for you if the case.   Do you have anything between your Exchange server and the internet like a antispam solution?

One Exchange server on 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.