https://bugs.exim.org/show_bug.cgi?id=2886
--- Comment #44 from Sergio Durigan Junior <[email protected]> --- (In reply to Gedalya from comment #43) > (In reply to Sergio Durigan Junior from comment #41) > > I'm following the steps outlined on comment #16 (assuming that Gedalya's > > server is still configured to defer the special email automatically), but I > > don't see the segfault. > > I'm not seeing your messages hitting my primary MX server (mail.gedalya.net) > which would be deferring. I do see two messages which hit mx2.gedalya.net, > apparently without going to the primary server first. > > exim would crash on a second attempt if it gets deferred on the first > attempt. > > Wild guess, are you running this in an IPv6-only container? mail.gedalya.net > is IPv4-only, sorry :-) Thanks for the help. I'm testing this using an Ubuntu Jammy container, which has exim4 4.95-4ubuntu2 and is not patched. There's in fact a downstream bug related to this problem; this is why I'm trying to come up with a reproducer. Thanks for also confirming that your server is still deferring emails. My container did have IPv6 enabled, so I completely disabled it just in case. Unfortunately, I'm still unable to reproduce the problem. Here's what I'm doing: - Launch container, disable IPv6 and also add "disable_ipv6" to exim4's config file. - Run "dpkg-reconfigure exim4-config" and make sure to configure the package as an "internet site; mail is sent and received directly using SMTP". Other than that, everything is left as is. - Run: # exim4 -odq -f [email protected] [email protected] < 1.msg # exim4 -bp 0m 333 1nxCYB-0000At-E1 <[email protected]> [email protected] # exim4 -d+all -q 1nxCYB-0000At-E1 2>&1 | tee /tmp/exim.debug I get the following output: https://dpaste.com//AVEDX2WT4 It seems strange that the second connectio (to mx2) didn't work either. I don't see a segmentation fault anywhere, although the email isn't being sent and keeps showing in "exim4 -bp". -- 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/ ##
