We have two organizations with a SMTP connector between the two. When users in one organization(domain1) send mail tomailbox1 in the second organization(domain2)that has server based Autoforwarding turned on to forward the message to mailbox2(domain2), they receive a NDR for the mailbox2(domain2). The message is delivered to mailbox1(domain2). We have tested this with external addresses and everything works fine. It is only when going through the SMTP connector that we encounter the problem. The event logs refer to a Categorizer Failure. I am wondering if the problem has to do with the fact that the message needs to be sent to the categorizer a second time to deliver the message to the Alternate recipient. And if this is the case then what is causing the problem. Any help is greatly appreciated. I get the following information in the event logs Event Type:InformationEvent Source:MSExchangeTransportEvent Category:Categorizer Event ID:6015Date:8/7/2008Time:1:33:18 PMUser:N/AComputer:Bridgeheadserver1.domain2Description:Categorizer is NDRing a recipient with address SMTP:mailbox2 with reason code 0xc0040557 (). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 57 05 04 c0 W.. Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:NDR Event ID:3009Date:8/7/2008Time:1:23:44 PMUser:N/AComputer:Bridgeheadserver1.domain2 Description:A non-delivery report with a status code of 5.1.0 was generated for recipient rfc822;mailbox2@domain2.com (Message-ID <D34A02ED8C6D8046A6D43A96FDB89A3116129A@domain1.LOCAL>). Cause: This is categorizer failure caused by a bad address. For more information, click http://www.microsoft.com/contentredirect.asp. Solution: Either the recipient address is incorrectly formatted or the categorizer was not able to properly resolve the recipient. Checking the recipient address and re-sending the message is the first step to resolving this error. Data:0000: 46 05 04 80 F..€

Hi, 1. Whether the issue can always be reproduced that every user in Domain1 sends an email to the mailbox1 (Domain2)? 2. If the user (domain1) sent email to mailbox2 (domain2) directly, is the issue can be reproduced? 3. Please let me know the Exchange Server version of the Bridgeheadserver1.domain2 In addition, please attempt the following method to troubleshoot the issue: Increase the Diagnostic Level of MSExchangeTransport\Categorizer to Maximum and then reproduced the issue. Please check the application log for more detailed information. Please also notice the MSExchangeDSAccess errors if they exist as the Exchange Server need to connect to GC to resolve the recipient. Mike

Yes the problem can be reproduced with any account in Domain 1 sending to any account in Domain 2. User in Domain 1 can send mail to mailbox2 in Domain 2 directly. All servers are running Exchange 2003 SP2. I get the following messages in the event log when I turn diagnostic loggong on to Maximum. Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:NDR Event ID:3009Date:8/18/2008Time:3:13:04 PMUser:N/AComputer:Bridgeheaddomain2Description:A non-delivery report with a status code of 5.1.0 was generated for recipient rfc822;EVS3SG3MB1.Test@domain.com (Message-ID <365525964388904597C3C5A47E5AAF631616A5@mailboxserverdomain1>). Cause: This is categorizer failure caused by a bad address. For more information, click http://www.microsoft.com/contentredirect.asp. Solution: Either the recipient address is incorrectly formatted or the categorizer was not able to properly resolve the recipient. Checking the recipient address and re-sending the message is the first step to resolving this error. Data:0000: 46 05 04 80 F..€ Event Type:InformationEvent Source:MSExchangeTransportEvent Category:Categorizer Event ID:6015Date:8/18/2008Time:3:13:04 PMUser:N/AComputer:EDMABSOWA1Description:Categorizer is NDRing a recipient with address SMTP:EVS3SG3MB1.Test@bchydro.com with reason code 0xc0040557 ().Data:0000: 57 05 04 c0 W..