Microsoft KB Archive/912433

= Uuencode attachments that are sent from non-Exchange servers are displayed as garbled text in Exchange Server 2003 Service Pack 2 =

Article ID: 912433

Article Last Modified on 10/30/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Service Pack 2

-



SYMPTOMS
After you install Microsoft Exchange Server 2003 Service Pack 2 (SP2), uuencode attachments that are sent from non-Exchange servers are displayed as garbled text in the body of the e-mail message.



CAUSE
This behavior occurs because the uuencode message is incorrectly tagged with a MIME Version 1.0 header. Therefore, the message is incorrectly formatted.

In Exchange Server, when a uuencode message is incorrectly tagged with a MIME Version 1.0 header, the text in the message is treated as MIME text. Therefore, the text of the attachment is displayed in the body of the message and appears garbled to the message recipient. This behavior occurs because the message combines two different Internet body formats by combining a MIME Version 1.0 header in a uuencode message.



RESOLUTION
Configure the non-Exchange SMTP server that is sending messages to Exchange Server so that the non-Exchange server does not add MIME version headers to uuencode messages.



STATUS
This behavior is by design.



MORE INFORMATION
The word &quot;uuencode&quot; is derived from &quot;Unix to Unix encoding.&quot; A uuencode message can be identified when the first word in the message is &quot;begin.&quot; The following is an example of a uuencode message:

begin 664 sampleletter.txt

begin

= the file's read/write/execute permissions as three octal digits

= output name to write the decoded data

The MIME Version 1.0 header usually identifies that a message is a MIME message and that the message complies with RFC 2045. The following is an example of a MIME Version 1.0 header:

Mime-Version: 1.0

&quot;MIME-Version&quot; &quot;:&quot; 1*DIGIT &quot;.&quot; 1*DIGIT

Both standards (MIME and uuencode) cannot be combined in the same message as displayed in the following sample header:

Date: Fri, 2 Dec 2005 14:21:33 +1100 (EDT)

From: John Doe 

Message-Id: <200512020321.server.domain.com>

To: Jane Doe@contoso.com

Subject: View the attachment

Mime-Version: 1.0

Content-Type: text/plain; charset=us-ascii

Content-Transfer-Encoding: 7bit

Return-Path: JohnDoe@contoso.com

X-OriginalArrivalTime: 02 Dec 2005 03:21:31.0901 (UTC)

FILETIME=[7DDA6AD0:01C5F6EF]

Here is your attachment report

begin 664 sampleletter.txt

M:6-L;W)P+G`@92L@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@

M(&quot;`@(#,N-BXV($EN=F5N=&]R>2!$971A:6P@8GD@3&]C871I;VX@(&quot;`@(&quot;`@

M(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@($1A=&4Z(#`R+S$R+S`U#0I0

M86P-&quot;E-I=&4@(&quot;`@($QO8V%T:6]N($ET96T@3G5M8F5R(&quot;`@(&quot;`@(&quot;!2968@

M(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@54T@(%%T>2!/;B!(86YD($-R96%T960@($5X<&ER

M92`@($%S<V%Y(&quot;4@1W)A9&4@4W1A='5S(&quot;`@079A:6P@3F5T($]V<DES#0H

M

M+2TM+2TM+2`M+2TM+2TM+2`M+2TM+2TM+2TM+2TM+2TM+2T@+2TM+2

TM+2TM

M+2TM+2TM+2TM(&quot;TM(&quot;TM+2TM+2TM+2TM+2`M+2TM+2TM+2`M+2TM+2T

M+2`

M M+2TM+2TM(&quot;TM+2TM(&quot;TM+2TM+2TM(&quot;TM+2TM(&quot;TM+2`M+2TM+0T*,C`P,&quot;

`@

M(&quot;`@1C`P,2`@(&quot;`@,3`P,#`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@(&quot;`@ M(&quot;`@(&quot;!%02`@(&quot;`@(&quot;`@+3$X+C`@,#(O,#