Exchange Server Forums

Outlook 2003 with server-side rules

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Message Routing >> Outlook 2003 with server-side rules

Page: [1]

Message

<< Older Topic Newer Topic >>

Outlook 2003 with server-side rules - 8.Feb.2008 1:39:37 PM

Blacktoe

Posts: 10
Joined: 12.Apr.2007
Status: offline

We are having issues where users set up autoreply rules in their mailboxes and the recipients receiving winmail.dat files for the body of the message. I have my Remote Domain set to never use richtext. This was working before we upgraded to SP1. Has anyone else seen this?

Post #: 1

Featured Links*

RE: Outlook 2003 with server-side rules - 12.Feb.2008 10:20:46 AM

dssbreilly

Posts: 31
Joined: 12.Feb.2008
Status: offline

If a recipient in a remote domain receives a file attachment named Winmail.dat in their e-mail, that remote domain is incompatible with Exchange RTF. To work around this issue, you can configure the remote domain to never use Exchange RTF. Select one of the Exchange RTF options in the following list:

Always use Select this option to always send messages that use Exchange rich-text format.
Never use Select this option to never send messages that use Exchange rich-text format.
Determined by individual user settings By default, this option is selected and the Exchange rich-text settings that are used to send e-mail messages are specified by the Outlook user.

The RTF settings also control whether Transport Neutral Encapsulation Format (TNEF) encoding is used for a message. In the Exchange Management Shell, you use the TNEFEnabled parameter with the Set-RemoteDomain cmdlet to configure these settings. TNEF is used to encode MAPI message properties for transmission through a message system that does not support those properties directly.
A TNEF-encoded message contains a plain text version of the message, and a binary attachment that packages parts of the message. The binary attachment may include special Outlook features, such as voting buttons, meeting requests, and custom forms. Some message features require TNEF encoding for the message to be received correctly by recipients in a mail system, such as Exchange Server version 5.5. When a message that contains TNEF information is received by a mail client that does not understand TNEF, there are three common results:

The plain text version of the message is received and contains an attachment named Winmail.dat. The Winmail.dat attachment does not contain any useful information when it is opened because it is in the TNEF format.
The plain text version of the message is received and contains an attachment that has a generic name, such as ATT00008.att or ATT00005.eml. In this case, the client is unable to recognize the TNEF part of the message. Therefore, it creates a file to hold the TNEF information.
The plain text version of the message is received, and the e-mail client ignores the Winmail.dat attachment.

If you frequently send meeting requests to Exchange Server 5.5 recipients, you must set the value of the TNEFEnabled parameter to $true for that domain so that those messages are received as meeting requests. Exchange 2007 sends meeting requests to the Internet in the iCalendar standard for calendar items. However, that format is not supported by Exchange Server 5.5. If you configure the message format settings to always use TNEF, the meeting requests are sent using TNEF instead.

(in reply to Blacktoe)

Post #: 2

RE: Outlook 2003 with server-side rules - 13.Feb.2008 9:21:41 AM

Blacktoe

Posts: 10
Joined: 12.Apr.2007
Status: offline

In my first posting, I had already set the remote domain to "never use" richtext. If I send out an email from outlook it works correctly with no winmail.dat file. If I have the server-side autoreply enabled then the message is sent with a winmail.dat for the body of the responding message. This was working before SP1 was installed on my Exchange 2007 server. This looks like an issue that will have to be escalated to PSS. I'll post my findings.

(in reply to Blacktoe)

Post #: 3

RE: Outlook 2003 with server-side rules - 25.Feb.2008 4:13:22 PM

Blacktoe

Posts: 10
Joined: 12.Apr.2007
Status: offline

Microsoft has confirmed that this is a bug within SP1 and administrators using disclaimers. They said that this is fixed within Update Rollup 1 for Exchange 2007 SP1. No release date was given.

(in reply to Blacktoe)

Post #: 4

RE: Outlook 2003 with server-side rules - 7.Mar.2008 4:56:34 PM

asn1bur

Posts: 1
Joined: 7.Mar.2008
Status: offline

I am having the exact same problem, very frustrating. I have just applied SP 1 Rollup 1 and it doesn't appear to have fixed the problem, have you had any luck resolving this?

(in reply to Blacktoe)

Post #: 5

RE: Outlook 2003 with server-side rules - 12.Mar.2008 3:23:02 PM

Blacktoe

Posts: 10
Joined: 12.Apr.2007
Status: offline

We have yet to receive an approved date to apply Update Rollup 1 for EX 2007 SP1. We will probably be installing this some time next month. Until then....

(in reply to Blacktoe)

Post #: 6