Your message dated Sat, 27 Apr 2024 15:04:56 -0400
with message-id <9318737.iVoKAc1ZZ4@zini-1880>
and subject line Re: Bug#1069957: postfix: false syslog_name (misinfo) in the
logs
has caused the Debian Bug report #1069957,
regarding postfix: false syslog_name (misinfo) in the logs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1069957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 3.7.10-0+deb12u1
Severity: normal
Tags: upstream
X-Debbugs-Cc: debbug.post...@sideload.33mail.com
When an smtp command failed to send an outbound message, Postfix
neglected to correctly log the syslog_name as specified by this
option:
-o syslog_name=postfix/smtptor
The logs are shown in bug report 1069949¹. This severely crippled
troubleshooting efforts because it misleads testers about what
actually executed. Notice in the logs of that bug report that a
well-behaved smtp program correctly yielded the “postfix/smtptor”
string.
In the failure scenario, the string “postfix/smtp” was logged, falsely
implying that the wrapper script was never called, yet it actually
logged output from the wrapper script. This resulting deception led
the bug chase down the wrong path.
I suspect whatever code applies the custom syslog_name is running
sequentially late and an initialised default value of “postfix/smtp”
is used as a placeholder.
A low-effort fix would be to change that initialisation to something
that’s at least non-misleading, such as:
* “postfix/TBD”
* “postfix/smtpAppTBD”
* “postfix/UNKNOWN”
* “postfix/UNSET”
* “postfix/UNSETsmtp”
* “postfix/DEADBEEF”
* “postfix/ifYouSeeThis,TellWietse”
* “postfix/thisWillNeverHappen”
* “postfix/youFoundAbug”
Any of those as an initialisation default would at least avoid
misinformation.
Going the extra mile would be fixing whatever caused the logger to act
before the custom syslog_name took effect.
¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069949
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990,
'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-28-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages postfix depends on:
ii adduser 3.134
ii cpio 2.13+dfsg-7.1
ii debconf [debconf-2.0] 1.5.82
ii dpkg 1.21.22
ii e2fsprogs 1.47.0-2
ii init-system-helpers 1.65.2
ii libc6 2.36-9+deb12u6
ii libdb5.3 5.3.28+dfsg2-1
ii libicu72 72.1-3
ii libnsl2 1.3.0-2
ii libsasl2-2 2.1.28+dfsg-10
ii libssl3 3.0.11-1~deb12u2
ii netbase 6.4
ii ssl-cert 1.1.2
Versions of packages postfix recommends:
ii ca-certificates 20230311
ii python3 3.11.2-1+b1
Versions of packages postfix suggests:
ii emacs-gtk [mail-reader] 1:28.2+1-15
ii libsasl2-modules 2.1.28+dfsg-10
ii mailutils [mail-reader] 1:3.15-4
ii neomutt [mail-reader] 20220429+dfsg1-4.1
pn postfix-cdb <none>
ii postfix-doc 3.7.10-0+deb12u1
pn postfix-ldap <none>
pn postfix-lmdb <none>
pn postfix-mta-sts-resolver <none>
pn postfix-mysql <none>
ii postfix-pcre 3.7.10-0+deb12u1
pn postfix-pgsql <none>
pn postfix-sqlite <none>
ii procmail 3.22-27
ii systemd-resolved [resolvconf] 252.22-1~deb12u1
ii ufw 0.36.2-1
-- Configuration Files:
/etc/postfix/post-install changed [not included]
/etc/postfix/postfix-files changed [not included]
/etc/postfix/postfix-script [Errno 2] No such file or directory:
'/etc/postfix/postfix-script'
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Saturday, April 27, 2024 10:49:02 AM EDT Manny wrote:
> Package: postfix
> Version: 3.7.10-0+deb12u1
> Severity: normal
> Tags: upstream
> X-Debbugs-Cc: debbug.post...@sideload.33mail.com
>
> When an smtp command failed to send an outbound message, Postfix
> neglected to correctly log the syslog_name as specified by this
> option:
>
> -o syslog_name=postfix/smtptor
>
> The logs are shown in bug report 1069949¹. This severely crippled
> troubleshooting efforts because it misleads testers about what
> actually executed. Notice in the logs of that bug report that a
> well-behaved smtp program correctly yielded the “postfix/smtptor”
> string.
>
> In the failure scenario, the string “postfix/smtp” was logged, falsely
> implying that the wrapper script was never called, yet it actually
> logged output from the wrapper script. This resulting deception led
> the bug chase down the wrong path.
>
> I suspect whatever code applies the custom syslog_name is running
> sequentially late and an initialised default value of “postfix/smtp”
> is used as a placeholder.
>
> A low-effort fix would be to change that initialisation to something
> that’s at least non-misleading, such as:
>
> * “postfix/TBD”
> * “postfix/smtpAppTBD”
> * “postfix/UNKNOWN”
> * “postfix/UNSET”
> * “postfix/UNSETsmtp”
> * “postfix/DEADBEEF”
> * “postfix/ifYouSeeThis,TellWietse”
> * “postfix/thisWillNeverHappen”
> * “postfix/youFoundAbug”
>
> Any of those as an initialisation default would at least avoid
> misinformation.
>
> Going the extra mile would be fixing whatever caused the logger to act
> before the custom syslog_name took effect.
>
> ¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069949
This isn't something we should deviate from upstream on, so I think you should
address this with them on postfix-users. I suspect that there isn't a bug here
and it's like a system setup issue. Nothing for Debian to do, so closing.
Scott K
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
