How to avoid delivering winmail.dat

  • Thread starter Thread starter P.Ravialahan
  • Start date Start date
P

P.Ravialahan

I'm using Ms "outlook" as client programm, "Ms Exchange 2000 + Ex2kSP3
on Windows 2000 + SP4" mail server connectivity "outlook-Exchange"

Earlier Used the same method with out any service pack installed to
Exchange. Now formatted the system and reinstalled with the
configurations mentioned above.
Also using trend micro Scanmail program.

Only difference from earlier configuration is Ex2kSP3 and also
introduced "Relay Restrictions" to unauthenticated client.

Previously there was no any complains about winmail.dat or any
such. now with the new configurations as mentioned above only getting
complains about "mail attachments are comming in a format of
winmail.datand so on". Here as i enquired about their mail client all
mentions that they are using Eudora or Lotus notes (Other than outlook
or Outlook Express).

Any how as person(myself) responsible for server administration and
client computers, what kind of measures can be taken form my end
Pls help me to get this hell out of the way..

Thanks in advance
Ravi
 
P.Ravialahan said:
I'm using Ms "outlook" as client programm, "Ms Exchange 2000 + Ex2kSP3
on Windows 2000 + SP4" mail server connectivity "outlook-Exchange"

Earlier Used the same method with out any service pack installed to
Exchange. Now formatted the system and reinstalled with the
configurations mentioned above.
Also using trend micro Scanmail program.

Only difference from earlier configuration is Ex2kSP3 and also
introduced "Relay Restrictions" to unauthenticated client.

Previously there was no any complains about winmail.dat or any
such. now with the new configurations as mentioned above only getting
complains about "mail attachments are comming in a format of
winmail.datand so on". Here as i enquired about their mail client all
mentions that they are using Eudora or Lotus notes (Other than outlook
or Outlook Express).

Any how as person(myself) responsible for server administration and
client computers, what kind of measures can be taken form my end
Pls help me to get this hell out of the way..

Thanks in advance
Ravi
Click to expand...

Are you sending mail as "Rich text format" in Outlook when folks are
getting winmail.dat? If so, switch to anything but Rich text. Plain text,
HTML, etc. shouldn't give this problem to your recipients.

Craig
 
I've tried those diffrent file formats(HTMl & plain text) aslo nothing
happened. they are still complaining the same way.

Ravi
 
P.Ravialahan said:
I've tried those diffrent file formats(HTMl & plain text) aslo nothing
happened. they are still complaining the same way.

Ravi
Click to expand...

Dont use Microsoft Outlook, use Thunderbird or Mozilla or Netscape 7,
then you wouldnt have the problem
 
As per my experience & testing-out with the system, it seems to be the
problem comes from ExchangeSP3 + "Outlook Corporate workgroup"
combination.

"Because earlier, without Ex2kSP3 their was no any such issues"
 
I have the same problem, however, I only seem to experience this problem on a
exchange server that is configured as an expansion server. On all my
exchange servers I have installed KB870540 which is a post SP3 patch. Try
that, I'm sure that will help.
 
Back
Top