TNEF playing up again

[Julian Field]

I would just set the Exchange servers to use HTML for rich text messages
and not TNEF. Microsoft have now pretty much deprecated TNEF as even they
finally realised it was a dead duck.

As an alternative, try using the "internal" TNEF expander.

At 13:59 06/04/2004, you wrote:
>Hi,
>
>We have had some strange problems regarding TNEF. People get messages
>back their TNEF message was partly not forwarded and they should choose
>plain text. Some admins have done that and tested it again. It seems
>TNEF goes wrong if the message is send to one particular subdomain under
>utwente.nl. All other domains (in- or outside) utwente.nl don't go
>wrong. It started when the sending department started using Exchange
>2003.
>
>I am further investigating what could be wrong. Which is a lot thinking
>about the migration to Exchange 2003 and AD going in different
>departments in different ways.
>
>--
>Peter Peters, senior netwerkbeheerder
>Dienst Informatietechnologie, Bibliotheek en Educatie (ITBE)
>Universiteit Twente,  Postbus 217,  7500 AE  Enschede
>telefoon: 053 - 489 2301, fax: 053 - 489 2383, http://www.utwente.nl/civ

--
Julian Field
www.MailScanner.info
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654