https://bugs.exim.org/show_bug.cgi?id=1877
Bug ID: 1877
Summary: partially broken bounce_message_file and
warn_message_file functionality
Product: Exim
Version: 4.86
Hardware: x86-64
OS: FreeBSD
Status: NEW
Severity: bug
Priority: medium
Component: Delivery in general
Assignee: nigel@???
Reporter: amal@???
CC: exim-dev@???
Created attachment 918
-->
https://bugs.exim.org/attachment.cgi?id=918&action=edit
To get back the ability of control the kind of bounce/warning generation -
simple patch for 4.87
Hello.
Since 4.86 we see in ChangeLog:
JH/08 The EXPERIMENTAL_DSN compile option is no longer needed; all Delivery
Status Notification (bounce) messages are now MIME format per RFC 3464.
Support for RFC 3461 DSN options NOTIFY,ENVID,RET,ORCPT can be advertised
under the control of the dsn_advertise_hosts option, and routers may
have a dsn_lasthop option.
This code merging partially broke old-time bounce_message_file and
warn_message_file functionality.
As we can see in a spec,
* The fourth, fifth and sixth items will be ignored and may be empty. The
fields exist for back-compatibility.
It disables possibility of defining MIME-sections manually using
bounce_message_file template, for example, for changing encoding of
bounce/warning message or add/delete some sections (satisfying RFC3464).
I propose to get back the ability of control the kind of bounce/warning
generation (f.e. using compile option) - fully manual or (semi-)autimatically.
Attaching the simple patch for 4.87.
Thank you.
--
You are receiving this mail because:
You are on the CC list for the bug.
