Exchange Categorizer fails

I have an issue where an email from an external source seems to get caught in the Exchange Categorizer, and never gets delivered to the Exchange recipient. I have no idea where to look? I have checked the BadMail folder, but there is nothing there for this particular message, nothing in any queue, or the pickup folder. Where did it go?

So far I have only been notified about two instances from one sender, but we cant seem to recieve email from this person?

Any ideas?
jguderianAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
David WilhoitConnect With a Mentor Senior Consultant, ExchangeCommented:
It may require a restart of the SMTP virtual server...

Anyway, it looks like the issue is on the other end. Specifically, that user's machine. The server on their end obviously can find you. You can send to them, and they can reply, which means that there's nothing wrong with your machine. It's only when they compose a new message from the other side and send does it get stuck. I'm thinking that the contact entry on their side is bad. Have them delete any entries, and recreate them from an email that you sent successfully.

D
0
 
jguderianAuthor Commented:
One more thing...

A "READ" reciept successfully delivered to the recipients mailbox form the send in question. So an email failed twice, but a "READ" reciept succeeded.

Just wanted to add that.
0
 
David WilhoitSenior Consultant, ExchangeCommented:
did you find where in the cat it gets stuck? pre or post cat?

D
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
ikm7176Commented:
Most of the time, if an outbound message is stuck in the categorizer it is
a problem with DNS. Make sure that you are ONLY pointing to internal DNS
servers in your TCPIP properties of the nic card. Also, take out any
references to other DNS servers from the Configure External DNS off the
Delivery Advanced of the Default SMTP Virtual Server. Then run ipconfig
/flushdns and ipconfig /registerdns


this link might be helpful

http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2Fen%2Fwc022201%2Fwct022201.asp
0
 
jguderianAuthor Commented:
Kidego: How do I identify where in the cat it gets stuck? I just viewed the message in the "Message Tracking Center", which said the last step was the Categorizer. Is there somewhere else I can look?

ikm7176: This is not an outbound message. This email is from an external source. I appreciate your DNS suggestions, however I know that DNS is configured properly on the clients, as well as all servers.
0
 
David WilhoitSenior Consultant, ExchangeCommented:
So you're able to find the message in the message tracking center, and when you clikc details, it just says the last place the message went was the categorizer? We need to turn up diagnostics logging on SMTP transport, probably to medium or maximum, whichever gets us the data we need to see.

http://support.microsoft.com/default.aspx?scid=kb;en-us;823489

http://support.microsoft.com/default.aspx?scid=kb;en-us;823864


http://support.microsoft.com/default.aspx?kbid=821910
0
 
jguderianAuthor Commented:
I turned up the logging on both the Categorizer, and SMTP to medium.  I asked the sender of the original email to send me a response, so when I get that, I can give you whatever information you need.
0
 
David WilhoitSenior Consultant, ExchangeCommented:
clear your logs and save them before you get too far, and you may want to increase the applog size. This will generate a TON of events....you sift thru them and watch the conversation.

D
0
 
jguderianAuthor Commented:
Hmm... I have recieved sevearl email since elevating the log levels, yet there are no additional log entries? Does this require a reboot, or stopping of a service?

Withing Diagnostic Logging -> MSExchangeTransport is where I made my changes. Is this correct?
0
 
jguderianAuthor Commented:
Just to throw a wrench in troubleshooting things. I happened to send a test email to the person who is getting stuck in the categorizer, and amazingly enough she replied, and I recieved it just fine. So here is the course of events

1. email@someplace.com emails internal Exchange recipient gets stuck in categorizer
2. "READ" reciept from email@someplace.com is successfully delivered to Exchange recipient
3. Additional email from email@someplace.com to Exchange recipient gets stuck in categorizer
4. I send email to email@someplace.com & successfully get a response

Why would the results of email coming from one specific sender to a specific recipient?

Again, the logging that I enabled isnt logging anything into the Application log.
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.