We are having an issue with one particular dist list. When someone send to this dist list, the message gets stuck in the "Messages Awaiting Directory Lookup" queue. A message trace on it shows the message being submitted to the Categorizer, and then 'Message Scheduled to Retry Categorization'. It will sit in the queue until it times out (48 hours or so) and then generate a NDR. This time, we cancelled the message and got the NDR immediatliy - it reads as:This message was rejected due to the current administrative policy by the destination server. Please retry at a later time. If that fails, contact your system administrator. <nyms1.NY.Corp.Verintsystems.com #4.3.2>"The DL that is causing the problem is our all company DL. It is an e-mail enabled Universal security group that resides in another domain with in the forest. There are 17 memebers, most are other DLs, that have other DLs nested, etc. The group is restricted in that only a few people can send to it. We are running Exchange 2003 SP2. We have also turned up logging on the categorizer to 7 (kinda like Spinal Tap and going to 11), and get NUMEROUS events - we get a TON of 6009 messages as well as 6008 and 6006 messages. The 6009's look like this:Event Type:ErrorEvent Source:MSExchangeTransportEvent Category:Categorizer Event ID:6009Date:1/21/2009Time:8:53:51 AMUser:N/AComputer:NYMS1Description:Categorizer encountered a hard error while processing a message. While processing user 'X500:CN<:<name removed>', the function 'CCatAddr:HrAddNewAddressesFromICatItemAttr' called 'HrAddAddresses' which returned error code '0xc004055a' (). ( f:\tisp2\transmt\src\phatq\cat\src\ccataddr.cpp@1459 ) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 5a 05 04 c0andEvent Type:ErrorEvent Source:MSExchangeTransportEvent Category:Categorizer Event ID:6009Date:1/21/2009Time:8:53:51 AMUser:N/AComputer:NYMS1Description:Categorizer encountered a hard error while processing a message. While processing user 'X500:<:<name removed>', the function 'CCatRecip::HrProcessItem_Default' called 'HrAddNewAddressesFromiCatItemAttr' which returned error code '0xc004055a' (). ( f:\tisp2\transmt\src\phatq\cat\src\ccatrecip.cpp@1988 ) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 5a 05 04 c0 Z.. The 6008's look like this:Event Type:WarningEvent Source:MSExchangeTransportEvent Category:Categorizer Event ID:6008Date:1/21/2009Time:8:53:51 AMUser:N/AComputer:NYMS1Description:Categorizer is temporarily unable to process a message. While processing user 'SMTP:<name removed>', the function 'CCatRecip::AddDLMember' called 'GetListResolveStatus' which returned error code '0xc0040520' (). ( f:\tisp2\transmt\src\phatq\cat\src\ccatrecip.cpp@852 ) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 20 05 04 c0 .. andEvent Type:WarningEvent Source:MSExchangeTransportEvent Category:Categorizer Event ID:6008Date:1/21/2009Time:8:53:51 AMUser:N/AComputer:NYMS1Description:Categorizer is temporarily unable to process a message. While processing user 'SMTP:<name removed>', the function 'CMembersInsertionRequest::HrInsertSearches' called 'm_pDLRecipAddr->AddDLMember' which returned error code '0xc0040520' (). ( f:\tisp2\transmt\src\phatq\cat\src\ccatrecip.cpp@3502 ) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 20 05 04 c0 .. and finally, the 6006'sEvent Type:WarningEvent Source:MSExchangeTransportEvent Category:Categorizer Event ID:6006Date:1/21/2009Time:8:53:51 AMUser:N/AComputer:NYMS1Description:Categorizer is temporarily unable to process a message. The function 'CBatchLdapConnection::DecrementPendingSearches' called 'pCInsertionRequest->HrInsertSearches' which returned error code '0xc0040520' (). ( f:\tisp2\transmt\src\phatq\cat\ldapstor\asyncctx.cpp@2290 ) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 20 05 04 c0 .. Any help would be greatly apprecitated. Thanks in advance!DAN

Hi Dan, After some research, I notice the issue may occur that some recipients including in the DL are not mail enabled. The Categorizer attempts to resolve these recipients by searching the Active Directory database. Because these accounts have no Exchange attributes, this search fails. The failure to resolve the Active Directory accounts is causing a large amount of Categorization errors. Therefore, please check the recipients indicated in the event 6009. Whether are the recipients mail enabled? If the recipients are not mail enabled, please remove the recipients or create a new DL to include only mail enabled recipients. Mike