winmail.dat problem all of a sudden

Martin Hepworth maxsec at
Sat Oct 8 17:39:59 IST 2011

tried the internal expander instead

winmail.dt should be killed off now !
Martin Hepworth
Oxford, UK

On 8 October 2011 14:58, Michael Masse <mrm at> wrote:

> Running MS 4.84.3 on latest Centos 5.   All of sudden I'm getting a bunch
> of incoming messages being quarantined due to: "Could not parse Outlook Rich
> Text attachment"    The TNEF setting for unparable TNEF is set to deliver,
> yet it is not doing so.    This is a new problem that just started within
> the last two weeks.   One oddity I'm noticing is that in the quarantine I
> can usually see the offending attachment sitting there extracted next to the
> df and qf files.    In all of these winmail.dat cases, the winmail.dat is
> not sitting there next to the df and qf files so I can't even manually run
> them against the tnef extractor to see if it's truly a problem with tnef not
> being able to extract the files, or if it's a problem with MailScanner not
> being to extract the attachment from the email.  The fact that there is no
> winmail.dat attachment in the quarantine leads me to believe the latter.
> Any help would be greatly appreciated.   The following are what I believe
> are my relevant MailScanner.conf config lines that have to do with TNEF:
> Expand TNEF = yes
> Use TNEF Contents = replace
> Deliver Unparsable TNEF = yes
> TNEF Expander = /usr/bin/tnef --maxsize=100000000
> TNEF Timeout = 120
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.**info <mailscanner at>
> Before posting, read**posting<>
> Support MailScanner development - buy the book off the website!
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the MailScanner mailing list