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:
972076 Description of Update Rollup 2 for Microsoft Exchange Server 2007 Service Pack 2
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:
On the Exchange Server 2007 server, start Windows Explorer.
Note If this line does not exist between the <appsettings> segment and the </appsettings> segment, insert this line.
Save the changes, and then exit Notepad.
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: