Mailman 3 June 2007 - Mailman-Users

People are dropping off several of our listservs and we don't know why
by Joellen Leavelle 19 Jun '07

19 Jun '07

Hi. My subject line basically says it all. We run several listservs (both internal and external) and all of a sudden several people just stopped receiving the messages we sent. At first we thought it was a problem with our internal e-mail set up, but a few months later other people started telling us that they hadn't received any listserv messages for 2 months. Have any of you ever experienced this problem? If so, how do you fix it? I've gone in to look at the subscription list and the people who aren't receiving the messages are still on the list. As a side note, our vendor does not know what the problem is nor does he know how to fix it. I'm posting here in hopes that there is something very simple that we are overlooking. I have been on this listserv for about a week and it seems that many of you are much more technically-savvy than I am. I apologize in advance for not knowing things that may be basic. Any advice you could give would be much appreciated. Thanks! Joellen Leavelle Communications Coordinator and Logistics Manager Pension Rights Center 1350 Connecticut Avenue, NW Suite 206 Washington, DC 20036 Phone: (202) 296-3776 Fax: (202) 296-1571 www.pensionrights.org

2 1

Cron gate news Illegal Command
by Michael Ballard 17 Jun '07

17 Jun '07

I recently installed mailman 2.1.9-2 via RPM on Fedora Core 6. Everything seems to be working fine except every 5 minutes I receive the following error via my mailman list: "Illegal command: /usr/lib/mailman/cron/gate_news" root is sending it. /usr/lib/mailman/cron/gate_news/ has the same permissions as the other cron jobs in //usr/lib/mailman/cron/ I edited /usr/lib/mailman/cron/crontab.in/, commenting out what I thought the offending line was: "0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/lib/mailman/cron/gate_news" to "# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/lib/mailman/cron/gate_news" After editing the file, I restart mailman as root, so the cron permissions are all correct. But I still receive the error. Any help would be much appreciated, the same E-mail every 5 minutes is getting awfully annoying. -- Censorship is telling a man he can't have a steak just because a baby can't chew it. - Mark Twain

2 2

List
by letb24＠aol.com 16 Jun '07

16 Jun '07

Hey everyone! Really new to all this, I know I can search the FAQ, and I did, but was hoping someone wasn't busy this morning and could give me a step by step at how to extract my email list so I can have a hard copy. Lately, I have been getting a lot of bounces and notices have been sent out that their account will be deleted. Any idea why this is happening? From about 980 people, almost 120 people don't get the email. I realize some might be from old emails but I know others used to get it with the old way. Thanks a lot. ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com.

2 1

Assertion error in senddigests
by Dan Lowe 15 Jun '07

15 Jun '07

I know a bit of Python, but this traceback is way over my head. I'm getting this every day when the senddigests cron job runs: Traceback (most recent call last): File "/usr/local/pkg/mailman/cron/senddigests", line 94, in <module> main() File "/usr/local/pkg/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/pkg/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line 142, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/pkg/mailman/Mailman/Handlers/Scrubber.py", line 373, in process t = t.encode(charset, 'replace') File "/usr/local/pkg/python/lib/python2.5/encodings/ quopri_codec.py", line 20, in quopri_encode assert errors == 'strict' AssertionError Searching list archives and Google haven't turned up anything that looks useful. The traceback doesn't even point to which list was being operated on at the time of the error. The only thing I've found in the Mailman logs is this sort of message, in logs/error: Jun 12 16:08:44 2007 (504) send_digests() failed: Jun 12 16:11:40 2007 (504) send_digests() failed: Jun 12 16:18:20 2007 (504) send_digests() failed: Jun 12 16:21:30 2007 (504) send_digests() failed: Jun 12 16:21:40 2007 (504) send_digests() failed: Jun 12 16:23:06 2007 (504) send_digests() failed: Jun 12 16:47:21 2007 (504) send_digests() failed: Jun 12 16:49:58 2007 (504) send_digests() failed: Jun 12 16:58:42 2007 (504) send_digests() failed: Jun 12 17:20:15 2007 (504) send_digests() failed: Also, though most of my lists are set as digestable (but not digesting by default), none of my lists have any digest-enabled subscribers... -dan

2 1

Problems with virtual domains on postfix...
by Roberto Leibman 15 Jun '07

15 Jun '07

Help! I can't get my list to work. For some reason postfix keeps redirecting email sent to the list to the non-list domain. Thanks for you help... Roberto ---------------------------- Details: The List: lug-nuts(a)saclug.org The "Real" Domain: leibmanland.com The message from a bounced back message sent to lug-nuts(a)saclug.org: <lug-nuts(a)leibmanland.com>: data format error. Command output: lug-nuts: Mailbox does not exist The postfix message (from mail.log) 6ADC07040E6: to=<lug-nuts(a)leibmanland.com>, orig_to=<lug-nuts(a)saclug.org>, relay=spamassassin, delay=2.4, delays=0.12/0.01/0/2.3, dsn=2.0.0, status=sent (delivered via spamassassin service) --------------------------- The configuration: Environment: Ubuntu feisty running on an AMD64. Postfix version: 2.3.8. Mailman (2.1.9... I think) Excerpts from /etc/postfix/main.cf alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases mydestination = localhost, localhost.localdomain, localhost, mail, mail.leibmanland.com, [69.62.235.30] virtual_alias_maps = hash:/etc/postfix/virtual, hash:/var/lib/mailman/data/virtual-mailman virtual_mailbox_domains=leibmanland.com list.saclug.org placerliberty.org freezlets.com leibman.net mail.leibman.net byrongalvez.com mail.freezlets.com mail.byrongalvez.com lpsacramento.com mail.lpsacramento.com lpsacramento.org mail.lpsacramento.org saclug.org owner_request_special=no allow_mail_to_commands = alias mailman_destination_recipient_limit = 1 Excerpts from /etc/postfix/master.cf mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py Excerpts from /etc/mailman/mm_cfg.py DEFAULT_EMAIL_HOST = 'leibmanland.com' DEFAULT_URL_HOST = 'www.leibmanland.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, 'saclug.org') MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS=['placerliberty.org', 'saclug.org'] Excerpts from /var/lib/mailman/data/virtual-mailman # STANZA START: lug-nuts # CREATED: Tue Jun 12 17:04:53 2007 lug-nuts(a)saclug.org lug-nuts lug-nuts-admin(a)saclug.org lug-nuts-admin lug-nuts-bounces(a)saclug.org lug-nuts-bounces lug-nuts-confirm(a)saclug.org lug-nuts-confirm lug-nuts-join(a)saclug.org lug-nuts-join lug-nuts-leave(a)saclug.org lug-nuts-leave lug-nuts-owner(a)saclug.org lug-nuts-owner lug-nuts-request(a)saclug.org lug-nuts-request lug-nuts-subscribe(a)saclug.org lug-nuts-subscribe lug-nuts-unsubscribe(a)saclug.org lug-nuts-unsubscribe # STANZA END: lug-nuts Excerpts from /var/lib/mailman/data/aliases # STANZA START: lug-nuts # CREATED: Tue Jun 12 17:04:53 2007 lug-nuts: "|/var/lib/mailman/mail/mailman post lug-nuts" lug-nuts-admin: "|/var/lib/mailman/mail/mailman admin lug-nuts" lug-nuts-bounces: "|/var/lib/mailman/mail/mailman bounces lug-nuts" lug-nuts-confirm: "|/var/lib/mailman/mail/mailman confirm lug-nuts" lug-nuts-join: "|/var/lib/mailman/mail/mailman join lug-nuts" lug-nuts-leave: "|/var/lib/mailman/mail/mailman leave lug-nuts" lug-nuts-owner: "|/var/lib/mailman/mail/mailman owner lug-nuts" lug-nuts-request: "|/var/lib/mailman/mail/mailman request lug-nuts" lug-nuts-subscribe: "|/var/lib/mailman/mail/mailman subscribe lug-nuts" lug-nuts-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe lug-nuts" # STANZA END: lug-nuts

3 4

Server Migration (and archive repair)
by Brian Hechinger 15 Jun '07

15 Jun '07

I need to build a new mailman server. What is the best/easiest way to migrate lists (and their archives) to the new machine? Something that used rsync would be nice so I could keep things as up to date as possible and then do a final rsync right before the migration. This is definitely something that needs to be done slowly and kept up with, our archives are currently 26GB in size. ;) The other thing is, a previous admin tried to clear out the archives for a couple of lists, and now the new messages are no longer archived. How do I repair these broken archives? Thanks, -brian -- "Perl can be fast and elegant as much as J2EE can be fast and elegant. In the hands of a skilled artisan, it can and does happen; it's just that most of the shit out there is built by people who'd be better suited to making sure that my burger is cooked thoroughly." -- Jonathan Patschke

2 2

mailman clustering?
by Pat Riehecky 15 Jun '07

15 Jun '07

I am trying to build a nice failover system for random parts of our infrastructure. Does anyone know how to force mailman to replicate changes over to another identically configured system? I thought about using rsync for this but I am trying to keep the sync triggered by updates on the primary server rather than just seeing if in the last few minutes any files have changed. Ideally I would like to round robin the primary and the secondary to split the load up, but I cannot do that without being sure that they are kept in sync with each other. How close to possible is this idea? Is there something I should read? I checked the FAQ and didn't see anything... Pat

2 1

Member only list?
by L. H. 15 Jun '07

15 Jun '07

Hi, I am currently running 2.1.9, and am trying to setup a member only list function using config_list. I've found a few instructions, but they seem to be for older versions of which the commands are no longer recognized. What I want to do is have 3 setups: 1) Everyone, members or no members, can post 2) Only members can post, no moderation required for them. Drop all non-member submissions. 3) All emails sent to the list (member + non member) must be approved by the admin. Which configuration lines should I use for this? I currently use: 1) Everyone: generic_nonmember_action = 0 default_member_moderation = 0 2) Members only: default_member_moderation = 0 generic_nonmember_action = 2 3) Moderation for everyone: default_member_moderation = 1 member_moderation_action = 0 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 Please advise. Thanks!

2 3

Member only list?
by L. H. 14 Jun '07

14 Jun '07

Hi, I am currently running 2.1.9, and am trying to setup a member only list function using config_list. I've found a few instructions, but they seem to be for older versions of which the commands are no longer recognized. What I want to do is have 3 setups: 1) Everyone, members or no members, can post 2) Only members can post, no moderation required for them. Drop all non- member submissions. 3) All emails sent to the list (member + non member) must be approved by the admin. Which configuration lines should I use for this? I currently use: 1) Everyone: generic_nonmember_action = 0 default_member_moderation = 0 2) Members only: default_member_moderation = 0 generic_nonmember_action = 2 3) Moderation for everyone: default_member_moderation = 1 member_moderation_action = 0 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 Please advise. Thanks!

1 0

List archive and config problem
by Jo'Asia 14 Jun '07

14 Jun '07

OK, the stroy is long, but there may be a lot of reasons for the problems, so here it goes. Last week the server running mailman had been upgraded (meaning a completly new machine with all the data migrated from the old one). At this time also mailman has been upgraded from 2.1.5 to 2.1.9 Some minor problems appeared, like rights to archives, but they have been fixed. Unfortunately, one of the lists set for public archive is creating a private archive. The WWW admin interface still showed the archive option set to 'public'. I tried to switch it to private and back to public and saw this error message: Bug in Mailman version 2.1.9 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. I checked the log - there is *some* info, nothing helpful to me, but, if necessary, I can quote it... Now even an attemt to log into the admin interface of this list generates this error message. :( I run check_db - it says the config.pck file is OK. List as such is running OK - mails are recieved, delivered and archived (still in *private* archive directory), only the admin interface is broken. Where else should I look for the cause? If everything else fails it's possible to create a new list and import as much information from "strings dump" of the pickle file but I'd rather revive the current one. And fix this damn archiving... Jo'Asia -- Joanna Slupek --- --- --- .-- --- " --- http://esensja.pl |--- '-- |--- | | '-- | --| joasia(a)redakcja.esensja.pl --- ---' --- | | ---' | '--. -------------------------------------------------------------------' ----

2 1