Exchange 2003 5.2.1 error bounces emails seemingly at random

SBS 2003 Exchange with SP2 no other rollups after that.
Server is upto date except some .net crap that won't install.

Email sent from outside LAN will sometimes bounce back to the sender with 5.2.1 error.
We have removed all limits on email sizes
It's not consistant at all, some will bounce some won't, we can't find a trigger that causes a message to bounce. Sometimes a message that's 17K will bounce from the server with a return to sender of 5.2.1

There does not appear to be anything touching the traffic like Anti Spam software or odd firewall software on the server.
Just plain old Anti Virus installed.

A telnet email session (25) with the server always results in a sucessfull email. With no 5.2.1 ever returned in my manual session with the server.

This has been going on for a few weeks, and I can not figure this out!
I have done extensive searching on this site and others.
Because it's across multiple users, I ruled out a currupt single user box.


Below is a transcript of a returned to sender message.

From: System Administrator
Sent: Wednesday, September 07, 2011 11:48 AM
To: ***********, J*****
Subject: Undeliverable: FW: DMV proposal
Your message did not reach some or all of the intended recipients.
      Subject:  FW: DMV proposal
      Sent:     9/7/2011 11:44 AM
The following recipient(s) cannot be reached:
      Ge**** ********** on 9/7/2011 11:48 AM
            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*********.com #5.2.1>
 
funman1Asked:
Who is Participating?
 
TalkExchangeConnect With a Mentor Commented:
Please increase the diagnostic logging on SMTP Protocol for all categories. Please check the logs when the email fails.

Also check if you get any 9667 ( name props) event ids

http://geekswithblogs.net/BWCA/archive/2009/06/09/another-reason-for-a-5.2.1-undeliverable-message-ndr.aspx
0
 
funman1Author Commented:
We will try those first thing thank you for the advice. Though, do you think SMTP logging will help with it isn't SENDING that is the issue, it is RECEIVING?  Also this seems to be all external, not internal (so it doesn't seem to from one exchange to another like the link talks about)

addtional info:  
It has NOTHING to do with public folders (we tried to apply that MS fixit)
0
 
TalkExchangeCommented:
Diagnostic logging will help in sending as well as receiving.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
funman1Author Commented:
Yep found LOTS of 9667
Cranked up the registry for NonMAPI Named Props Quota and Added Named Props Quota and set it to the same value.
Then dismounted and remounted the store.

So now we wait till I hear back from users :)
0
 
funman1Author Commented:
TalkExchange:  we DID find some 9667 errors and upped the registry entries, we just have to wait now to see if it worked!  Thanks so much for your thoughts.
0
 
TalkExchangeCommented:
Good to know surely it should fix it
0
 
funman1Author Commented:
No Issues now so far, so I call it solved!
0
 
funman1Author Commented:
Issue Resolved now
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.