asked on

E-mail Body Becomes an Attachment for One of Two Recipients

We are using Exchange Server 2003 and all users have Outlook 2003 and Outlook Web Access. A client addresses an html format e-mail to two of our users. For one user, the body of the e-mail is normal. For the other user, the body of the e-mail is an attachment whose name matches the subject line of the e-mail. It's not a .dat attachment. If I try to save the attachment it, it defaults to type "message file." I looked at the headers of the e-mail in both users' mailboxes and noticed where one has "Content-Type: text/plain;" the other that is making the attachment has "Content-Type: message/rfc822." I don't know if that's of any significance.

I haven't been able to find a setting between the two user accounts that might cause this condition. Any ideas will be greatly appreciated.

Ludovick Lagrevol

use html or text message instead of RTF with outlook

You can specify it on exchange server (ESM -> internet mail format -> never use RTF)

larubbo

ASKER

Does that impact inbound messages? The problem is with messages we're getting from other companies, not messages we're sending. I know the user in question sends messages in plain text format.

Vahik

maybe a detect and repair of outlook is inorder....

larubbo

ASKER

It happens in Outlook and OWA. I also tried opening her mailbox from a different computer with the same results, so would that indicate the problem doesn't lie with Outlook? The user is out today with her laptop, so I can't try doing a detect and repair just yet.

Vahik

well then the problem cant be outlook....and maybe profile related....so which profile??? outlook or user profile???u have to find out urself...
u can always try a detect and repair first it solves most outlook problems...

ASKER CERTIFIED SOLUTION

Sembee

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

larubbo

ASKER

The e-mails are coming from different people, but all of them are at the same company. I learned this morning that it's not just one user here that's having the problem. Apparently multiple users here have experienced this problem intermittently over the last month, but only one user reported it before today. All indications are that Simon is right; the problem must be on the sender's side. I've put the ball in the client's court for resolution.

Thanks for all your help. I'm not technically trained, but I'm the go-to person for this small office. Don't know what I'd do without EE as my first level go-to resource.