586964 - Attachments not included when forwarding an email

Status: RESOLVED DUPLICATE of bug 548507

(Thunderbird :: General, defect)

Description

[David]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6

I can't say if it is happening for all types of attachments, but when I try to forward an email with a .pdf attachment, the attachment is not included on the new message.

Reproducible: Always

Steps to Reproduce:
1.set the focus on the email (click the email)
2.click the forward button (that appears at the top of the email)
3.when new message is opened for edit/update/send, the attachment is missing.
Actual Results:  
You will send the message body but not the attachment.

Expected Results:  
the attachment should have been included in the new message.

I can't think of anything else to describe what is happening.. I know that I have been able to forward attachments in the past (with earlier versions of Thunderbird) but for some reason this version won't do it.

Comment 1

[David]

BTW: I updated my Thunderbird to version: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2

The problem is still present.

Comment 2

[[:Aureliano Buendía]]

David, please, can you check in message source code (select the message and then click CTRL+U) if Content-Transfer-Encoding is base64 (search "Content-Transfer-Encoding: base64")?
In this case this issue is (at least) dupe of bug #548507.

In alternative, please, attach here an email that has this issue.

Comment 3

[David]

Yes, the base coding is 64...:

Content-Type: application/pdf; name=31298612_8884082_NEW.pdf
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=31298612_8884082_NEW.pdf

so perhaps it is a duplicate... do you have an estimate for when this bug might be fixed?

Comment 4

[Ludovic Hirlimann [:Usul]]

(In reply to comment #3)

> so perhaps it is a duplicate... do you have an estimate for when this bug might
> be fixed?

No