https://bugs.exim.org/show_bug.cgi?id=2477
Jeremy Harris <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|bug |wishlist --- Comment #1 from Jeremy Harris <[email protected]> --- You don't get a msg:host:defer because this case of a post-data defer is not classed as a host-specific problem but a problem with the message. That classification is arguable - there could be some temporary issue on one MX host of the set such as a filesystem full, only detected after data starts - but we still blame the message. We don't attempt to parse error code to tell the difference. It'd be reasonable, and fit the current code structure, to create a new event type "msg:defer" for this. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
