Incoming message is garbled if the To line exceeds 1,022 characters (821733)
The information in this article applies to:
- Microsoft Exchange 2000 Conferencing Server
- Microsoft Exchange 2000 Conferencing Server SP1
- Microsoft Exchange 2000 Conferencing Server SP2
- Microsoft Exchange 2000 Conferencing Server SP3
- Microsoft Exchange 2000 Enterprise Server
- Microsoft Exchange 2000 Server
- Microsoft Exchange 2000 Server SP1
- Microsoft Exchange 2000 Server SP2
- Microsoft Exchange 2000 Server SP3
SYMPTOMSIf 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.CAUSEThis 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.
WORKAROUNDThere 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
REFERENCESFor more information, visit the following RFC Web site:
| Modification Type: | Major | Last Reviewed: | 12/23/2005 |
|---|
| Keywords: | kbprb KB821733 |
|---|
|