In a Microsoft Exchange Server 2003 and Microsoft Exchange Server 2007 coexisting environment, after you enable per-mailbox database journaling, you may find that some messages stay in the submission queue with the "Retry" status on the Exchange 2007 hub transport server. If you check the messages in the Queue Viewer in Exchange Management Console, the Last Error field shows the following message:
Categorization failed. The message will be deferred and retried because it was marked for retry if rejected.
When this issue occurs, the following event message is logged in the Application log on the Exchange server.
Event Type: Error Event Source: MSExchangeTransport Event Category: Categorizer Event ID: 9213 Description: A non-expirable message with the internal message ID xx could not be categorized. This message may be a journal report or other system message. The message will remain in the queue until administrative action is taken to resolve the error. Other messages may also have encountered this error. To further diagnose the error, use the Queue Viewer or the Mail Flow Troubleshooter.
This issue occurs after you configure the send size restriction in the global transport settings to a certain value. When an Exchange Server 2003 user sends a message that is close to the size of the size restriction, the corresponding journaling report on the Exchange 2007 server may be larger than the size restriction because additional data is attached. Then, the journaling report message is queued.
To resolve this problem, install Update Rollup 7 for Exchange 2007 Service Pack 1.
For more information about Update Rollup 7 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic: