Microsoft KB Archive/126497

= Limiting the number of recipients of a message =

Article ID: 126497

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 4.0 Standard Edition
 * Microsoft Exchange Server 5.0 Standard Edition
 * Microsoft Exchange Server 5.5 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange Server 2003 Enterprise Edition

-



This article was previously published under Q126497



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SUMMARY
A new registry value has been added to the Microsoft Exchange Information Store service that allows an administrator to set a limit on the number of recipients that a mail message can have.



MORE INFORMATION
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To set this parameter, perform the following steps:  Start Registry Editor (Regedt32.exe). Locate the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ ParametersSystem

Note The above registry key is one path; it has been wrapped for readability. On the Edit menu, click Add Value, and then add the following registry value:

Value Name: Max Recipients on Submit

Data Type: REG_DWORD

String:

 Quit Registry Editor.

In Exchange Server 5.5 and earlier, this limit also applies to messages that are transferred into the store by the Internet Mail Service. An event ID 4117 message is logged and the message is moved to the Archive folder. The message is not delivered and it does not send a non-delivery report (NDR).

Note In Exchange 2000 and later, only messages submitted with MAPI are subject to this restriction. To configure recipient limits that work for all messages regardless of how they are submitted, use the setting that is located under Global Settings\Message Delivery in Exchange System Manager.



If a user attempts to send a message to more recipients than is designated by the Max Recipients on Submit parameter and the user has the new Emsmdb(32).dll, the following error message may be displayed when the user attempts to send the message:

The item could not be sent. The number of recipients on this message exceeds the upper limit configured by the administrator.

If a user attempts to send a message to more recipients than is designated by the Max Recipients on Submit parameter and the user DOES NOT have the new Emsmdb(32).dll, the following error message may be displayed when the user attempts to send the message:

The item could not be sent. The client operation failed.

Note the following when you add the above registry key:
 * You do not have to stop and restart services for this change to take effect.
 * The number you choose applies to total recipients associated with a message (To+Cc+Bcc=Total).
 * You cannot circumvent the limit by using a personal distribution list; it is evaluated for number of entries before the send.
 * In Exchange Server 5.5 only, server-based distribution lists let you exceed the total number of recipients. You can do this by using the Max Recipients on Submit registry value if you have the correct permissions.

Note The new Emsmdb32.dll file referenced in this article is included in Exchange Server 4.0 SP2 and all later versions of Exchange Server.

Additional query words: maximum xcln header restrict restrictions bedlam XADM

Keywords: kbinfo kbusage KB126497

-

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

© Microsoft Corporation. All rights reserved.