Mailman 3 April 2008 - Mailman-Users

Re: [Mailman-Users] "IOError reading list extension" Message
by b19141＠anl.gov April 25, 2008

April 25, 2008

Barry Finkel wrote: >>I am running a home-built Mailman 2.1.9 Ubuntu package with the latest >>security patch. I see messages in the error log like this one: >> >> Apr 25 08:00:05 2008 (27326) IOError reading list extension: >> [Errno 20] Not a directory: >> '/var/lib/mailman/lists/append_description.newdescription/extend.py' >> >>I do not see any >> >> extend.py >> >>in the directory in which I build Mailman. And Mark Sapiro replied: >Is 'append_description.newdescription' the name of a list? > >This error occurs when Mailman attempts to read (actually execute) the >optional extend.py module for a list during the instantiation of that >list, and it gets an error exception other than 'doesn't exist'. The three files in the /var/lib/mailman/lists directory append_description.newdescription append_description.description append_description.configfile were created when I was testing a script to add "{category}" to the description field of each Mailman list. I am not sure how they got there, as my script was running from my home directory. I have deleted them. Since these three files are not Mailman lists, which Mailman process that was treating them as list names is not important. We find the Mailman "home" page (i.e., listinfo) not user-friendly, as it lists all of the advertised lists in alphabetical order. We have about 80 advertised lists. We want the lists sorted by category, so I wrote a script to append "{category}" to each list description. I have defined eighteeen different "{category}" strings, and we are working on generating a new listinfo page with the lists sorted by category. The plan is to 1) Make "listinfo.original" point to the Mailman-generated page. 2) Have the new "listinfo" page use the "listinfo.original" page to extract the advertised list names and descriptions. A new list of lists page will be displayed using the category strings at the send of each list's "description" field and an external file that describes the various category strings. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994

2 1

Re: [Mailman-Users] unparseable message
by b19141＠anl.gov April 25, 2008

April 25, 2008

Mark Sapiro replied to one of my postings: >Mailman (actually the Python email package) doesn,t like the fact that >there is no intervening empty line between the terminating boundary of >the message/rfc822 part and the terminating boundary of the outer >message. > >Quoting from section 5.1.1 of RFC 2045 > > The boundary may be followed by zero or more characters of linear > whitespace. It is then terminated by either another CRLF and the > header fields for the next part, or by two CRLFs, in which case > there are no header fields for the next part. For the record (i.e., anyone who looks in the archives), the RFC is 2046. This DSN message is being generated by our Ironport anti-spam appliance, so we will report this to Ironport. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994

2 1

"IOError reading list extension" Message
by b19141＠anl.gov April 25, 2008

April 25, 2008

I am running a home-built Mailman 2.1.9 Ubuntu package with the latest security patch. I see messages in the error log like this one: Apr 25 08:00:05 2008 (27326) IOError reading list extension: [Errno 20] Not a directory: '/var/lib/mailman/lists/append_description.newdescription/extend.py' I do not see any extend.py in the directory in which I build Mailman. I see an archived posting http://www.mail-archive.com/mailman-users@python.org/msg37089.html that has a similar complaint from 16 Feb 2006, but the response from Mark Sapiro to that posting does not seem to fit my situation. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994

2 1

How to import a list of members?
by lists.mailman-users＠duinheks.nl April 25, 2008

April 25, 2008

Hallo mailman-users, Is it possible to import an ASCII list of members for a mailing list? If yes, how to do it? Groeten, Hans. jdh punt beekhuizen bij duinheks punt nl --- GoldED+/LNX 1.1.5/080305 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

1 0

Re: [Mailman-Users] How to make a list read-only ?
by lists.mailman-users＠duinheks.nl April 25, 2008

April 25, 2008

Hallo Mark and Joerg, Op donderdag 24 april 2008 schreef Mark Sapiro aan lists.mailman-users(a)duinheks.nl: MS> This is desdribed at MS> www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.011.htp>. Many thanks to both of you. Groeten, Hans. jdh punt beekhuizen bij duinheks punt nl --- GoldED+/LNX 1.1.5/080305 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

1 0

unparseable message
by b19141＠anl.gov April 25, 2008

April 25, 2008

I built an Ubuntu package for the patched Mailman 2.1.9, and when I tried to install it this morning, there was an error message stating that The directory /var/lib/mailman/qfiles contains files. It needs to be empty for the upgrade work properly. I looked at that directory, and I found a number of bounces/xxxxx.bak files. Per a reply posting on 12 Feb-2008 by Mark Sapiro (Subject: [Mailman-Users] bounce file questions) I moved those files elsewhere (for further study). Then I was able to install the updated Mailman 2.1.9 package. Mark wrote: Yes, it's safe to delete. It is the backup of the file that BounceRunner was processing when something happened, and BounceRunner never 'finished' processing the file. There was a hole that allowed this to occur on an 'unparseable' (almost always spam) message in 2.1.9, no whenever you get the "Ignoring unparseable message" in the error log, the .bak file is left behind. This is fixed in 2.1.10n now in beta. I looked at the logs and found an unparseable rejection message. I am including it below. I am not sure what the problem is, but I believe that the content-type: message/rfc822 attachment contains the beginning of the original MIME-encoded posting, and Mailman is getting confused with this MIME-within-MIME. Here is a message from the Mailman error log: Uncaught runner exception: No terminating boundary and no trailing empty line Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 100, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/var/lib/mailman/Mailman/Queue/Switchboard.py", line 164, in dequeue msg = email.message_from_string(msg, Message.Message) File "/var/lib/mailman/pythonlib/email/__init__.py", line 51, in message_from_string return Parser(_class, strict=strict).parsestr(s) File "/var/lib/mailman/pythonlib/email/Parser.py", line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File "/var/lib/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/var/lib/mailman/pythonlib/email/Parser.py", line 240, in _parsebody msgobj = self.parsestr(part) File "/var/lib/mailman/pythonlib/email/Parser.py", line 75, in parsestr return self.parse(StringIO(text), headersonly=headersonly) File "/var/lib/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/var/lib/mailman/pythonlib/email/Parser.py", line 265, in _parsebody msg = self.parse(fp) File "/var/lib/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/var/lib/mailman/pythonlib/email/Parser.py", line 206, in _parsebody raise Errors.BoundaryError( BoundaryError: No terminating boundary and no trailing empty line Am I correct in my diagnosis? And is this (i.e., the unparseability) something that can be corrected? Thanks. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 ----- Here is the unparseable rejection message. ----- >From MAILER-DAEMON Mon Apr 21 07:03:34 2008 Return-Path: <> Received: from mailrelay.anl.gov (localhost [127.0.0.1]) by localhost.ctd.anl.gov (Postfix) with ESMTP id 8BE2E5F0C03; Mon, 21 Apr 2008 07:03:34 -0500 (CDT) Received: from mailgateway.anl.gov (mailgateway.anl.gov [130.202.101.28]) by mailrelay2.anl.gov (Postfix) with ESMTP id 601025F0C02 for <LISTNAME-bounces(a)lists.anl.gov>; Mon, 21 Apr 2008 07:03:34 -0500 (CDT) Received: from localhost by mailgateway.anl.gov; 21 Apr 2008 07:03:34 -0500 Date: 21 Apr 2008 07:03:34 -0500 To: LISTNAME-bounces(a)lists.anl.gov From: "Mail Delivery System" <MAILER-DAEMON(a)mailgateway.anl.gov> Subject: Delivery Status Notification (Failure) MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="orAt.4Is3ZceEe.1I4wvb.Aylgfr0" Message-Id: <20080421120334.601025F0C02(a)mailrelay.anl.gov> --orAt.4Is3ZceEe.1I4wvb.Aylgfr0 content-type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable The following message to <abcdefgh(a)anl.gov> was undeliverable. The reason for the problem: 5.1.0 - Unknown address error 550-'5.1.1 <abcdefgh(a)anl.gov>: Recipient a= ddress rejected: User unknown in relay recipient table' --orAt.4Is3ZceEe.1I4wvb.Aylgfr0 content-type: message/delivery-status Reporting-MTA: dns; mailgateway.anl.gov Final-Recipient: rfc822;abcdefgh(a)anl.gov Action: failed Status: 5.0.0 (permanent failure) Remote-MTA: dns; [130.202.101.23] Diagnostic-Code: smtp; 5.1.0 - Unknown address error 550-'5.1.1 <abcdefgh(a)anl.gov>: Recipient address rejected: User unknown in relay recipient table' (delivery attempts: 0) --orAt.4Is3ZceEe.1I4wvb.Aylgfr0 content-type: message/rfc822 Received: from cliff.mcs.anl.gov (HELO mcs.anl.gov) ([140.221.9.17]) by mailgateway.anl.gov with ESMTP; 21 Apr 2008 07:03:34 -0500 Received: from cliff.mcs.anl.gov (HELO mcs.anl.gov) ([140.221.9.17]) by mailgateway.anl.gov with ESMTP; 21 Apr 2008 07:03:34 -0500 Received: from mailgw.mcs.anl.gov (mailgw.mcs.anl.gov [140.221.9.4]) by mcs.anl.gov (8.11.6/8.9.3) with ESMTP id m3LC1HQ149680; Mon, 21 Apr 2008 07:01:17 -0500 Received: from localhost (localhost [127.0.0.1]) by mailgw.mcs.anl.gov (Postfix) with ESMTP id 28A6434800C; Mon, 21 Apr 2008 07:01:17 -0500 (CDT) Received: from mailhost.anl.gov (mailhost.anl.gov [130.202.113.50]) by mailgw.mcs.anl.gov (Postfix) with ESMTP id 7C8CA348009; Mon, 21 Apr 2008 07:01:16 -0500 (CDT) Received: from mailhost.anl.gov (localhost [127.0.0.1]) by localhost.ctd.anl.gov (Postfix) with ESMTP id 1F6518A; Mon, 21 Apr 2008 07:00:54 -0500 (CDT) Received: from lists.anl.gov (katydid.it.anl.gov [146.137.96.32]) by mailhost.anl.gov (Postfix) with ESMTP id 2987EA3; Mon, 21 Apr 2008 07:00:40 -0500 (CDT) Received: from katydid.it.anl.gov (localhost [127.0.0.1]) by lists.anl.gov (Postfix) with ESMTP id A51C180D88; Mon, 21 Apr 2008 07:00:33 -0500 (CDT) X-Original-To: LISTNAME(a)lists.anl.gov Delivered-To: LISTNAME(a)lists.anl.gov Received: from SCOOBY.anl.gov (velma.anl.gov [146.137.8.21]) by lists.anl.gov (Postfix) with ESMTP id D35AF80D70 for <LISTNAME(a)lists.anl.gov>; Mon, 21 Apr 2008 07:00:29 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/related; type="multipart/alternative"; boundary="----_=_NextPart_001_01C8A3A7.4B24E858" Subject: Today - Monday, April 21 Date: Mon, 21 Apr 2008 07:00:29 -0500 Message-ID: <A685CE80C33C75408D34E0883DEA6F800134184B(a)SCOOBY.anl.gov> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Argonne Today - Monday, April 21 Thread-Index: Acihm/Er7Ksidh3fQHeKTEnEZRl9Yg== From: "Newsroom" <xxxxxxxxxxx(a)anl.gov> To: <LISTNAME(a)lists.anl.gov> X-BeenThere: LISTNAME(a)lists.anl.gov X-Mailman-Version: 2.1.9 Precedence: list List-Id: "This is the LISTNAME" <LISTNAME.lists.anl.gov> List-Unsubscribe: <https://lists.anl.gov/mailman/listinfo/LISTNAME>, <mailto:LISTNAME-request@lists.anl.gov?subject=unsubscribe> List-Archive: <https://lists.anl.gov/mailman/private/LISTNAME> List-Post: <mailto:LISTNAME@lists.anl.gov> List-Help: <mailto:LISTNAME-request@lists.anl.gov?subject=help> List-Subscribe: <https://lists.anl.gov/mailman/listinfo/LISTNAME> <mailto:LISTNAME-request@lists.anl.gov?subject=subscribe> Sender: LISTNAME-bounces(a)lists.anl.gov Errors-To: LISTNAME-bounces(a)lists.anl.gov X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at mailgw.mcs.anl.gov ------_=_NextPart_001_01C8A3A7.4B24E858-- --orAt.4Is3ZceEe.1I4wvb.Aylgfr0--

2 1

Re: [Mailman-Users] Messages remain in spool/mailman/in
by Mark Sapiro April 24, 2008

April 24, 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sebastian Hagedorn wrote: | | --On 23. April 2008 18:28:44 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: | |>> Update: I just noticed that the number of messages in "in" is |>> decreasing. |>> Could it be that something just overwhelmed Mailman so that now there is |>> a backlog that's slowly being worked through? I don't think we ever had |>> such issues prior to today. |> |> There are two possibilities. One is that your IncomingRunner is sliced | | It's not. I didn't even know that feature until just now. Perhaps I | should look into that. | |> The other is that somehow you are working through a flood of messages, |> or some problem (maybe locks - see |> <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.076.htp>) |> is making IncomingRunner run slowly. | | Well, there were really some locking issues, see below. | |> A backlogged IncomingRunner is |> rare. It's more usual to see a backlogged OutgoingRunner due to delays |> in SMTP. |> |> Check all of Mailman's logs for any clues. | | Let's start with mmdsr: | | Hourly Summary of Posts Note that the 'post' log which is the source of these data is written when the message is sent, not when it arrives. | ----------------------- | <snip> | 126 11:00-11:59 | 97 12:00-12:59 | 121 13:00-13:59 | 1355 14:00-14:59 | 760 15:00-15:59 | 617 16:00-16:59 | 1293 17:00-17:59 | 207 18:00-18:59 | <snip> | | So starting around 2pm there was an unusually high number of posts. On | other days there are never more than about 150 messages per hour. It | turns out that one list by itself hat 3,518 posts yesterday. And that | list had locking issues: | | Apr 23 16:28:35 2008 (13393) jura-pruefungsamt.lock lifetime has | expired, breaking | Apr 23 16:28:35 2008 (13393) File "/usr/lib/mailman/bin/qrunner", line | 278, in ? | Apr 23 16:28:35 2008 (13393) main() | Apr 23 16:28:35 2008 (13393) File "/usr/lib/mailman/bin/qrunner", line | 238, in main | Apr 23 16:28:35 2008 (13393) qrunner.run() | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run | Apr 23 16:28:35 2008 (13393) filecnt = self._oneloop() | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop | Apr 23 16:28:35 2008 (13393) self._onefile(msg, msgdata) | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/Queue/Runner.py", line 171, in _onefile | Apr 23 16:28:35 2008 (13393) keepqueued = self._dispose(mlist, msg, | msgdata) | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose | Apr 23 16:28:35 2008 (13393) return IncomingRunner._dispose(self, | mlist, msg, msgdata) | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose | Apr 23 16:28:35 2008 (13393) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock | Apr 23 16:28:35 2008 (13393) self.__lock.lock(timeout) | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/LockFile.py", line 306, in lock | Apr 23 16:28:35 2008 (13393) important=True) | Apr 23 16:28:35 2008 (13393) File | "/usr/lib/mailman/Mailman/LockFile.py", line 416, in __writelog | Apr 23 16:28:35 2008 (13393) traceback.print_stack(file=logf) | Apr 23 16:51:54 2008 (13389) jura-pruefungsamt.lock unexpected | linkcount: -1 | Apr 23 16:51:54 2008 (13389) File "/usr/lib/mailman/bin/qrunner", line | 278, in ? | Apr 23 16:51:54 2008 (13389) main() | Apr 23 16:51:54 2008 (13389) File "/usr/lib/mailman/bin/qrunner", line | 238, in main | Apr 23 16:51:54 2008 (13389) qrunner.run() | Apr 23 16:51:54 2008 (13389) File | "/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run | Apr 23 16:51:54 2008 (13389) filecnt = self._oneloop() | Apr 23 16:51:54 2008 (13389) File | "/usr/lib/mailman/Mailman/Queue/Runner.py", line 113, in _oneloop | Apr 23 16:51:54 2008 (13389) self._onefile(msg, msgdata) | Apr 23 16:51:54 2008 (13389) File | "/usr/lib/mailman/Mailman/Queue/Runner.py", line 171, in _onefile | Apr 23 16:51:54 2008 (13389) keepqueued = self._dispose(mlist, msg, | msgdata) | Apr 23 16:51:54 2008 (13389) File | "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose | Apr 23 16:51:54 2008 (13389) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) | Apr 23 16:51:54 2008 (13389) File | "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock | Apr 23 16:51:54 2008 (13389) self.__lock.lock(timeout) | Apr 23 16:51:54 2008 (13389) File | "/usr/lib/mailman/Mailman/LockFile.py", line 287, in lock | Apr 23 16:51:54 2008 (13389) self.__linkcount(), important=True) | Apr 23 16:51:54 2008 (13389) File | "/usr/lib/mailman/Mailman/LockFile.py", line 416, in __writelog | Apr 23 16:51:54 2008 (13389) traceback.print_stack(file=logf) | | It turns out that our law school department informed all their students | of some news. They did so by sending separate mails to each student, | each time Cc'ing themselves on their Mailman list ... Ouch! | I will talk to | them about that, but still I'd like to know how to avoid such a | situation. Would slices have helped here? No. Slicing would make things worse by increasing lock contention. Since all the posts were for one list, and since the list is locked by IncomingRunner for the entire duration of it's processing of a message, slicing wouldn't help. It normally helps by increasing parallelism, but only if the load is across multiple lists so the the sliced runners aren't blocking each other. In this case, IncomingRunner was doing the best that could be done. I see that VirginRunner was involved in the locking, so perhaps these messages were being held and moderator notices were being generated. Then perhaps a moderator went to the admindb interface, which can keep a list locked for a long time if it is processing a large list of requests. - -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIEJtWVVuXXpU7hpMRAl4yAKDJ9yg2toE5zzDk8kk+e6f71hgW/QCcDnRN AXHyImxm5q4nkvdkV3yjfdc= =fb+L -----END PGP SIGNATURE-----

2 1

SME Server Contrib?
by Jim Hale April 24, 2008

April 24, 2008

Does anyone know if an SME Server (7.3) Contrib has been created yet for 2.1.10? Thanks! :) Jim Hale The MIDI Trombone BBS - http://bbs.themiditrombone.net Fantastic Adventures Online BBS - http://bbs.fantasticadventuresonline.net

4 4

How to make a list read-only ?
by lists.mailman-users＠duinheks.nl April 24, 2008

April 24, 2008

Hallo mailman-users, I believe I saw this question before, but I couldn't find it any more. I'd like to configure a list so that only a few users may post to it. In other words, make it a news letter. How can I achieve this? Groeten, Hans. jdh punt beekhuizen bij duinheks punt nl --- GoldED+/LNX 1.1.5/080305 * Origin: The Wizard is using MBSE/Linux (2:280/1018)

2 1

Re: [Mailman-Users] Messages remain in spool/mailman/in
by Mark Sapiro April 24, 2008

April 24, 2008

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sebastian Hagedorn wrote: | | Ultrafunk Popcorn? That's one I'd never heard of until today! I just saw | that it isn't actively developed any more, otherwise I would've | suggested a bug report: it doesn properly rfc2047-encode headers ... | that's why "Köln" appears as KXln in the Cc: field. Yes. It has issues. Usually I deal with these manually, or if encodings are a problem, I just use Thunderbird, but I was clearly rushing too much yesterday morning, as that wasn't the only thing I didn't do well. Back when it was being actively maintained, I had a good relationship with the developer, and he would fix things very responsively, but it's a dead product now. I'm replying on the list to the rest of your message, as I never meant to take it off list in the first place. That was another result of rushing. - -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIEJZmVVuXXpU7hpMRAqmmAJ9xE1ihAivJvLQ7Oahj9cu8jg88nwCfbPTc 8RK52LjazBm30+vG/i4LXyg= =yw1f -----END PGP SIGNATURE-----

1 0