Closed
Bug 506015
Opened 17 years ago
Closed 16 years ago
Forward messages both inline and as attachment
Categories
(Thunderbird :: Preferences, enhancement)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: volkanorh, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729)
Build Identifier: 2.0.0.22 (20090605)
There are two choices for message forwarding, which are inline and as attachment. A third choice which is for both inline and as attachment would be excellent. In addition, make the third choice default since attached mail which has eml extension can't be viewed on web based e-mail clients, and inline forwarded mail is not the exact copy of the forwarded e-mail.
Reproducible: Always
Steps to Reproduce:
Feature request
| Reporter | ||
Updated•17 years ago
|
Hardware: x86_64 → All
| Reporter | ||
Updated•17 years ago
|
Version: unspecified → 2.0
This option was proposed in bug 230448 comment #23 by dmose himself and basically won't-fixed in the discussion there. Only a limited number of use cases actually require the message being forwarded "as is" with the original structure and headers intact (e.g., spam reporting). The overhead of forwarding a message in a way that replicates the message body up to four times doesn't seem to be justified, specifically as a default setting. There are ambiguities in sending attachments multiple times (as part of the forwarding message and the message attachment). Also, inheriting the issues associated with forwarding as attachment, servers may reject message attachments and block the entire e-mail in the worst case.
By the way, there is an easy workaround to accomplish the mode you desire on a per-message basis: Just forward inline, then drag-and-drop the message from the thread list to the attachment pane of the composition window to also attach it.
Comment 2•16 years ago
|
||
->WONTFIX, as per comment 1
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•