Msg forwarded as EML not viewable in Gmail [Content-Disposition: Attachment]

NEW
Unassigned

Status

Thunderbird
Message Compose Window
9 years ago
8 years ago

People

(Reporter: JoeS1, Unassigned)

Tracking

(Depends on: 1 bug)

Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
Forward any message as an attachment to a gmail user.

Since Gmail offers no way to view content if Content-disposition= Attachment the only choice of a Gmail user is to save it and open it with another program.

The problem is that "inline" has been the default "forever" and there is no way to change the disposition other than changing the pref in ConfigEditor.
pref("mail.content_disposition_type", 0);

Updated

9 years ago
OS: Windows XP → All
Hardware: PC → All

Comment 1

9 years ago
This would be somewhat difficult to cover by the "intuitive" mechanism suggested in bug 452092 (originally from bug 65794 comment #79 and earlier). However, if based on the message/rfc822, or in general on the fact that a message is forwarded, this could be covered by a MIMI-type look-up table. The problem is also caused in part by the Gmail web interface, which is unable to render message attachments with an actual attachment content disposition.

I'm wondering if there are any strong use cases for forwarding a message as a "true" attachment, rather than using the message body for an introductory message and then having an inline representation of the original message, intended to show with that introduction. In this case, an inline disposition for forwarding as attachment could be just hardwired.
(Reporter)

Comment 2

9 years ago
(In reply to comment #1)
> This would be somewhat difficult to cover by the "intuitive" mechanism
> suggested in bug 452092 (originally from bug 65794 comment #79 and earlier).
> However, if based on the message/rfc822, or in general on the fact that a
> message is forwarded, this could be covered by a MIMI-type look-up table. The
> problem is also caused in part by the Gmail web interface, which is unable to
> render message attachments with an actual attachment content disposition.

Certainly the fact that you are forwarding would seem to imply that you want the gmail recipient to be able to view the content. In gmails case that would have to be "inline"

> I'm wondering if there are any strong use cases for forwarding a message as a
> "true" attachment, rather than using the message body for an introductory
> message and then having an inline representation of the original message,
> intended to show with that introduction. In this case, an inline disposition
> for forwarding as attachment could be just hardwired.

I can't think of any, but I'm sure someone will. I think we must stay flexible to some degree on the issue.

Gmail seems to strictly respect the disposition, which led to some very strange results when I was toggling the pref. For instance for pref set=1 the disposition is set to attachment even for "inserted" images. If you then toggle and forward as an inline eml, the image shows inline, and also as a separate attachment.

Comment 3

9 years ago
The problem here is not with the Content-Disposition of the attachment.  Gmail have no support for Content-Type: message/rfc822. 

Until Gmail add this support, you will need to forward messages to Gmail users in-line.

Comment 4

9 years ago
OK. I see that they now support message/rfc822 when it has an inline disposition.  That did not work the last time I tried it.  

The downside is that you can no longer detach the full attached message, but it is displayed correctly, along with any nested attachments.

Comment 5

8 years ago
This is still a problem, reconfirmed per bug 312025 comment #90.
You need to log in before you can comment on or make changes to this bug.