Package: nullmailer Version: 1:2.2+10~g7ed88a0-5 Severity: important Control: found -1 1:2.2-3
Dear David, I managed to reproducibly crash nullmailer-smtpd with a "general protection fault" by calling the following command: swaks -t a...@debian.org --pipe 'sendmail -bs' This call produces the following output first: === Trying pipe to sendmail -bs... === Connected to sendmail -bs. <- 220 nullmailer-smtpd ready -> EHLO kote1.lugs.ch <- 250 2.3.0 OK -> MAIL FROM:<r...@kote1.lugs.ch> <- 250 2.1.0 Sender accepted -> RCPT TO:<a...@debian.org> <- 250 2.1.5 Recipient accepted -> DATA <- 354 End your message with a period on a line by itself -> Date: Mon, 10 Jun 2024 13:21:49 +0200 -> To: a...@debian.org -> From: r...@kote1.lugs.ch -> Subject: test Mon, 10 Jun 2024 13:21:49 +0200 -> Message-Id: <20240610132149.015...@kote1.lugs.ch> -> X-Mailer: swaks v20240103.0 jetmore.org/john/code/swaks/ -> -> This is a test mailing -> -> -> . *** Child process closed connection unexpectedly. In /var/log/syslog I then find these log entries: 2024-06-10T13:21:49.468475+02:00 kote1 nullmailer: Trigger pulled. 2024-06-10T13:21:49.468687+02:00 kote1 nullmailer: Rescanning queue. 2024-06-10T13:21:49.468781+02:00 kote1 nullmailer: Starting delivery, 1 message(s) in queue. 2024-06-10T13:21:49.468793+02:00 kote1 nullmailer: Starting delivery: host: … protocol: smtp file: 1718018509.15060 2024-06-10T13:21:49.468802+02:00 kote1 nullmailer: From: <r...@kote1.lugs.ch> to: <a...@debian.org> 2024-06-10T13:21:49.468808+02:00 kote1 nullmailer: Message-Id: <20240610132149.015...@kote1.lugs.ch> 2024-06-10T13:21:49.471688+02:00 kote1 kernel: traps: nullmailer-smtp[15059] general protection fault ip:7f0368d73dd9 sp:7fff5e3d7088 error:0 in libc.so.6[7f0368c41000+157000] 2024-06-10T13:21:49.600127+02:00 kote1 nullmailer: smtp: Succeeded: 250 2.6.0 <20240610132149.015...@kote1.lugs.ch> [InternalId=172490181574991, Hostname=…] 1171 bytes in 0.106, 10.754 KB/sec Queued mail for delivery 2024-06-10T13:21:49.601067+02:00 kote1 nullmailer: Sent file. 2024-06-10T13:21:49.601118+02:00 kote1 nullmailer: Delivery complete, 0 message(s) remain. The mail though seemed to end up in the queue. But since swaks exits with non-zero due to "sendmail -bs" exits with non-zero, our Ansible playbook fails, too. I initially ran into this on a production host running Debian 11 Bullseye with different settings (hence marking as found in the version in Bullseye), but I can still reproduce it on a test VM with Debian Unstable where I installed nullmailer temporarily as well. (Bug report resembles state on the latter.) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages nullmailer depends on: ii debconf [debconf-2.0] 1.5.86 ii libc6 2.38-12.1 ii libgnutls30t64 3.8.5-4 ii libstdc++6 14.1.0-1 nullmailer recommends no packages. nullmailer suggests no packages. -- debconf information: * shared/mailname: kote1.lugs.ch * nullmailer/relayhost: * nullmailer/adminaddr: a...@deuxchevaux.org nullmailer/defaultdomain: lugs.ch
