<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=FR-CA link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Hi guys,<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'> </span><span lang=EN-CA style='color:#1F497D'>I may have « found » the problem but I’m not sure :<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>2013-03-20T16:28:26.021724+00:00 mailserver MailScanner[11855]: Corrupt TNEF winmail.dat that cannot be analysed in message 4E5601ED1.AD737<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>2013-03-20T16:30:00.824823+00:00 mailserver MailScanner[12178]: Expanding TNEF archive at /var/spool/MailScanner/incoming/12178/D07311ED1.A0ADA/winmail.dat<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>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<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>2013-03-20T16:30:00.826566+00:00 mailserver MailScanner[12178]: Corrupt TNEF winmail.dat that cannot be analysed in message D07311ED1.A0ADA<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>I hacked the code a bit and seems like we’re in /var/spool/postfix/hold instead of /var/spool/MailScanner/incoming/ !<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>If that’s the case, perhaps the patch will be easily done?<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Dave<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR-CA'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR-CA'> David Hill <br><b>Sent:</b> March-20-13 12:24 PM<br><b>To:</b> 'mailscanner@lists.mailscanner.info'<br><b>Subject:</b> TNEF external expander vs internal<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi guys,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> <span lang=EN-CA>We’ve upgraded from mailscanner 4.71.10-1 to 4.84.5-3 and we’re running into an issue.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>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<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>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.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>So, just to leave a trace, external is broken, internal works well.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Thank you very much,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Dave<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p></div></body></html>