[exim-dev] [Bug 2339] message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #5 from Jeremy Harris --- Nobody commented -- 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/ ##
[exim-dev] [Bug 2339] message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added Assignee|ni...@exim.org |jgh146...@wizmail.org Status|NEW |ASSIGNED --- Comment #4 from Jeremy Harris --- 049782c0de addresses. -- 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/ ##
[exim-dev] [Bug 2339] message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339 --- Comment #3 from Jeremy Harris --- Fix for consideration: https://bugs.exim.org/attachment.cgi?id=1164 -- 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/ ##
[exim-dev] [Bug 2339] message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added See Also||https://bugs.exim.org/show_ ||bug.cgi?id=219 -- 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/ ##
[exim-dev] [Bug 2339] message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added Severity|bug |wishlist --- Comment #2 from Jeremy Harris --- Given that a locally-generated Message-ID: header includes the $message_exim_id, which is already logged, you can search on the latter. I'm unconvinced of the utility of logging the extra (you'd get to see the results of setting the message_id_header_domain and message_id_header_text, I guess). To implement this would also affect the log of locally-submitted (commandline) mails. If done, it should be behind a log_selector, default disabled. -- 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/ ##
[exim-dev] [Bug 2339] message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339 Jeremy Harris changed: What|Removed |Added See Also||https://bugs.exim.org/show_ ||bug.cgi?id=1840 -- 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/ ##
[exim-dev] [Bug 2339] message-id not logged for own bounces
https://bugs.exim.org/show_bug.cgi?id=2339 --- Comment #1 from Arkadiusz Miskiewicz --- My use case was: trying to find out if bounce was delivered to remote system and the message was relayed via few servers. Much easier (check only destination server would be enough) to track by message-id than one by one server in the path when using exim queue id. -- 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/ ##