Unable to expand TNEF files in Mailscanner (bug #607747)

Carlos Acedo <[email protected]>
Newsgroups gmane.linux.debian.user.isp
Message-ID <[email protected]>
Hi,

Since the upgrade to squeeze I'm unable to expand TNEF files (winmail.dat)
for examination, all the details are in this bug:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607747

<http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607747>In the second post
there is a patch which I have applied, but the problem persists, the bug
claims the problem is in the last slash (/) when creating a directory, but
you can actually create directories like foo//bar in perl with no problems.

Permissions seem right, perl mkdir function throws this error: "No such file
or directory"

The mkdir function tries to create a subdirectory, ie mkdir "foo//bar", but
foo doesn't exists, the problem is here, there is something messed up with
the directories.

Here is a log with some debug lines of my own:

Feb 21 11:59:12 mail MailScanner[9515]: Expanding TNEF archive at
/var/spool/MailScanner/incoming/9515/AC9DD4D4039.AC0D8/winmail.dat
Feb 21 11:59:12 mail MailScanner[9515]: DEBUG(winmail.dat): mkdir Error is :
No such file or directory
Feb 21 11:59:12 mail MailScanner[9515]: DEBUG(winmail.dat): mkdir
AC9DD4D4039.AC0D8//tnefT9COXB
Feb 21 11:59:12 mail MailScanner[9515]: DEBUG(winmail.dat): current
directory: /var/spool/MailScanner/incoming/9515/B34B74D4038.AE841
Feb 21 11:59:12 mail MailScanner[9515]: DEBUG(winmail.dat): current
directory: /var/spool/MailScanner/incoming/9515/B34B74D4038.AE841 EXISTS!!
Feb 21 11:59:12 mail MailScanner[9515]: Trying to unpack nwinmail.dat in
message AC9DD4D4039.AC0D8, could not create subdirectory
AC9DD4D4039.AC0D8//tnefT9COXB, failed to unpack TNEF message
Feb 21 11:59:12 mail MailScanner[9515]: Corrupt TNEF winmail.dat that cannot
be analysed in message AC9DD4D4039.AC0D8

This is a mail released from quarantine, I'm not sure if this could be
related.

Thank you in advance

-- 
Carlos.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.