Microsoft KB Archive/821733

= Incoming message is garbled if the To line exceeds 1,022 characters =

Article ID: 821733

Article Last Modified on 2/27/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Conferencing Server
 * Microsoft Exchange 2000 Conferencing Server Service Pack 1
 * Microsoft Exchange 2000 Conferencing Server Service Pack 2
 * Microsoft Exchange 2000 Conferencing Server Service Pack 3
 * Microsoft Exchange 2000 Enterprise Server
 * Microsoft Exchange 2000 Server Standard Edition
 * Microsoft Exchange Server 2000 Service Pack 1
 * Microsoft Exchange 2000 Server Service Pack 2
 * Microsoft Exchange Server 2000 Service Pack 3

-





SYMPTOMS
If you receive Simple Mail Transfer Protocol (SMTP) mail from computers that do not belong to your Exchange organization, some of the incoming messages may be garbled and the client may display header information in the message body.



CAUSE
This problem is caused by messages that are not compliant with Request for Comments (RFC) format. It occurs if all the following conditions are true:
 * The To line in the message header is longer than 1,022 characters.
 * The message was transmitted by using the BDAT command.



WORKAROUND
There are two possible workarounds:  If you have a relay server that is between the Internet and your Exchange organization, configure the relay server to use the DATA command instead of the BDAT command to forward mail to Exchange 2000. When you use the Microsoft Windows 2000 SMTP service as a relay server, you can do this by enabling the Send HELO instead of EHLO option for the remote domain or the remote domains. You can turn off the Extended SMTP (ESMTP) verb CHUNKING and BINARYMIME on the Exchange 2000 computer. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

257569 XFOR: How to Turn Off ESMTP Verbs in Exchange 2000



