A return address is split into two separate and incomplete addresses when a recipient replies to a specific message in Exchange 2007

Consider the following scenario:

• A user sends an e-mail message from a Microsoft Exchange Server 2007 server to an external recipient who is not located on the Exchange Server 2007 server.
• The Exchange Server 2007 user's e-mail address contains an extended character such as "ü" or "ä," and the display name contains a comma.
• The recipient replies to the message

In this scenario, the return address is split into two separate and incomplete e-mail addresses. The split e-mail addresses each contain part of the original address. Therefore, the message is not sent successfully.

To resolve this problem, install the following update rollup:
After you apply this fix, you must add a new entry to the Edgetransport.exe.config XML file to enable the function on the server.

Note For the IMAP4 protocol, add the new entry to the Microsoft.Exchange.Imap4.exe.config file. For the POP3 protocol, add the new entry to the Microsoft.Exchange.POP3.exe.config file. To do this, follow these steps:

1. On the Exchange Server 2007 server, start Windows Explorer.
2. Locate the following folder:

   Drive :\Program Files\Microsoft\Exchange Server\Bin 

3. Make a backup copy of the EdgeTransport.exe.config file by saving a copy of the file. Name the backup copy EdgeTransport.exe.config.old.
4. Open the EdgeTransport.exe.config file in Notepad, and then locate the following line between the <appsettings> segment and the </appsettings> segment:

   <add key="QuoteDisplayNameBeforeRfc2047Encoding" value="true"/> 

   Note If this line does not exist between the <appsettings> segment and the </appsettings> segment, insert this line.
5. Save the changes, and then exit Notepad.
6. Restart the Exchange Transport service.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The Exchange Server 2007 encoding behavior does not follow the Request for Comments (RFC) requirements that are described in RFC 2047. Microsoft Exchange Server 2003 Service Pack 2(SP2) includes the RFC2047Compliant registry entry that changes the encoding behavior so that Exchange Server 2003 adds quotation marks. For example, in Exchange Server 2003 an address is encoded as follows: =?iso-8859-1?Q?=22F=F6rst=2C_Arie=22?= First.Last@testdomain.com <mailto:First.Last@testdomain.com>

Note In this encoded text, "=22" indicates the quotation mark.

When the address is encoded in this manner, the external mail application will treat it as a single address.

For more information about RFC 2047, visit the following Internet Engineering Task Force (IETF) Web site:

For more information about RFC 2822, visit the following IETF Web site: