627795 - Message Filter Trashing Attachments multipart/mixed; and base64 attachments

Status: RESOLVED DUPLICATE of bug 570914

(MailNews Core :: MIME, defect)

Description

[Geoff]

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0b9) Gecko/20100101 Firefox/4.0b9
Build Identifier: 3.1.7

I have a problem with a message filter that started at about TB 3.1. The filter forwards selected messages with attachments to several email addresses. When run automatically it trashes the attachments. When run manually it's fine. The filter has been running successfully for several years until recently.

The attachments are bad at the sending end. They can be seen to be bad in the Sent folder on the sending end. They are also bad at the receiving end. I've observed it with both .doc and .pdf documents. The message about a bad file comes from Word and Adobe Reader when the attachments are opened. The filenames of the attachments do not get corrupted.

I've confirmed that the problem exists in TB on both Windows XP and OSX and that the problem doesn't occur with an equivalent filter in another email client (OSX Mail)

Reproducible: Always

Comment 1

[Ludovic Hirlimann [:Usul]]

can you provide us with a email that will get messed up when forwarded ?

Does running Thunderbird in -safe-mode (see http://support.mozillamessaging.com/en-US/kb/Safe+Mode) helps with the attachment ?

Also in your outbox/sent folders are the forwarded emails ok ?

Comment 2

[Geoff]

Thanks for responding Ludovic,

I tested safe mode as you suggest and it doesn't help.

The forward as it exists in the sent box is always mangled. What is mangled is the attachments, not the message itself. I'm not sure how to send an example to you because of this. I'll try forwarding to you at [e-mail].  Attachments are Word files and pdfs.

Note that this only happens when the filter runs in automatic mode.  When I execute the filter manually it does not happen.

Note that it happens with TB in Windows XP as well as OSX.

Geoff

Comment 3

[Ludovic Hirlimann [:Usul]]

Mail structure is as follow :


Content-type: multipart/mixed; boundary="Boundary_(ID_lNc/F88PKuTWNStE97ufEQ)"

--Boundary_(ID_lNc/F88PKuTWNStE97ufEQ)
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT

--Boundary_(ID_lNc/F88PKuTWNStE97ufEQ)
Content-type: application/msword; name=K110216.doc
Content-transfer-encoding: base64
Content-disposition: attachment; filename=K110216.doc

--Boundary_(ID_lNc/F88PKuTWNStE97ufEQ)
Content-type: application/pdf; name=K110216.pdf
Content-transfer-encoding: base64
Content-disposition: attachment; filename=K110216.pdf

--Boundary_(ID_lNc/F88PKuTWNStE97ufEQ)
Content-type: application/pdf; name=m110216.pdf
Content-transfer-encoding: base64
Content-disposition: attachment; filename=m110216.pdf

--Boundary_(ID_lNc/F88PKuTWNStE97ufEQ)
Content-type: text/x-vcard; charset=utf-8; name=mike_sowko.vcf
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=mike_sowko.vcf

--Boundary_(ID_lNc/F88PKuTWNStE97ufEQ)--

Comment 4

[Gary]

I too have the same problem, again only with a message forwarded by a filter - forwarding manually is OK.  The reason the file is corrupt is because the attachment is replaced with the following example text (taken from the source text on the receiving pc)

--------------080505010401080100020802
Content-Type: application/msword;
 name="SEN report to GOVS may 11.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="SEN report to GOVS may 11.doc"

Thisbodypartwillbedownloadedondemand
--------------080505010401080100020802--

The phrase 'Thisbodypartwillbedownloadedondemand' must be inserted by Thunderbird as the attachment in the original email is fine, and the copy in the Sent folder is corrupted in the same way.  It would seem the message filter is forwarding the email before the attachment has been downloaded? This always happens with all attachment types and is giving me real problems with emails forwarded from my work account.

Comment 5

[Gary]

Further searching shows this to be Bug 570914

Comment 6

[Gary]

(In reply to comment #5)
> Further searching shows this to be Bug 570914

sorry, meant to say 'similar to'

Comment 7

[Ludovic Hirlimann [:Usul]]

(In reply to comment #6)
> (In reply to comment #5)
> > Further searching shows this to be Bug 570914
> 
> sorry, meant to say 'similar to'

Indeed.