Ticket #183 <https://gitlab.com/muttmua/mutt/issues/183> notes that when piping a message with $pipe_decode set, mime headers such as content-type and content-transfer-encoding are passed through as-is.

This can confuse programs that look at those headers, since they are no longer correct.

I haven't dug through the twisty maze of _mutt_copy_message() flags very much. I do note that set_copy_flags() sets different flags than pipe_set_flags() for the decode case. Specifically (CH_MIME | CH_TXTPLAIN).

I'm wondering if anyone on the list can supply context for the difference between pipe decode and copy decode, before I experiment with adding those two flags for piping too.

Thank you!

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

Attachment: signature.asc
Description: PGP signature

Reply via email to