TNEF external expander vs internal

David Hill david.hill at
Wed Mar 20 16:34:58 GMT 2013

Hi guys,

                I may have < found > the problem but I'm not sure :

2013-03-20T16:28:26.021724+00:00 mailserver  MailScanner[11855]: Corrupt TNEF winmail.dat that cannot be analysed in message 4E5601ED1.AD737
2013-03-20T16:30:00.824823+00:00 mailserver MailScanner[12178]: Expanding TNEF archive at /var/spool/MailScanner/incoming/12178/D07311ED1.A0ADA/winmail.dat
2013-03-20T16:30:00.826306+00:00 mailserver MailScanner[12178]: Trying to unpack nwinmail.dat in message D07311ED1.A0ADA, could not create subdirectory D07311ED1.A0ADA//tnef6sGA3q, failed to unpack TNEF message - /var/spool/postfix/hold
2013-03-20T16:30:00.826566+00:00 mailserver MailScanner[12178]: Corrupt TNEF winmail.dat that cannot be analysed in message D07311ED1.A0ADA

I hacked the code a bit and seems like we're in /var/spool/postfix/hold instead of /var/spool/MailScanner/incoming/ !

If that's the case, perhaps the patch will be easily done?


From: David Hill
Sent: March-20-13 12:24 PM
To: 'mailscanner at'
Subject: TNEF external expander vs internal

Hi guys,

                We've upgraded from mailscanner 4.71.10-1 to 4.84.5-3 and we're running into an issue.
Some people said that TNEF external expander was broken, that they applied a patch and/or updated to tnef 1.4.9 but this doesn't
seem to solve our problem.     If we switch to internal, it's definitely solving the issue  but I think this is a hack for something that's broken.

So, just to leave a trace, external is broken, internal works well.

Thank you very much,


-------------- next part --------------
An HTML attachment was scrubbed...

More information about the MailScanner mailing list