XCON: Messages Stack Up in SMTP Local Delivery Queue (319461)



The information in this article applies to:

  • Microsoft Exchange 2000 Server

This article was previously published under Q319461

SYMPTOMS

In Microsoft Exchange 2000 Server, messages stack up in the Simple Mail Transfer Protocol (SMTP) Local Delivery queue when the following conditions are true
  • More than two Exchange 2000 servers exist in the same routing group.
  • A mail-enabled public folder exists on only one Exchange 2000 server.
  • The Forwarding Address is set to "Deliver messages to both forwarding address and folder," and specifies a user that exists on the same Exchange 2000 server as the public folder's home Exchange 2000 server.
  • There is no replica of this public folder on any other Exchange 2000 server.

CAUSE

During the forwarding process, when a message item is posted to a public folder, Exchange 2000 creates a message item from the original posted message item. However, because Exchange 2000 does not configure the property of the message item correctly, Exchange 2000 tries to expand the alternative recipient value two times. This causes messages to stack up in the SMTP Local Delivery queue.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

The version of this fix should have the following file attributes or later:

Component: Transport

File nameVersion
Davex.dll6.0.5770.87
Drviis.dll6.0.5770.87
Dsaccess.dll6.0.5770.87
Dscmsg.dll6.0.5770.87
Excdo.dll6.0.5770.87
Exmgmt.exe6.0.5770.87
Exoledb.dll6.0.5770.87
Exprox.dll6.0.5770.87
Exres.dll6.0.5770.87
Exsmtp.dll6.0.5770.87
Exsp.dll6.0.5770.87
Exwmi.dll6.0.5770.87
Jcb.dll6.0.5770.87
Mad.exe6.0.5770.87
Mdbmsg.dll6.0.5770.87
Mdbsz.dll6.0.5770.87
Msgtrack.dll6.0.5770.87
Peexch50.dll6.0.5770.87
Phatcat.dll6.0.5770.87
Store.exe6.0.5770.87

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

Modification Type:MinorLast Reviewed:6/5/2003
Keywords:kbbug kbExchange2000preSP3fix kbExchange2000sp3fix kbfix KB319461