Exchange 2003 5.2.1 NDR
This is driving me crazy. I have two scenarios where users are getting 5.2.1 NDRs.
Scenario 1:
User1 gets the 5.2.1 NDR when sending any mail to user2. User1 can send mail to anyone else without issue. User2 receives mail from others without issue. The issue is not consistent. Sometimes mail from user1 to user2 is delivered without issue.
Scenario 2:
This user getting the 5.2.1 NDR on any meeting requests sent or accepted to several users Regular mail works fine, and user has no issues receiving mail.
I have already checked the obvious:
- No MBXs are disabled
- All associated accounts has valid SIDs
- Neither of the two scenarios involve sending mail to a public folder
- No phantom delegates anywhere
- Messages being sent are not too large
I am at a loss. Thoughts?
Scenario 1:
User1 gets the 5.2.1 NDR when sending any mail to user2. User1 can send mail to anyone else without issue. User2 receives mail from others without issue. The issue is not consistent. Sometimes mail from user1 to user2 is delivered without issue.
Scenario 2:
This user getting the 5.2.1 NDR on any meeting requests sent or accepted to several users Regular mail works fine, and user has no issues receiving mail.
I have already checked the obvious:
- No MBXs are disabled
- All associated accounts has valid SIDs
- Neither of the two scenarios involve sending mail to a public folder
- No phantom delegates anywhere
- Messages being sent are not too large
I am at a loss. Thoughts?
Last Comment
ASKER
^^ nope
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Sorry.. here is the full error:
"The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator. "
"The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator. "
You shouldn't be getting SMTP error messages like that if the users are internal.
Have you got message tracking enabled? If so, what does that say? If not, turn it on and then test again. You need to see what Exchange is doing with the message.
Simon.
Have you got message tracking enabled? If so, what does that say? If not, turn it on and then test again. You need to see what Exchange is doing with the message.
Simon.
ASKER
Yep.. However.. Message tracking is failing when the tracking needs to go from one cluster to the other:
"The tracking database on EVS1.domain.company.com is not available or the message has left the Exchange organization. Facility: Microsoft Exchange Management ID no: c1032751 Microsoft Exchange Management"
"The tracking database on EVS1.domain.company.com is not available or the message has left the Exchange organization. Facility: Microsoft Exchange Management ID no: c1032751 Microsoft Exchange Management"
So this is a cluster?
Anything else you have failed to mention?
Simon.
Anything else you have failed to mention?
Simon.
ASKER
Yep.. I didn't think it being a cluster mattered much.
ASKER
Simon - Did you forget about me? :)
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
http://support.microsoft.com/default.aspx/kb/870585