BadTNEF

[Denis Beauchemin]

Le mer 03/12/2003 à 10:24, Julian Field a écrit :
> Not really worth the effort any more. TNEF is now (thankfully) a rare 
> sight, since Microsoft learnt the error of their ways and started using 
> HTML instead.

Maybe some day they will be rare, but I get an average of 175 "Corrupt
TNEF" messages per day using the external decoder (this includes
weekends where they drop near zero).

I think I will try the internal one to see if it can do better.

Denis
> 
> At 14:54 03/12/2003, you wrote:
> >Le mer 03/12/2003 à 09:33, Julian Field a écrit :
> >
> > > 3) The "tnef" program really couldn't decode the winmail.dat attachment in
> > > the message
> > > 4) You might be better off setting the location of the "tnef" program to
> > > "internal" so that MailScanner uses the internal Perl module which is
> > > slower but often better at decoding TNEF attachments (winmail.dat).
> >
> >Julian,
> >
> >Could MS be modified to use both tnef decoders if need be?
> >
> >Let's say the first decoder cannot analyze the winmail.dat file, then MS
> >fires off the second one to try to do better.
> >
> >We could write something like:
> >External TNEF Expander = /usr/bin/tnef --maxsize=100000000
> >TNEF Expander = external internal
> >
> >Denis
> >--
> >Denis Beauchemin, analyste
> >Université de Sherbrooke, S.T.I.
> >T: 819.821.8000x2252 F: 819.821.8045
-- 
Denis Beauchemin, analyste
Université de Sherbrooke, S.T.I.
T: 819.821.8000x2252 F: 819.821.8045