Mailman 3 March 2007 - Mailman-Users

Nested groups problems
by Chris Rogers March 1, 2007

March 1, 2007

Have anyone had problems with nesting email groups in Mailman? The reason I am using nested groups is that I work in a very transient community where we have about 10 email lists and on occasion we need to send a message to all those lists. About every third email sent to an all-users(a)somewhere.com crashes my server. There are not messages in any of the server logs to help diagnose the problem. Any suggestions would be welcome. Chris

2 1

No mail and no posts from mailman
by Bob McClure Jr March 1, 2007

March 1, 2007

I am befuddled. mailman-2.1.8-0.FC4.1 (from RPM) Fedora Core 4 (kept up to date with nightly yum) postfix-2.2.2-2 (from RPM) This is an established list server that has had one functioning list (albeit very low volume, so I can't swear that it is still working). I added a new list, put myself and one other person as the administrator, set it to send notifications of new subscribers, and subscribed both of us to the list. Then I sent two test emails to the list, but they seem to have gone into a black hole. My workstation mail server sent them: Feb 26 18:07:33 bobcat postfix/smtp[1119]: 5B3EF42C8: to=<foobarlist(a)lists.bobcatos.com>, relay=bubba.bobcatos.com[192.168.3.2], delay=0, status=sent (250 Ok: queued as AC98C2057) Feb 26 22:08:54 bobcat postfix/smtp[11974]: DFFA742C8: to=<foobarlist(a)lists.bobcatos.com>, relay=bubba.bobcatos.com[192.168.3.2], delay=1, status=sent (250 Ok: queued as 429CA2056) My list server got it: Feb 26 18:07:41 bubba postfix/local[17421]: AC98C2057: to=<foobarlist(a)lists.bobcatos.com>, relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post foobarlist) Feb 26 22:09:03 bubba postfix/local[20514]: 429CA2056: to=<foobarlist(a)lists.bobcatos.com>, relay=local, delay=1, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post foobarlist) But nothing came out. Nothing held for moderation. Nothing in the /var/log/mailman/* logs about them. Nothing in the archives. Following FAQ 3.14: 0) Did it. 1) # ps auxww| grep mailmanctl |grep -v grep mailman 7087 0.0 0.3 13048 1672 ? Ss 2006 0:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start # ps auxww | egrep 'p[y]thon' mailman 7087 0.0 0.3 13048 1672 ? Ss 2006 0:00 /usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start mailman 7097 0.0 0.5 12912 2508 ? S 2006 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s 2) My /etc/mailman/aliases contains (among other things) # STANZA START: foobarlist # CREATED: Sat Feb 24 18:33:52 2007 foobarlist: "|/usr/lib/mailman/mail/mailman post foobarlist" foobarlist-admin: "|/usr/lib/mailman/mail/mailman admin foobarlist" foobarlist-bounces: "|/usr/lib/mailman/mail/mailman bounces foobarlist" foobarlist-confirm: "|/usr/lib/mailman/mail/mailman confirm foobarlist" foobarlist-join: "|/usr/lib/mailman/mail/mailman join foobarlist" foobarlist-leave: "|/usr/lib/mailman/mail/mailman leave foobarlist" foobarlist-owner: "|/usr/lib/mailman/mail/mailman owner foobarlist" foobarlist-request: "|/usr/lib/mailman/mail/mailman request foobarlist" foobarlist-subscribe: "|/usr/lib/mailman/mail/mailman subscribe foobarlist" foobarlist-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe foobarlist" # STANZA END: foobarlist And the aliases.db file was updated. But then we knew that from the maillog entries. Also, my postfix main.cf contains alias_maps = hash:/etc/postfix/aliases, hash:/etc/mailman/aliases But then we knew that from the maillog entries, too. 3) Smrsh (not applicable) 4) Interface: This is a full-bore company mail server and has serviced the other list just fine, not to mention Squirrelmail and several daemons and cron jobs that send mail. 5) qrunner: Mailman is started by /etc/rc.d/init.d/mailman, and # service mailman status mailman (pid 7087) is running... 6) Locks: # ls -l ~mailman/locks ls: /usr/lib/mailman/locks: No such file or directory 7) Logs: The only things in the logs are the subscriptions: [root@bubba mailman]# cat qrunner Feb 25 04:08:42 2007 (7087) Master watcher caught SIGHUP. Re-opening log files. Feb 25 04:08:44 2007 (7097) RetryRunner qrunner caught SIGHUP. Reopening logs. [root@bubba mailman]# cat subscribe Feb 26 17:42:35 2007 (10359) foobarlist: new bob(a)bobcatos.com, admin mass sub Feb 26 17:42:35 2007 (10359) foobarlist: new otherperson(a)domain.com, admin mass sub The only thing in error is the result of running mailmanctl with no arguments. /var/log/mailman/smtp is zero-length. 8) Qfiles: # ls -l ~mailman/qfiles ls: /usr/lib/mailman/qfiles: No such file or directory # locate qfiles /usr/lib/mailman/bin/show_qfiles Okay, with this and (6), I'm wondering if some directories are missing. But if so, why is (or was) the other list functioning, and why is there nothing in the logs about it? Also, the server has been up for 216 days, and the other list was created since the last boot, so there's been no system crash to take something out. 9) SMTPHOST: /var/log/mailman/smtp shows no signs of distress, in fact, it is zero-length (and owned by mailman). 10) Sendmail + mm-handler (not applicable) For FAQ 1.7: a) N/A since this is v2.1.8. b, c, and d) Aliases are ok by inspection and log entries, above. e) qrunner is running. f) No messages for moderation. g) /etc/mailman/mm_cfg.py contains DEFAULT_URL_HOST = "www.bobcatos.com" DEFAULT_EMAIL_HOST = "lists.bobcatos.com" add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) What clues am I missing? Cheers, -- Bob McClure, Jr. Bobcat Open Systems, Inc. bob(a)bobcatos.com http://www.bobcatos.com "But what about you?" Jesus asked. "Who do you say I am?" Peter answered, "You are the Christ." Mark 8:29 (NIV)

2 3

Re: [Mailman-Users] Moderation issues
by Mark Sapiro March 1, 2007

March 1, 2007

Bill Lempesis wrote: > >I believe your first response was correct. I was using a non member email >address that was associated with my name as a test of the list. It appears >that Mailman was allowing it to pass since I am subscribed to the list with >another email address. Would Mailman allow it because the names match even >though email addresses are different? No. membership is tested only by email address, however a member's address appearing in any of the headers From:, Reply-To: or Sender: or in the unix From_ line which is normally the envelope sender's address is sufficient. Actually, the list of headers searched for a member is SENDER_HEADERS which can be set in mm_cfg.py, but the above four are the default. So if your test had ,e.g., Reply-To: your member address, or the envelope was sent by your member address, that would suffice to get the post accepted. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Users] Moderation issues
by Mark Sapiro March 1, 2007

March 1, 2007

Bill Lempesis wrote: > >To summarize: There is no way to block non-members who you don't know from >posting to a list that is Open. Can't have a list that allows only members >to post. This was a feature in older versions of Mailman. If by 'older' you mean older than 2.1.3, then you are correct. If members are not moderated and generic_nonmember_action is Reject or Discard, then posts via email from members should go directly to the list and posts via email from non-members not in *_these_nonmembers should be rejected or discarded. OTOH, posts arriving via the news->mail gateway are held or not based on the setting of news_moderation regardless of who they are from, although this is not the intended use of the news_moderation setting. Prior to Mailman 2.1.3, posts arriving from usenet via the news-mail gateway were subject to the same membership filtering as posts arriving by email. If you want to restore that behavior, you need to make the change to Mailman/Handlers/Moderate.py that I indicated in my reply at <http://mail.python.org/pipermail/mailman-users/2007-March/055896.html>. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Users] Moderation issues
by Mark Sapiro March 1, 2007

March 1, 2007

Bill Lempesis > >Non-member mail still goes directly to the list. What is the setting for >Mail <-> News Gateways Moderation policy of the news group? If None all mail >goes directly to the list. If Moderated, all are moderated including >members. Am I missing something? Mail from the News->Mail (i.e. from the newsgroup to the list) is passed through without any membership or moderation checks on the poster whatsoever. If Mail<->News gateways -> news_moderation is set to Moderated, then all mail from usenet to the list is held. I.e. it is designed to work just as you observe. There is no way to moderate/reject only those posts from usenet that are not From: a list member. I think you can do what you seem to want by editing Mailman/Handlers/Moderate.py and changing def process(mlist, msg, msgdata): if msgdata.get('approved') or msgdata.get('fromusenet'): return to def process(mlist, msg, msgdata): if msgdata.get('approved'): return and setting news_moderation to other than 'Moderated', however if you do this and set generic_nonmember_action = Reject, you will send reject notices to non-members whose posts were accepted by the newsgroup which may be confusing. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0