https://bugs.exim.org/show_bug.cgi?id=1630
Wolfgang Breyha <wbreyha@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #811 is|0 |1
obsolete| |
--- Comment #3 from Wolfgang Breyha <wbreyha@???> ---
Created attachment 819
-->
https://bugs.exim.org/attachment.cgi?id=819&action=edit
removed usage of user_message again
This is the same patch as before fixing the SEGV, but I removed usage of
user_message again since I'm uncertain in which circumstances it is set. At
least it has no error code and the caller has to submit one in case "426" is
inappropriate (eg. Status: 5.0.0).
The event which initially caused the SEGV had no user_message set and I found
no other example which does. If the rare situation occurs there is a Remote-MTA
field without Diagnostic-Code which is not allowed by RFC 1891. Maybe it's
better to set a addr->message in this case instead of user_message fallback.
Most likely this happens for deferrals caused by DNS tempfails (eg. DANE
lookups).
--
You are receiving this mail because:
You are on the CC list for the bug.
