Improper Coding in Outlook sent email.

[jberlin]

I have a co-worker who gets an email from another company that also uses
Exchange. What happens is that the MIME type for one attachment is
incorrect. I believe the sender is composing in Word then uses the "Send To:
Mail Recipient (As Attachment)" function. My co-worker gets the email and
the attachment displays as "Base64" on screen. Inside the email, the
Content-Type for the attachment is "application/msword" and
Content-Transfer-Encoding is "7bit" which is incorrect for the following
base64 encoded attachment. Has anyone else seen this before and what did you
do about it?

 

[Vanguard]

I have a co-worker who gets an email from another company that also uses
Exchange. What happens is that the MIME type for one attachment is
incorrect. I believe the sender is composing in Word then uses the "Send
To:
Mail Recipient (As Attachment)" function. My co-worker gets the email and
the attachment displays as "Base64" on screen. Inside the email, the
Content-Type for the attachment is "application/msword" and
Content-Transfer-Encoding is "7bit" which is incorrect for the following
base64 encoded attachment. Has anyone else seen this before and what did
you
do about it?

Why would your sender bother using Base64 encoding in the first place? This
is something the sending user is doing with their own instance of Outlook.
Exchange isn't doing this. I didn't know that Outlook could do Base64
(unless that is the same as UUencode, so tell the sender to disable the
UUencode option for attachments).