Mailing List Archive

https://bugs.exim.org/show_bug.cgi?id=2747

Heiko Schlittermann <hs@schlittermann.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |hs@schlittermann.de

--- Comment #1 from Heiko Schlittermann <hs@schlittermann.de> ---
Hi Rico,
i've set up a plain Debian11 and installed the default exim4-daemon-light
package.
And I used the minimalistic configuration file you provided.

Unfortunately I can't reproduce the SegFault. Are you aware of any other
related things that can differ between your system and the above mentioned
system I'm running locally?

Can you run your Exim with the debug symbols enabled and produce a stack
backtrace?

--
Heiko

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #2 from Andreas Metzler <eximusers@bebt.de> ---
(In reply to Nico Rittner from comment #0)
[...]
> tested with version 4.94.2 of debian "bullseye"
[...]

That would be 4.94.2-1?

Could you doublecheck with 4.94.2-2 (or the just uploaded 4.94.2-3)

Gentoo's package seems to be almost vanilla 4.94.2, except for
localscan-dlopen.
cu Andreas

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #3 from Heiko Schlittermann <hs@schlittermann.de> ---
http://ftp.debian.org/debian/dists/bullseye/main/binary-amd64/ is still at
4.94.2-1

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #4 from Nico Rittner <nrittner@layer23.de> ---
hi Heiko,

(In reply to Heiko Schlittermann from comment #1)

> i've set up a plain Debian11 and installed the default exim4-daemon-light

Sorry, i forgot to mention that i used exim4-daemon-heavy for comparison,
because on gentoo we make use of external db-lookups, and the "heavy" package
in debian comes more close to the feature-set that we use in gentoo.

> things that can differ between your system and the above mentioned system I'm running locally?

I also installed exim on top of plain debian11, ~3 hours ago via netinstall.
then executed "exim -bd -d+all" and tried to send email with msmtp from a
remote machine.

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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #5 from Nico Rittner <nrittner@layer23.de> ---
(In reply to Andreas Metzler from comment #2)

> Could you doublecheck with 4.94.2-2 (or the just uploaded 4.94.2-3)

i will try 4.94.2-2 as soon as possible.
at the moment i am unable to locate 4.94.2-3 anywhere.

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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #6 from Heiko Schlittermann <hs@schlittermann.de> ---
Even with exim4-daemon-heavy (4.94.2-1) and the configuration you provided I
can't reproduce it.

Can you please attach the test config you used to this ticket? The config line
numbers differ between my and your debug output.

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #7 from Heiko Schlittermann <hs@schlittermann.de> ---
And an additional question: can you reproduce it using swaks:

swaks -f mailbox@example.org -t mailbox@example.org --pipe 'exim -bh
192.168.178.9'

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

Heiko Schlittermann <hs@schlittermann.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|unallocated@exim.org |hs@schlittermann.de

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #8 from Nico Rittner <nrittner@layer23.de> ---
Created attachment 1387
--> https://bugs.exim.org/attachment.cgi?id=1387&action=edit
Exim Test-ConfigFile and some Debug-Output

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #9 from Nico Rittner <nrittner@layer23.de> ---
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 mailbox@example.org -t mailbox@example.org --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} --from=mailbox@example.org --port 25 --tls-starttls=off
--tls=off mailbox@example.org </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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

--- Comment #10 from Heiko Schlittermann <hs@schlittermann.de> ---
Bingo! I can reproduce it now. Additional condition to make it segfaulting is:
the sender host IP must have an associated sender host name.

I can work with that now. Thank you for providing the additional logs and
information.

--
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/ ##

https://bugs.exim.org/show_bug.cgi?id=2747

Heiko Schlittermann <hs@schlittermann.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED

--- Comment #11 from Heiko Schlittermann <hs@schlittermann.de> ---
- fixed on exim-4.94.2+fixes: 20812729e3e47a193a21d326ecd036d67a8b2724
- merged into exim-4.94.2+taintwarn
- cherry-picked onto master: d4bc023436e4cce7c23c5f8bb5199e178b4cc743

--
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/ ##