[exim-dev] [Bug 138] Use shared memory segment for queue list
https://bugs.exim.org/show_bug.cgi?id=138 --- Comment #8 from Jeremy Harris --- Fast queue ramp is now supported by default. -- You are receiving this mail because: You are the QA Contact for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2922] exim using random ipv6 for sending outbound mail
https://bugs.exim.org/show_bug.cgi?id=2922 Jeremy Harris changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from Jeremy Harris --- Since it's working as designed, closing. -- 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 2890] autoreply driver: return_path option not working for that driver
https://bugs.exim.org/show_bug.cgi?id=2890 Jeremy Harris changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Jeremy Harris --- A local count would not be sufficient; a loop of more than one system is possible. Automated bounces should hae a null sender. The standard say so, for good reason. Closing as will-not-fix. -- 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 2980] exiqgrep -i broken
https://bugs.exim.org/show_bug.cgi?id=2980 --- Comment #1 from Jeremy Harris --- I'm not sure why you'd want to have no selector option as a usable function? Using "-i" in combination with a selector would not be affected by the proposed change. -- 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 2890] autoreply driver: return_path option not working for that driver
https://bugs.exim.org/show_bug.cgi?id=2890 --- Comment #3 from Arkadiusz Miskiewicz --- It's not a bounce but regular message, just autogenerated, using autoreply exim driver functionality. Standards AFAIK say nothing about sender for such message. So your claim seems wrong. And preventing loops is possible with hash added to the message or any other solution. Keep exim a swiss knife and don't impose artificial limits based on wrong assumptions. -- 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 452] Request variable(s) to show which item has matched in a list
https://bugs.exim.org/show_bug.cgi?id=452 Jeremy Harris changed: What|Removed |Added Assignee|unalloca...@exim.org|jgh146...@wizmail.org Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Jeremy Harris --- >From 4.95 :- $host_data, $local_part_data, $domain_data, $sender_data or $recipient_data are filled in. See docs Ch. 10 Sec. 5. -- You are receiving this mail because: You are the QA Contact for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
[exim-dev] [Bug 2980] exiqgrep -i broken
https://bugs.exim.org/show_bug.cgi?id=2980 --- Comment #2 from Douglas Phillips --- -i by itself is useful in processing the output from another command which was piped in (for example exim -bp) or if one needed to purge the entire queue (e.g., if a PHP had been abused or there was a runaway process). -- 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/ ##
