> 'z' _used to_ encapsulate the forwarded message as message/rfc822, but
> not with all headers - just some "interesting" ones (as defined by the
> vm-forwarded-headers list).
>
> I would say that 80% of the time I want the latter behavior. 20% of the
> time the former. Maybe 90/10.
Ok, I see that I changed this in revision 971, in October 2010. Since then,
MIME-encapsulated forwarding, irrespective which key-binding is used, has
been forwarding all headers.
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.
So, if you use MIME-forwarding, you don't need
vm-forward-message-all-headers. You get all the headers in the normal
forward.
John Hein writes:
> 'z' _used to_ encapsulate the forwarded message as message/rfc822, but headers list).
> not with all headers - just some "interesting" ones (as defined by the
> vm-forwarded-
>
> I would say that 80% of the time I want the latter behavior. 20% of the
> time the former. Maybe 90/10.
Ok, I see that I changed this in revision 971, in October 2010. Since then,
MIME-encapsulated forwarding, irrespective which key-binding is used, has
been forwarding all headers.
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.
So, if you use MIME-forwarding, you don't need message- all-headers. You get all the headers in the normal
vm-forward-
forward.
Cheers,
Uday