VM

Bug #732943
Comment #22

Comment 22 for bug 732943

Revision history for this message

John Hein (xpqheqdvq4) wrote on 2011-04-26:

#22

Uday Reddy wrote in comment 21:
> The rationale is two-fold. If people make mistakes in the forwarded
> headers, the MIME might be broken and the recipients won't be able to
> process the encapsulated message. Secondly, there is no harm in sending all
> the headers because the recipients are expected to process the
> MIME-encapsulated message and use their own formatting to view the headers.

re: "no harm in sending all the headers". Often I don't want to forward on all the headers because I don't want to expose internal header information. My only recourse now (for encapsulated message/rfc822 forwarding) is to edit the message before forwarding which is klunky (and a [tiny] step backward in vm functionality).

So I think there are two different independent behavior knobs for forwarding that we're talking about:
(1) inline vs. mime encapsulated attachment
(2) all or partial headers

The combination I would probably never use: inline + full headers.
The next combinations in order of what would be used most (for me):

- mime + partial (most of the time)

- mime + all (for the occasional circumstance where I specifically want to include all the header noise)

- inline + partial (rarely)

Having mime + all be the default is fine. Often people don't forward me enough (typically outlook users that only show names and not email addresses in forwarded messages), so if mime + all is the default, that's okay with me. But keeping a way to easily do mime + partial (like 'z' has done for a long time now) would be much appreciated.

inline forwarding is new for vm. I'll take a moment here to lobby for _not_ making it the default (even for a forward of a single message). Reading "threaded" followup conversations in outlook style (top post on top of 20 messages that have already been sent) is difficult and people never prune content. If you're going to forward email conversations, a mime digest is the better way to go (especially for recipients who use a decent mail reader that get help show proper threading - like vm!) - yes, vm still does the digest when forwarding multiple messages, but I'd like to see mime be the default for a single message as well. Discouraging that kind of top-post forwarding makes the world a better place ;) Plus, it's more consistent with what vm has been doing for the last ('z' => mime, not inline) decade+.

Uday Reddy wrote in comment 21:                                                            
 > The rationale is two-fold.  If people make mistakes in the forwarded
 > headers, the MIME might be broken and the recipients won't be able to
 > process the encapsulated message.  Secondly, there is no harm in sending all
 > the headers because the recipients are expected to process the
 > MIME-encapsulated message and use their own formatting to view the headers.

re: "no harm in sending all the headers".  Often I don't want to forward on all the headers because I don't want to expose internal header information.  My only recourse now (for encapsulated message/rfc822 forwarding) is to edit the message before forwarding which is klunky (and a [tiny] step backward in vm functionality).

So I think there are two different independent behavior knobs for forwarding that we're talking about:
 (1) inline vs. mime encapsulated attachment
 (2) all or partial headers

The combination I would probably never use: inline + full headers.
The next combinations in order of what would be used most (for me):

- mime + partial (most of the time)

- mime + all        (for the occasional circumstance where I specifically want to include all the header noise)

- inline + partial (rarely)

Having mime + all be the default is fine.  Often people don't forward me enough (typically outlook users that only show names and not email addresses in forwarded messages), so if mime + all is the default, that's okay with me.  But keeping a way to easily do mime + partial (like 'z' has done for a long time now) would be much appreciated.

inline forwarding is new for vm.  I'll take a moment here to lobby for _not_ making it the default (even for a forward of a single message).  Reading "threaded" followup conversations in outlook style (top post on top of 20 messages that have already been sent) is difficult and people never prune content.  If you're going to forward email conversations, a mime digest is the better way to go (especially for recipients who use a decent mail reader that get help show proper threading - like vm!) - yes, vm still does the digest when forwarding multiple messages, but I'd like to see mime be the default for a single message as well.  Discouraging that kind of top-post forwarding makes the world a better place ;)  Plus, it's more consistent with what vm has been doing for the last ('z' => mime, not inline) decade+.