Join or sign in Register for your free TechRepublic membership or if you are already a member, sign in using your preferred method below. Use Your Email Use FacebookUse Linkedin

Exchange Attachment issue

Locked

I just implemented an Exchange 2003 server. I have upgraded my clients PC’s from Outlook 2000 to Outlook 2003. I have clients who now cannot send attachments to recipients who use Outlook Express.

The recipients are NOT on the Exchange server. They are internet reciepents. They were always able to send to this person prior to the cut over to Exchange/Outlook 2003.

Not all clients on the Exchange Server are having this problem. But the clients who have this problem so far are in a separate Exchange Storage group from the ones who do not seem to be having the problem.

Ideas…please? Going crazy over here. 🙂

Topic

Reply To: Exchange Attachment issue

In reply to Exchange Attachment issue

Is there a routing group connecting the new Exchange server to the server they are on?

Reply To: Exchange Attachment issue

In reply to Reply To: Exchange Attachment issue

Poster rated this answer.

Reply To: Exchange Attachment issue

In reply to Exchange Attachment issue

sporry just double checking-you have eliminated outlook express as possible culprit (due to attachement blocking) yes?
would u elaborate ‘cannot send attachments’ is there error in anybodys log or on screen. what exactly happens. can you reproduce at will from an affected client?

Reply To: Exchange Attachment issue

In reply to Reply To: Exchange Attachment issue

Poster rated this answer.

Reply To: Exchange Attachment issue

In reply to Exchange Attachment issue

The emails where attachments seem to be missing may be encoded using a microsoft proprietary format called TNEF. Only Outlook/Exchange clients can read this, not outlook express.
To check that this is the case, look at one of these emails in Outlook Express. Using right click, properties, message source to see the raw data. Scroll down through the message, and if there is a big block of base64 code, the attachment is there. If encoded as TNEF, the block will have the heading “Content-Type: application/ms-tnef;” and the attachment filename might be “Winmail.dat”.
To stop this happening, the email clients must be configured under options to send mail either in HTML or Plain text format, not RTF (Rich Text Format). A further complication can be the Exchange server address book list. I am unfamilliar with Exchange Server, but make sure every contact address and groups etc do not have any settings checked that may allow the server to recode the message using RTF.
Further info on http://support.microsoft.com/kb/138053/EN-US/

Reply To: Exchange Attachment issue

In reply to Reply To: Exchange Attachment issue

The resolve for this was Outlook 2003 – Office SP 1.

Reply To: Exchange Attachment issue

In reply to Exchange Attachment issue

This question was closed by the author

[Author]

Replies