XADM: Duplicate Messages are Received When Message is Sent to Large DL and Recipient's Quotas are Exceeded

ID: Q232391


The information in this article applies to:


SYMPTOMS

When a user sends a message to a large distribution list (DL), it is possible for some recipients to receive the message multiple times. For this to happen, most of the recipients in the DL must be over their mailbox quota and not allowed to receive new mail. Also, the message must originate from outside the server so that the message is delivered by the Message Transfer Agent (MTA). Users who are not over their quota and are a member of the DL will receive the message once an hour.


RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or later:

Component: Information Store

File name Version
Store.exe 2621.0
Mdbmsg.dll 2621.0
Gapi32.dll 2621.0
Netif.dll 2621.0


Component: MTA

File name Version
Dbserver.sch 2621.0
Dcprods.cat 2621.0
Ems_rid.dll 2621.0
Emsmta.exe 2621.0
Info4log.cfg 2621.0
Infoblog.cfg 2621.0
Infodlog.cfg 2621.0
Infollog.cfg 2621.0
Infoplog.cfg 2621.0
Infotlog.cfg 2621.0
Mtacheck.exe 2621.0
Mtamsg.dll 2621.0
P2.xv2 2621.0
X400om.dll 2621.0
X400omv1.dll 2621.0



NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.


MORE INFORMATION

When the Exchange Server information store is attempting to deliver the message, it will log the following error:

Event ID: 2025
Category: Transport Delivering
Source: MSExchangePrivate
Type: Information
Description:
The delivery of a message failed due to error 000004DD. A non-delivery report is being sent to the message's originator.
At this point, the store builds a list of users who cannot take delivery of the message. After this is completed, the store sends the MTA the object with the list. When the MTA sees this large object, the MTA responds with an "out of resources" error. When this occurs, the message does not get purged from the queue, but rather remains in the queue. By default, the store tracks duplicate message delivery for one hour. When the message remains in the queue for over an hour, the store will again try to deliver this message. The users that can accept delivery of the message will get a second copy. Users will continue to get a copy of the message every hour until the message is manually removed from the queue.

To resolve this problem, both the MTA and the store had to be modified to work together. Both components are required for this to work correctly.

Additional query words: restriction lockout quota exceed over


Keywords          : 
Version           : winnt:5.5
Platform          : winnt 
Issue type        : kbbug 

Last Reviewed: June 28, 1999