Comment 20 for bug 732943

I'm not sure I understand exactly what you're asking.

'Z' (vm-forward-message-encapsulated) in the trunk (r1187) does what I want when I want all the headers.

'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.

I almost never want a plain-textified inline include as a forward. vm-forward-message-all-headers does this now (again, r1187). It _used to_ do the same thing vm-forward-message-encapsulated does now, if I recall correctly.

What I was thinking was that 'z' do the same it's always done (encapsulated mime message/rfc822 with selected headers). 'Z' could do the new inline include thing (normal outlook style forwarding) - some people might like to use that. Perhaps 'C-u z' could do message/rfc822 with "all headers".

Do I need it to be called "vm-forward-message-all-headers". No, I don't care about the name. But it's nice to have both the reduced headers and full headers forwarding as functional options.

Sorry if I wasn't sure what you were asking. I hope my longer explanation clarifies my thinking and explains my usage.