The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. SUMMARYAfter you enable the Message Journaling feature of Exchange Server version 5.5 Service Pack 1, if you send large messages to other users on your local Exchange Server computer, you receive non-delivery reports (NDRs) similar to the following: Your message did not reach some or all of the intended recipients.Subject: MSG Sent: 8/11/98 11:14 AMThe following recipient(s) could not be reached:Exchange User on 8/11/98 11:16 AM Either the message size exceeds the maximum allowed for the recipient or transport, or you have exceeded the storage limit on your mailbox.MSEXCH:MSExchangeIS:Site:SERVER MORE INFORMATION
This occurs when size limits are set on the Exchange Server message transfer agent (MTA). Before you enable the Message Journaling feature, only messages that you send to users on another Exchange Server computer go to the MTA, and these are sent back if the size limit is exceeded. After you enable the Message Journaling feature, messages that are sent to local users also go to the MTA and, therefore, the size restriction is invoked.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\No Local DeliveryNOTE: The No Local Delivery value is a DWORD type value. If this value is non-zero, journaling is enabled for all messages submitted to local recipients and is subject to any size restrictions that may be enabled for the local MTA. Additional query words: journal content too long mta
Keywords : exc55 exc55sp1 exc55sp2 exc55sp3 |
Last Reviewed: February 3, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |