Improvement suggestion for TNEF files

Denis Beauchemin Denis.Beauchemin at USHERBROOKE.CA
Fri Oct 28 14:33:16 IST 2005

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

Hello all,

I sometimes get "Corrupt TNEF winmail.dat that cannot be analysed" using 
the internal TNEF decoder.  I have seen others have problems with it 
lately and switching to the external decoder.

If MS was modified to try both decoders if and only if the first one 
can't parse the TNEF file, would it be interesting for people?

The settings could be changed to something like:
TNEF Expander = internal external   (or any combination of these 2)
External TNEF Expander = /usr/bin/tnef --maxsize=100000000

I would like to use "internal external" because the internal one is 
faster but I would like to fall back to the external one if there was a 
problem with the expansion of the winmail.dat file.


  °v°   Denis Beauchemin, analyste
 /(_)\  Université de Sherbrooke, S.T.I.
  ^ ^   T: 819.821.8000x2252 F: 819.821.8045

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at with the words:
'leave mailscanner' in the body of the email.
Before posting, read the Wiki ( and
the archives (

Support MailScanner development - buy the book off the website!

More information about the MailScanner mailing list