https://bugs.exim.org/show_bug.cgi?id=1686
--- Comment #10 from Jeremy Harris <jgh146exb@???> ---
Actually the Content-type: header appeared in 6c1c3d1dbe1a, for 4.82, while
adding DSN support per. RFC 3461.
An RFE for scanning the "headers" portion of bounce_message_file (etc) and
avoiding adding a second Content-type: header might be appropriate.
Implementation feels a bit painful, though.
--
You are receiving this mail because:
You are on the CC list for the bug.