Re: [Mailman-Users] Missing confirmation requests and held messages
Hi Mark and et al, I apologize for not explaining myself very well before. The collaboration that I work for has had MailMan lists for over 10 years, and we've recently run into a problem with our lists. I've read through the install directions and have even googled the problem; without any results. The problem we're having looks like this. When we have messages held for moderator approval, when there approved the message disappears and doesn't get delivered to the list. The things we've already look at are: the mailman cron job, owned my mailman is in place and functioning. The options for not allowing html/MIME content is disabled. This problem happens all the time, and I can reproduce it consistently. I'm wondering if there's anything else we've missed, doesn't anyone have an idea? Thanks Much, Gregory On Sat, 1 Aug 2009, Mark Sapiro wrote: Gregory Skelton wrote: I'm kinda new to the administrating mailman lists, and I've recently run into a problem with our current setup. We have multiple list, all the data is mounted over nfs, and we're seeing missing emails. For instance, we've had some users try to subscribe to a list but don't get a confirmation email, other times we're seeing held messages no show up in the qeue for the administrator to authorize them. This is starting to become a real problem for our scientific colaboration, and I need to get it fixed soon. Is this a new problem, or just newly discovered? If it is a new problem, what changed? We're running mailman 2.1.9, and sendmail sendmail-8.13.8-2 on a Centos 5.2 system. Does anyone have any idea what might be the problem? It's almost impossible to even guess based on only the above. I've ran check_perms script, and it gave me this output: Warning: Private archive directory is other-executable (o+x). This could allow other users on your system to read private archives. If you're on a shared multiuser system, you should consult the installation manual on how to fix this. No problems found This is completely normal. And running check_db -a -v I noticed most of mailing list are ok, but found a few list that have this problem. List: lalsuite-commits /var/mailman/lists/lalsuite-commits/config.pck: okay /var/mailman/lists/lalsuite-commits/config.pck.last: okay [Errno 2] No such file or directory: '/var/mailman/lists/lalsuite-commits/config.db' [Errno 2] No such file or directory: '/var/mailman/lists/lalsuite-commits/config.db.last' This is normal too. The lists that don't have config.db and config.db.last files were created under Mailman 2.1.x. Those that do have them were migrated from 2.0.x. In fact it is a good idea to remove the config.db and config.db.last files from the lists that have them. Otherwise, if the config.pck and config.pck.last files ever get corrupted, Mailman could fall back to the config.db or config.db.last and then you'd wind up with a years-old configuration and membership list. -- Gregory R. Skelton Phone: (414)229-2678 (Office) System Administrator: (920) 246-4415 (Cell) 1900 E. Kenwood Blvd: gskel...@gravity.phys.uwm.edu University of Wisconsin : AIM/ICQ gregor159 Milwaukee, WI 53201 http://www.lsc-group.phys.uwm.edu/~gskelton Emergency Email: grego...@vzw.blackberry.net -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman and group mismatch error
Mark wrote: Greg wrote: # ls -lhZ /etc/aliases* -rw-r--r-- root root system_u:object_r:etc_aliases_t /etc/aliases -rw-r--r-- root root system_u:object_r:etc_aliases_t /etc/aliases.db # ls -lhZ /etc/mailman/aliases* -rw-rw root mailman user_u:object_r:mailman_data_t /etc/mailman/aliases -rw-rw-r-- mailman mailman user_u:object_r:mailman_data_t /etc/mailman/aliases.db This looks good. The key thing is that Mailman's aliases.db is owned by mailman. snip So do I have everything configured right?? Do I have to recompile mailman? If so it looks like I have to recompile starting with ./configure --with-mail-gid=root The above looks good. what is the exact group mismatch error message you get in the DSN and/or maillog when you mail to t...@list.xyz.com? To send the test message I sshd into my box as user, su - to root, and did: # /usr/lib/mailman/mail/mailman post test Group mismatch error. Mailman expected the mail wrapper script to be executed as one of the following groups: [mail, postfix, mailman, nobody, daemon], but the system's mail server executed the mail script as group: root. Try tweaking the mail server to run the script as one of these groups: [mail, postfix, mailman, nobody, daemon], or re-run configure providing the command line option: '--with-mail-gid=root'. I then use mutt (still as root) to send an email and this is what I see in /var/log/maillog Aug 1 13:21:44 list postfix/postfix-script: starting the Postfix mail system Aug 1 13:21:44 list postfix/master[2494]: daemon started -- version 2.3.3, configuration /etc/postfix Aug 1 13:22:23 list Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as one of the following groups: [mail, postfix, mailman, nobody, daemon], but the system's mail server executed the mail script as group: root. Try tweaking the mail server to run the script as one of these groups: [mail, postfix, mailman, nobody, daemon], or re-run configure providing the command line option: '--with-mail-gid=root'. Aug 1 13:25:01 list postfix/pickup[2498]: C122C8604E0: uid=41 from= Aug 1 13:25:01 list postfix/cleanup[2767]: C122C8604E0: message-id= Aug 1 13:25:01 list postfix/qmgr[2499]: C122C8604E0: from=, size=625, nrcpt=1 (queue active) Aug 1 13:25:02 list postfix/local[2769]: C122C8604E0: to=, orig_to=, relay=local, delay=0.51, delays=0.25/0.05/0/0.21, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post mailman) Aug 1 13:25:02 list postfix/qmgr[2499]: C122C8604E0: removed Aug 1 13:25:04 list postfix/smtpd[2771]: connect from localhost.localdomain[127.0.0.1] Aug 1 13:25:04 list postfix/smtpd[2771]: 792BE8604DD: client=localhost.localdomain[127.0.0.1] Aug 1 13:25:04 list postfix/cleanup[2767]: 792BE8604DD: message-id= Aug 1 13:25:04 list postfix/qmgr[2499]: 792BE8604DD: from=, size=1952, nrcpt=1 (queue active) Aug 1 13:25:04 list postfix/smtpd[2771]: disconnect from localhost.localdomain[127.0.0.1] Aug 1 13:25:04 list postfix/local[2769]: 792BE8604DD: to=, relay=local, delay=0.07, delays=0.01/0/0/0.06, dsn=2.0.0, status=sent (delivered to maildir) Aug 1 13:25:04 list postfix/qmgr[2499]: 792BE8604DD: removed Aug 1 13:26:19 list postfix/pickup[2498]: C49B88604E0: uid=0 from= Aug 1 13:26:19 list postfix/cleanup[2767]: C49B88604E0: message-id= Aug 1 13:26:19 list postfix/qmgr[2499]: C49B88604E0: from=, size=418, nrcpt=1 (queue active) Aug 1 13:26:20 list postfix/local[2769]: C49B88604E0: to=, relay=local, delay=0.28, delays=0.1/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post test) Aug 1 13:26:20 list postfix/qmgr[2499]: C49B88604E0: removed Finally I exit root and go back to being a user and I do: /usr/lib/mailman/mail/mailman post test Group mismatch error. Mailman expected the mail wrapper script to be executed as one of the following groups: [mail, postfix, mailman, nobody, daemon], but the system's mail server executed the mail script as group: user. Try tweaking the mail server to run the script as one of these groups: [mail, postfix, mailman, nobody, daemon], or re-run configure providing the command line option: '--with-mail-gid=user'. Thanks, Greg _ Get free photo software from Windows Live http://www.windowslive.com/online/photos?ocid=PID23393::T:WLMTAGL:ON:WL:en-US:SI_PH_software:082009 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] mailman user password
Hello, I'm still trying to fix a problem I've had for a long time (started after an update) where mailman won't start from the standard init script. I think I have finally figured out what the problem is, but wanted to ask... Is the mailman user supposed to be passwordless? I know I'm running a non vanilla version, but my question is mostly generic I think... Currently, the init script contains: su - mailman -c '/bin/mailmanctl -s start' /dev/null 21 When I do this from a non-root account: myu...@myhost ~ $ su - mailman -c '/bin/mailmanctl -s start' /dev/null 21 I see this in the log: myhost su[6114]: pam_unix(su:auth): authentication failure; logname=myuser uid=1001 euid=0 tty=pts/2 ruser=myuser rhost= user=mailman myhost su[6114]: pam_authenticate: Authentication failure myhost su[6114]: FAILED su for mailman by myuser myhost su[6114]: - pts/2 myuser:mailman My problem is I don't know how this works/is supposed to work. Is mailmans passwd supposed to be empty/blank? That seems like a bad idea, but if not, how is it supposed to start without giving the password for the mailman account somehow? It starts fine if I start it from the command line as root, so it has to be something to do with the init script and/or permissions (the password for the mailman account)... Thanks for any comments/thoughts... -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman and group mismatch error
On 1-Aug-2009, at 12:43, Greg White wrote: To send the test message I sshd into my box as user, su - to root, and did: # /usr/lib/mailman/mail/mailman post test Group mismatch error. Mailman expected the mail wrapper script to be executed as one of the following groups: [mail, postfix, mailman, nobody, daemon], but the system's mail server executed the mail script as group: root. Try tweaking the mail server to run the script as one of these groups: [mail, postfix, mailman, nobody, daemon], or re-run configure providing the command line option: '--with-mail-gid=root'. Right. The error message is quite clear. Why do you think running the command as root WOULD work? try su mailman ( or sudo -u mailman ) and then run the command. I then use mutt (still as root) to send an email and this is what I see in /var/log/maillog Sent an email to what, exactly? the list? Aug 1 13:21:44 list postfix/postfix-script: starting the Postfix mail system Aug 1 13:21:44 list postfix/master[2494]: daemon started -- version 2.3.3, configuration /etc/postfix Aug 1 13:22:23 list Mailman mail-wrapper: Group mismatch error. Mailman expected the mail wrapper script to be executed as one of the following groups: [mail, postfix, mailman, nobody, daemon], but the system's mail server executed the mail script as group: root. Try tweaking the mail server to run the script as one of these groups: [mail, postfix, mailman, nobody, daemon], or re-run configure providing the command line option: '--with-mail-gid=root'. This looks like test attempt above. Aug 1 13:25:02 list postfix/local[2769]: C122C8604E0: to=, orig_to=, relay=local, delay=0.51, delays=0.25/0.05/0/0.21, dsn=2.0.0, status=sent (delivered to command: /usr/lib/mailman/mail/ mailman post mailman) That worked. Mailman is configured correctly. Finally I exit root and go back to being a user and I do: /usr/lib/mailman/mail/mailman post test And why do you think that would work? Again, the error message is quite clear. What is the problem? It looks to me like everything is working properly. -- Do not meddle in the affairs of Dragons for you are crunchy and taste good with ketchup -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Detecting Autoresponders
Adam McGreggor writes: As others have said, if an autoresponder is responding repeatedly to the same address in the course of a few days it is certainly behaving badly. Lotus Notes and Exchange autoresponders should not be allowed near the Internet. I'd rewrite that last part to: Lotus Notes and poorly-setup Microsoft Exchange installations should not be allowed near the Internet. I'm not sure that's acceptable. People might be tempted to think that MCSE + CCNA qualify one to do better than poorly set up a mail server. :-/ approach is. (I don't always see those messages: through filtering, I attempt to ditch 'out of office' type messages.) My butt has been saved (from Usenet-style flaming, not corporate-style firing) on a number of occasions by the practice of making my personal filter a subset of the rules used on my lists. I realize for various reasons that's not always feasible, but it's a good rule of thumb to start with. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] mailman user password
tansta...@libertytrek.org writes: Is the mailman user supposed to be passwordless? AFAIK there is no need to log in as the mailman user, so that user should have no password (in the sense of disabled, not in the sense of zero-length string). When I do this from a non-root account: myu...@myhost ~ $ su - mailman -c '/bin/mailmanctl -s start' /dev/null 21 [it doesn't work as expected] My problem is I don't know how this works/is supposed to work. It's not supposed to work. mailman privileges should only be accessible by the system administrator, ie, someone who has the root password. It starts fine if I start it from the command line as root, That's how you're supposed to do it, if you need to do it. so it has to be something to do with the init script and/or permissions (the password for the mailman account)... It's not a problem with the password for the mailman user. :-) The init script itself may be broken. AFAIK, the init script should be invoking the set-gid binary called mailman or wrapper. This just cleans up the environment, changes the effective user id to mailman, and execs the command specified. (There's no good reason for *any* mailman program to be on anybody's PATH, so yes, just having /bin/mailmanctl makes your installation nonstandard.) The best thing to do at this point is to run the check_perms script provided with mailman. It usually resides in $prefix/lib/mailman/bin, but since your installation is non-standard, you may have to search a bit. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mailman user password
tansta...@libertytrek.org wrote: Is the mailman user supposed to be passwordless? It doesn't matter. It's up to you and your own policy. I know I'm running a non vanilla version, but my question is mostly generic I think... Currently, the init script contains: su - mailman -c '/bin/mailmanctl -s start' /dev/null 21 This is the real issue. mailmanctl should always be run by root. Your init script should just contain /bin/mailmanctl -s start /dev/null 21 without the su - mailman When I do this from a non-root account: myu...@myhost ~ $ su - mailman -c '/bin/mailmanctl -s start' /dev/null 21 I see this in the log: myhost su[6114]: pam_unix(su:auth): authentication failure; logname=myuser uid=1001 euid=0 tty=pts/2 ruser=myuser rhost= user=mailman myhost su[6114]: pam_authenticate: Authentication failure myhost su[6114]: FAILED su for mailman by myuser myhost su[6114]: - pts/2 myuser:mailman My problem is I don't know how this works/is supposed to work. Is mailmans passwd supposed to be empty/blank? That seems like a bad idea, but if not, how is it supposed to start without giving the password for the mailman account somehow? You're supposed to start it as root. Unprivileged users aren't supposed to be able to start, stop, restart Mailman. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Disable attachment scrubbing?
If you mean include an arbitrary binary attachment (say an executable file) displayed inline in the archived message rather that removed and replaced by a link, then no, there is no way to do that. If you mean replace the attachment with a link that preserves the original attachment file name and extension, put the following in mm_cfg.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True That is precisely what I was looking for, thank you very much. The root cause of the problem was - People are starting to use docx and xlsx files by default now, and these mime types aren't recognized (at least in the version of mailman that I have.) So they get renamed attachment.bin and that's a problem for non-technical users. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Disable attachment scrubbing?
Edward Harvey quoted me and wrote: If you mean replace the attachment with a link that preserves the original attachment file name and extension, put the following in mm_cfg.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True That is precisely what I was looking for, thank you very much. The root cause of the problem was - People are starting to use docx and xlsx files by default now, and these mime types aren't recognized (at least in the version of mailman that I have.) So they get renamed attachment.bin and that's a problem for non-technical users. Actually, it's not mailman that doesn't recognize the MIME type. Mailman (Scrubber) calls the Python library mimetypes.guess_all_extensions() to 'guess' the extension for the MIME type. This in turn, at least with Python 2.3 and newer, looks in the following list of system files for mappings from MIME type to extension. knownfiles = [ /etc/mime.types, /etc/httpd/mime.types,# Mac OS X /etc/httpd/conf/mime.types, # Apache /etc/apache/mime.types, # Apache 1 /etc/apache2/mime.types, # Apache 2 /usr/local/etc/httpd/conf/mime.types, /usr/local/lib/netscape/mime.types, /usr/local/etc/httpd/conf/mime.types, # Apache 1.2 /usr/local/etc/mime.types,# Apache 1.3 ] -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] set up mailman, but no email notification
I finally got mailman working to the point I created 'mailman' list successfully. Everything has worked correctly, but despite it showing that mailman has sent a notice to the administrator email account, that email has never made it into my email inbox. What would cause that email not to correctly send out the message? Scott -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
