Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Incoming message is garbled if the To line exceeds 1,022 characters

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

View products that this article applies to.

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.

↑ Back to the top

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.

↑ Back to the top

Workaround

There are two possible workarounds:
  1. 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.
  2. 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

↑ Back to the top

Article Info
Article ID : 821733
Revision : 5
Created on : 1/1/0001
Published on : 1/1/0001
Exists online : False
Views : 522