Re: Possible issue when user has single space as comment
On Monday, January 3, 2022 10:24:07 AM EST Wietse Venema wrote: > Scott Kitterman: > > I have been remiss in forwarding this bug report, thinking I would get > > time to build a concise test case. It keeps not happening, so here you > > go. > > > > A Debian user reported [1] a problem where their cleanup process was > > killed by signal 11 during local mail injection: > > > > Aug 06 16:57:30 amilcar postfix/pickup[11470]: warning: > > maildrop/88D7A333A: error writing 7082252D6: queue file write error > > Aug 06 16:57:30 amilcar postfix/master[6205]: warning: process > > /usr/lib/postfix/sbin/cleanup pid 18641 killed by signal 11 > > > > We did the usual is it apparmor dance. They did provide a trace [2]. > > After some work they discovered that the users associated with all the > > failures had a passwd comment set to a single space, e.g.[3]: > > > > username:x:1234:1234: :/home/username:/bin/bash > > > > This was using Postfix 3.4.14. > > > > Any suggestions? > > This was FIXED IN JULY 2021 with: > > postfix-3.3.19 > postfix-3.4.22 > postfix-3.5.12 > postfix-3.6.2 > > Do we have a process problem? > > Wietse > > 20210705 > > Bugfix (introduced: Postfix 3.3): "null pointer read" error > in the cleanup daemon when "header_from_format = standard" > (the default as of Postfix 3.3) and email was submitted > with /usr/sbin/sendmail without From: header, and an all-space > full name was specified in 1) the password file, 2) with > "sendmail -F", or 3) with the NAME environment variable. > Found by Renaud Metrich. File: cleanup/cleanup_message.c. Thanks. We (meaning me) had a problem where I ended up getting distracted from Debian for almost a year and no one picked up on postifx stuff while I was gone. I'm working on catching up, both on updating stable releases and on bug triage. Maybe I picked the wrong order ... Scott K
Re: Possible issue when user has single space as comment
Scott Kitterman: > I have been remiss in forwarding this bug report, thinking I would get time > to > build a concise test case. It keeps not happening, so here you go. > > A Debian user reported [1] a problem where their cleanup process was killed > by > signal 11 during local mail injection: > > Aug 06 16:57:30 amilcar postfix/pickup[11470]: warning: > maildrop/88D7A333A: error writing 7082252D6: queue file write error > Aug 06 16:57:30 amilcar postfix/master[6205]: warning: process > /usr/lib/postfix/sbin/cleanup pid 18641 killed by signal 11 > > We did the usual is it apparmor dance. They did provide a trace [2]. After > some work they discovered that the users associated with all the failures had > a passwd comment set to a single space, e.g.[3]: > > username:x:1234:1234: :/home/username:/bin/bash > > This was using Postfix 3.4.14. > > Any suggestions? This was FIXED IN JULY 2021 with: postfix-3.3.19 postfix-3.4.22 postfix-3.5.12 postfix-3.6.2 Do we have a process problem? Wietse 20210705 Bugfix (introduced: Postfix 3.3): "null pointer read" error in the cleanup daemon when "header_from_format = standard" (the default as of Postfix 3.3) and email was submitted with /usr/sbin/sendmail without From: header, and an all-space full name was specified in 1) the password file, 2) with "sendmail -F", or 3) with the NAME environment variable. Found by Renaud Metrich. File: cleanup/cleanup_message.c.
Possible issue when user has single space as comment
I have been remiss in forwarding this bug report, thinking I would get time to build a concise test case. It keeps not happening, so here you go. A Debian user reported [1] a problem where their cleanup process was killed by signal 11 during local mail injection: Aug 06 16:57:30 amilcar postfix/pickup[11470]: warning: maildrop/88D7A333A: error writing 7082252D6: queue file write error Aug 06 16:57:30 amilcar postfix/master[6205]: warning: process /usr/lib/postfix/sbin/cleanup pid 18641 killed by signal 11 We did the usual is it apparmor dance. They did provide a trace [2]. After some work they discovered that the users associated with all the failures had a passwd comment set to a single space, e.g.[3]: username:x:1234:1234: :/home/username:/bin/bash This was using Postfix 3.4.14. Any suggestions? Scott K [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968057 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi? att=1;bug=968057;filename=cleanup.strace.out;msg=5 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968057#29
