FS#28675 - [mailman] Executed as wrong group error
Attached to Project:
Arch Linux
Opened by Sebastian Köhler (kart0ffelsack) - Monday, 27 February 2012, 09:46 GMT
Last edited by Pierre Schmitz (Pierre) - Monday, 27 February 2012, 11:16 GMT
Opened by Sebastian Köhler (kart0ffelsack) - Monday, 27 February 2012, 09:46 GMT
Last edited by Pierre Schmitz (Pierre) - Monday, 27 February 2012, 11:16 GMT
|
Details
Description:
Ok I posted this in the Forum but was asked to open a bug report. After I updated and restarted my server postfix can't give mails to mailman instead mailman throws this error: Command died with status 2: "/usr/lib/mailman/mail/mailman post admins". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "80", but the system's mail server executed the mail script as group "mailman". Try tweaking the mail server to run the script as group "80", or re-run configure, providing the command line option `--with-mail-gid=mailman'. But the mailman group has ID 80: grep mailman /etc/group mailman:x:80: and all the alias tables and transport maps from mailman are owned by the mailman group so postfix is running the wrapper script as the mailman group. ls -l /var/lib/mailman/data/ insgesamt 60 -rw-r----- 1 mailman mailman 41 6. Feb 2011 adm.pw -rw-rw---- 1 mailman mailman 1887 6. Feb 2011 aliases -rw-rw---- 1 mailman mailman 12288 26. Feb 16:31 aliases.db -rw-r----- 1 mailman mailman 41 6. Feb 2011 creator.pw -rw-rw---- 1 mailman mailman 6 27. Feb 09:05 master-qrunner.pid -rw-r--r-- 1 mailman mailman 14100 18. Feb 16:51 sitelist.cfg -rw-rw---- 1 mailman mailman 1184 6. Feb 2011 virtual-mailman -rw-rw---- 1 mailman mailman 12288 6. Feb 2011 virtual-mailman.db Additional info: * package version(s) 2.1.14-2 |
This task depends upon
Comment by Pierre Schmitz (Pierre) -
Monday, 27 February 2012, 10:38 GMT
So the latest version of mailman (2.1.14-4) did not fix this
issue?
Comment by
Sebastian Köhler (kart0ffelsack) -
Monday, 27 February 2012, 10:46 GMT
No. I get the same error with 2.1.14-3
Comment by Pierre Schmitz (Pierre) -
Monday, 27 February 2012, 10:54 GMT
Might be fixed now.
Comment by
Sebastian Köhler (kart0ffelsack) -
Monday, 27 February 2012, 11:10 GMT
Yes the last version did the trick :) Thank you