Microsoft KB Archive/925379

= Recipients may receive non-delivery reports (NDRs) after you enable the envelope journaling feature in Exchange Server 2003 Service Pack 2 (SP2) =

Article ID: 925379

Article Last Modified on 10/25/2007

-

APPLIES TO

 Microsoft Exchange Server 2003 Service Pack 2, when used with:  Microsoft Exchange Server 2003 Standard Edition

 Microsoft Exchange Server 2003 Enterprise Edition 

-



SYMPTOMS
You enable the envelope journaling feature in Microsoft Exchange Server 2003 Service Pack 2 (SP2). After you do this, recipients may receive non-delivery reports (NDRs) when the recipients send or reply to an e-mail message that is sent to certain distribution groups.

Additionally, the following events are logged in the Application log: Event Type: Error

Event Source: MSExchangeTransport

Event Category: Categorizer

Event ID: 9004

Description: Categorizer encountered a hard error while processing a message. While processing user 'smtp:DL@domain.com', the function 'CPhatCat::HrReResolveAllJournalRecipients' called 'HrReadDsvalGuid' which returned error code '0x8004090a'. A DSN has been generated. ( f:\tisp2\transmt\src\cat\sinks\phatcat\cptenvelope.cpp@1170 )

Event Type: Error

Event Source: MSExchangeTransport

Event Category: Categorizer

Event ID: 9004

Description: Categorizer encountered a hard error while processing a message. While processing user 'smtp:DL@domain.com', the function 'CPhatCat::HrSaveEJRecipIfNecessary' called 'HrReResolveAllJournalRecipients' which returned error code '0x8004090a'. A DSN has been generated. ( f:\tisp2\transmt\src\cat\sinks\phatcat\cptenvelope.cpp@936 )

Event Type: Error

Event Source: MSExchangeTransport

Event Category: Categorizer

Event ID: 9004

Description: Categorizer encountered a hard error while processing a message. While processing user 'smtp:DL@domain.com', the function 'CompleteRecipient' called 'HrSaveEJRecipIfNecessary' which returned error code '0x8004090a'. A DSN has been generated. ( f:\tisp2 \transmt\src\cat\sinks\phatcat\cptcomplete.cpp@55 )

Event Type: Error

Event Source: MSExchangeTransport

Event Category: NDR

Event ID: 3009

Description: A non-delivery report with a status code of 5.1.0 was generated for recipient rfc822;DL@domain.com (Message-ID  <4CB23381E40E0A41B397C1007C2F20C60424F3A8@ . .com>).

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.



CAUSE
This problem occurs because the envelope journaling feature uses the domain controller instead of the global catalog server to resolve the journaling mailbox GUID to the domain name of the user account. This process occurs when the e-mail message is re-categorized and then is journaled again.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
Because of file dependencies, you must have Microsoft Exchange Server 2003 SP2 installed to apply this hotfix.

Restart requirement
You do not have to restart your computer after you apply this hotfix. However, the following services are stopped and then restarted:
 * Simple Mail Transfer Protocol (SMTP)
 * Microsoft Exchange Routing Engine
 * Network News Transfer Protocol (NNTP)
 * HTTP Secure Sockets Layer (SSL)
 * Microsoft Internet Information Services (IIS) Admin Service

Hotfix replacement information
This hotfix does not replace any other hotfix.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Note Only apply the hotfix to the journaling server.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
A journal recipient must be re-resolved if the following conditions are true:
 * An e-mail message was already journaled.
 * A new recipient was added to a distribution group.

Consider the following scenario. An e-mail message originates from a server that is other than the distribution group expansion server. The initial categorization and envelope journaling should occur on the original server. However, the e-mail message is sent to the distribution group expansion server for expansion.

Then, after the e-mail message is received by the expansion server, the distribution group is expanded, and new recipients are added.

In this scenario, the e-mail message must be re-journaled, because new recipients are added to the expansion server. Then, an NDR is sent to the recipient.

For more information about how to enable envelope journaling, click the following article number to view the article in the Microsoft Knowledge Base:

843105 Troubleshooting message journaling in Exchange Server 2003 and in Exchange 2000 Server

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

817903 New naming schema for Exchange Server software update packages

Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver KB925379

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.