Mailman 3 October 2006 - Mailman-Users

Spamassassin Integration Question
by Christopher Hatty 25 Oct '06

25 Oct '06

I've followed the instructions at this site: http://www.jamesh.id.au/articles/mailman-spamassassin/ It works wonderfully, with one caveat. If a message is detected as spam, it is sent to the moderation queue, even if that message would otherwise have been discarded. Has anyone else run into this and managed to find a workaround? At present, my plan is to simply use a custom global pipeline for each list. Thanks Christopher

3 3

Users subscribe with their emails being classified in the Subject field
by Starkey, Joel 25 Oct '06

25 Oct '06

Many of our subscribers cannot reply to the confirmation email to confirm their subscription/unsubscription as their emails are being classified on the way out of their email gateway. This is occurring in both Government and Industry associations. I have seen these in various format which have included: Subject: confirm f901053f30c0fe1b3050899370ed960e6303a68e [SEC:UNCLASSIFIED] Subject: confirm f901053f30c0fe1b3050899370ed960e6303a68e[SEC:UNCLASSIFIED] Subject: [SEC:UNCLASSIFIED]confirm f901053f30c0fe1b3050899370ed960e6303a68e Subject: Unclassified - confirm f901053f30c0fe1b3050899370ed960e6303a68e Has anyone come across this before and does anybody have a fix for this so Mailman accepts and processes the confirmation. As currently if this occurs mailman returns an "unprocessed" email. Many thanks Joel _______________________________________________________________________________________________________ The information transmitted is for the use of the intended recipient only and may contain confidential and/or legally privileged material. Any review, re-transmission, disclosure, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may result in severe penalties. If you have received this e-mail in error please notify the Security Advisor of the Department of Communications, Information Technology and the Arts, telephone (02) 6271-1880 and delete all copies of this transmission together with any attachments. For all other enquiries please ring (02) 6271-1000. _______________________________________________________________________________________________________

2 1

Re: [Mailman-Users] Holding messages from non-members?
by Elizabeth Schwartz 25 Oct '06

25 Oct '06

I'm sorry , this one was our screwup. An old test list was around with a name that was one letter off. (It would be a nice touch if the 'vette' log showed which list the discarded mail was sent to...)

2 1

Holding messages from non-members?
by Elizabeth Schwartz 24 Oct '06

24 Oct '06

I am running mailman 2.1.8 on Solaris 10 with sendmail. I have an umbrella list which seems to be discarding messages from non-members. With the settings below, I expected that the correct behavior would be to hold the messages: On the Privacy options: Action to take for postings from non-members for which no explicit action is defined [hold] Should messages from non-members, which are automatically discarded, be forwarded to the list moderator? [no] The Privacy Options page also says: " Any posting from a non-member who is not explicitly accepted, rejected, or discarded, will have their posting filtered by the general non-member rules<http://lists.gsd.harvard.edu/mailman/admin/gsd-announce-l/privacy/sender?VA…> ." My general non-member rules page is set to: When a post from a non-member is received, the message's sender is matched against the list of explicitly accepted<http://lists.gsd.harvard.edu/mailman/admin/gsd-announce-l/privacy/sender?VA…>, held<http://lists.gsd.harvard.edu/mailman/admin/gsd-announce-l/privacy/sender?VA…>, rejected<http://lists.gsd.harvard.edu/mailman/admin/gsd-announce-l/privacy/sender?VA…>(bounced), and discarded<http://lists.gsd.harvard.edu/mailman/admin/gsd-announce-l/privacy/sender?VA…>addresses. If no match is found, then this action is taken. [Hold] ---- So, why am I not seeing hold? Is there another setting somewhere that I missed? I did change the settingso that automatically discarded postings are forwarded to the moderator.

3 4

Re: [Mailman-Users] nodupes flag
by Mark Sapiro 24 Oct '06

24 Oct '06

Bochkov, Natasha wrote: > >I was looking for an answer on the issue I have with the MailMan and >your name came out on the MailMan forum. Do you know by any chance how >to turn On nodupes for all list members in a batch? Use the following withlist script. Cut here---------------------------------------- """Set all members of a list to not receive from the list those posts in which they are directly addressed in To: or Cc: Save as bin/set_nodups.py Run via bin/withlist -r set_nodups <listname> """ from Mailman import mm_cfg def set_nodups(mlist): if not mlist.Locked(): mlist.Lock() for member in mlist.getMembers(): mlist.setMemberOption(member, mm_cfg.DontReceiveDuplicates, 1) mlist.Save() mlist.Unlock() Cut here----------------------------------------- -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

how to force mailman to process bounces but not send out anymore emails
by Josh Orchard 24 Oct '06

24 Oct '06

Hello, I have many bounces in the thousands from a very large list (800K) that was sent. Will the list was stopped after 500K or so. I would like to stop it from sending any more emails and have it process only the bounced emails and clean up only the bounces. So, basically how to make it only do the -leave emails that were sent. Thanks, Josh

2 4

Changing archive template for a specific list
by Rusty Wilson 24 Oct '06

24 Oct '06

Hi Everyone, mm 2.1.5 I want to make a template change to one specific archive template. I've reviewed: http://mail.python.org/pipermail/mailman-users/2004-June/037493.html> and <http://mail.python.org/pipermail/mailman-users/2004-June/037646.html>. These seem to show how to make a template change that will affect all lists. On a hunch I edited: $prefix/mailman/archives/public/<listname>/index.html I then restarted mailman qrunners (per messages above). As you've guessed, the change stuck, until the next post was made to the list. What obvious step have I overlooked? Again, I want to make a template change to just one archive in particular. TIA, Rusty

2 1

Newgroup gatway and specific user rights
by Rob Jackson 24 Oct '06

24 Oct '06

I have several newgroup gateways set up, but I need to tweak it a little. I have a two sets of users. One set is LIST ONLY, and the other set is LIST and NEWSGROUP. Is there a way I can set this up in mailman? -Rob

1 0

mail keeps looping back to list due to filter rule
by Matthew Clarkson 23 Oct '06

23 Oct '06

My mailing lists have been running fine on our mailman 2.1.7 server for the last year, however, I just implemented a filter for spam on one of our public lists to catch anything that spamassassin marks with a ***SPAM*** subject. The filter rule I imposed on this list is subject: .*SPAM.* however, now it loops mail back to the list that match this filter rule, locking the list up (I get stale locks in the locks/ directory). The only way to recover from the endless loops is by removing the stale locks and then discarding all .pck's to the list with the discard command (otherwise, the web interface gets locked up due to too many messages). Here is the first bit of the moderator request email I get notifying me of pending requests to be dealt with (list name replaced by mylist). ------------------------------------------------ Pending posts: From: theoeustacia(a)enterfree.it on Fri Oct 20 22:54:04 2006 Subject: ***SPAM*** Sweet Cause: The message headers matched a filter rule From: mylist-owner(a)mailman.netera.ca on Fri Oct 20 22:54:08 2006 Subject: mylist post from theoeustacia(a)enterfree.it requires approval Cause: The message headers matched a filter rule From: mylist-owner(a)mailman.netera.ca on Fri Oct 20 22:54:16 2006 Subject: mylist post from mylist-owner(a)mailman.netera.ca requires approval Cause: The message headers matched a filter rule From: mylist-owner(a)mailman.netera.ca on Fri Oct 20 22:54:20 2006 Subject: mylist post from mylist-owner(a)mailman.netera.ca requires approval Cause: The message headers matched a filter rule ... ... ... ------------------------------------------------ Does anyone know what my be causing this, or where I can fix this? it seems as though the mylist-owner@... address is looping it right back to the original address, of which it gives "Cause: The message headers matched a filter rule", is there an easy way around this? since I know this must be common practice to filter via spam headers. Thanks for any help. -- Matthew Clarkson Netera Alliance

2 1

Re: [Mailman-Users] Help newbie with a common error (smrsh)?
by Mark Sapiro 23 Oct '06

23 Oct '06

Tony Croes wrote: > > Mark Sapiro wrote: > > Yes, the mail is delivered to Mailman. Its appearance in the archive >proves that. Your problem is why is mail from Mailman not getting out. > > Is OutgoingRunner Running? > >I think so. Output from #ps auxww | egrep 'p[y]thon': >mailman 5600 0.0 0.3 11096 3976 ? Ss Oct21 0:00 >/usr/bin/python /usr/lib/mailman/bin/mailmanctl -s -q start >mailman 5601 0.1 0.8 14692 8584 ? S Oct21 2:14 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s >mailman 5602 0.0 0.5 10260 5416 ? S Oct21 0:00 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s >mailman 5603 0.0 0.5 11248 5412 ? S Oct21 0:00 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s >mailman 5604 0.0 0.5 11936 5772 ? S Oct21 0:04 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s >mailman 5605 0.0 0.5 11208 5440 ? S Oct21 0:00 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s >mailman 5606 0.0 0.5 11096 5660 ? S Oct21 0:01 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s >mailman 5607 0.0 0.5 12372 5668 ? S Oct21 0:00 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s >mailman 5608 0.0 0.5 11356 5408 ? S Oct21 0:00 >/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s Yes. It looks like Outgoing Runner is running. > Mark Sapiro wrote: > > What's in Mailman's 'smtp' and 'smtp-failure' logs? > > Are there entries in mailman's qfiles/out/, qfiles/retry/ and/or >qfiles/shunt queue directories? > > If there are entries in qfiles/shunt/, what's in Mailman's error >log. > >There is not an smtp-failure log. This means nothing was ever written to it so it wasn't created yet. >The smtp and error logs are here: >smtp: >Oct 22 16:01:44 2006 (5606) ><mailman.0.1161550902.5604.mailman(a)server.ctrcc.com> smtp for 1 recips, >completed in 0.465 seconds >Oct 22 16:01:44 2006 (5606) ><mailman.1.1161550902.5604.mailman(a)server.ctrcc.com> smtp for 1 recips, >completed in 0.374 seconds >Oct 22 16:02:02 2006 (5606) ><mailman.1.1161550902.5604.mailman(a)server.ctrcc.com> smtp for 1 recips, >completed in 0.342 seconds The above are delivery of Mailman generated messages, not posts. If they are associated with posts, they may be a message to the poster that the post was held, a message to <list>-owner@... that the post was held and resend of the <list>-owner message to the actual list owner address. However, you say the posts ARE in the archive, so they aren't being held or if they are, they are being approved. >error: >Oct 21 11:52:13 2006 mailmanctl(6580): PID unreadable in: >/var/run/mailman/master-qrunner.pid >Oct 21 11:52:13 2006 mailmanctl(6580): [Errno 2] No such file or directory: >'/var/run/mailman/master-qrunner.pid' >Oct 21 11:52:13 2006 mailmanctl(6580): Is qrunner even running? These are not relevant to your problem. >More newbie questions. Where is ~/qfiles under version 2.1.5? I have not >been able to find it. Is this the equivalent: > >[root@server mailman]# pwd >/var/spool/mailman >[root@server mailman]# ll >total 60 >drwxrws--- 2 mailman mailman 12288 Oct 22 16:03 archive >drwxrws--- 2 mailman mailman 4096 Oct 20 22:53 bounces >drwxrws--- 2 mailman mailman 4096 Oct 20 23:14 commands >drwxrws--- 2 mail mailman 20480 Oct 22 16:03 in >drwxrws--- 2 mailman mailman 4096 Oct 20 22:53 news >drwxrws--- 2 mailman mailman 4096 Oct 22 16:03 out >drwxrws--- 2 mailman mailman 4096 Oct 20 22:53 retry >drwxrws--- 2 mailman mailman 4096 Oct 20 22:53 shunt >drwxrws--- 2 root mailman 4096 Oct 22 16:01 virgin > >All of these directories are empty. This is where the RedHat rpm puts them. If you look in mm_cfg.py, you will see definitions of QUEUE_DIR, INQUEUE_DIR, OUTQUEUE_DIR, CMDQUEUE_DIR, BOUNCEQUEUE_DIR, NEWSQUEUE_DIR, ARCHQUEUE_DIR, SHUNTQUEUE_DIR, VIRGINQUEUE_DIR, BADQUEUE_DIR and RETRYQUEUE_DIR that define the location. Anyway, the fact that they are all empty means Mailman has finished processing the message - it is not queued anywhere for further processing. It could be 'held', but not if it appeared in the archive. The implication is the message had no recipients. i.e., the list has no members eligible for delivery - the list members - subscribe to the digest, - have delivery disabled, - are the poster who doesn't receive her own posts or - are a direct addressee who doesn't receive dups. There are a couple of other interesting things in the above. All the queue directories are 'default size' except 'in' and 'archive' which are large. This indicates a lot of messages were posted (and in the 'in' queue) before the qrunners (mailmanctl) were started. Thus the 'in' directory grew. Then Mailman (mailmanctl) was started and the 'in' queue was processed and a lot of messages were dumped in the 'archive' queue which also grew, but ArchRunner was running so the 'archive' queue was being processed and didn't grow as big. The 'out' queue never grew so presumably those messages had no direct recepients. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 1