https://bugs.exim.org/show_bug.cgi?id=2747
--- Comment #9 from Nico Rittner <[email protected]> --- hi heiko, i did some testing this afternoon and could figure out, that the segfault does not happen when the connection is ipv6, respectively pretends to be (via the -bh switch). swaks -f [email protected] -t [email protected] --pipe 'exim -bh ${HOST} -C /root/exim.conf'; fails with "*** Child process closed connection unexpectedly" and exit code 6, when ${HOST} is an ipv4 address. when redirecting stderr of the --pipe argument to a file "Segmentation fault" appears as the last line immeditaly after expanding \N^some_regex$\N. if ${HOST} is ipv6 - ::1 or the current link-local address, swaks can successfully finish smtp and exits with 0 "=== Connection closed with child process". the behaviour when doing real smtp is similar: msmtp -d --host=${HOST} [email protected] --port 25 --tls-starttls=off --tls=off [email protected] </dev/null; leads to segfault when the connection is ipv4. remote and locally. for testing purposes i told exim to listen on 127.0.0.1 only. same results with ipv4-addresses. in case it matters: ipv6 is not used in our environment/setup here. i attached the test-configfile i used and some debug output (ipv4,ipv6,swaks,msmtp) with meaningful filenames. nico -- 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/ ##
