From joab at inbox.com Fri Oct 1 03:22:42 2010 From: joab at inbox.com (wilby) Date: Thu, 30 Sep 2010 18:22:42 -0700 (PDT) Subject: [Mailman-Users] Mailman 2.1.12 can't accept email from Thunerbird 3.1.4 help! Message-ID: <29853820.post@talk.nabble.com> For some reason a very recent update to Thunderbird 3.1.4 email has suddenly stopped the Mailman 2.1.12 account, that I administer, from accepting my messages. I can send to this Mailman account from non-Tbird email software. Help needed badly. Thanks, Wilby -- View this message in context: http://old.nabble.com/Mailman-2.1.12-can%27t-accept-email-from-Thunerbird-3.1.4--help%21-tp29853820p29853820.html Sent from the Mailman - Users mailing list archive at Nabble.com. From mark at msapiro.net Fri Oct 1 04:02:22 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 30 Sep 2010 19:02:22 -0700 Subject: [Mailman-Users] Digest options as email attachments In-Reply-To: <252D260E27384A84AE6DF0CD44AB2872@userPC> Message-ID: Danny hendrawan wrote: > >I'd like to have my members list who choose to receive a digest mail to >receive similar to the digest of this list i.e. with summary page and >attachment emails for each topic. > >I looked at 'digest options' but cannot find anything to enable this option. >Where can I set it up? What you want is called a MIME format digest. This is not a list option. it is a "by member" option. You can set the default for new members by setting Digest options -> mime_is_default_digest to MIME, but for existing members you either need to uncheck the member's 'plain' box on Membership Management... -> Membership List or the member has to select MIME digests on her member options page. Note that the plain/MIME setting only affects digests and is irrelevant for non-digest members. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Oct 1 04:07:54 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 30 Sep 2010 19:07:54 -0700 Subject: [Mailman-Users] Mailman 2.1.12 can't accept email from Thunerbird3.1.4 help! In-Reply-To: <29853820.post@talk.nabble.com> Message-ID: wilby wrote: > >For some reason a very recent update to Thunderbird 3.1.4 email has suddenly >stopped the Mailman 2.1.12 account, that I administer, from accepting my >messages. Exactly what happens when you send a post from T-bird. If it bounces or if Mailman rejects it, what does the bounce/rejection message say? If it is held for approval, what does the admindb interface say is the reason? If it just disappears, and you have access to the server's logs, what does the MTA log and Mailman's vette log say, and if you don't have access to those logs, ask the server admins or the hosting provider. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Oct 1 06:47:31 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 30 Sep 2010 21:47:31 -0700 Subject: [Mailman-Users] /etc/mailman/aliases.db In-Reply-To: Message-ID: Troy Campbell wrote: >For some reason when I moved the mailman configuration a few months ago >I had to add /etc/mailman/aliases to the alias_maps e.g.,: > >alias_maps = hash:/etc/aliases > > hash:/etc/mailman/aliases > > > >whereas on the old installation I didn't. Since this is on a server >that can fail over to another server that has the IMAP configuration >which > >doesn't need /etc/mailman/aliases I would like to see if there is a >workaround so that they both have the same postfix configuration. Sorry > >if this is more of a postfix question but I didn't get an answer on >their list yet. Postfix doesn't do IMAP, nor do other MTAs, so I'm not sure if the IMAP reference is relevant. Is the Mailman package on the other server the same as the one on this server which is clearly a downstream package if aliases are in /etc/mailman. >Basically trying to get the /etc/postfix/main.cf files identical so I >don't have to manage the differences and bounce postfix on failover. If Mailman is installed the same way from the same package on both servers, and there are no non-mailman differences in the Postfix configuration, there should be no reason why they couldn't use the same main.cf. On the other hand if the two servers have different Mailman packages, then their Postfix requirements could be different. On the third hand, this could be simply that on the other server, Mailman's aliases were copied to /etc/aliases so /etc/mailman/aliases wasn't needed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Oct 1 07:04:18 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 30 Sep 2010 22:04:18 -0700 Subject: [Mailman-Users] Hold.py fails in hold_for_approval In-Reply-To: <4CA40C11.6040106@whiteoaks.com> Message-ID: Morris Jones wrote: >I recently discovered that all of my moderated posts have been failing, >most likely because my mailman version was older than my python version. > >This is the error: > >Sep 29 20:52:12 2010 (5588) Uncaught runner exception: unbound method >reason_notice() must be called with ModeratedMemberPost instance as >first argument (got nothing instead) >Sep 29 20:52:12 2010 (5588) Traceback (most recent call last): > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop > filebase) > File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 169, in _onefile > 'Dequeuing message destined for missing list: %s', > File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in >_dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in >_dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/usr/lib/mailman/Mailman/Handlers/Moderate.py", line 67, in process > msgdata['sender'] = sender Something is really wrong with this traceback. The above line actually is line 67 in Mailman/Handlers/Moderate.py in all Mailman versions since 2.1.9, but the actual lines that were executed here must have been Hold.hold_for_approval(mlist, msg, msgdata, ModeratedMemberPost) which are the lines following msgdata['sender'] = sender > File "/usr/lib/mailman/Mailman/Handlers/Hold.py", line 212, in >hold_for_approval > if usersubject: Similarly here. The line that threw the exception must have been reason = Utils.wrap(exc.reason_notice()) which comes 10 lines later. >TypeError: unbound method reason_notice() must be called with >ModeratedMemberPost instance as first argument (got nothing instead) > >Sep 29 20:52:12 2010 (5588) SHUNTING: >1285818731.142787+9ceab13e8549d5e6690de9b9880bef9c7c238b8d > >My python version is 2.6.2, and I've been very careful to be sure that >older pythons are not in the PATH. > >The first thing I did was update mailman to 2.1.14, which seemed to go >just fine, but I still see this error. The timestamps of all the >executables are current, and were overwritten by the new versions. The >"version' command reports 2.1.14. > >Actually ... > >I see now that the actual line of code changed after installing the new >version of mailman. Where it used to be: > > reason = Utils.wrap(exc.reason_notice()) > >it's now ... > > if usersubject: > >So it would appear that I need to get python to recompile all the pyc >files, is that correct? How do I do that? I tried touching the .py >files to make them newer ... No. It appears that you didn't stop Mailman before installing 2.1.14 and then start it after. Try restarting Mailman now and see if that helps -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From joab at inbox.com Fri Oct 1 04:22:54 2010 From: joab at inbox.com (wilby) Date: Thu, 30 Sep 2010 19:22:54 -0700 (PDT) Subject: [Mailman-Users] Mailman 2.1.12 can't accept email from Thunerbird3.1.4 help! In-Reply-To: References: <29853820.post@talk.nabble.com> Message-ID: <29854205.post@talk.nabble.com> Mark Sapiro-3 wrote: > > wilby wrote: >> >>For some reason a very recent update to Thunderbird 3.1.4 email has suddenly >>stopped the Mailman 2.1.12 account, that I administer, from accepting my >>messages. > > > Exactly what happens when you send a post from T-bird. If it bounces or > if Mailman rejects it, what does the bounce/rejection message say? > > If it is held for approval, what does the admindb interface say is the > reason? > > If it just disappears, and you have access to the server's logs, what > does the MTA log and Mailman's vette log say, and if you don't have > access to those logs, ask the server admins or the hosting provider. > > -- > Mark: > > The message is sent back to me (and only to me). > It starts with the rejection message under "privacy Options", "rejection > to moderated members". > > Then it presents me with a .eml file that contains me original message to > MM. > > At the end is an attachment of my original email. > > The text in the open .eml file clearly shows a blank space just before the > approve: pw line. > > approve: pw rather than > approve: pw > > The original message does not get in the archive. > I tried a message with the approve: pw on the second line, leaving the > first line blank. This did ge in the archive, but didn't get sent. > > Does this help? > > Thanks > Wilby > > > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com > > -- View this message in context: http://old.nabble.com/Mailman-2.1.12-can%27t-accept-email-from-Thunerbird-3.1.4--help%21-tp29853820p29854205.html Sent from the Mailman - Users mailing list archive at Nabble.com. From mark at msapiro.net Fri Oct 1 08:33:15 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 30 Sep 2010 23:33:15 -0700 Subject: [Mailman-Users] Mailman 2.1.12 can't accept email fromThunerbird3.1.4 help! In-Reply-To: <29854205.post@talk.nabble.com> Message-ID: wilby wrote: >> >> The message is sent back to me (and only to me). >> It starts with the rejection message under "privacy Options", "rejection >> to moderated members". >> >> Then it presents me with a .eml file that contains me original message to >> MM. >> >> At the end is an attachment of my original email. >> >> The text in the open .eml file clearly shows a blank space just before the >> approve: pw line. >> >> approve: pw rather than >> approve: pw >> >> The original message does not get in the archive. So you are relying on pre-approving the post, and since it is not properly pre-approved (T-Bird's fault somehow) it is rejected, presumably per your list settings. >> I tried a message with the approve: pw on the second line, leaving the >> first line blank. This did ge in the archive, but didn't get sent. If it got to the archive, it reached the list and should have been sent. The only reason it wouldn't have been sent is an error in outgoing message processing or OutgoingRunner not running. If other mail is being sent from Mailman, the problem is not that OutgoingRunner is not running, so it would have to be an exception in outgoing message processing which can only be diagnosed with information from Mailman's error log. One thing you can do is set T-Bird to allow you to add the Approved: pw as an actual header. To do this, in T-Bird go to Tools -> Options -> Advanced -> Config Editor and set mail.compose.other.header to the string "Approved" (or "Approve" if you prefer) without the quotes. Then, when composing a message, the button that sets To:, Cc:, Bcc:, etc for an address will have an Approved: choice and you can chose Approved and enter the pw on that line. Beyond that, this is a T-Bird issue, and I don't know how to fix it except that I use T-Bird 3.1.4 sometimes, and I have used most prior versions of T-Bird, and I can't recall ever seeing T-Bird "space stuff" the first line of a message. Do you have any plug-ins that might be doing this? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From troy.campbell at fedex.com Fri Oct 1 16:57:20 2010 From: troy.campbell at fedex.com (Troy Campbell) Date: Fri, 1 Oct 2010 09:57:20 -0500 Subject: [Mailman-Users] Mailman-Users Digest, Vol 80, Issue 2 In-Reply-To: References: Message-ID: Thanks again Mark. I've decided to manage it with separate postfix config files (one for when there is no service group on a server, one for when there is just the Mailman service group, one for when there is just the IMAP service group and one when there is both) and just restart postfix and monitor it as part of VCS as it doesn't make sense to merge config files for other reasons anyway. Regards, Troy -----Original Message----- Troy Campbell wrote: >For some reason when I moved the mailman configuration a few months ago >I had to add /etc/mailman/aliases to the alias_maps e.g.,: > >alias_maps = hash:/etc/aliases > > hash:/etc/mailman/aliases > > > >whereas on the old installation I didn't. Since this is on a server >that can fail over to another server that has the IMAP configuration >which > >doesn't need /etc/mailman/aliases I would like to see if there is a >workaround so that they both have the same postfix configuration. >Sorry > >if this is more of a postfix question but I didn't get an answer on >their list yet. Postfix doesn't do IMAP, nor do other MTAs, so I'm not sure if the IMAP reference is relevant. Is the Mailman package on the other server the same as the one on this server which is clearly a downstream package if aliases are in /etc/mailman. >Basically trying to get the /etc/postfix/main.cf files identical so I >don't have to manage the differences and bounce postfix on failover. If Mailman is installed the same way from the same package on both servers, and there are no non-mailman differences in the Postfix configuration, there should be no reason why they couldn't use the same main.cf. On the other hand if the two servers have different Mailman packages, then their Postfix requirements could be different. On the third hand, this could be simply that on the other server, Mailman's aliases were copied to /etc/aliases so /etc/mailman/aliases wasn't needed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From joab at inbox.com Fri Oct 1 21:27:22 2010 From: joab at inbox.com (wilby) Date: Fri, 1 Oct 2010 12:27:22 -0700 (PDT) Subject: [Mailman-Users] Mailman 2.1.12 can't accept email fromThunerbird3.1.4 help! In-Reply-To: References: <29853820.post@talk.nabble.com> <29854205.post@talk.nabble.com> Message-ID: <29859305.post@talk.nabble.com> Mark Sapiro-3 wrote: > > wilby wrote: >>> >>> The message is sent back to me (and only to me). >>> It starts with the rejection message under "privacy Options", "rejection >>> to moderated members". >>> >>> Then it presents me with a .eml file that contains me original message >>> to >>> MM. >>> >>> At the end is an attachment of my original email. >>> >>> The text in the open .eml file clearly shows a blank space just before >>> the >>> approve: pw line. >>> >>> approve: pw rather than >>> approve: pw >>> >>> The original message does not get in the archive. > > > So you are relying on pre-approving the post, and since it is not > properly pre-approved (T-Bird's fault somehow) it is rejected, > presumably per your list settings. > > >>> I tried a message with the approve: pw on the second line, leaving the >>> first line blank. This did ge in the archive, but didn't get sent. > > > If it got to the archive, it reached the list and should have been > sent. The only reason it wouldn't have been sent is an error in > outgoing message processing or OutgoingRunner not running. If other > mail is being sent from Mailman, the problem is not that > OutgoingRunner is not running, so it would have to be an exception in > outgoing message processing which can only be diagnosed with > information from Mailman's error log. > > One thing you can do is set T-Bird to allow you to add the Approved: pw > as an actual header. To do this, in T-Bird go to Tools -> Options -> > Advanced -> Config Editor and set mail.compose.other.header to the > string "Approved" (or "Approve" if you prefer) without the quotes. > Then, when composing a message, the button that sets To:, Cc:, Bcc:, > etc for an address will have an Approved: choice and you can chose > Approved and enter the pw on that line. > > Beyond that, this is a T-Bird issue, and I don't know how to fix it > except that I use T-Bird 3.1.4 sometimes, and I have used most prior > versions of T-Bird, and I can't recall ever seeing T-Bird "space > stuff" the first line of a message. Do you have any plug-ins that > might be doing this? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com > > Hi Mark: Thank you for this information, I'd probably never would have figured this out myself. Your suggestion to add an "Approved" option in the header is exactly the solution to my problem. It worked the very first time I tried it. If it was later in the day I'd probably be sipping a cool beer. Peace, Wilby PS: A T-Bird forum user told me that the next TB version, 3.1.5, has fixed this leading blank space issue. Now I don't really care if they have or not. -- View this message in context: http://old.nabble.com/Mailman-2.1.12-can%27t-accept-email-from-Thunerbird-3.1.4--help%21-tp29853820p29859305.html Sent from the Mailman - Users mailing list archive at Nabble.com. From guillaume.chartrand at collanaud.qc.ca Fri Oct 1 17:23:54 2010 From: guillaume.chartrand at collanaud.qc.ca (Guillaume Chartrand) Date: Fri, 1 Oct 2010 15:23:54 +0000 Subject: [Mailman-Users] after new installation 403 Forbiden Access Message-ID: <23A9B7CAD2EEE64F8FC5BF1E8AB5345F09594C@csr-exch.Intranet.Collanaud.Qc.Ca> I know it's been posted many time but all the answer wasn't apply to me. So I will ask it another time I run Red Hat Enterprise Linux 4 AS I installed Python 2.6.6 I installed Apache 2.2.16 I download and try to install mailman 2.1.14 All the installation steps working fine, but when I try to create the first list with the web interface I've got the 403 Forbidden page Whenever I try to reach http://mywebserver.com/mailman/create admin listinfo I've always get the 403 error. Here is the output of the command ls -la /usr/local/mailman/cgi-bin/ drwxrwsr-x 2 root mailman 4096 Sep 30 14:57 . drwxrwsr-x 20 root mailman 4096 Sep 30 14:57 .. -rwxr-sr-x 1 root mailman 15658 Sep 30 14:57 admin -rwxr-sr-x 1 root mailman 15662 Sep 30 14:57 admindb -rwxr-sr-x 1 root mailman 15662 Sep 30 14:57 confirm -rwxr-sr-x 1 root mailman 15662 Sep 30 14:57 create -rwxr-sr-x 1 root mailman 15666 Sep 30 14:57 edithtml -rwxr-sr-x 1 root mailman 15666 Sep 30 14:57 listinfo -rwxr-sr-x 1 root mailman 15662 Sep 30 14:57 options -rwxr-sr-x 1 root mailman 15662 Sep 30 14:57 private -rwxr-sr-x 1 root mailman 15662 Sep 30 14:57 rmlist -rwxr-sr-x 1 root mailman 15662 Sep 30 14:57 roster -rwxr-sr-x 1 root mailman 15666 Sep 30 14:57 subscribe Here's some of the httpd.conf line Alias /pipermail/ /usr/local/mailman/archives/public/ ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" AddDefaultCharset Off Options Indexes FollowSymlinks MultiViews AllowOverride None Order allow,deny Allow from all The apache runs with the user nobody And this is an other command to see if right seems ok ls -la /usr/local/mailman/lists/ total 12 drwxrwsr-x 3 root mailman 4096 Oct 1 08:39 . drwxrwsr-x 20 root mailman 4096 Sep 30 14:57 .. drwxrwsr-x 2 root mailman 4096 Oct 1 09:00 mailman I've modified the mm_cfg.py also and add these line DEFAULT_EMAIL_HOST = 'listes2.collanaud.qc.ca' DEFAULT_URL_HOST = 'listes2.collanaud.qc.ca' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) So what i'm doing wrong. Thanks for helping me resolve that Guillaume From tyler at beloit.edu Fri Oct 1 17:06:42 2010 From: tyler at beloit.edu (Tim Tyler) Date: Fri, 1 Oct 2010 10:06:42 -0500 Subject: [Mailman-Users] can't delete users in a list? Message-ID: Mailman experts, We are running Mailman 2.1.9 on a Centos 5.5 system. One of the list managers must have done some copy and pasting of addresses into their list as now she can?t delete certain entries. When I look at the error logs, I see a potential hidden character at the end of the address. I can?t unsubscribe or mass remove the user and I can?t remove them using the command line. Is there a trick for trying to delete a potentially corrupt address from a list short of starting the list over from scratch? Tim Tyler Network Engineer Beloit College From mark at msapiro.net Sat Oct 2 18:15:30 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 2 Oct 2010 09:15:30 -0700 Subject: [Mailman-Users] after new installation 403 Forbiden Access In-Reply-To: <23A9B7CAD2EEE64F8FC5BF1E8AB5345F09594C@csr-exch.Intranet.Collanaud.Qc.Ca> Message-ID: Guillaume Chartrand wrote: > >All the installation steps working fine, but when I try to create the first list with the web interface I've got the 403 Forbidden page >Whenever I try to reach >http://mywebserver.com/mailman/create > admin > listinfo > >I've always get the 403 error. This has nothing to do with Mailman per se. Your web server is not allowing you to access the Mailman CGIs. >Alias /pipermail/ /usr/local/mailman/archives/public/ >ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > > AddDefaultCharset Off > Options Indexes FollowSymlinks MultiViews > AllowOverride None > Order allow,deny > Allow from all > You apparently have some allow/deny directives that don't allow access and which apply to /usr/local/mailman/cgi-bin/. This is most likely the Apache default that denies access to the root directory and thus requires subordinate directories to be explicitly allowed. Try adding Order allow,deny Allow from all -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Oct 2 18:24:49 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 2 Oct 2010 09:24:49 -0700 Subject: [Mailman-Users] can't delete users in a list? In-Reply-To: Message-ID: Tim Tyler wrote: > > Is there a trick for trying to delete a potentially corrupt >address from a list short of starting the list over from scratch? See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From b19141 at anl.gov Mon Oct 4 21:02:28 2010 From: b19141 at anl.gov (Barry Finkel) Date: Mon, 4 Oct 2010 14:02:28 -0500 (CDT) Subject: [Mailman-Users] Mailman 2.1.14 Multiple Owner(s) Patch - Problem In-Reply-To: Mail from 'Mark Sapiro ' dated: Tue, 28 Sep 2010 14:45:00 -0700 Message-ID: <20101004190228.DFA2B4D3F8@britaine.cis.anl.gov> I wrote last week about a problem I was having with Mailman 2.1.14 and Mark Sapiro's multi-owner patch. I am not going to include my mail and Mark's response here; I will summarize. I created some test lists, and each had only one owner. Mark could not reproduce the error. I ran some more tests, and I discovered that the procedure I was using /usr/sbin/newlist ... config_list -i ... was in error because the list template file I was using in the config_list -i ... had not been changed to include the second owner address, so the second address created by the /usr/sbin/newlist ... command was indeed in the list configuration until the subsequent config_list -i ... reset the list owner to a single address. I created a new test list with an updated template file, and the new list does indeed have two owners. Since the patch code does not check the second and subsequent owner e-mail addresses for syntax, the patch is not ready to be put into the production code, I assume. ---------------------------------------------------------------------- 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 240, Room 5.B.8 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From rosenbaumlm at ornl.gov Mon Oct 4 20:51:30 2010 From: rosenbaumlm at ornl.gov (Rosenbaum, Larry M.) Date: Mon, 04 Oct 2010 14:51:30 -0400 Subject: [Mailman-Users] Approved message is discarded Message-ID: We are running Mailman v2.1.13 on Solaris 9 Sparc. We have a list with about 13,000 members that we currently have "emergency moderation" turned on because of previous problems with reply storms. Today somebody sent a message to the list, which (of course) was held for moderation. The list owner approved it, but then it disappeared. Here is what was in the "vette" log: Oct 04 10:35:12 2010 (21271) XXXXX_Cohorts post from michael.xxxx at xxxx.edu held, message-id=<2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu>: Post to moderated list Oct 04 10:38:26 2010 (5774) held message approved, message-id: <2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu> Oct 04 10:38:28 2010 (21271) Message discarded, msgid: 2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu What caused the message to be discarded after it was approved? Thanks, Larry M. Rosenbaum Oak Ridge National Laboratory From Ralf.Hildebrandt at charite.de Mon Oct 4 22:06:55 2010 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Mon, 4 Oct 2010 22:06:55 +0200 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: References: Message-ID: <20101004200655.GD4959@charite.de> * Rosenbaum, Larry M. : > We are running Mailman v2.1.13 on Solaris 9 Sparc. We have a list with about 13,000 members that we currently have "emergency moderation" turned on because of previous problems with reply storms. > > Today somebody sent a message to the list, which (of course) was held for moderation. The list owner approved it, but then it disappeared. Here is what was in the "vette" log: > > Oct 04 10:35:12 2010 (21271) XXXXX_Cohorts post from michael.xxxx at xxxx.edu held, message-id=<2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu>: Post to moderated list > Oct 04 10:38:26 2010 (5774) held message approved, message-id: <2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu> > Oct 04 10:38:28 2010 (21271) Message discarded, msgid: 2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu The first and third line seem to match, but why is the size for the second line only a 5k instead of 20k? (if the number in () is actually the size) -- Ralf Hildebrandt Gesch?ftsbereich IT | Abteilung Netzwerk Charit? - Universit?tsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt at charite.de | http://www.charite.de From mark at msapiro.net Mon Oct 4 22:21:08 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 04 Oct 2010 13:21:08 -0700 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <20101004200655.GD4959@charite.de> References: <20101004200655.GD4959@charite.de> Message-ID: <4CAA3734.5000506@msapiro.net> On 10/4/2010 1:06 PM, Ralf Hildebrandt wrote: > * Rosenbaum, Larry M. : >> >> Oct 04 10:35:12 2010 (21271) XXXXX_Cohorts post from michael.xxxx at xxxx.edu held, message-id=<2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu>: Post to moderated list >> Oct 04 10:38:26 2010 (5774) held message approved, message-id: <2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu> >> Oct 04 10:38:28 2010 (21271) Message discarded, msgid: 2034674BF9D4714BAE35B22BF073EEF402E70996 at MS-XXXX.xxxx.edu > > The first and third line seem to match, but why is the size for the > second line only a 5k instead of 20k? (if the number in () is actually > the size) The number in parens is thi PID of the process that made the log entry. In the first and third cases, this is IncomingRunner and in the second it is the admindb CGI. It has nothing to do with message size. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Oct 4 22:24:37 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 04 Oct 2010 13:24:37 -0700 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: References: Message-ID: <4CAA3805.1080204@msapiro.net> On 10/4/2010 11:51 AM, Rosenbaum, Larry M. wrote: > > What caused the message to be discarded after it was approved? Most likely, Content filtering -> filter_action is Discard, and there was nothing left of the message after content filtering. E.g. the message was text/html or maybe multipart/related and the list doesn't accept that content type. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cwieland at uci.edu Mon Oct 4 22:35:42 2010 From: cwieland at uci.edu (Con Wieland) Date: Mon, 4 Oct 2010 13:35:42 -0700 Subject: [Mailman-Users] number of subscribers Message-ID: Does anybody already have a script to get the total number of subscribers across all the lists on a system? Con Wieland Office of Information Technology University of California at Irvine From adam-mailman at amyl.org.uk Mon Oct 4 22:54:12 2010 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Mon, 4 Oct 2010 21:54:12 +0100 Subject: [Mailman-Users] number of subscribers In-Reply-To: References: Message-ID: <20101004205412.GP2315@hendricks.amyl.org.uk> On Mon, Oct 04, 2010 at 01:35:42PM -0700, Con Wieland wrote: > Does anybody already have a script to get the total number of > subscribers across all the lists on a system? something like: list_lists -b | while read L; do echo "List is ${L}"; list_members ${L} | wc -l ; done perhaps? If you're after something more complicated, that handles archives and bits, http://hendricks.amyl.org.uk/~adam/tmp/list-stats may be of interest (one day I'll get around to fixing up my repo's browsey thing) -- "We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary." -- Booker T. Washington From mark at msapiro.net Mon Oct 4 22:57:11 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 4 Oct 2010 13:57:11 -0700 Subject: [Mailman-Users] number of subscribers In-Reply-To: Message-ID: Con Wieland wrote: >Does anybody already have a script to get the total number of >subscribers across all the lists on a system? If you want the total number of unique addresses in all your lists, you can get that with bin/find_member . | grep "found in:" | wc -l If you want the sum over all lists of the number of members in each list, you can do (for l in `bin/list_lists --bare`; do bin/list_members $l; done)| wc -l -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dsl225 at gmail.com Mon Oct 4 17:30:34 2010 From: dsl225 at gmail.com (dsl225 at gmail.com) Date: Mon, 4 Oct 2010 16:30:34 +0100 Subject: [Mailman-Users] Content Filtering options Message-ID: <008801cb63d9$2624a560$726df020$@com> I've read many messages regarding this section's configuration, but, I have to confess, the more I read the less I understand. Probably not the only one... Would it be possible for someone to explain simply and clearly which configuration settings should I use in this section in order to obtain: - HTML messages (yes, right, I NEED to have HTML messages for this list) - Footers being part of the body of the same HTML message - and not as attachments Many thanks in advance! From mark at msapiro.net Tue Oct 5 02:03:13 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 4 Oct 2010 17:03:13 -0700 Subject: [Mailman-Users] Content Filtering options In-Reply-To: <008801cb63d9$2624a560$726df020$@com> Message-ID: dsl225 at gmail.com wrote: > >Would it be possible for someone to explain simply and clearly which >configuration settings should I use in this section in order to obtain: > >- HTML messages (yes, right, I NEED to have HTML messages for this list) >- Footers being part of the body of the same HTML message - and not as >attachments This is not a content filtering question. It has to do with the way list footers are added to messages which are not (after content filtering) a single part, text/plain message. In short if you have an HTML part in the message the footer will always be added as a separate part. See the FAQ at for more about this issue including some links to contributed patches/work-arounds. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ckoeber at gmail.com Tue Oct 5 03:29:57 2010 From: ckoeber at gmail.com (Christopher Koeber) Date: Mon, 4 Oct 2010 21:29:57 -0400 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: <4CA3E9B2.4070001@msapiro.net> References: <4CA3E9B2.4070001@msapiro.net> Message-ID: OK, I tried much of the suggestions given before and I made progress! When I actually send a message to the list I get this: --------------------------------------------- Oct 4 20:49:04 WTS-ZIMBRA postfix/virtual[9636]: 25656321552: to=< allstudents at wts-zimbra.wesleysem.edu>, orig_to=< allstudents at students.wesleyseminary.edu>, relay=virtual, delay=406, delays=0.36/405/0/0.12, dsn=4.2.0, status=deferred (delivery failed to mailbox //"|/usr/lib64/mailman/mail/mailman post allstudents": unable to create lock file //"|/usr/lib64/mailman/mail/mailman post allstudents".lock: No such file or directory) Oct 4 20:49:09 WTS-ZIMBRA postfix/virtual[9635]: 0635D321524: to=< allstudents at wts-zimbra.wesleysem.edu>, orig_to=< allstudents at students.wesleyseminary.edu>, relay=virtual, delay=566, delays=72/489/0/5, dsn=4.2.0, status=deferred (delivery failed to mailbox //"|/usr/lib64/mailman/mail/mailman post allstudents": unable to create lock file //"|/usr/lib64/mailman/mail/mailman post allstudents".lock: No such file or directory) --------------------------------------------- Notice that instead of piping to the mailman service I get this "unable to create lockfile" problem. Shouldn't postfix actually pipe to the program mailman? Anyone seen that before? Thanks. Regards, Christopher Koeber On Wed, Sep 29, 2010 at 9:36 PM, Mark Sapiro wrote: [...] > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From mark at msapiro.net Tue Oct 5 05:08:14 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 4 Oct 2010 20:08:14 -0700 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: Message-ID: Christopher Koeber wrote: >OK, I tried much of the suggestions given before and I made progress! > >When I actually send a message to the list I get this: > >--------------------------------------------- >Oct 4 20:49:04 WTS-ZIMBRA postfix/virtual[9636]: 25656321552: to=< >allstudents at wts-zimbra.wesleysem.edu>, orig_to=< >allstudents at students.wesleyseminary.edu>, relay=virtual, delay=406, >delays=0.36/405/0/0.12, dsn=4.2.0, status=deferred (delivery failed to >mailbox //"|/usr/lib64/mailman/mail/mailman post allstudents": unable to >create lock file //"|/usr/lib64/mailman/mail/mailman post allstudents".lock: >No such file or directory) >Oct 4 20:49:09 WTS-ZIMBRA postfix/virtual[9635]: 0635D321524: to=< >allstudents at wts-zimbra.wesleysem.edu>, orig_to=< >allstudents at students.wesleyseminary.edu>, relay=virtual, delay=566, >delays=72/489/0/5, dsn=4.2.0, status=deferred (delivery failed to mailbox >//"|/usr/lib64/mailman/mail/mailman post allstudents": unable to create lock >file //"|/usr/lib64/mailman/mail/mailman post allstudents".lock: No such >file or directory) >--------------------------------------------- > >Notice that instead of piping to the mailman service I get this "unable to >create lockfile" problem. > >Shouldn't postfix actually pipe to the program mailman? The basic issue is you are delivering via relay=virtual rather than relay=local. Only the local LDA knows how to pipe to a command. The virtual LDA is trying to deliver to the mailbox named "|/usr/lib64/mailman/mail/mailman post allstudents" which clearly doesn't work. I think the problem is students.wesleyseminary.edu is a virtual_mailbox_domain whereas it needs to be a virtual_alias_domain. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ckoeber at gmail.com Tue Oct 5 07:42:37 2010 From: ckoeber at gmail.com (Christopher Kurtis Koeber) Date: Tue, 5 Oct 2010 01:42:37 -0400 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: References: Message-ID: <004801cb6450$1ed64030$5c82c090$@com> See below. > -----Original Message----- > From: Mark Sapiro [mailto:mark at msapiro.net] > Sent: Monday, October 04, 2010 11:08 PM > To: Christopher Koeber; mailman-users at python.org > Subject: Re: [Mailman-Users] Postfix and Mailman ... > > Christopher Koeber wrote: > > >OK, I tried much of the suggestions given before and I made > progress! > > > >When I actually send a message to the list I get this: > > > >--------------------------------------------- > >Oct 4 20:49:04 WTS-ZIMBRA postfix/virtual[9636]: 25656321552: to=< > >allstudents at wts-zimbra.wesleysem.edu>, orig_to=< > >allstudents at students.wesleyseminary.edu>, relay=virtual, delay=406, > >delays=0.36/405/0/0.12, dsn=4.2.0, status=deferred (delivery failed > to > >mailbox //"|/usr/lib64/mailman/mail/mailman post allstudents": > unable to > >create lock file //"|/usr/lib64/mailman/mail/mailman post > allstudents".lock: > >No such file or directory) > >Oct 4 20:49:09 WTS-ZIMBRA postfix/virtual[9635]: 0635D321524: to=< > >allstudents at wts-zimbra.wesleysem.edu>, orig_to=< > >allstudents at students.wesleyseminary.edu>, relay=virtual, delay=566, > >delays=72/489/0/5, dsn=4.2.0, status=deferred (delivery failed to > mailbox > >//"|/usr/lib64/mailman/mail/mailman post allstudents": unable to > create lock > >file //"|/usr/lib64/mailman/mail/mailman post allstudents".lock: No > such > >file or directory) > >--------------------------------------------- > > > >Notice that instead of piping to the mailman service I get this > "unable to > >create lockfile" problem. > > > >Shouldn't postfix actually pipe to the program mailman? > > > The basic issue is you are delivering via relay=virtual rather than > relay=local. Only the local LDA knows how to pipe to a command. The > virtual LDA is trying to deliver to the mailbox named > "|/usr/lib64/mailman/mail/mailman post allstudents" which clearly > doesn't work. > > I think the problem is students.wesleyseminary.edu is a > virtual_mailbox_domain whereas it needs to be a > virtual_alias_domain. > [Christopher Kurtis Koeber] Thanks. The problem is that using the virtual transport was the only way I could get the OpenLDAP setup I had to work with postfix. Is there a way to conditionally use transports? Say, if one email address is found via a rule to use a local transport versus the virtual one? > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. > Dylan From ckoeber at gmail.com Tue Oct 5 15:19:36 2010 From: ckoeber at gmail.com (Christopher Koeber) Date: Tue, 5 Oct 2010 09:19:36 -0400 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: <004801cb6450$1ed64030$5c82c090$@com> References: <004801cb6450$1ed64030$5c82c090$@com> Message-ID: Also, in additional to my question on whether the transport can be rules based I am wondering if it is possible to switch everything to the local transport but still support virtual domains. This is necessary for my setup. Thank you for your time. Regards, Christopher Koeber On Oct 5, 2010 1:43 AM, "Christopher Kurtis Koeber" wrote: > See below. > >> -----Original Message----- >> From: Mark Sapiro [mailto:mark at msapiro.net] >> Sent: Monday, October 04, 2010 11:08 PM >> To: Christopher Koeber; mailman-users at python.org >> Subject: Re: [Mailman-Users] Postfix and Mailman ... >> >> Christopher Koeber wrote: >> >> >OK, I tried much of the suggestions given before and I made >> progress! >> > >> >When I actually send a message to the list I get this: >> > >> >--------------------------------------------- >> >Oct 4 20:49:04 WTS-ZIMBRA postfix/virtual[9636]: 25656321552: to=< >> >allstudents at wts-zimbra.wesleysem.edu>, orig_to=< >> >allstudents at students.wesleyseminary.edu>, relay=virtual, delay=406, >> >delays=0.36/405/0/0.12, dsn=4.2.0, status=deferred (delivery failed >> to >> >mailbox //"|/usr/lib64/mailman/mail/mailman post allstudents": >> unable to >> >create lock file //"|/usr/lib64/mailman/mail/mailman post >> allstudents".lock: >> >No such file or directory) >> >Oct 4 20:49:09 WTS-ZIMBRA postfix/virtual[9635]: 0635D321524: to=< >> >allstudents at wts-zimbra.wesleysem.edu>, orig_to=< >> >allstudents at students.wesleyseminary.edu>, relay=virtual, delay=566, >> >delays=72/489/0/5, dsn=4.2.0, status=deferred (delivery failed to >> mailbox >> >//"|/usr/lib64/mailman/mail/mailman post allstudents": unable to >> create lock >> >file //"|/usr/lib64/mailman/mail/mailman post allstudents".lock: No >> such >> >file or directory) >> >--------------------------------------------- >> > >> >Notice that instead of piping to the mailman service I get this >> "unable to >> >create lockfile" problem. >> > >> >Shouldn't postfix actually pipe to the program mailman? >> >> >> The basic issue is you are delivering via relay=virtual rather than >> relay=local. Only the local LDA knows how to pipe to a command. The >> virtual LDA is trying to deliver to the mailbox named >> "|/usr/lib64/mailman/mail/mailman post allstudents" which clearly >> doesn't work. >> >> I think the problem is students.wesleyseminary.edu is a >> virtual_mailbox_domain whereas it needs to be a >> virtual_alias_domain. >> > [Christopher Kurtis Koeber] > > Thanks. The problem is that using the virtual transport was the only way I > could get the OpenLDAP setup I had to work with postfix. Is there a way to > conditionally use transports? Say, if one email address is found via a rule > to use a local transport versus the virtual one? > >> -- >> Mark Sapiro The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. >> Dylan > > From mark at msapiro.net Tue Oct 5 16:38:20 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 5 Oct 2010 07:38:20 -0700 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: <004801cb6450$1ed64030$5c82c090$@com> Message-ID: Christopher Kurtis Koeber wrote: > >Is there a way to >conditionally use transports? Say, if one email address is found via a rule >to use a local transport versus the virtual one? That's what transport_maps is for. See the FAQ at for a way to automate this for Mailman lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ckoeber at gmail.com Tue Oct 5 16:58:14 2010 From: ckoeber at gmail.com (Christopher Koeber) Date: Tue, 5 Oct 2010 10:58:14 -0400 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: References: <004801cb6450$1ed64030$5c82c090$@com> Message-ID: On Tue, Oct 5, 2010 at 10:38 AM, Mark Sapiro wrote: > Christopher Kurtis Koeber wrote: > > > >Is there a way to > >conditionally use transports? Say, if one email address is found via a > rule > >to use a local transport versus the virtual one? > > > > That's what transport_maps is for. See the FAQ at > for a way to automate this for Mailman > lists. > > Thanks so much. I didn't see this in the link but will I need to switch the "local transport" piece in Postfix to local? I am guessing not, as that is what transport_maps is doing for me, right? Regards, Christopher Koeber -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From mark at msapiro.net Tue Oct 5 17:16:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 5 Oct 2010 08:16:40 -0700 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: Message-ID: Christopher Koeber wrote: >Also, in additional to my question on whether the transport can be rules >based I am wondering if it is possible to switch everything to the local >transport but still support virtual domains. You can support virtual domains with the local transport, but in general, they need to be virtual_alias_domains, not virtual_mailbox_domains. Whether that works in your case depends on your exact configuration/requirements and is probably beyond the scope of this list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Tue Oct 5 17:24:37 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 5 Oct 2010 08:24:37 -0700 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: Message-ID: Christopher Koeber wrote: > >Thanks so much. I didn't see this in the link but will I need to switch the >"local transport" piece in Postfix to local? > >I am guessing not, as that is what transport_maps is doing for me, right? Yes. local_transport is a default. transport_maps overrides it for any address found therein. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lists at pbw.id.au Wed Oct 6 04:26:53 2010 From: lists at pbw.id.au (Peter B. West) Date: Wed, 6 Oct 2010 12:26:53 +1000 Subject: [Mailman-Users] virtual-mailman not generated Message-ID: <65BCC931-8738-42C9-A893-2F84359CC3EA@pbw.id.au> Hi, No doubt I'm overlooking something which is obvious to experienced users, but for a newcomer to both mail server setup and mailman setup, is opaque. When I run genaliases, I get aliases, but not virtual-mailman. The host that I'm generating this on is eunuch.pbw.id.au (to the outside world.) The virtual host I want to use with postfix-to-mailman.py is lists.eunuch.pbw.id.au. Any idea what I'm doing wrong? Here's my postfix config. ----------------------------------- # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings #delay_warning_time = 4h readme_directory = /usr/share/doc/postfix # TLS parameters smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key smtpd_use_tls=yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. myhostname = eunuch.pbw.id.au mydomain = pbw.id.au proxy_interfaces = 60.241.99.30 alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydestination = $myhostname, localhost.localdomain, , localhost relayhost = mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 192.168.1.0/8 relay_domains = lists.eunuch.pbw.id.au relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman virtual_alias_domains = lists.eunuch.pbw.id.au virtual_alias_maps = hash:/etc/postfix/virtual transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all html_directory = /usr/share/doc/postfix/html --------------------------------------------------- Here's my mm_cfg.py =================================================== # -*- python -*- # Copyright (C) 1998,1999,2000 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA # 02110-1301 USA """This is the module which takes your site-specific settings. From a raw distribution it should be copied to mm_cfg.py. If you already have an mm_cfg.py, be careful to add in only the new settings you want. The complete set of distributed defaults, with annotation, are in ./Defaults. In mm_cfg, override only those you want to change, after the from Defaults import * line (see below). Note that these are just default settings - many can be overridden via the admin and user interfaces on a per-list or per-user basis. Note also that some of the settings are resolved against the active list setting by using the value as a format string against the list-instance-object's dictionary - see the distributed value of DEFAULT_MSG_FOOTER for an example.""" ####################################################### # Here's where we get the distributed defaults. # from Defaults import * ############################################################## # Put YOUR site-specific configuration below, in mm_cfg.py . # # See Defaults.py for explanations of the values. # #------------------------------------------------------------- # The name of the list Mailman uses to send password reminders # and similar. Don't change if you want mailman-owner to be # a valid local part. MAILMAN_SITE_LIST = 'mailman' #------------------------------------------------------------- # If you change these, you have to configure your http server # accordingly (Alias and ScriptAlias directives in most httpds) DEFAULT_URL_PATTERN = 'http://%s/mailman/' PRIVATE_ARCHIVE_URL = '/mailman/private' IMAGE_LOGOS = '/images/mailman/' #------------------------------------------------------------- # Default domain for email addresses of newly created MLs DEFAULT_EMAIL_HOST = 'localhost.localdomain' #------------------------------------------------------------- # Default host for web interface of newly created MLs DEFAULT_URL_HOST = 'localhost.localdomain' #------------------------------------------------------------- # Required when setting any of its arguments. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) #------------------------------------------------------------- # The default language for this server. DEFAULT_SERVER_LANGUAGE = 'en' #------------------------------------------------------------- # Iirc this was used in pre 2.1, leave it for now USE_ENVELOPE_SENDER = 0 # Still used? #------------------------------------------------------------- # Unset send_reminders on newly created lists DEFAULT_SEND_REMINDERS = 0 #------------------------------------------------------------- # Uncomment this if you configured your MTA such that it # automatically recognizes newly created lists. # (see /usr/share/doc/mailman/README.Exim4.Debian or # /usr/share/mailman/postfix-to-mailman.py) # MTA=None # Misnomer, suppresses alias output on newlist #------------------------------------------------------------- # Uncomment if you use Postfix virtual domains (but not # postfix-to-mailman.py), but be sure to see # /usr/share/doc/mailman/README.Debian first. MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.eunuch.pbw.id.au'] DEB_LISTMASTER = 'postmaster at lists.eunuch.pbw.id.au' #------------------------------------------------------------- # Uncomment if you want to filter mail with SpamAssassin. For # more information please visit this website: # http://www.jamesh.id.au/articles/mailman-spamassassin/ # GLOBAL_PIPELINE.insert(1, 'SpamAssassin') # Note - if you're looking for something that is imported from mm_cfg, but you # didn't find it above, it's probably in /usr/lib/mailman/Mailman/Defaults.py. ============================================================================== Peter West "Nicodemus said to him, 'How can this be?'" From andykerich at gmail.com Tue Oct 5 14:57:20 2010 From: andykerich at gmail.com (Andrew Kerich) Date: Tue, 5 Oct 2010 15:57:20 +0300 Subject: [Mailman-Users] Running multiple instances of mailman on the same server Message-ID: Hi Guys, Has anyone implemented the above. please assist with sample configs of your apache and MTA (exim for my case) Kerich. From mark at msapiro.net Wed Oct 6 17:10:41 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 6 Oct 2010 08:10:41 -0700 Subject: [Mailman-Users] virtual-mailman not generated In-Reply-To: <65BCC931-8738-42C9-A893-2F84359CC3EA@pbw.id.au> Message-ID: Peter B. West wrote: > >No doubt I'm overlooking something which is obvious to experienced users, but for a newcomer to both mail server setup and mailman setup, is opaque. > >When I run genaliases, I get aliases, but not virtual-mailman. Because you have no lists whose host_name attribute matches one of the entries in POSTFIX_STYLE_VIRTUAL_DOMAINS (i.e. lists.eunuch.pbw.id.au). >The host that I'm generating this on is eunuch.pbw.id.au (to the outside world.) > >The virtual host I want to use with postfix-to-mailman.py is lists.eunuch.pbw.id.au. > >Any idea what I'm doing wrong? First of all, if you are using postfix-to-mailman.py, you don't want/need Mailman to generate any aliases or virtual mappings. These are mutually exclusive ways of delivering mail to Mailman. Also please note that this list is the primary support for GNU Mailman as distributed by the Mailman project. If you use a downstream package, we will generally try to help, but your primary support resources should be those provided by your packager. >Here's my postfix config. See comments inserted below. Note that this config doesn't reference Mailman's aliases or virtual-mailman at all which is correct for postfix-to-mailman.py. [...] > >alias_maps = hash:/etc/aliases >alias_database = hash:/etc/aliases > >mydestination = $myhostname, localhost.localdomain, , localhost > >relayhost = > >mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 192.168.1.0/8 > >relay_domains = lists.eunuch.pbw.id.au >relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman > >virtual_alias_domains = lists.eunuch.pbw.id.au You don't want the above. The domain is a relay domain, not a virtual alias domain. >virtual_alias_maps = hash:/etc/postfix/virtual > >transport_maps = hash:/etc/postfix/transport Presumably (hopefully) there is an entry in /etc/postfix/transport that specifies a "mailman" transport for the lists.eunuch.pbw.id.au, and an entry in master.cf defining this transport >mailman_destination_recipient_limit = 1 > > >mailbox_size_limit = 0 >recipient_delimiter = + >inet_interfaces = all >html_directory = /usr/share/doc/postfix/html >--------------------------------------------------- > > >Here's my mm_cfg.py Again see comments: [...] > >#------------------------------------------------------------- ># Default domain for email addresses of newly created MLs >DEFAULT_EMAIL_HOST = 'localhost.localdomain' Should be DEFAULT_EMAIL_HOST = 'lists.eunuch.pbw.id.au' This is why your lists don't get created with the correct host_name >#------------------------------------------------------------- ># Default host for web interface of newly created MLs >DEFAULT_URL_HOST = 'localhost.localdomain' This should probably be DEFAULT_URL_HOST = 'lists.eunuch.pbw.id.au' or whatever host name you use to access Mailman's web interface. It should not be localhost as it is the host in URLs exposed to users to access their options page, list archives, etc. >#------------------------------------------------------------- ># Required when setting any of its arguments. >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > >#------------------------------------------------------------- [...] >#------------------------------------------------------------- ># Uncomment this if you configured your MTA such that it ># automatically recognizes newly created lists. ># (see /usr/share/doc/mailman/README.Exim4.Debian or ># /usr/share/mailman/postfix-to-mailman.py) ># MTA=None # Misnomer, suppresses alias output on newlist > >#------------------------------------------------------------- ># Uncomment if you use Postfix virtual domains (but not ># postfix-to-mailman.py), but be sure to see ># /usr/share/doc/mailman/README.Debian first. >MTA='Postfix' As it says, you don't specify MTA='Postfix' if you use postfix_to_mailman.py. You want MTA = None >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.eunuch.pbw.id.au'] And the above is irrelevant because virtual-mailman is not used. >DEB_LISTMASTER = 'postmaster at lists.eunuch.pbw.id.au' > [...] -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From geoff at QuiteLikely.com Wed Oct 6 20:45:38 2010 From: geoff at QuiteLikely.com (Geoff Shang) Date: Wed, 6 Oct 2010 20:45:38 +0200 (IST) Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: References: Message-ID: On Mon, 4 Oct 2010, Mark Sapiro wrote: > I think the problem is students.wesleyseminary.edu is a > virtual_mailbox_domain whereas it needs to be a virtual_alias_domain. Maybe I'm missing something, but I've never had trouble using virtual mailbox domains to host Mailman lists. In fact, I'm not sure that I've ever done anything else. Geoff. From ckoeber at gmail.com Thu Oct 7 00:14:15 2010 From: ckoeber at gmail.com (Christopher Koeber) Date: Wed, 6 Oct 2010 18:14:15 -0400 Subject: [Mailman-Users] Postfix and Mailman ... In-Reply-To: References: Message-ID: On Wed, Oct 6, 2010 at 2:45 PM, Geoff Shang wrote: > On Mon, 4 Oct 2010, Mark Sapiro wrote: > > I think the problem is students.wesleyseminary.edu is a >> virtual_mailbox_domain whereas it needs to be a virtual_alias_domain. >> > > Maybe I'm missing something, but I've never had trouble using virtual > mailbox domains to host Mailman lists. In fact, I'm not sure that I've ever > done anything else. > > Geoff. > I tried it and it never gets to the local pipes for the mailman processes. Essentially Postfix still believes that anything going to the mailman system is going to the setups for virtual_mailbox_domain. So you end up needing to do a transport map, which is what I am experimenting with. > > ------------------------------------------------------ > Mailman-Users mailing list Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://wiki.list.org/x/AgA3 > Security Policy: http://wiki.list.org/x/QIA9 > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/ckoeber%40gmail.com > From tanstaafl at libertytrek.org Thu Oct 7 22:51:54 2010 From: tanstaafl at libertytrek.org (Tanstaafl) Date: Thu, 07 Oct 2010 16:51:54 -0400 Subject: [Mailman-Users] User Preferences Message-ID: <4CAE32EA.1030705@libertytrek.org> How does one go about defining which user prefs are available to users when they log into their users page? Is it possible to pick and choose? Hopefully without having to dog into the code? Thanks... From mark at msapiro.net Thu Oct 7 23:50:45 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 7 Oct 2010 14:50:45 -0700 Subject: [Mailman-Users] User Preferences In-Reply-To: <4CAE32EA.1030705@libertytrek.org> Message-ID: Tanstaafl wrote: >How does one go about defining which user prefs are available to users >when they log into their users page? > >Is it possible to pick and choose? Hopefully without having to dog into >the code? The user options page is built from the options.html template. If you want to remove certain settings from the page, you can make sitewide, domainwide or list specific edited version of the options.html template with those settings removed. See the FAQ at for info on where to save the edited template. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From tanstaafl at libertytrek.org Fri Oct 8 21:02:52 2010 From: tanstaafl at libertytrek.org (Tanstaafl) Date: Fri, 08 Oct 2010 15:02:52 -0400 Subject: [Mailman-Users] User Preferences In-Reply-To: References: Message-ID: <4CAF6ADC.50307@libertytrek.org> On 2010-10-07 5:50 PM, Mark Sapiro wrote: > Tanstaafl wrote: >> How does one go about defining which user prefs are available to users >> when they log into their users page? >> >> Is it possible to pick and choose? Hopefully without having to dog into >> the code? > The user options page is built from the options.html template. If you > want to remove certain settings from the page, you can make sitewide, > domainwide or list specific edited version of the options.html > template with those settings removed. Thanks Mark... IS pretty much every option available as a per user pref? I'm specifically interested in the inclusion (or not) of [Subject Tags]... > See the FAQ at for info on where to save > the edited template. Thanks again... :) From tanstaafl at libertytrek.org Fri Oct 8 22:25:58 2010 From: tanstaafl at libertytrek.org (Tanstaafl) Date: Fri, 08 Oct 2010 16:25:58 -0400 Subject: [Mailman-Users] User Preferences In-Reply-To: <4CAF7618.8030106@msapiro.net> References: <4CAF6ADC.50307@libertytrek.org> <4CAF7618.8030106@msapiro.net> Message-ID: <4CAF7E56.4040506@libertytrek.org> On 2010-10-08 3:50 PM, Mark Sapiro wrote: > No. The subject prefix is a list setting an there is no user option to > enable/disable it. > > User options include those things which are check boxes on the admin > Membership list page plus topics subscription and that's about it. The > default options page shows them all. You can remove some of those from > the template, but you can't add anything. Ok, thanks... Any chance this could be a per user option in MM3? The reason I ask is some people like them, and some people don't, and it would be nice if the list setting could be the default, then each user could override it by defining their own, or just disabling it completely... From mark at msapiro.net Fri Oct 8 21:50:48 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 08 Oct 2010 12:50:48 -0700 Subject: [Mailman-Users] User Preferences In-Reply-To: <4CAF6ADC.50307@libertytrek.org> References: <4CAF6ADC.50307@libertytrek.org> Message-ID: <4CAF7618.8030106@msapiro.net> On 10/8/2010 12:02 PM, Tanstaafl wrote: > > IS pretty much every option available as a per user pref? I'm > specifically interested in the inclusion (or not) of [Subject Tags]... No. The subject prefix is a list setting an there is no user option to enable/disable it. User options include those things which are check boxes on the admin Membership list page plus topics subscription and that's about it. The default options page shows them all. You can remove some of those from the template, but you can't add anything. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Oct 9 06:26:49 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 8 Oct 2010 21:26:49 -0700 Subject: [Mailman-Users] User Preferences In-Reply-To: <4CAF7E56.4040506@libertytrek.org> Message-ID: Tanstaafl wrote: > >Any chance this could be a per user option in MM3? The reason I ask is >some people like them, and some people don't, and it would be nice if >the list setting could be the default, then each user could override it >by defining their own, or just disabling it completely... It could be considered for MM3. The problem is it would essentially (at least if enabled) require that the list be personalized in that each user potentially wants a message with a different subject. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pub88 at numericable.fr Sat Oct 9 18:11:56 2010 From: pub88 at numericable.fr (pub88) Date: Sat, 9 Oct 2010 18:11:56 +0200 Subject: [Mailman-Users] Traffic information for each list Message-ID: <8538AFBC047D410F917360D4FEB05738@ACERCORE2> Bonjour, I have several list using mailman and I want to know. Size of archive Traffic (monthly) generated by the list (SMPTP I suppose) for each list I use plesk to manage the domain which is hosted by OVH. Any ideas ? or where I can found this information ? TIA Ives From mark at msapiro.net Sun Oct 10 15:58:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 10 Oct 2010 06:58:32 -0700 Subject: [Mailman-Users] Traffic information for each list In-Reply-To: <8538AFBC047D410F917360D4FEB05738@ACERCORE2> Message-ID: pub88 wrote: > >I have several list using mailman and I want to know. >Size of archive If you mean size as in disk space du --summarize /path/to/archives/private/LISTNAME and/or ls -l /path/to/archives/private/LISTNAME.mbox/LISTNAME.mbox If you mean number of messages grep "^From " /path/to/archives/private/LISTNAME.mbox/LISTNAME.mbox \ | wc -l >Traffic (monthly) generated by the list (SMPTP I suppose) >for each list You can get this information from Mailman's 'smtp' log. See the mmdsr script for an example of reporting from Mailman's logs. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at bradakis.com Mon Oct 11 02:25:13 2010 From: mark at bradakis.com (Mark J Bradakis) Date: Sun, 10 Oct 2010 18:25:13 -0600 Subject: [Mailman-Users] A rare moment Message-ID: <4CB25969.6030907@bradakis.com> I've been running various automotive related mailing lists, web pages, FTP sites and such for over twenty years. It is a labor of love, not a means of making money, so tending to outstanding requests is not top priority. But I've had a nasty cold the last few days, and have spent some time working on Team.Net since I can't do much else besides sit at the computer, sniffle and cough. With 60 or so lists and 12,000+ subscribers around the globe it is easy to get behind. I've seen 10,000 or more held messages at times. Today, though: autox /local/mailman/teamnet/data 131 :: ls held* ls: No match. This could be the first time in many years I have *no* outstanding requests to deal with. Sweet. mjb. From khillo100 at hotmail.com Mon Oct 11 23:46:47 2010 From: khillo100 at hotmail.com (Khalil Abbas) Date: Mon, 11 Oct 2010 21:46:47 +0000 Subject: [Mailman-Users] bounce unsubscriptions.. Message-ID: Hi, many people get removed from my lists due to bounces and I recieve many complaints that they re-subscribe then get kicked out again.. my bounce processing settings are as follows: The maximum member bounce score before the member's subscription is disabled. This value can be a floating point number = 5.0 The number of days after which a member's bounce information is discarded, if no new bounces have been received in the interim. This value must be an integer = 7 How many Your Membership Is Disabled warnings a disabled member should get before their address is removed from the mailing list. Set to 0 to immediately remove an address from the list once their bounce score exceeds the threshold. This value must be an integer =0 The number of days between sending the Your Membership Is Disabled warnings. This value must be an integer = 7 is there anything wromg with that ?? thanks.. From mark at msapiro.net Tue Oct 12 05:19:10 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 11 Oct 2010 20:19:10 -0700 Subject: [Mailman-Users] bounce unsubscriptions.. In-Reply-To: Message-ID: Khalil Abbas wrote: > >many people get removed from my lists due to bounces and I recieve many complaints that they re-subscribe then get kicked out again.. my bounce processing settings are as follows: > > > >The maximum member bounce score before the member's subscription is disabled. This value can be a floating point number = 5.0 > > > >The number of days after which a member's bounce information is discarded, if no new bounces have been received in the interim. This value must be an integer = 7 > > > >How many Your Membership Is Disabled warnings a disabled member should get before their address is removed from the mailing list. Set to 0 to immediately remove an address from the list once their bounce score exceeds the threshold. This value must be an integer =0 Consider raising this to 2 or 3, so that they get a few warnings at 1 week intervals between disable and unsubscribe. >The number of days between sending the Your Membership Is Disabled warnings. This value must be an integer = 7 Make sure that bounce_notify_owner_on_disable is Yes so you get a notice containing the triggering bounce when a member is disabled by bounce processing. Then, using this information plus possible information from Mailman's smtp-failure log and the MTA logs, figure out why apparently valid addresses are bouncing and fix the underlying problem. If the problem is "spam" rejection by the receiving ISP, make sure the the member whitlists your list and/or complains to her ISP. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rmcleran at ix.netcom.com Tue Oct 12 16:20:51 2010 From: rmcleran at ix.netcom.com (Bob McLeran) Date: Tue, 12 Oct 2010 10:20:51 -0400 Subject: [Mailman-Users] How to get list of subscribers in moderated status In-Reply-To: <45AED6A7.60204@ix.netcom.com> References: <45AED6A7.60204@ix.netcom.com> Message-ID: <4CB46EC3.3030000@ix.netcom.com> On the list I administer as owner, I'd like to get a list of all subscribers who are in a moderated status. Is there any way to do this using the "who password" email command line? <><><><><><><><><><><><>Mozilla Thunderbird<><><><><><><><><><> Bob McLeran and Judy Young Manatee Cove Marina MV Sanderling Patrick Air Force Base DeFever 41 Trawler Melbourne, Florida Blog: http://sanderlingcruise2010.blogspot.com/ Pics: http://tinyurl.com/yjx2vky& http://tinyurl.com/yhxjvas From mark at msapiro.net Wed Oct 13 16:10:47 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 13 Oct 2010 07:10:47 -0700 Subject: [Mailman-Users] How to get list of subscribers in moderated status In-Reply-To: <4CB46EC3.3030000@ix.netcom.com> Message-ID: Bob McLeran wrote: > On the list I administer as owner, I'd like to get a list of all >subscribers who are in a moderated status. > >Is there any way to do this using the "who password" email command line? No. The email who command doesn't distinguish moderated/unmoderated members. See the FAQ at for links to a script which can run on your workstation and get this invormation via the web admin interface. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From borjariesgo at gmail.com Thu Oct 14 14:30:58 2010 From: borjariesgo at gmail.com (Borja Riesgo Juan) Date: Thu, 14 Oct 2010 14:30:58 +0200 Subject: [Mailman-Users] Forbide sending mails from users differents Message-ID: I would like to create a list called all at corodiocesano.es. I would like to forbid the sending of mails from everybody except the administrator users. i would like to know an automatic method to subscribe new users using php code. best regards, Borja Riesgo From mark at msapiro.net Thu Oct 14 15:37:01 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 14 Oct 2010 06:37:01 -0700 Subject: [Mailman-Users] Forbide sending mails from users differents In-Reply-To: Message-ID: Borja Riesgo Juan wrote: >I would like to create a list called all at corodiocesano.es. I would like to >forbid the sending of mails from everybody except the administrator users. See the FAQ at . > i >would like to know an automatic method to subscribe new users using php >code. See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From aaron at campusactivism.org Fri Oct 15 05:39:05 2010 From: aaron at campusactivism.org (Aaron Kreider) Date: Thu, 14 Oct 2010 23:39:05 -0400 Subject: [Mailman-Users] Mailman Crashes Regularly Message-ID: <4CB7CCD9.5040905@campusactivism.org> I'm getting regular mailman crashes every 2-4 weeks. I've had 4 so far. I'm running a centos VPS with mailman 2.1.13. What is the best way to restart mailman? I've been restarting the entire vps, which obviously is a bad idea. What can I do to prevent this from happening? Here is the error log entries from when it crashed: Oct 13 01:30:23 2010 mailmanctl(19680): No child with pid: 3683 Oct 13 01:30:23 2010 mailmanctl(19680): [Errno 3] No such process Oct 13 01:30:23 2010 mailmanctl(19680): Stale pid file removed. Oct 13 01:30:23 2010 mailmanctl(19694): Traceback (most recent call last): Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 548, in ? Oct 13 01:30:23 2010 mailmanctl(19694): main() Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 367, in main Oct 13 01:30:23 2010 mailmanctl(19694): check_for_site_list() Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 277, in check_for_site_list Oct 13 01:30:23 2010 mailmanctl(19694): sitelist = MailList(sitelistname, lock=0) Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 115, in __init__ Oct 13 01:30:23 2010 mailmanctl(19694): execfile(filename, dict) Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py", line 5, in ? Oct 13 01:30:23 2010 mailmanctl(19694): from Mailman.MysqlMemberships import MysqlMemberships Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MysqlMemberships.py", line 49, in ? Oct 13 01:30:23 2010 mailmanctl(19694): import MySQLdb Oct 13 01:30:23 2010 mailmanctl(19694): File "build/bdist.linux-x86_64/egg/MySQLdb/__init__.py", line 19, in ? Oct 13 01:30:23 2010 mailmanctl(19694): File "build/bdist.linux-x86_64/egg/_mysql.py", line 7, in ? Oct 13 01:30:23 2010 mailmanctl(19694): File "build/bdist.linux-x86_64/egg/_mysql.py", line 4, in __bootstrap__ Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 881, in resource_filename Oct 13 01:30:23 2010 mailmanctl(19694): return get_provider(package_or_requirement).get_resource_filename( Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1351, in get_resource_filename Oct 13 01:30:23 2010 mailmanctl(19694): self._extract_resource(manager, self._eager_to_zip(name)) Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1372, in _extract_resource Oct 13 01:30:23 2010 mailmanctl(19694): real_path = manager.get_cache_path( Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 962, in get_cache_path Oct 13 01:30:23 2010 mailmanctl(19694): self.extraction_error() Oct 13 01:30:23 2010 mailmanctl(19694): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 928, in extraction_error Oct 13 01:30:23 2010 mailmanctl(19694): raise err Oct 13 01:30:23 2010 mailmanctl(19694): pkg_resources . ExtractionError : Can't extract file(s) to egg cache The following error occurred while trying to extract file(s) to the Python egg cache: [Errno 13] Permission denied: '/root/.python-eggs' The Python egg cache directory is currently set to: /root/.python-eggs Perhaps your account does not have write access to this directory? You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory. Oct 13 01:30:23 2010 mailmanctl(19694): Oct 13 01:31:11 2010 mailmanctl(22029): PID unreadable in: /usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid Oct 13 01:31:11 2010 mailmanctl(22029): [Errno 2] No such file or directory: '/usr/local/cpanel/3rdparty/mailman/data/master-qrunner.pid' Oct 13 01:31:11 2010 mailmanctl(22029): Is qrunner even running? Oct 13 01:31:14 2010 mailmanctl(22123): Traceback (most recent call last): Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 548, in ? Oct 13 01:31:14 2010 mailmanctl(22123): main() Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 367, in main Oct 13 01:31:14 2010 mailmanctl(22123): check_for_site_list() Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 277, in check_for_site_list Oct 13 01:31:14 2010 mailmanctl(22123): sitelist = MailList(sitelistname, lock=0) Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 115, in __init__ Oct 13 01:31:14 2010 mailmanctl(22123): execfile(filename, dict) Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py", line 5, in ? Oct 13 01:31:14 2010 mailmanctl(22123): from Mailman.MysqlMemberships import MysqlMemberships Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/local/cpanel/3rdparty/mailman/Mailman/MysqlMemberships.py", line 49, in ? Oct 13 01:31:14 2010 mailmanctl(22123): import MySQLdb Oct 13 01:31:14 2010 mailmanctl(22123): File "build/bdist.linux-x86_64/egg/MySQLdb/__init__.py", line 19, in ? Oct 13 01:31:14 2010 mailmanctl(22123): File "build/bdist.linux-x86_64/egg/_mysql.py", line 7, in ? Oct 13 01:31:14 2010 mailmanctl(22123): File "build/bdist.linux-x86_64/egg/_mysql.py", line 4, in __bootstrap__ Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 881, in resource_filename Oct 13 01:31:14 2010 mailmanctl(22123): return get_provider(package_or_requirement).get_resource_filename( Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1351, in get_resource_filename Oct 13 01:31:14 2010 mailmanctl(22123): self._extract_resource(manager, self._eager_to_zip(name)) Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 1372, in _extract_resource Oct 13 01:31:14 2010 mailmanctl(22123): real_path = manager.get_cache_path( Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 962, in get_cache_path Oct 13 01:31:14 2010 mailmanctl(22123): self.extraction_error() Oct 13 01:31:14 2010 mailmanctl(22123): File "/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", line 928, in extraction_error Oct 13 01:31:14 2010 mailmanctl(22123): raise err Oct 13 01:31:14 2010 mailmanctl(22123): pkg_resources . ExtractionError : Can't extract file(s) to egg cache The following error occurred while trying to extract file(s) to the Python egg cache: [Errno 13] Permission denied: '/root/.python-eggs' The Python egg cache directory is currently set to: /root/.python-eggs Perhaps your account does not have write access to this directory? You can change the cache directory by setting the PYTHON_EGG_CACHE environment variable to point to an accessible directory. Oct 13 01:31:14 2010 mailmanctl(22123): -- Energy Justice Communities Map Developer - http://www.energyjustice.net/map From mark at msapiro.net Fri Oct 15 14:53:36 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Oct 2010 05:53:36 -0700 Subject: [Mailman-Users] Mailman Crashes Regularly In-Reply-To: <4CB7CCD9.5040905@campusactivism.org> Message-ID: Aaron Kreider wrote: > I'm getting regular mailman crashes every 2-4 weeks. I've had 4 so >far. I'm running a centos VPS with mailman 2.1.13. > >What is the best way to restart mailman? I've been restarting the >entire vps, which obviously is a bad idea. What can I do to prevent >this from happening? The best way to restart Mailman depends on whether just mailmanctl or also all the qrunners die. If all the qrunners are gone, you can just run Mailman's "bin/mailmanctl start" or whatever cPanel voodoo starts the Mailman service. If there are still qrunner processes running when mailmanctl dies, see the FAQ at . (see below) >Here is the error log entries from when it crashed: > > > > > >Oct 13 01:30:23 2010 mailmanctl(19680): No child with pid: 3683 >Oct 13 01:30:23 2010 mailmanctl(19680): [Errno 3] No such process >Oct 13 01:30:23 2010 mailmanctl(19680): Stale pid file removed. >Oct 13 01:30:23 2010 mailmanctl(19694): Traceback (most recent call last): >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 548, in ? >Oct 13 01:30:23 2010 mailmanctl(19694): main() >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 367, in main >Oct 13 01:30:23 2010 mailmanctl(19694): check_for_site_list() >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/local/cpanel/3rdparty/mailman/bin/mailmanctl", line 277, in >check_for_site_list >Oct 13 01:30:23 2010 mailmanctl(19694): sitelist = >MailList(sitelistname, lock=0) >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/local/cpanel/3rdparty/mailman/Mailman/MailList.py", line 115, in >__init__ >Oct 13 01:30:23 2010 mailmanctl(19694): execfile(filename, dict) >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py", line 5, in ? >Oct 13 01:30:23 2010 mailmanctl(19694): from >Mailman.MysqlMemberships import MysqlMemberships Why do you have /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py which imports MysqlMemberships? As far as I know, this is not something that cPanel Mailman does by default? (see below) >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/local/cpanel/3rdparty/mailman/Mailman/MysqlMemberships.py", line >49, in ? >Oct 13 01:30:23 2010 mailmanctl(19694): import MySQLdb >Oct 13 01:30:23 2010 mailmanctl(19694): File >"build/bdist.linux-x86_64/egg/MySQLdb/__init__.py", line 19, in ? >Oct 13 01:30:23 2010 mailmanctl(19694): File >"build/bdist.linux-x86_64/egg/_mysql.py", line 7, in ? >Oct 13 01:30:23 2010 mailmanctl(19694): File >"build/bdist.linux-x86_64/egg/_mysql.py", line 4, in __bootstrap__ >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", >line 881, in resource_filename >Oct 13 01:30:23 2010 mailmanctl(19694): return >get_provider(package_or_requirement).get_resource_filename( >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", >line 1351, in get_resource_filename >Oct 13 01:30:23 2010 mailmanctl(19694): >self._extract_resource(manager, self._eager_to_zip(name)) >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", >line 1372, in _extract_resource >Oct 13 01:30:23 2010 mailmanctl(19694): real_path = >manager.get_cache_path( >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", >line 962, in get_cache_path >Oct 13 01:30:23 2010 mailmanctl(19694): self.extraction_error() >Oct 13 01:30:23 2010 mailmanctl(19694): File >"/usr/lib/python2.4/site-packages/setuptools-0.6c12dev_r80622-py2.4.egg/pkg_resources.py", >line 928, in extraction_error >Oct 13 01:30:23 2010 mailmanctl(19694): raise err >Oct 13 01:30:23 2010 mailmanctl(19694): pkg_resources . ExtractionError >: Can't extract file(s) to egg cache > >The following error occurred while trying to extract file(s) to the >Python egg >cache: > > [Errno 13] Permission denied: '/root/.python-eggs' > >The Python egg cache directory is currently set to: > > /root/.python-eggs > >Perhaps your account does not have write access to this directory? You can >change the cache directory by setting the PYTHON_EGG_CACHE environment >variable to point to an accessible directory. [...] The underlying issue here is that Python's MySQLdb was apparently installed by root in a way that the the Python egg cache directory is not writeable by the Mailman process. You can get rid of the above errors by simply removing /usr/local/cpanel/3rdparty/mailman/lists/mailman/extend.py and perhaps any other /usr/local/cpanel/3rdparty/mailman/lists/*/extend.py files, but this will defeat your use of MysqlMemberships.py, but since it doesn't work anyway, and maybe is only installed for the site list, that shouldn't be too much of an issue. Also, please read the FAQ at . Finally, it is not clear to me that the above error is from the crash. It seems to me it would occur whenever mailmanctl starts. Is this all that's in Mailman's error log? What's in Mailman's qrunner log? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Alessandro.Bruchi at iit.it Fri Oct 15 15:46:31 2010 From: Alessandro.Bruchi at iit.it (Alessandro Bruchi) Date: Fri, 15 Oct 2010 15:46:31 +0200 Subject: [Mailman-Users] mailman 2.1.14 new features In-Reply-To: References: <4C62E62D.1080901@gmail.com> Message-ID: <3E8C1B0F5B2161419B02BEC08536162548A4F34995@IITMXMBX.iit.local> Does mailman 2.1.14 solve the virtual domain problem? In particular the ability to create: list at domain1 list at domain2 I read that the new version support virtual domains. Do you know when mailman 2.1.14 will be included as package in some debian distribution? Thank you Alessandro From rclemings at gmail.com Fri Oct 15 16:39:06 2010 From: rclemings at gmail.com (Russell Clemings) Date: Fri, 15 Oct 2010 07:39:06 -0700 Subject: [Mailman-Users] Mailman Crashes Regularly Message-ID: The cPanel command I believe is: /usr/local/cpanel/3rdparty/mailman/bin/mailmanctl restart From: Aaron Kreider > To: mailman-users at python.org > Date: Thu, 14 Oct 2010 23:39:05 -0400 > Subject: [Mailman-Users] Mailman Crashes Regularly > I'm getting regular mailman crashes every 2-4 weeks. I've had 4 so far. > I'm running a centos VPS with mailman 2.1.13. > > What is the best way to restart mailman? I've been restarting the entire > vps, which obviously is a bad idea. What can I do to prevent this from > happening? > > From mark at msapiro.net Fri Oct 15 16:47:17 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Oct 2010 10:47:17 -0400 Subject: [Mailman-Users] mailman 2.1.14 new features In-Reply-To: <3E8C1B0F5B2161419B02BEC08536162548A4F34995@IITMXMBX.iit.local> References: <4C62E62D.1080901@gmail.com> <3E8C1B0F5B2161419B02BEC08536162548A4F34995@IITMXMBX.iit.local> Message-ID: "Alessandro Bruchi" wrote: >Does mailman 2.1.14 solve the virtual domain problem? >In particular the ability to create: > >list at domain1 >list at domain2 No. >I read that the new version support virtual domains. That support is in MM 3. It is not yet ready for production use. >Do you know when mailman 2.1.14 will be included as package in some debian distribution? No. -- Mark Sapiro - mark at msapiro.net Sent from my Android phone with K-9 Mail. Please excuse my brevity. From joonho at a9.com Fri Oct 15 20:52:47 2010 From: joonho at a9.com (Syn, Joonho) Date: Fri, 15 Oct 2010 11:52:47 -0700 Subject: [Mailman-Users] one line command to change generic_nonmember_action Message-ID: I'm writing a simplified mailman dashboard page for my company's internal use and one of the functions we want is to be able to toggle the generic_nonmember_action for any given list. Has anyone out there devised a one line command which will allow this? From cmallon at earthlink.net Fri Oct 15 23:22:28 2010 From: cmallon at earthlink.net (cmallon) Date: Fri, 15 Oct 2010 14:22:28 -0700 Subject: [Mailman-Users] mailman configuration issues? Message-ID: <7465A161-62E3-4A9B-8394-E0F2DE62361D@earthlink.net> HI, This may seem like a dumb question but I've been seeing a lot of this in my mail.logs All the messages are being delivered and there are no bad recipients in the list. Could there be a misconfiguration somewhere? I'd like to write a script that extracts information from the keyword bounces, but don't want to get data from legitimate emails. Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 1984F691A316: from=, size=3824, nrcpt=6 (queue active) Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 8D1F4691A31D: from=, size=3958, nrcpt=1 (queue active) Oct 15 10:53:45 apps25 postfix/qmgr[16897]: 59760691A45E: from=, size=5939, nrcpt=1 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: C16EC691B4C7: from=, size=4830, nrcpt=6 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: 66308691B4DE: from=, size=4964, nrcpt=1 (queue active) Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: from=, size=4174, nrcpt=4 (queue active) Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 1984F691A316: from=, size=3824, nrcpt=6 (queue active) Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 8D1F4691A31D: from=, size=3958, nrcpt=1 (queue active) Oct 15 10:53:45 apps25 postfix/qmgr[16897]: 59760691A45E: from=, size=5939, nrcpt=1 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: C16EC691B4C7: from=, size=4830, nrcpt=6 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: 66308691B4DE: from=, size=4964, nrcpt=1 (queue active) Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: from=, size=4174, nrcpt=4 (queue active) If I grep one of the message ids and take a closer look: mail:/var/mail root# grep C5760691BA29 /var/log/mail.log Oct 15 11:08:27 apps25 postfix/smtpd[18204]: C5760691BA29: client=localhost[127.0.0.1] Oct 15 11:08:28 apps25 postfix/cleanup[18211]: C5760691BA29: message-id=<17120997.1287166102753.JavaMail.resin at server12> Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: from=, size=4174, nrcpt=4 (queue active) Oct 15 11:08:28 apps25 postfix/pipe[18230]: C5760691BA29: to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/pipe[18188]: C5760691BA29: to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/pipe[18241]: C5760691BA29: to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/pipe[18230]: C5760691BA29: to=, orig_to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: removed It appears that all the messages have been delivered. There no bad recipients. Is the "my-list-bounces" as reported in my logs normal? Its reported in the logs the same way for all the lists -- every mailman email that goes out looks like this. Thank you for your time From geoff at QuiteLikely.com Fri Oct 15 23:53:48 2010 From: geoff at QuiteLikely.com (Geoff Shang) Date: Fri, 15 Oct 2010 23:53:48 +0200 (IST) Subject: [Mailman-Users] mailman configuration issues? In-Reply-To: <7465A161-62E3-4A9B-8394-E0F2DE62361D@earthlink.net> References: <7465A161-62E3-4A9B-8394-E0F2DE62361D@earthlink.net> Message-ID: On Fri, 15 Oct 2010, cmallon wrote: > This may seem like a dumb question but I've been seeing a lot of this in > my mail.logs All the messages are being delivered and there are no bad > recipients in the list. Could there be a misconfiguration somewhere? > I'd like to write a script that extracts information from the keyword > bounces, but don't want to get data from legitimate emails. > Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 1984F691A316: > from=, size=3824, nrcpt=6 (queue > active) This is normal. List messages are sent out as -bounces so that if one does indeed bounce, it gets sent back to an address that can do something about it. Geoff. From frank.vandamme at gmail.com Fri Oct 15 15:31:13 2010 From: frank.vandamme at gmail.com (Frank Van Damme) Date: Fri, 15 Oct 2010 15:31:13 +0200 Subject: [Mailman-Users] can't display list config Message-ID: <4CB857A1.6030403@gmail.com> Hi list, I'm getting errors while trying to dump the config of a mailing list to a text file. /usr/lib/mailman/bin/config_list -o listname listname [...] # For backwards compatibility with Mailman 1.1, if the regexp does not # contain an `@', then the pattern is matched against just the local # part of the recipient address. If that match fails, or if the pattern # does contain an `@', then the pattern is matched against the entire # recipient address. # # Matching against the local part is deprecated; in a future release, # the pattern will always be matched against the entire recipient # address. acceptable_aliases = Traceback (most recent call last): File "/usr/lib/mailman/bin/config_list", line 362, in main() File "/usr/lib/mailman/bin/config_list", line 355, in main do_output(listname, outfile) File "/usr/lib/mailman/bin/config_list", line 131, in do_output do_list_categories(mlist, k, subcat, outfp) File "/usr/lib/mailman/bin/config_list", line 183, in do_list_categories lines = value.splitlines() AttributeError: 'list' object has no attribute 'splitlines' I must add to this that we have a very large number (24000+) of mailing lists. I'm not sure if that matters, but we've had problems with the webinterface, which doesn't display the full list of mailing lists. list_lists works fine though, and it also doesn't seem to matter if I try this with a list from the top or from the bottom of the "list of lists". I'd try to fix this myself but unfortunately I don't speak Python... -- No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. From cmallon at earthlink.net Fri Oct 15 20:23:32 2010 From: cmallon at earthlink.net (cmallon) Date: Fri, 15 Oct 2010 11:23:32 -0700 Subject: [Mailman-Users] mailman configuration issue? Message-ID: <73CBEE4B-A60B-442C-BA14-3361F2ED7251@earthlink.net> HI, This may seem like a dumb question but I've been seeing a lot of this in my mail.logs All the messages are being delivered and there are no bad recipients in the list. Could there be a misconfiguration somewhere? I'd like to write a script that extracts information from the keyword bounces, but don't want to get data from legitimate emails. Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 1984F691A316: from=, size=3824, nrcpt=6 (queue active) Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 8D1F4691A31D: from=, size=3958, nrcpt=1 (queue active) Oct 15 10:53:45 apps25 postfix/qmgr[16897]: 59760691A45E: from=, size=5939, nrcpt=1 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: C16EC691B4C7: from=, size=4830, nrcpt=6 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: 66308691B4DE: from=, size=4964, nrcpt=1 (queue active) Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: from=, size=4174, nrcpt=4 (queue active) Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 1984F691A316: from=, size=3824, nrcpt=6 (queue active) Oct 15 10:53:20 apps25 postfix/qmgr[16897]: 8D1F4691A31D: from=, size=3958, nrcpt=1 (queue active) Oct 15 10:53:45 apps25 postfix/qmgr[16897]: 59760691A45E: from=, size=5939, nrcpt=1 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: C16EC691B4C7: from=, size=4830, nrcpt=6 (queue active) Oct 15 11:04:12 apps25 postfix/qmgr[16897]: 66308691B4DE: from=, size=4964, nrcpt=1 (queue active) Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: from=, size=4174, nrcpt=4 (queue active) If I grep one of the message ids and take a closer look: mail:/var/mail root# grep C5760691BA29 /var/log/mail.log Oct 15 11:08:27 apps25 postfix/smtpd[18204]: C5760691BA29: client=localhost[127.0.0.1] Oct 15 11:08:28 apps25 postfix/cleanup[18211]: C5760691BA29: message-id=<17120997.1287166102753.JavaMail.resin at server12> Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: from=, size=4174, nrcpt=4 (queue active) Oct 15 11:08:28 apps25 postfix/pipe[18230]: C5760691BA29: to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/pipe[18188]: C5760691BA29: to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/pipe[18241]: C5760691BA29: to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/pipe[18230]: C5760691BA29: to=, orig_to=, relay=cyrus, delay=1, status=sent (mail.mydomain.com) Oct 15 11:08:28 apps25 postfix/qmgr[16897]: C5760691BA29: removed It appears that all the messages have been delivered. There no bad recipients. Is the "my-list-bounces" as reported in my logs normal? Its reported in the logs the same way for all the lists -- every mailman email that goes out looks like this. Thank you for your time From BiLL at thebat.net Fri Oct 15 20:58:06 2010 From: BiLL at thebat.net (BiLL) Date: Fri, 15 Oct 2010 11:58:06 -0700 Subject: [Mailman-Users] new user question Message-ID: <1817611939.20101015115806@thebat.net> Hello, I am new to this mailman program. It works very good so far. It mails to over 900 people with no problems. My question is, How can I set up mailman to send me an email when there is a post held for moderation? Sometimes I will go for days, and not check the moderation page. Mailman used to send me an email when there was a post awaiting approval, but we bought a new server, and it doesn't send me an email anymore.? I have to remember to check Q every day. thank you for any suggestions. -- 10/15/2010 Bill Fuller BiLL at thebat.net From mark at msapiro.net Sat Oct 16 03:27:31 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 15 Oct 2010 21:27:31 -0400 Subject: [Mailman-Users] new user question In-Reply-To: <1817611939.20101015115806@thebat.net> References: <1817611939.20101015115806@thebat.net> Message-ID: <2d87163e-44ff-45eb-addc-3af093ef3a0c@email.android.com> "BiLL" wrote: >My question is, >How can I set up mailman to send me an email when there is a >post held for moderation? Set General Options / admin_immed_notify to Yes. -- Mark Sapiro - mark at msapiro.net Sent from my Android phone with K-9 Mail. Please excuse my brevity. From mark at msapiro.net Sat Oct 16 14:19:45 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 16 Oct 2010 05:19:45 -0700 Subject: [Mailman-Users] can't display list config In-Reply-To: <4CB857A1.6030403@gmail.com> Message-ID: Frank Van Damme wrote: > >I'm getting errors while trying to dump the config of a mailing list to >a text file. > > >/usr/lib/mailman/bin/config_list -o listname listname > >[...] > [...] >acceptable_aliases = >Traceback (most recent call last): >File "/usr/lib/mailman/bin/config_list", line 362, in > main() > File "/usr/lib/mailman/bin/config_list", line 355, in main > do_output(listname, outfile) > File "/usr/lib/mailman/bin/config_list", line 131, in do_output > do_list_categories(mlist, k, subcat, outfp) > File "/usr/lib/mailman/bin/config_list", line 183, in >do_list_categories > lines = value.splitlines() >AttributeError: 'list' object has no attribute 'splitlines' It appears that this list's acceptable_aliases attribute is a Python list of aliases - ['alias1 at domain1', 'alias2 at domain2', ...] - instead of a string of aliases separated by newlines - 'alias1 at domain1\r\nalias2 at domain2\r\n...'. I don't know how this came about, but you may be able to fix it via the web if you can access this list's Privacy options... -> Recipient filters page or via config_list -i or via withlist. >I must add to this that we have a very large number (24000+) of mailing >lists. I'm not sure if that matters, but we've had problems with the >webinterface, which doesn't display the full list of mailing lists. This may be related to the above issue or it may be a different corruption of some lists' attributes. >list_lists works fine though, and it also doesn't seem to matter if I >try this with a list from the top or from the bottom of the "list of lists". > >I'd try to fix this myself but unfortunately I don't speak Python... We can help, but we'd need details such as the actual output and maybe Mailman error log output, although the 'partial' overview listing could be due to timeout or other limits in the web server so check the web server logs too. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From phanh at canby.k12.or.us Mon Oct 18 08:31:22 2010 From: phanh at canby.k12.or.us (Hung Phan) Date: Sun, 17 Oct 2010 23:31:22 -0700 Subject: [Mailman-Users] Expected behavior with password reminder? Message-ID: <6E6ED17F-C10E-4A24-89BC-E029B4079267@canby.k12.or.us> Hello, While we testing the password reminder feature, we discover that a user asking for password reminder from a specific list that s/he isn't a member of that list, s/he still receives the message "A reminder of your password has been emailed to you." Is this an expected behavior? Thank you very much for the advice. From odhiambo at gmail.com Mon Oct 18 11:34:41 2010 From: odhiambo at gmail.com (Odhiambo Washington) Date: Mon, 18 Oct 2010 12:34:41 +0300 Subject: [Mailman-Users] Expected behavior with password reminder? In-Reply-To: <6E6ED17F-C10E-4A24-89BC-E029B4079267@canby.k12.or.us> References: <6E6ED17F-C10E-4A24-89BC-E029B4079267@canby.k12.or.us> Message-ID: On Mon, Oct 18, 2010 at 9:31 AM, Hung Phan wrote: > Hello, > > While we testing the password reminder feature, we discover that a user > asking for password reminder from a specific list that s/he isn't a member > of that list, s/he still receives the message "A reminder of your password > has been emailed to you." Is this an expected behavior? > > Well, do they get any e-mail at all, and worse still, containing a password? It would worry me if they did. >From what I know, a password will only be sent to a validly subscribed address. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! From s.watkins at nhm.ac.uk Mon Oct 18 11:46:20 2010 From: s.watkins at nhm.ac.uk (Steff Watkins) Date: Mon, 18 Oct 2010 10:46:20 +0100 Subject: [Mailman-Users] one line command to change generic_nonmember_action In-Reply-To: Message-ID: <8A17F10FEBA5C841956578C5AD9027D30105EE9D@HOMER.nhm.ac.uk> > -----Original Message----- > On Behalf Of Syn, Joonho > Sent: Friday, October 15, 2010 7:53 PM > To: mailman-users at python.org > Subject: [Mailman-Users] one line command to change > generic_nonmember_action > > I'm writing a simplified mailman dashboard page for my > company's internal use and one of the functions we want is to > be able to toggle the generic_nonmember_action for any given > list. Has anyone out there devised a one line command which > will allow this? Hi, I'm not sure if there is a direct command that can do this but I've been doing something similar lately. I had a setup of 20+ mailing lists which had to be identical in a specialised configuration. Doing that by the web interface filled me with dread so I started looking around and found the mailman utility 'bin/config_list'. This brilliant (imnsho!) utility allows you to either dump out a list's configuration in plain text or read in a list's configuration, again in plain text. Let's see you have a list called SomeList. You can dump out the entire configuration (not the members list, just the list's functional settings) by typing: > cd ~mailman > bin/config_list -o - SomeList This will dump to screen ( -o - ) the configuration of SomeList. It's just a minor logical step to do bin/config_list -o /usr/tmp/somelist-conf.txt SomeList Which dumps the config into a file /usr/tmp/somelist-conf.txt If you were to look at that file you'd find a section like this: ====== # When a post from a non-member is received, the message's sender is # matched against the list of explicitly accepted, # held, rejected (bounced), and discarded # addresses. If no match is found, then this action is taken. # # legal values are: # 0 = "Accept" # 1 = "Hold" # 2 = "Reject" # 3 = "Discard" generic_nonmember_action = 1 ===== You could either replace the value at the end of the line, or just swap in a whole new line. Then save the text file and read the configuration BACK to the list: bin/config_list -i /usr/tmp/somelist-conf.txt SomeList Note the change from '-o' (output) to '-i' (input). It would be easily possible to pipe these commands together, maybe using sed as the output=>input parser. So something like, bin/config_list -o - SomeList | /usr/bin/sed -f swapscript - | bin/config_list -i - SomeList Where 'swapscript' is a simple script to detect the "generic_nonmember_action = 1" line and change it as you want. Of course there's probably a simpler/better way of doing this but it should work. Regards, S Watkins --------------- Steff Watkins Natural History Museum, Cromwell Road, London, SW7 5BD Systems programmer Email: s.watkins at nhm.ac.uk Systems Team Phone: +44 (0)20 7942 6000 opt 2 ======== Many were increasingly of the opinion that they'd all made a big mistake in coming down from the trees in the first place. And some said that even the trees had been a bad move, and that no one should ever have left the oceans. - HHGTTG From mark at msapiro.net Mon Oct 18 13:29:24 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 18 Oct 2010 04:29:24 -0700 Subject: [Mailman-Users] Expected behavior with password reminder? In-Reply-To: <6E6ED17F-C10E-4A24-89BC-E029B4079267@canby.k12.or.us> Message-ID: Hung Phan wrote: > >While we testing the password reminder feature, we discover that a user asking for password reminder from a specific list that s/he isn't a member of that list, s/he still receives the message "A reminder of your password has been emailed to you." Is this an expected behavior? If the list's Privacy options... -> Subscription rules -> private_roster attribute is set to Anyone (i.e. if the list membership roster is public), a non-member requesting a reminder will be told "No such member". Otherwise, the user gets the same message whether or not she is a member to prevent using the reminder request to "fish" for list membership. On the "never to be released" branch at , the message is changed to "If you are a list member, your password has been emailed to you.", but it has not been changed on the 2.1 branch for i18n reasons. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Oct 18 13:43:10 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 18 Oct 2010 04:43:10 -0700 Subject: [Mailman-Users] one line command to change generic_nonmember_action In-Reply-To: Message-ID: Syn, Joonho wrote: >I'm writing a simplified mailman dashboard page for my company's internal use and one of the functions we want is to be able to toggle the generic_nonmember_action for any given list. Has anyone out there devised a one line command which will allow this? See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adam-mailman at amyl.org.uk Mon Oct 18 13:54:45 2010 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Mon, 18 Oct 2010 12:54:45 +0100 Subject: [Mailman-Users] one line command to change generic_nonmember_action In-Reply-To: <8A17F10FEBA5C841956578C5AD9027D30105EE9D@HOMER.nhm.ac.uk> References: <8A17F10FEBA5C841956578C5AD9027D30105EE9D@HOMER.nhm.ac.uk> Message-ID: <20101018115445.GI2315@hendricks.amyl.org.uk> On Mon, Oct 18, 2010 at 10:46:20AM +0100, Steff Watkins wrote: > bin/config_list -o /usr/tmp/somelist-conf.txt SomeList > Which dumps the config into a file /usr/tmp/somelist-conf.txt > > Then save the text file and read the configuration BACK to the list: > bin/config_list -i /usr/tmp/somelist-conf.txt SomeList > > Of course there's probably a simpler/better way of doing this but it > should work. I've been quite happy using: http://code.amyl.org.uk/adam/mailman-scripts/debian/editlistconfig (patches welcome, should anyone think it necessary) -- "Any person who knowingly causes a nuclear weapon test explosion or any other nuclear explosion is guilty of an offence" -- Nuclear Explosions Act, 1998 From aray10 at gmail.com Mon Oct 18 16:46:32 2010 From: aray10 at gmail.com (Aaron Ray) Date: Mon, 18 Oct 2010 10:46:32 -0400 Subject: [Mailman-Users] Problem with accept_these_nonmembers using another list in installation Message-ID: Version 2.1.13 I am having some trouble getting the accept_these_nonmembers filter to work when using another list as the value (eg @test or @all). I have searched through the mailman-user mailing list, but I can't seem to find a solution. One of the threads mentioned something about USE_ENVELOPE_SENDER being set in the mm_cfg.py. I am not hosting this site myself, and I only administrative interface is through cPanel. So I am not sure how to verify this setting without opening the file (which I don't have access to). The sender filter appears to work when I do explicit e-mail addresses, but not when I try to filter on other lists in the installation. I would like to use the list option since it is more dynamic. My list architecture is essentially like this: -all at domain -parents at domain -mentors at domain -students at domain The all at domain list contains every e-mail from the other 3 lists. So I am adding the all at domain mailing list to the other mailing list's accept_these_nonmembers sender filter with the following syntax: @all I have also tried: @all at domain Neither of them seem to work. I appreciate any advice/help anyone can offer. Sincerely, Aaron Ray From Alessandro.Bruchi at iit.it Tue Oct 19 12:48:47 2010 From: Alessandro.Bruchi at iit.it (Alessandro Bruchi) Date: Tue, 19 Oct 2010 12:48:47 +0200 Subject: [Mailman-Users] howto run multiple instances of mailman In-Reply-To: References: Message-ID: <3E8C1B0F5B2161419B02BEC08536162548A4F34BDB@IITMXMBX.iit.local> I all, who can explain me howto run multiple instances of mailman in a single host (one for different domain)? Do I have to create different /etc/init.d/mailman?? Thank you Bye Alessandro From mark at msapiro.net Tue Oct 19 15:49:08 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Oct 2010 06:49:08 -0700 Subject: [Mailman-Users] Problem with accept_these_nonmembers using anotherlist in installation In-Reply-To: Message-ID: Aaron Ray wrote: > >The all at domain list contains every e-mail from the other 3 lists. So I am >adding the all at domain mailing list to the other mailing list's >accept_these_nonmembers sender filter with the following syntax: > >@all > >I have also tried: > >@all at domain > >Neither of them seem to work. I appreciate any advice/help anyone can offer. You have to use the cPanel list name. This is the list name that is used in web URLs. For most cPanel lists it is of the form LISTNAME_DOMAIN. Try @all_domain -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From aray10 at gmail.com Tue Oct 19 15:56:47 2010 From: aray10 at gmail.com (aray10 at gmail.com) Date: Tue, 19 Oct 2010 13:56:47 +0000 Subject: [Mailman-Users] Problem with accept_these_nonmembers using anotherlist in installation In-Reply-To: Message-ID: <0016363b7980e98a580492f8a9a5@google.com> Thanks Mark that did the trick. I saw that I had to use the cPanel listname elsewhere, but I was using the name listed in the table on cPanel's interface rather than the URL. It is working as expected now. On Oct 19, 2010 9:49am, Mark Sapiro wrote: > Aaron Ray wrote: > > > >The all at domain list contains every e-mail from the other 3 lists. So I am > >adding the all at domain mailing list to the other mailing list's > >accept_these_nonmembers sender filter with the following syntax: > > > >@all > > > >I have also tried: > > > >@all at domain > > > >Neither of them seem to work. I appreciate any advice/help anyone can > offer. > You have to use the cPanel list name. This is the list name that is > used in web URLs. For most cPanel lists it is of the form > LISTNAME_DOMAIN. > Try > @all_domain > -- > Mark Sapiro mark at msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From drew.tenenholz at isid.org Tue Oct 19 20:53:45 2010 From: drew.tenenholz at isid.org (Drew Tenenholz) Date: Tue, 19 Oct 2010 14:53:45 -0400 Subject: [Mailman-Users] Inadvertent Postings - Approved Header; how does it work? Message-ID: All-- Sorry for the ridiculously simple question, but I'm pretty sure I don't quite understand how to prevent inadvertent postings; and we just managed to send a moderately embarrassing post. I want to use the Approved: header in the message body to help with inadvertent postings as well as block most inappropriate posts. Will the following settings work? 1) Mailman 2.1.9 on Red Hat Linux. 2) All subscribers (including myself) have the moderation flag set ON. 3) My address is also listed as a List-Admin (which is appropriate) 4) Another user's address is listed as a List-Mod (which I think is appropriate) 5) This moderator's address happens to be in the accept_these_nonmembers list as well. 7) Other settings: default_member_moderation=YES member_moderation_action=HOLD generic_nonmember_action=HOLD Test: SUCCESS! If I send a post without any subject or body from my list-admin address, the post is held for moderation. But, should I be clearing out the accept_these_nonmembers list as well? Does receiving a post from an address in this list supercede/evade the moderation flag? Once correctly set, EVERYONE MUST use the Approved: header, correct? -- Drew Tenenholz From mark at msapiro.net Wed Oct 20 00:41:01 2010 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 19 Oct 2010 15:41:01 -0700 Subject: [Mailman-Users] Inadvertent Postings - Approved Header; how does it work? In-Reply-To: Message-ID: Drew Tenenholz wrote: > >I want to use the Approved: header in the message body to help with inadvertent postings as well as block most inappropriate posts. Will the following settings work? > >1) Mailman 2.1.9 on Red Hat Linux. >2) All subscribers (including myself) have the moderation flag set ON. Good. >3) My address is also listed as a List-Admin (which is appropriate) >4) Another user's address is listed as a List-Mod (which I think is appropriate) >5) This moderator's address happens to be in the accept_these_nonmembers list as well. > >7) Other settings: > default_member_moderation=YES > member_moderation_action=HOLD > generic_nonmember_action=HOLD > > >Test: SUCCESS! If I send a post without any subject or body from my list-admin address, the post is held for moderation. > >But, should I be clearing out the accept_these_nonmembers list as well? Does receiving a post from an address in this list supercede/evade the moderation flag? Once correctly set, EVERYONE MUST use the Approved: header, correct? If you want everyone to be required to use an Approved: header to post, accept_these_nonmembers should be empty. If a non-member is in accept_these_nonmembers with the above settings, a post from that non-member (or a spoof of that non-member's address) will be accepted. With accept_these_nonmembers empty, any post with a valid Approved: header, whether or not from a member, will be accepted and all others will be held. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From webmaster at smutees.com Wed Oct 20 03:43:36 2010 From: webmaster at smutees.com (Webmaster) Date: Tue, 19 Oct 2010 21:43:36 -0400 Subject: [Mailman-Users] clearing nomail flags Message-ID: <6.2.3.4.2.20101019214131.043510e0@mail.comcast.net> I searched and found some old scripts to clear all of the nomail flags for every user in a mailing list but none of what I discovered work with version 2.1.13 which is what is on my server. Can someone please point me to a way to clear all the nomail flags for a specific list? Thanks! From mark at msapiro.net Wed Oct 20 14:40:07 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 Oct 2010 05:40:07 -0700 Subject: [Mailman-Users] clearing nomail flags In-Reply-To: <6.2.3.4.2.20101019214131.043510e0@mail.comcast.net> Message-ID: Webmaster wrote: >I searched and found some old scripts to clear all of the nomail >flags for every user in a mailing list but none of what I discovered >work with version 2.1.13 which is what is on my server. Can someone >please point me to a way to clear all the nomail flags for a specific >list? Thanks! The withlist script at (mirrored at will clear all "nomail by bounce" flags for a list. If you want to also clear other nomail flags, you could change the first line of if mlist.getDeliveryStatus(member) == MemberAdaptor.BYBOUNCE: mlist.setDeliveryStatus(member, MemberAdaptor.ENABLED) count += 1 in the script to if mlist.getDeliveryStatus(member) <> MemberAdaptor.ENABLED: -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adam-mailman at amyl.org.uk Wed Oct 20 14:53:30 2010 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Wed, 20 Oct 2010 13:53:30 +0100 Subject: [Mailman-Users] mailman 2.1.14 new features In-Reply-To: <3E8C1B0F5B2161419B02BEC08536162548A4F34995@IITMXMBX.iit.local> References: <4C62E62D.1080901@gmail.com> <3E8C1B0F5B2161419B02BEC08536162548A4F34995@IITMXMBX.iit.local> Message-ID: <20101020125330.GA8970@hendricks.amyl.org.uk> On Fri, Oct 15, 2010 at 03:46:31PM +0200, Alessandro Bruchi wrote: > Do you know when mailman 2.1.14 will be included as package in some debian distribution? The XSS patch, per 2010-September's announcement, seems to now be in Debian's repositories: http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/2010-October/003355.html http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/2010-October/003360.html (et. seq.) and http://lists.alioth.debian.org/pipermail/pkg-mailman-hackers/2010-October/003369.html It appears that 'official' Mailman packages for lenny are a wee bit behind upstream. I believe others on this list use the Umbungo packages on lenny (Debian 5), without too many difficulties. YMMV. (I don't really have the time to take on debian package maint, at the moment.) -- "Life was simple before World War II. After that, we had systems." -- Grace Hopper From rmj at aviation.org Wed Oct 20 14:55:05 2010 From: rmj at aviation.org (Robert M. Jenney) Date: Wed, 20 Oct 2010 08:55:05 -0400 Subject: [Mailman-Users] Newsletter bounce processing Message-ID: Good morning, **I send out newsletter A twice a month and want to be careful not to lose a subscriber unless it's clear the address is invalid. Please comment on these settings: 4.0 Threshold (default is 5.0) 90 Stale After (default is 7) 3 Disabled Warnings (default is 3) 14 Disabled Warning Interval (default is 7) **Also, I send out newsletter B once a month. Please comment on these settings: 3.0 Threshold (default is 5.0) 120 Stale After (default is 7) 3 Disabled Warnings (default is 3) 21 Disabled Warning Interval (default is 7) **Finally, I assume the Disabled Warnings receive the same bounce processing as the original newsletters. Correct? Thanks for the great service, Bob Jenney ____________________________ Robert M. Jenney, Director Aviation Safety Connection, Inc. 11 Lake Street, Unit #121 Wakefield, MA 01880 USA rmj at aviation.org; (781) 245-1391 Go to http://aviation.org From mark at msapiro.net Wed Oct 20 16:26:12 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 Oct 2010 07:26:12 -0700 Subject: [Mailman-Users] Newsletter bounce processing In-Reply-To: Message-ID: Robert M. Jenney wrote: > >**I send out newsletter A twice a month and want to be careful not to lose a >subscriber unless it's clear the address is invalid. Please comment on these >settings: > >4.0 Threshold (default is 5.0) > >90 Stale After (default is 7) 90 may be higher than you want here. Assume post 1 bounces, post 2 does not and post 3 does, if you want the score resulting from post 3 to be 1 rather than 2 because of the apparent successful delivery of post 2, then you want stale after to be < 30. You are correct that it must be > 15 or all prior bounce info will be stale. >3 Disabled Warnings (default is 3) > >14 Disabled Warning Interval (default is 7) See below. > > >**Also, I send out newsletter B once a month. Please comment on these >settings: > >3.0 Threshold (default is 5.0) > >120 Stale After (default is 7) The same applies here. In this case, this must be > 30 but should be less than 60 if you want to require 3 consecutive bounces for disable. >3 Disabled Warnings (default is 3) > >21 Disabled Warning Interval (default is 7) See below > > >**Finally, I assume the Disabled Warnings receive the same bounce processing >as the original newsletters. Correct? No. Once a member's delivery is disabled by bounce, any subsequent bounces are logged as residual but otherwise ignored, so bounces or non-bounces of the disabled warning have no effect. The only thing which will prevent the member from being removed after (disabled warnings) X (disabled warning interval) days is re-enabling delivery, either by the member from the member options page or by the admin. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mcnutt at utk.edu Wed Oct 20 22:09:46 2010 From: mcnutt at utk.edu (McNutt Jr, William R) Date: Wed, 20 Oct 2010 20:09:46 +0000 Subject: [Mailman-Users] Message for Single List Not Going Out Message-ID: <0CD7A72044B75D478D36624D96C5D44103B494@kmbx2.utk.tennessee.edu> I have a single list on my server that Is not sending messages out. Other lists are operating normally. Where should I begin my diagnosis? Bill From mark at msapiro.net Thu Oct 21 01:25:04 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 20 Oct 2010 16:25:04 -0700 Subject: [Mailman-Users] Message for Single List Not Going Out In-Reply-To: <0CD7A72044B75D478D36624D96C5D44103B494@kmbx2.utk.tennessee.edu> Message-ID: McNutt Jr, William R wrote: >I have a single list on my server that Is not sending messages out. Other lists are operating normally. > >Where should I begin my diagnosis? With Mailman's logs. in particular 'error' but also maybe 'locks'. This could be a stale lock. See the FAQ at . Also, if your Mailman is not too recent, it could be a corrupt message in lists/LISTNAME/digest.mbox (recent Mailman protects against this stopping list mail, but it still affects digests). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jon at brazoslink.net Wed Oct 20 16:52:51 2010 From: jon at brazoslink.net (Jon Gardner) Date: Wed, 20 Oct 2010 09:52:51 -0500 Subject: [Mailman-Users] Google distribution list as list admin Message-ID: <6DD6A758-87BA-4774-8965-C473A01C5002@brazoslink.net> I have a list admin who is using a Google distribution list as the admin email for a Mailman list. Whenever Mailman sends an administrative email, the Google server responds thus: >> Delivery to the following recipient failed permanently: >> >> >> >> Technical details of permanent failure: >> Bounce messages should not be posted to a mailinglist. Apparently Google is misinterpreting the From/Return-Path address of "mailman-bounces at ..." as a bounce. Has anyone else run into this issue? Obviously the workaround is to not use a Google distribution list as a Mailman list admin, but I'd sorta like to figure out a real fix. Jon From barry at list.org Thu Oct 21 17:54:44 2010 From: barry at list.org (Barry Warsaw) Date: Thu, 21 Oct 2010 11:54:44 -0400 Subject: [Mailman-Users] mailman 2.1.14 new features In-Reply-To: <20101020125330.GA8970@hendricks.amyl.org.uk> References: <4C62E62D.1080901@gmail.com> <3E8C1B0F5B2161419B02BEC08536162548A4F34995@IITMXMBX.iit.local> <20101020125330.GA8970@hendricks.amyl.org.uk> Message-ID: <20101021115444.50f64af8@mission> On Oct 20, 2010, at 01:53 PM, Adam McGreggor wrote: >It appears that 'official' Mailman packages for lenny are a wee bit >behind upstream. > >I believe others on this list use the Umbungo packages on lenny >(Debian 5), without too many difficulties. YMMV. > >(I don't really have the time to take on debian package maint, at the >moment.) Sadly, I do not either, but I am willing to help anyone who steps forward to do so. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From b19141 at anl.gov Thu Oct 21 21:18:44 2010 From: b19141 at anl.gov (Barry Finkel) Date: Thu, 21 Oct 2010 14:18:44 -0500 (CDT) Subject: [Mailman-Users] mailman 2.1.14 new features In-Reply-To: Mail from 'Barry Warsaw ' dated: Thu, 21 Oct 2010 11:54:44 -0400 Message-ID: <20101021191844.9B7B84D1EA@britaine.cis.anl.gov> On Oct 20, 2010, at 01:53 PM, Adam McGreggor wrote: >>It appears that 'official' Mailman packages for lenny are a wee bit >>behind upstream. >> >>I believe others on this list use the Umbungo packages on lenny >>(Debian 5), without too many difficulties. YMMV. >> >>(I don't really have the time to take on debian package maint, at the >>moment.) Barry Warsaw replied: >Sadly, I do not either, but I am willing to help anyone who steps >forward to do so. > >-Barry As I have posted before, I looked at the Debian packaging for Mailman, and I found there are lots of patches (most undocumented as to what they do). There was one patch that removed a library that may be needed. And one security of three I researched had different code in Debian/Ubuntu than in SourceForge. I assume that the Debian/Ubuntu patch that differed fixed the security problem, but I can not be sure. After following the discussions on mailman-users where users were running non-SourceForge code, I decided that I had to take the SourceForge code and build a Mailman package. It took me a while to discover exactly what to do, but once I did it (IIRC for 2.1.9), I have had no trouble building packages for 10 through 14. I can send my steps to anyone who wants them. My Mailman machines are still Ubuntu/dapper, but I assume that my steps would work unchanged on any later release of Debian/Ubuntu. ---------------------------------------------------------------------- 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 240, Room 5.B.8 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From ifetch at du.edu Fri Oct 22 05:08:23 2010 From: ifetch at du.edu (Ivan Fetch) Date: Thu, 21 Oct 2010 21:08:23 -0600 Subject: [Mailman-Users] Frequent use of clone_member Message-ID: <79C2D3933C76AB41B6D135F3480AC5C957C46D16@EXCH.du.edu> Hello, We are changing student email from mailboxes, to forwarding addresses. Among other challenges, we are exploring various ways to deal with students who are subscribed to closed (only subscribers may post) mailing lists. (There are a lot of similar challenges when switching to an email forwarding model - any list members who have gone through this, I would love to pick your brain!) One possibility we're exploring, is to change a student's mailing list subscriptions, when they change their forwarding address. We would iterate through these address changes and run clone_member, like: Clone_member --remove --admin old at our.domain new at outside.domain We could end up processing as many as 500 address changes nightly (running clone_member for each one), with each run of clone_member iterating through all mailing lists. I'm concerned that this is much more than clone_member was intended for. Can Mailman developers or heavy uses of Mailman comment on this? Thanks very much, Ivan. From stephen at xemacs.org Fri Oct 22 06:12:30 2010 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Fri, 22 Oct 2010 13:12:30 +0900 Subject: [Mailman-Users] Frequent use of clone_member In-Reply-To: <79C2D3933C76AB41B6D135F3480AC5C957C46D16@EXCH.du.edu> References: <79C2D3933C76AB41B6D135F3480AC5C957C46D16@EXCH.du.edu> Message-ID: <878w1qlvbl.fsf@uwakimon.sk.tsukuba.ac.jp> Ivan Fetch writes: > One possibility we're exploring, is to change a student's mailing > list subscriptions, when they change their forwarding address. We > would iterate through these address changes and run clone_member, > like: > > Clone_member --remove --admin old at our.domain new at outside.domain I can't really comment on the burden on the host, but ISTM that this would be a substantial burden on the students. They would have to remember which account is their real account to make any changes, or to post. This might be non-trivial for students with multiple mailboxes. How about having the forwarding address setup update accept_these_nonmembers, instead? Also, what are you going to do about the old forwarding address? It seems likely that in many cases students will want to do things like receive on their cellphone account but sometimes post from their home ISP, etc. Then they change back, creating a real muddle. OTOH, allowing dead or dormant accounts to post is a potential issue. From juandarcy2000 at jjwifi.com Fri Oct 22 06:40:56 2010 From: juandarcy2000 at jjwifi.com (Juan Carlos Mendoza D'Arcy) Date: Thu, 21 Oct 2010 22:40:56 -0600 Subject: [Mailman-Users] how send newsletter without the from list-bounce Message-ID: everytime i sent a newsletter i have the moderate bit for all user to avoid people send a message to all my list so when i sent a newsletter i have to accept it in the web interface of mailman but the email is sent from mylist-bounce at mydomain.com so how can i accept the message and the mail i sent to all my list only appears mylist at mydomain.com with out the -bounce -- Este mensaje ha sido analizado por MailScanner en busca de virus y otros contenidos peligrosos, y se considera que est? limpio. For all your IT requirements visit: http://www.transtec.co.uk From mark at msapiro.net Fri Oct 22 09:35:17 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 22 Oct 2010 00:35:17 -0700 Subject: [Mailman-Users] how send newsletter without the from list-bounce In-Reply-To: Message-ID: Juan Carlos Mendoza D'Arcy wrote: > >everytime i sent a newsletter i have the moderate bit for all user to >avoid people send a message to all my list so when i sent a >newsletter i have to accept it in the web interface of mailman but >the email is sent from mylist-bounce at mydomain.com so how can i accept >the message and the mail i sent to all my list only appears >mylist at mydomain.com with out the -bounce Please try to be more detailed and specific as to exactly what your problem is. If you go to the web interface and accept the message, it should be delivered to the list, so I don't understand the issue. If you are trying to approve the message by replying to the held message notice, you need to reply to the message/rfc822 attached part which is From: LISTNAME-request at ... with Subject: confirm so your reply goes to LISTNAME-request at ... with the same Subject:, but note that if you just reply in that way, the message will be discarded. In order to accept the message, you need to include an Approved: header, and if you are going to do that, you might as well just include that in the original post so it isn't held in the first place. You may find the FAQs at and of interest. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From marshall at cliffhanger.com Sat Oct 23 16:08:19 2010 From: marshall at cliffhanger.com (Dale & Lora Marshall) Date: Sat, 23 Oct 2010 10:08:19 -0400 Subject: [Mailman-Users] Mailman mailing lists are gone! In-Reply-To: <20101021191844.9B7B84D1EA@britaine.cis.anl.gov> Message-ID: <8CD40D2E12BFAB8-1960-604E@web-mmc-m08.sysops.aol.com> Using Mailman version: 2.1.12rc2 For some reason all of my mailing lists are now disconnected from mailman. There is data in /usr/local/mailman/lists, and also lots of data in the archives/private dir. But when I try to go to the admin page on any list I get a "list does not exist" message. I did a yum update the other day. What has happened and how do I fix it? Second question: In my Apache logfile I'm getting the following warning: [Sat Oct 23 09:44:08 2010] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 583 will probably never match because it overlaps an earlier Alias. [Sat Oct 23 09:44:08 2010] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 584 will probably never match because it overlaps an earlier ScriptAlias. The two lines in question are: # # MailMan Settings # Alias /pipermail/ "/usr/local/mailman/archives/public/" ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" I don't remember seeing this before I did a yum update the other day. Thanks. - Dale -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Dale & Lora Marshall Internet Marketing Services http://www.SpottedDragon.com/ http://www.internet-ms.com marshall at cliffhanger.com dalem at internet-ms.com loram at internet-ms.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From mark at msapiro.net Sat Oct 23 17:12:38 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 23 Oct 2010 08:12:38 -0700 Subject: [Mailman-Users] Mailman mailing lists are gone! In-Reply-To: <8CD40D2E12BFAB8-1960-604E@web-mmc-m08.sysops.aol.com> Message-ID: Dale & Lora Marshall wrote: > >Using Mailman version: 2.1.12rc2 > >For some reason all of my mailing lists are now disconnected from mailman. There is data in /usr/local/mailman/lists, and also lots of data in the archives/private dir. But when I try to go to the admin page on any list I get a "list does not exist" message. I did a yum update the other day. > >What has happened and how do I fix it? I haven't a clue? What did you update with Yum? Do you see any lists on the admin or listinfo overview pages? What does /usr/local/mailman/bin/list_lists report? >Second question: > >In my Apache logfile I'm getting the following warning: > >[Sat Oct 23 09:44:08 2010] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 583 will probably never match because it overlaps an earlier Alias. >[Sat Oct 23 09:44:08 2010] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 584 will probably never match because it overlaps an earlier ScriptAlias. > >The two lines in question are: > ># ># MailMan Settings ># >Alias /pipermail/ "/usr/local/mailman/archives/public/" >ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > >I don't remember seeing this before I did a yum update the other day. Aha. Now I have a clue. The Yum update most likely installed a Mailman package which is now being accessed by Apache and has no lists. There is most likeley now a /etc/httpd/conf.d/mailman file containing "Alias /pipermail/" and "ScriptAlias /mailman/" directives pointing to this new installation. Remove that file. Then you'll also have to figure out if other things such as aliases or other MTA stuff were clobbered by the Yum update. Possibly just doing "yum remove mailman" will fix things as long as there are no other conflicts between the package yum installed and your existing Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From marshall at cliffhanger.com Sat Oct 23 17:35:40 2010 From: marshall at cliffhanger.com (Dale & Lora Marshall) Date: Sat, 23 Oct 2010 11:35:40 -0400 Subject: [Mailman-Users] Mailman mailing lists are gone! In-Reply-To: Message-ID: <8CD40DF15204084-11B4-6F90@web-mmc-d02.sysops.aol.com> I did a yum update and then a "yum install mailman". I run a server with a lot of domains on it and a few of them have mailing lists but not all. list_lists reports 17 mailing lists which is I believe correct. There was a mailman.conf file in the conf.d dir. Thanks! I moved it to a different name (just in case) and now I can at least see the two lists I maintain. I'll email the guy with the other lists and see if he's ok now. Thanks again! - Dale -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Dale & Lora Marshall Internet Marketing Services http://www.SpottedDragon.com/ http://www.internet-ms.com marshall at cliffhanger.com dalem at internet-ms.com loram at internet-ms.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -----Original Message----- From: Mark Sapiro To: Dale & Lora Marshall ; mailman-users at python.org Sent: Sat, Oct 23, 2010 10:12 am Subject: Re: [Mailman-Users] Mailman mailing lists are gone! Dale & Lora Marshall wrote: > >Using Mailman version: 2.1.12rc2 > >For some reason all of my mailing lists are now disconnected from mailman. There is data in /usr/local/mailman/lists, and also lots of data in the archives/private dir. But when I try to go to the admin page on any list I get a "list does not exist" message. I did a yum update the other day. > >What has happened and how do I fix it? I haven't a clue? What did you update with Yum? Do you see any lists on the admin or listinfo overview pages? What does /usr/local/mailman/bin/list_lists report? >Second question: > >In my Apache logfile I'm getting the following warning: > >[Sat Oct 23 09:44:08 2010] [warn] The Alias directive in /etc/httpd/conf/httpd.conf at line 583 will probably never match because it overlaps an earlier Alias. >[Sat Oct 23 09:44:08 2010] [warn] The ScriptAlias directive in /etc/httpd/conf/httpd.conf at line 584 will probably never match because it overlaps an earlier ScriptAlias. > >The two lines in question are: > ># ># MailMan Settings ># >Alias /pipermail/ "/usr/local/mailman/archives/public/" >ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > >I don't remember seeing this before I did a yum update the other day. Aha. Now I have a clue. The Yum update most likely installed a Mailman package which is now being accessed by Apache and has no lists. There is most likeley now a /etc/httpd/conf.d/mailman file containing "Alias /pipermail/" and "ScriptAlias /mailman/" directives pointing to this new installation. Remove that file. Then you'll also have to figure out if other things such as aliases or other MTA stuff were clobbered by the Yum update. Possibly just doing "yum remove mailman" will fix things as long as there are no other conflicts between the package yum installed and your existing Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Oct 23 18:15:28 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 23 Oct 2010 09:15:28 -0700 Subject: [Mailman-Users] Mailman mailing lists are gone! In-Reply-To: <8CD40DF15204084-11B4-6F90@web-mmc-d02.sysops.aol.com> Message-ID: Dale & Lora Marshall wrote: > >I did a yum update and then a "yum install mailman". That was your mistake. Your Mailman was apparently installed from a source distribution, not from a yum package. You should not have done "yum install mailman" and you should probably now do "yum remove mailman" so that a future yum update does not create the same problem. If you want to update Mailman, dounload the current version from and configure and install it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From marshall at cliffhanger.com Sat Oct 23 18:17:28 2010 From: marshall at cliffhanger.com (Dale & Lora Marshall) Date: Sat, 23 Oct 2010 12:17:28 -0400 Subject: [Mailman-Users] Server name change - how? Message-ID: <8CD40E4EBCD7CC0-11B4-7126@web-mmc-d02.sysops.aol.com> When I originally set up mailman my server had a name that wasn't in DNS. I have since changed the name of my server to something that is in DNS. But, emails that go out still reference the old name and some messages are bouncing because the recipient does a DNS check on incoming emails. How can this be fixed? Thanks. - Dale -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Dale & Lora Marshall Internet Marketing Services http://www.SpottedDragon.com/ http://www.internet-ms.com marshall at cliffhanger.com dalem at internet-ms.com loram at internet-ms.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From frank.vandamme at gmail.com Sat Oct 23 18:32:19 2010 From: frank.vandamme at gmail.com (Frank Van Damme) Date: Sat, 23 Oct 2010 18:32:19 +0200 Subject: [Mailman-Users] Server name change - how? In-Reply-To: <8CD40E4EBCD7CC0-11B4-7126@web-mmc-d02.sysops.aol.com> References: <8CD40E4EBCD7CC0-11B4-7126@web-mmc-d02.sysops.aol.com> Message-ID: 2010/10/23 Dale & Lora Marshall : > > When I originally set up mailman my server had a name that wasn't in DNS. ?I have since changed the name of my server to something that is in DNS. ?But, emails that go out still reference the old name and some messages are bouncing because the recipient does a DNS check on incoming emails. > > How can this be fixed? > > Thanks. > > - Dale It's probably in the configuration of the mailing list itself (directive host_name I would guess). -- Frank Van Damme No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. From mark at msapiro.net Sat Oct 23 18:37:45 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 23 Oct 2010 09:37:45 -0700 Subject: [Mailman-Users] Server name change - how? In-Reply-To: <8CD40E4EBCD7CC0-11B4-7126@web-mmc-d02.sysops.aol.com> Message-ID: Dale & Lora Marshall wrote: > >When I originally set up mailman my server had a name that wasn't in DNS. I have since changed the name of my server to something that is in DNS. But, emails that go out still reference the old name and some messages are bouncing because the recipient does a DNS check on incoming emails. > >How can this be fixed? As far as Mailman is concerned, the domain used in all email from a list is the list's host_name attribute which is near the bottom of the list's General Options web admin page. You can set the for a given list from that page and/or set appropriate values for DEFAULT_EMAIL_HOST and add_virtualhost directives in mm_cfg.py and run fix_url to update existing lists. See the FAQ at . Note, if the list's host_name is what you want, but outgoing mail references a different domain, it is probably due to your MTA rewriting the domain. Fixing this is an MTA question, but see the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Oct 24 20:58:43 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 24 Oct 2010 11:58:43 -0700 Subject: [Mailman-Users] Google distribution list as list admin In-Reply-To: <6DD6A758-87BA-4774-8965-C473A01C5002@brazoslink.net> Message-ID: Jon Gardner wrote: >I have a list admin who is using a Google distribution list as the admin email for a Mailman list. Whenever Mailman sends an administrative email, the Google server responds thus: > >>> Delivery to the following recipient failed permanently: >>> >>> >>> >>> Technical details of permanent failure: >>> Bounce messages should not be posted to a mailinglist. > > >Apparently Google is misinterpreting the From/Return-Path address of "mailman-bounces at ..." as a bounce. Has anyone else run into this issue? Obviously the workaround is to not use a Google distribution list as a Mailman list admin, but I'd sorta like to figure out a real fix. If Google is misinterpreting the envelope sender (Return-Path) as meaning the message is a bounce DSN, that is Google's problem and up to Google to fix. If Google is looking at the Sender: header, see the FAQ at , particularly the 2.1.14 note at the bottom. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From skip at pobox.com Mon Oct 25 04:31:25 2010 From: skip at pobox.com (skip at pobox.com) Date: Sun, 24 Oct 2010 21:31:25 -0500 Subject: [Mailman-Users] A rare moment In-Reply-To: <4CB25969.6030907@bradakis.com> References: <4CB25969.6030907@bradakis.com> Message-ID: <19652.60413.283564.234038@montanaro.dyndns.org> Mark> With 60 or so lists and 12,000+ subscribers around the Mark> globe it is easy to get behind. I've seen 10,000 or more Mark> held messages at times. Today, though: Mark> Mark> autox /local/mailman/teamnet/data 131 :: ls held* Mark> ls: No match. Mark, That's a pleasant sight, I agree. (I'm a former member of both the triumphs and british-car lists, though not for several years. I appreciate all the time and effort you put into maintaining team.net.) I help manage the python.org mailing lists. In fact, I came across your mail while doing a bit of backend triage this evening. To help with the process, a couple years ago I wrote a script to help me quickly process held messages: http://www.smontanaro.net/python/mmfold.py I invoke it from a shell function which executes it once for each list I admin or moderate: mmcheck () { for url in http://mail.python.org/mailman/admindb/pydotorg-checkins?admpw=XXXXXX http://mail.python.org/mailman/admindb/python-bugs-list?admpw=XXXXXX http://mail.python.org/mailman/admindb/python-list?admpw=XXXXXX ... do mmfold $url; done } then just step through the pages it generates. Information for each held message is displayed in a single line and the default action is to discard, which I find is the most useful action. Maybe it will help to keep your held message lists down under 1,000. Cheers, -- Skip Montanaro - skip at pobox.com - http://www.smontanaro.net/ From mj at mjw.se Mon Oct 25 02:52:52 2010 From: mj at mjw.se (mattias) Date: Mon, 25 Oct 2010 02:52:52 +0200 Subject: [Mailman-Users] trouble Message-ID: <000501cb73de$f430bd80$f717e255@mj> Have run a mailman install on my centos 5.5 server Installed from centos repo I have added MTA = 'Postfix' to mm_cfg.py But the aliases don't go to the aliases file So posting to my lists not work From mike at maughan.co.uk Mon Oct 25 15:55:43 2010 From: mike at maughan.co.uk (Mike Maughan) Date: Mon, 25 Oct 2010 14:55:43 +0100 Subject: [Mailman-Users] Auto-generating messages "to the list", instead of "to the member" Message-ID: Afternoon all, Amongst others I run a mailman list for our family history society (The Maughan Society) and like many such lists we get quite a lot of new members "dropping in" with a specific query then "dropping out" again once they have that specific question answered. Our community aims to keep interested members and to grow in numbers, so one specific moderation task has been to post a "welcome to new member xxxxx" message to the list to draw the new member in to discuss their interests and hopefully to become engaged with the community. So far, this has been an entirely manual task but has suffered at times as I and the other moderators are getting on a bit and periodically go offline with one medical complication or another. This can mean that the potential member has gotten bored and moved on if we haven't responded within the magic 3-day period. Is there any way I can set up MM to send predefined posts to the list (as opposed to direct to the poster) on receipt of various triggers? Also on a related note, is there a way to default MM to put all new members on moderation by default, perhaps until they have made nn posts? Regards, Mike From mark at msapiro.net Mon Oct 25 16:13:44 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 Oct 2010 07:13:44 -0700 Subject: [Mailman-Users] trouble In-Reply-To: <000501cb73de$f430bd80$f717e255@mj> Message-ID: mattias wrote: >Have run a mailman install on my centos 5.5 server >Installed from centos repo Have you asked for help on a CentOS forum? Have you looked at /usr/share/doc/mailman-2.1.9/INSTALL.REDHAT ? >I have added >MTA = 'Postfix' to mm_cfg.py >But the aliases don't go to the aliases file >So posting to my lists not work In RedHat/CentOS, with MTA = 'Postfix', Mailman should create aliases in /etc/mailman/aliases. Is that file referenced in alias_maps in Postfix main.cf? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Oct 25 16:25:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 Oct 2010 07:25:40 -0700 Subject: [Mailman-Users] Auto-generating messages "to the list", instead of "to the member" In-Reply-To: Message-ID: Mike Maughan wrote: > >Is there any way I can set up MM to send predefined posts to the list (as >opposed to direct to the poster) on receipt of various triggers? I don't think so. Depending on the nature of the triggers, it may be possible to do this outside of Mailman with some other process that posts to the list. >Also on a related note, is there a way to default MM to put all new members >on moderation by default, perhaps until they have made nn posts? Set Privacy options... -> Sender filters -> default_member_moderation to Yes. This will moderate new members by default. There is no way to automatically set moderation off after nn posts, but the moderator summary interface contains a check box to clear a members moderation flag for posts from moderated members so it is easy to do this manually when approving the moderated member's post. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mike at maughan.co.uk Mon Oct 25 16:41:54 2010 From: mike at maughan.co.uk (Mike Maughan) Date: Mon, 25 Oct 2010 15:41:54 +0100 Subject: [Mailman-Users] Auto-generating messages "to the list", instead of "to the member" In-Reply-To: References: Message-ID: Thanks, Mark. Don't you ever sleep? :)) Regards, Mike On 25 October 2010 15:25, Mark Sapiro wrote: > Mike Maughan wrote: > > > >Is there any way I can set up MM to send predefined posts to the list (as > >opposed to direct to the poster) on receipt of various triggers? > > > I don't think so. Depending on the nature of the triggers, it may be > possible to do this outside of Mailman with some other process that > posts to the list. > > > >Also on a related note, is there a way to default MM to put all new > members > >on moderation by default, perhaps until they have made nn posts? > > > Set Privacy options... -> Sender filters -> default_member_moderation > to Yes. This will moderate new members by default. There is no way to > automatically set moderation off after nn posts, but the moderator > summary interface contains a check box to clear a members moderation > flag for posts from moderated members so it is easy to do this > manually when approving the moderated member's post. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From mark at msapiro.net Mon Oct 25 16:45:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 25 Oct 2010 07:45:40 -0700 Subject: [Mailman-Users] howto run multiple instances of mailman In-Reply-To: <3E8C1B0F5B2161419B02BEC08536162548A4F34BDB@IITMXMBX.iit.local> Message-ID: Alessandro Bruchi wrote: >I all, who can explain me howto run multiple instances of mailman in a single host (one for different domain)? >Do I have to create different /etc/init.d/mailman?? Each instance of Mailman needs to be configured with a unique value for prefix (and var-prefix if different from prefix), and each instance needs to be started by its own $prefix/bin/malmanctl. Whether you have separate /etc/init.d/ scripts for each instance or combine them all into one is up to you. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dma+mailman at witbe.net Mon Oct 25 15:53:18 2010 From: dma+mailman at witbe.net (Daniel Maher) Date: Mon, 25 Oct 2010 15:53:18 +0200 Subject: [Mailman-Users] trouble In-Reply-To: <000501cb73de$f430bd80$f717e255@mj> References: <000501cb73de$f430bd80$f717e255@mj> Message-ID: <4CC58BCE.3000804@witbe.net> On 10/25/2010 02:52 AM, mattias wrote: > Have run a mailman install on my centos 5.5 server > Installed from centos repo > I have added > MTA = 'Postfix' to mm_cfg.py > But the aliases don't go to the aliases file > So posting to my lists not work You also need to specify the aliases file in Postfix : /etc/postfix$ grep ^alias_maps main.cf alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases -- Daniel Maher "The Internet is completely over." -- Prince From terri at zone12.com Tue Oct 26 21:54:31 2010 From: terri at zone12.com (Terri Oda) Date: Tue, 26 Oct 2010 15:54:31 -0400 Subject: [Mailman-Users] Archives! Two neat demos from my GSoC students Message-ID: <4CC731F7.9000407@zone12.com> As some of you may know, Mailman had a bunch of Google Summer of Code students working on our codebase via Systers, which hired students to do improvements on their Mailman-based list infrastructure. I was mentoring for the project which worked on the archives, where we had two students, Yian Shang who worked on the web interface for the archives, and Priya Iyer who worked on integrating search. They've produced some great demos that you all need to see, and some code that I'd really like to see integrated into Mailman 3. I was going to forward their final summaries to the lists, but since they're quite long, here's the things I'd like you all to check out first and foremost. There's two neat demos here! #1: Yian's been working on a variety of UI infrastructure improvements (note that in this case, she's working at the code to support the UI, not the graphics and theming, so this may not *look* fancy but it *behaves* really well) Her threaded conversation demo is here: http://dev.systers.org/pipermail/testing/all/conversation-3.html and note that you can actually click through and read messages there, so try poking around those archives and see how you like them! And you might be interested in hearing about the use cases that went into threading and quote detection that made that demo possible. Many of you may have answered the surveys I sent out on her behalf which were used to generate these use cases! She's got a whole series of posts on it, but here's one of interest: http://movicont.nfshost.com/blog/mailman-archives-ui-added-automatically-detecting-quotes-support #2: Priya's search demo is here: http://lists.priyakuber.in/cgi-bin/mailman/mailocate/search.py She'd originally hoped to find and integrate an existing search package, but licensing proved to be an issue for upstream contribution, so she wound up implementing her own. You can search a string, a phrase, wildcard searches with *, by author, by subject, and using some basic operators (AND OR NOT all work). It's got a basic spell check, though she expects that will need to be improved. The documentation is here: http://systers.org/systers-dev/doku.php/doumentation-priya And the code is here: http://github.com/beachbrake/Mailocate/tree/master/demo/ ----- I've cc'ed mailman-users on this email since many people there contributed to the surveys we used to develop use-cases, but follow-ups should probably go to mailman-developers! Terri From melinko2003 at gmail.com Wed Oct 27 07:02:20 2010 From: melinko2003 at gmail.com (Llewellyn Curran) Date: Tue, 26 Oct 2010 22:02:20 -0700 Subject: [Mailman-Users] Follow up to a Lock problem. Message-ID: Hi All, I've summarized my issue below, and I would like to say I have around 215K subscribers on a Dedicated Server With a Quad Xeon CPU and 4GB's Ram. Most notably Mailman chews up around 2GB's+ of Ram but completely max's my CPU usage in top on CentOS. Python runs about 98% to 100% - I suspect this is from a mail drop going on however it doesn't explain below. Please read on. Mailman Version: 2.1.9 Symptoms: I had an issue a month or so ago where my web interface on " http://mysite.com/mailman/admin/mylist" would lock up on login, and I couldnt access that list. The other lists I could access no problems. I was guided to the FAQ at by Mark S. and that temporarily relieved the problem. I find now that I have to completely delete my locks everytime I want to go to a new location in the admin interface. I have included some errors from the locks log below. Can you assist me? Errors: [root at x mailman]# tail -50 /var/log/mailman/locks Oct 26 21:13:56 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose Oct 26 21:13:56 2010 (17763) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) Oct 26 21:13:56 2010 (17763) File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock Oct 26 21:13:56 2010 (17763) self.__lock.lock(timeout) Oct 26 21:13:56 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", line 287, in lock Oct 26 21:13:56 2010 (17763) self.__linkcount(), important=True) Oct 26 21:13:56 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", line 416, in __writelog Oct 26 21:13:56 2010 (17763) traceback.print_stack(file=logf) Oct 26 21:13:58 2010 (17763) xlt.lock unexpected linkcount: 1 Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line 278, in ? Oct 26 21:13:58 2010 (17763) main() Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line 238, in main Oct 26 21:13:58 2010 (17763) qrunner.run() Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run Oct 26 21:13:58 2010 (17763) filecnt = self._oneloop() Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop Oct 26 21:13:58 2010 (17763) self._onefile(msg, msgdata) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile Oct 26 21:13:58 2010 (17763) keepqueued = self._dispose(mlist, msg, msgdata) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose Oct 26 21:13:58 2010 (17763) return IncomingRunner._dispose(self, mlist, msg, msgdata) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose Oct 26 21:13:58 2010 (17763) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock Oct 26 21:13:58 2010 (17763) self.__lock.lock(timeout) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", line 287, in lock Oct 26 21:13:58 2010 (17763) self.__linkcount(), important=True) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", line 416, in __writelog Oct 26 21:13:58 2010 (17763) traceback.print_stack(file=logf) Oct 26 21:13:58 2010 (17763) xlt.lock unexpected linkcount: 1 Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line 278, in ? Oct 26 21:13:58 2010 (17763) main() Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line 238, in main Oct 26 21:13:58 2010 (17763) qrunner.run() Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run Oct 26 21:13:58 2010 (17763) filecnt = self._oneloop() Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop Oct 26 21:13:58 2010 (17763) self._onefile(msg, msgdata) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile Oct 26 21:13:58 2010 (17763) keepqueued = self._dispose(mlist, msg, msgdata) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose Oct 26 21:13:58 2010 (17763) return IncomingRunner._dispose(self, mlist, msg, msgdata) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose Oct 26 21:13:58 2010 (17763) mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/MailList.py", line 161, in Lock Oct 26 21:13:58 2010 (17763) self.__lock.lock(timeout) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", line 287, in lock Oct 26 21:13:58 2010 (17763) self.__linkcount(), important=True) Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", line 416, in __writelog Oct 26 21:13:58 2010 (17763) traceback.print_stack(file=logf) [root at x mailman]# -- Llewellyn G.S. Curran From mark at msapiro.net Thu Oct 28 23:50:14 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 28 Oct 2010 14:50:14 -0700 Subject: [Mailman-Users] Follow up to a Lock problem. In-Reply-To: Message-ID: Llewellyn Curran wrote: > >I have included some errors from the locks log below. Can you >assist me? > >Errors: >[root at x mailman]# tail -50 /var/log/mailman/locks >Oct 26 21:13:56 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose >Oct 26 21:13:56 2010 (17763) >mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) >Oct 26 21:13:56 2010 (17763) File "/usr/lib/mailman/Mailman/MailList.py", >line 161, in Lock >Oct 26 21:13:56 2010 (17763) self.__lock.lock(timeout) >Oct 26 21:13:56 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", >line 287, in lock >Oct 26 21:13:56 2010 (17763) self.__linkcount(), important=True) >Oct 26 21:13:56 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", >line 416, in __writelog >Oct 26 21:13:56 2010 (17763) traceback.print_stack(file=logf) >Oct 26 21:13:58 2010 (17763) xlt.lock unexpected linkcount: 1 >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line >278, in ? >Oct 26 21:13:58 2010 (17763) main() >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line >238, in main >Oct 26 21:13:58 2010 (17763) qrunner.run() >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run >Oct 26 21:13:58 2010 (17763) filecnt = self._oneloop() >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop >Oct 26 21:13:58 2010 (17763) self._onefile(msg, msgdata) >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile >Oct 26 21:13:58 2010 (17763) keepqueued = self._dispose(mlist, msg, >msgdata) >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose >Oct 26 21:13:58 2010 (17763) return IncomingRunner._dispose(self, mlist, >msg, msgdata) >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose >Oct 26 21:13:58 2010 (17763) >mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/MailList.py", >line 161, in Lock >Oct 26 21:13:58 2010 (17763) self.__lock.lock(timeout) >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", >line 287, in lock >Oct 26 21:13:58 2010 (17763) self.__linkcount(), important=True) >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", >line 416, in __writelog >Oct 26 21:13:58 2010 (17763) traceback.print_stack(file=logf) >Oct 26 21:13:58 2010 (17763) xlt.lock unexpected linkcount: 1 >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line >278, in ? >Oct 26 21:13:58 2010 (17763) main() >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/bin/qrunner", line >238, in main >Oct 26 21:13:58 2010 (17763) qrunner.run() >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/Runner.py", line 71, in run >Oct 26 21:13:58 2010 (17763) filecnt = self._oneloop() >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop >Oct 26 21:13:58 2010 (17763) self._onefile(msg, msgdata) >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/Runner.py", line 170, in _onefile >Oct 26 21:13:58 2010 (17763) keepqueued = self._dispose(mlist, msg, >msgdata) >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/VirginRunner.py", line 38, in _dispose >Oct 26 21:13:58 2010 (17763) return IncomingRunner._dispose(self, mlist, >msg, msgdata) >Oct 26 21:13:58 2010 (17763) File >"/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 115, in _dispose >Oct 26 21:13:58 2010 (17763) >mlist.Lock(timeout=mm_cfg.LIST_LOCK_TIMEOUT) >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/MailList.py", >line 161, in Lock >Oct 26 21:13:58 2010 (17763) self.__lock.lock(timeout) >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", >line 287, in lock >Oct 26 21:13:58 2010 (17763) self.__linkcount(), important=True) >Oct 26 21:13:58 2010 (17763) File "/usr/lib/mailman/Mailman/LockFile.py", >line 416, in __writelog >Oct 26 21:13:58 2010 (17763) traceback.print_stack(file=logf) >[root at x mailman]# When we attempt to obtain a lock, the process attempting the lock first writes a file named, e.g. .lock... and then attempts to create a hard link to that file named .lock. In the case above, the OS returned an EEXIST error to the attempted link meaning that the .lock file existed (xlt.lock in this case), but 'unexpected linkcount: 1' says that file is not linked to any .lock... file or any other file. When this happens, the contents of that xlt.lock file should give the hostname and pid of the process that obtained the lock. That may help. Also see the FAQ at for information about ensuring that only one mailmanctl and one set of qrunners are running and make sure that's the case. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Hagedorn at uni-koeln.de Fri Oct 29 13:33:36 2010 From: Hagedorn at uni-koeln.de (Sebastian Hagedorn) Date: Fri, 29 Oct 2010 13:33:36 +0200 Subject: [Mailman-Users] Definition of get_site_email in Utils.py Message-ID: Hi, we recently moved our Mailman server from a RHEL 3 machine running Mailman 2.1.9 to a RHEL 5 system running Mailman 2.1.14. Everything went very smoothly, but today I noticed one small issue. For various reasons we use 'lists.uni-koeln.de' as URL_HOST, but as EMAIL_HOST we use 'uni-koeln.de'. So the address for the sitelist is mailman at uni-koeln.de. On the old system we were able to receive mail for @lists.uni-koeln.de addresses as well, but on the new system we can't. But the listinfo CGI uses mailman at lists.uni-koeln.de as the site address. I checked out the code, but didn't really understand it ? I'm more of a Perl guy ;) def get_site_email(hostname=None, extra=None): if hostname is None: hostname = mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain()) if extra is None: return '%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, hostname) return '%s-%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, extra, hostname) Shouldn't that use the DEFAULT_EMAIL_HOST instead? I fixed our specific problem by hardcoding the return value, but it seems to me that could be a more general issue ... Thanks, Sebastian -- .:.Sebastian Hagedorn - RZKR-R1 (Geb?ude 52), Zimmer 18.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universit?t zu K?ln / Cologne University - ? +49-221-478-5587.:. From TW150001 at ncr.com Fri Oct 29 16:46:15 2010 From: TW150001 at ncr.com (Williams, Theona) Date: Fri, 29 Oct 2010 10:46:15 -0400 Subject: [Mailman-Users] API version 1012-module hangul 1011 runtime error Message-ID: Hi, The server on which Mailman was installed was upgraded from Linux 3 to 4 to 5 (32 bit). Mailman no longer works on this server. I am receiving the error: /u004/mailman/pythonlib/korean/hangul.py:24: RuntimeWarning: Python C API versio n mismatch for module hangul: This Python has API version 1012, module hangul ha s version 1011. from korean.c.hangul import * Traceback (most recent call last): File "./mailmanctl", line 548, in ? main() File "./mailmanctl", line 367, in main check_for_site_list() File "./mailmanctl", line 277, in check_for_site_list sitelist = MailList(sitelistname, lock=0) File "/u004/mailman/Mailman/MailList.py", line 130, in __init__ self.Load() File "/u004/mailman/Mailman/MailList.py", line 629, in Load dict, e = self.__load(file) File "/u004/mailman/Mailman/MailList.py", line 595, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/u004/mailman/lists/mailman/config.pck How do I go about resolving this problem? I am running Mailman version 2.1.9. Currently, Python 2.4.3 is on the server but I believe Mailman was originally built with a lower version of Python. Thanks, Theona From adam-mailman at amyl.org.uk Fri Oct 29 17:27:34 2010 From: adam-mailman at amyl.org.uk (Adam McGreggor) Date: Fri, 29 Oct 2010 16:27:34 +0100 Subject: [Mailman-Users] API version 1012-module hangul 1011 runtime error In-Reply-To: References: Message-ID: <20101029152734.GV4740@hendricks.amyl.org.uk> On Fri, Oct 29, 2010 at 10:46:15AM -0400, Williams, Theona wrote: > IOError: [Errno 13] Permission denied: '/u004/mailman/lists/mailman/config.pck > > How do I go about resolving this problem? The clue might be in there ("IOError..."). What are the permissions on that file/directory. Maybe look at bin/check_perms (I don't think I've seen a fix to the Debian '/var/lib/mailman' symlink issue (see this list's archive) committed) -- "All women become like their mothers. That is their tragedy. No man does. That's his." -- The Importance of Being Earnest From b19141 at anl.gov Fri Oct 29 18:03:16 2010 From: b19141 at anl.gov (Barry Finkel) Date: Fri, 29 Oct 2010 11:03:16 -0500 (CDT) Subject: [Mailman-Users] An Anonymous, No-reply List Message-ID: <20101029160317.00EE14D27B@britaine.cis.anl.gov> I have a customer who wants a announce-only list. She does not want any replies to the list or to the poster. In production we are running 2.1.13, and I have 2.1.14 on my test machine. We made the list anonymous anonymous_list = yes and the resulting mail from the list has a header line: Reply-To: LISTNAME at nodename so all replies go back to the list. I tried reply_goes_to_list - Explicit address reply_to_address: user at example.com and the resulting mail from the list has a header line: Reply-To: user at example.com, LISTNAME at nodename This results in replies going to both the list and to the explicit address. What I want is either a) no "Reply-To:" line in the RFC 5322 mail header (With no sender info nor reply info, I have no idea the address to which an MUA will direct any reply.) or b) Reply-To: user at example.com Is this possible? If not, then we will have to set member_moderation_action = Reject member_moderation_notice = Some polite text - This is an outbound list only. 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 240, Room 5.B.8 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From ckoeber at gmail.com Fri Oct 29 18:39:33 2010 From: ckoeber at gmail.com (Christopher Kurtis Koeber) Date: Fri, 29 Oct 2010 12:39:33 -0400 Subject: [Mailman-Users] An Anonymous, No-reply List In-Reply-To: <20101029160317.00EE14D27B@britaine.cis.anl.gov> References: <20101029160317.00EE14D27B@britaine.cis.anl.gov> Message-ID: <005001cb7787$de826950$9b873bf0$@com> > -----Original Message----- > From: mailman-users-bounces+ckoeber=gmail.com at python.org > [mailto:mailman-users-bounces+ckoeber=gmail.com at python.org] On > Behalf Of Barry Finkel > Sent: Friday, October 29, 2010 12:03 PM > To: Mailman-Users at python.org > Subject: [Mailman-Users] An Anonymous, No-reply List > > I have a customer who wants a announce-only list. She does not want > any replies to the list or to the poster. [Christopher Kurtis Koeber] I did this before. What I did was set both "member_moderation_action" and "generic_nonmember_action" to discard and added the email addresses who need to send emails to "accept_these_nonmembers". After that everything worked as you would like. No replies and people couldn't email each other. Also, if you keep the default settings the email account that is shown is the address of the list. From mark at msapiro.net Fri Oct 29 19:06:09 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Oct 2010 10:06:09 -0700 Subject: [Mailman-Users] An Anonymous, No-reply List In-Reply-To: <20101029160317.00EE14D27B@britaine.cis.anl.gov> Message-ID: Barry Finkel wrote: >I have a customer who wants a announce-only list. She does not want >any replies to the list or to the poster. > >In production we are running 2.1.13, and I have 2.1.14 on my test >machine. We made the list anonymous > > anonymous_list = yes Why, Is this needed or is it just an attempt to make replies not go to the poster? >and the resulting mail from the list has a header line: > > Reply-To: LISTNAME at nodename > >so all replies go back to the list. I tried > > reply_goes_to_list - Explicit address > reply_to_address: user at example.com > >and the resulting mail from the list has a header line: > > Reply-To: user at example.com, LISTNAME at nodename If you set first_strip_reply_to to Yes, the LISTNAME entry should be removed. >This results in replies going to both the list and to the explicit >address. What I want is either > > a) no "Reply-To:" line in the RFC 5322 mail header (With no > sender info nor reply info, I have no idea the address to which > an MUA will direct any reply.) If you set first_strip_reply_to to Yes and reply_goes_to_list to Poster, there should be no Reply-To: header in list mail which means "reply" will be to the From: address which is the poster or the list in the case of an anonymous list. >or > b) Reply-To: user at example.com > >Is this possible? If not, then we will have to set > > member_moderation_action = Reject > member_moderation_notice = Some polite text - This is an outbound > list only. You need to do that anyway because nothing prevents a member from doing "reply all" or in some other way addressing a message to the list or to the poster if the list is not anonymous. See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Oct 29 19:14:29 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Oct 2010 10:14:29 -0700 Subject: [Mailman-Users] API version 1012-module hangul 1011 runtime error In-Reply-To: Message-ID: Williams, Theona wrote: >Hi, >The server on which Mailman was installed was upgraded from Linux 3 to 4 to 5 (32 bit). Mailman no longer works on this server. I am receiving the error: >/u004/mailman/pythonlib/korean/hangul.py:24: RuntimeWarning: Python C API versio >n mismatch for module hangul: This Python has API version 1012, module hangul ha >s version 1011. > from korean.c.hangul import * The above is only a warning, but as you note below it is because Mailman was built with a different Python version than it is being run with. This is very bad. You should rebuild Mailman with the current Python. >Traceback (most recent call last): > File "./mailmanctl", line 548, in ? > main() > File "./mailmanctl", line 367, in main > check_for_site_list() > File "./mailmanctl", line 277, in check_for_site_list > sitelist = MailList(sitelistname, lock=0) > File "/u004/mailman/Mailman/MailList.py", line 130, in __init__ > self.Load() > File "/u004/mailman/Mailman/MailList.py", line 629, in Load > dict, e = self.__load(file) > File "/u004/mailman/Mailman/MailList.py", line 595, in __load > fp = open(dbfile) >IOError: [Errno 13] Permission denied: '/u004/mailman/lists/mailman/config.pck > >How do I go about resolving this problem? Run Mailman's bin/check_perms to fix this. >I am running >Mailman version 2.1.9. Currently, Python 2.4.3 is on the server but I believe Mailman was originally built with a lower version of Python. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From TW150001 at ncr.com Fri Oct 29 20:40:56 2010 From: TW150001 at ncr.com (Williams, Theona) Date: Fri, 29 Oct 2010 14:40:56 -0400 Subject: [Mailman-Users] API version 1012-module hangul 1011 runtime error In-Reply-To: References: Message-ID: I ran the bin/check_perms and that resolved all errors except the API version warning. I am still not able to send out messages. I will attempt to rebuild Mailman. Thanks Theona -----Original Message----- From: Mark Sapiro [mailto:mark at msapiro.net] Sent: Friday, October 29, 2010 12:14 PM To: Williams, Theona; mailman-users at python.org Subject: Re: [Mailman-Users] API version 1012-module hangul 1011 runtime error Williams, Theona wrote: >Hi, >The server on which Mailman was installed was upgraded from Linux 3 to 4 to 5 (32 bit). Mailman no longer works on this server. I am receiving the error: >/u004/mailman/pythonlib/korean/hangul.py:24: RuntimeWarning: Python C >API versio n mismatch for module hangul: This Python has API version >1012, module hangul ha s version 1011. > from korean.c.hangul import * The above is only a warning, but as you note below it is because Mailman was built with a different Python version than it is being run with. This is very bad. You should rebuild Mailman with the current Python. >Traceback (most recent call last): > File "./mailmanctl", line 548, in ? > main() > File "./mailmanctl", line 367, in main > check_for_site_list() > File "./mailmanctl", line 277, in check_for_site_list > sitelist = MailList(sitelistname, lock=0) > File "/u004/mailman/Mailman/MailList.py", line 130, in __init__ > self.Load() > File "/u004/mailman/Mailman/MailList.py", line 629, in Load > dict, e = self.__load(file) > File "/u004/mailman/Mailman/MailList.py", line 595, in __load > fp = open(dbfile) >IOError: [Errno 13] Permission denied: >'/u004/mailman/lists/mailman/config.pck > >How do I go about resolving this problem? Run Mailman's bin/check_perms to fix this. >I am running >Mailman version 2.1.9. Currently, Python 2.4.3 is on the server but I believe Mailman was originally built with a lower version of Python. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From b19141 at anl.gov Fri Oct 29 21:09:09 2010 From: b19141 at anl.gov (Barry Finkel) Date: Fri, 29 Oct 2010 14:09:09 -0500 (CDT) Subject: [Mailman-Users] An Anonymous, No-reply List In-Reply-To: Mail from 'Mark Sapiro ' dated: Fri, 29 Oct 2010 10:06:09 -0700 Message-ID: <20101029190910.7D04D4D2A3@britaine.cis.anl.gov> Barry Finkel wrote: >>I have a customer who wants a announce-only list. She does not want >>any replies to the list or to the poster. >> >>In production we are running 2.1.13, and I have 2.1.14 on my test >>machine. We made the list anonymous >> >> anonymous_list = yes Mark Sapiro replied: >Why, Is this needed or is it just an attempt to make replies not go to >the poster? This is a mailing to a club membership, and is for announcements only. The one or two people who will do the monthly postings do not want to get replies sent to their mailboxes, and they do not want replies sent back to the list. They have changed the list footer to read: All mail/replies should be sent to . where "" is another list for the club officers where anyone can post. ---------------------------------------------------------------------- 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 240, Room 5.B.8 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From mark at msapiro.net Sat Oct 30 06:02:33 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Oct 2010 21:02:33 -0700 Subject: [Mailman-Users] Approved message is discarded In-Reply-To: <4CCAE41D.2010305@nikhef.nl> References: <4CCAE41D.2010305@nikhef.nl> Message-ID: <4CCB98D9.8030605@msapiro.net> On 10/29/2010 8:11 AM, Andr? van Kan wrote: > Hi Larry, > > Although we have the same problem, ours is even weird in > some aspects. I made an test-list - groep3 - with two members. > If mail is send by a non-member, all messages are discarded > after approval: > > Oct 29 15:59:09 2010 (20460) groep3: Discarded posting: > From: acvankan at gmail.com > Subject: test after restart > Oct 29 16:04:30 2010 (21937) groep3: Discarded posting: > From: acvankan at gmail.com > Subject: last one Please post to the list, not to me personally. However, the above messages, presumably from Mailman's vette log, come from two different PIDs. Thus, I'm guessing that you are approving these messages via the admindb web interface, and something is going wrong in that process resulting in the message being discarded by the admindb CGI itself. > BUT if messages are sent by senders as mentioned in [Sender Filters] / > "List of non-member addresses whose postings should be automatically accepted" > THEN messages are delivered (of course without the necessity of approval). > > Since the vette-contents is rather concise, I editted > IncomingRunner.py'sErrors.DiscardMessage as follows, according > a earlier posting about this subject: > syslog('vette', 'Message discarded, msgid: %s, handler: %s', > msg.get('message-id', 'n/a'), handler) > but to no avail. Nothing changes in the output-format. Because the message is not discarded by IncomingRunner. It is discarded by the HandleRequest method in Mailman/ListAdmin.py called from Mailman/Cgi/admindb.py. > Since all our lists suffer the same problem, a generic > configuration error may be assumed, but I've no idea > how to fix it. Any hint would be gratly appreciated. Have you modified admindb.py in any way? Does the web admin interface work? What Mailman version is this? How exactly are you approving messages? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sat Oct 30 06:22:34 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 29 Oct 2010 21:22:34 -0700 Subject: [Mailman-Users] Definition of get_site_email in Utils.py In-Reply-To: References: Message-ID: <4CCB9D8A.10702@msapiro.net> On 10/29/2010 4:33 AM, Sebastian Hagedorn wrote: > > For various reasons > we use 'lists.uni-koeln.de' as URL_HOST, but as EMAIL_HOST we use > 'uni-koeln.de'. So the address for the sitelist is mailman at uni-koeln.de. > On the old system we were able to receive mail for @lists.uni-koeln.de > addresses as well, but on the new system we can't. But the listinfo CGI > uses mailman at lists.uni-koeln.de as the site address. I checked out the > code, but didn't really understand it ? I'm more of a Perl guy ;) > > def get_site_email(hostname=None, extra=None): > if hostname is None: > hostname = mm_cfg.VIRTUAL_HOSTS.get(get_domain(), get_domain()) The code is correct. The problem is you have no VIRTUAL_HOSTS entry with key lists.uni-koeln.de and value uni-koeln.de. > if extra is None: > return '%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, hostname) > return '%s-%s@%s' % (mm_cfg.MAILMAN_SITE_LIST, extra, hostname) > > Shouldn't that use the DEFAULT_EMAIL_HOST instead? I fixed our specific > problem by hardcoding the return value, but it seems to me that could be > a more general issue ... If you have defined DEFAULT_URL_HOST = 'lists.uni-koeln.de' DEFAULT_EMAIL_HOST = 'uni-koeln.de' in mm_cfg.py then you also need to include after those definitions add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Hagedorn at uni-koeln.de Sat Oct 30 09:16:12 2010 From: Hagedorn at uni-koeln.de (Sebastian Hagedorn) Date: Sat, 30 Oct 2010 09:16:12 +0200 Subject: [Mailman-Users] Definition of get_site_email in Utils.py In-Reply-To: <4CCB9D8A.10702@msapiro.net> References: <4CCB9D8A.10702@msapiro.net> Message-ID: -- Mark Sapiro is rumored to have mumbled on 29. Oktober 2010 21:22:34 -0700 regarding Re: [Mailman-Users] Definition of get_site_email in Utils.py: > If you have defined > > DEFAULT_URL_HOST = 'lists.uni-koeln.de' > DEFAULT_EMAIL_HOST = 'uni-koeln.de' > > in mm_cfg.py then you also need to include after those definitions > > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) D'oh! Thanks, Mark, we actually had that, but in the course of the upgrade I messed it up :( The add_virtualhost was placed *before* the definition of the variables ... Thanks for your help! -- Sebastian Hagedorn - RZKR-R1 (Flachbau), Zi. 18, Robert-Koch-Str. 10 Regionales Rechenzentrum (RRZK) Universit?t zu K?ln / Cologne University - Tel. +49-221-478-5587 From measl at mfn.org Sat Oct 30 09:42:08 2010 From: measl at mfn.org (J.A. Terranson) Date: Sat, 30 Oct 2010 02:42:08 -0500 (CDT) Subject: [Mailman-Users] Mailman DOA after power outage crash. Message-ID: Greetings, We had a series of longer than battery outages on wednesday, and when we came back online, mailman refused to run. Heres the messages: mailman# tail -f error Oct 30 02:28:06 2010 (11862) couldn't load config file /usr/mailman/lists/[listname]/config.pck.last 1778451844 Oct 30 02:28:06 2010 (11862) couldn't load config file /usr/mailman/lists/[listname]/config.db [Errno 2] No such file or directory: '/usr/mailman/lists/[listname]/config.db' Oct 30 02:28:06 2010 (11862) couldn't load config file /usr/mailman/lists/[listname]/config.db.last [Errno 2] No such file or directory: '/usr/mailman/lists/[listname]/config.db.last' Oct 30 02:28:06 2010 (11862) All [listname]B fallbacks were corrupt, giving up Oct 30 02:28:06 2010 (11862) error opening list: [listname] [Errno 2] No such file or directory: '/usr/mailman/lists/[listname]/config.db.last' Please tell me theres a reasonable recovery for this on 2.1.21 (plus a patch)? Thanks! //Alif -- "Never belong to any party, always oppose privileged classes and public plunderers, never lack sympathy with the poor, always remain devoted to the public welfare, never be satisfied with merely printing news, always be drastically independent, never be afraid to attack wrong, whether by predatory plutocracy or predatory poverty." Joseph Pulitzer, 1907 Speech From mark at msapiro.net Sat Oct 30 17:51:20 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 30 Oct 2010 08:51:20 -0700 Subject: [Mailman-Users] Mailman DOA after power outage crash. In-Reply-To: Message-ID: J.A. Terranson wrote: > > We had a series of longer than battery outages on wednesday, and >when we came back online, mailman refused to run. Heres the messages: > >mailman# tail -f error >Oct 30 02:28:06 2010 (11862) couldn't load config file >/usr/mailman/lists/[listname]/config.pck.last 1778451844 > >Oct 30 02:28:06 2010 (11862) couldn't load config file >/usr/mailman/lists/[listname]/config.db >[Errno 2] No such file or directory: >'/usr/mailman/lists/[listname]/config.db' > >Oct 30 02:28:06 2010 (11862) couldn't load config file >/usr/mailman/lists/[listname]/config.db.last >[Errno 2] No such file or directory: >'/usr/mailman/lists/[listname]/config.db.last' > >Oct 30 02:28:06 2010 (11862) All [listname]B fallbacks were corrupt, >giving up > >Oct 30 02:28:06 2010 (11862) error opening list: [listname] >[Errno 2] No such file or directory: >'/usr/mailman/lists/[listname]/config.db.last' > >Please tell me theres a reasonable recovery for this on 2.1.21 (plus a >patch)? 2.1.12? The recovery is to restore the corrupt /usr/mailman/lists/[listname]/config.pck from the most recent good backup. Mailman does the best it can by trying to first write config.pck.tmp.. and then removing config.pck.last, moving config.pck to config.pck.last and finally moving config.pck.tmp.. to config.pck. You could check for a /usr/mailman/lists/[listname]/config.pck.tmp.. file and try moving that to /usr/mailman/lists/[listname]/config.pck if it exists, but even if it does, it may be bad too. It appears that your system is caching disk writes to the extent that both the config.pck and config.pck.last were incompletely written when the power failed. You might look into that, and also consider setting SYNC_AFTER_WRITE = Yes in mm_cfg.py (see the documentation of this in Defaults.py). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From measl at mfn.org Sat Oct 30 18:17:20 2010 From: measl at mfn.org (J.A. Terranson) Date: Sat, 30 Oct 2010 11:17:20 -0500 (CDT) Subject: [Mailman-Users] Mailman DOA after power outage crash. In-Reply-To: References: Message-ID: On Sat, 30 Oct 2010, Mark Sapiro wrote: > /usr/mailman/lists/[listname]/config.pck.tmp.. file and > try moving that to /usr/mailman/lists/[listname]/config.pck if it > exists, but even if it does, it may be bad too. Thanks for the terrible news :-/ Is my [completely off the cuff] understanding of the config file correct that it just holds the settings from the config pages? If so, is there any reason I cannot "create" a new list (after moving the existing one) with the same name and then sub the new config.pck for the old corrupted one? Thanks for the flush information: even though this was a unique situation (every box in the rack was damaged, several beyond repair [including the backup server]), living in the middle of the tornado capital of the world means it could realistically happen again, so thats a really good one to know. //Alif -- "Never belong to any party, always oppose privileged classes and public plunderers, never lack sympathy with the poor, always remain devoted to the public welfare, never be satisfied with merely printing news, always be drastically independent, never be afraid to attack wrong, whether by predatory plutocracy or predatory poverty." Joseph Pulitzer, 1907 Speech From mark at msapiro.net Sat Oct 30 19:15:40 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 30 Oct 2010 10:15:40 -0700 Subject: [Mailman-Users] Mailman DOA after power outage crash. In-Reply-To: Message-ID: J.A. Terranson wrote: > >> /usr/mailman/lists/[listname]/config.pck.tmp.. file and >> try moving that to /usr/mailman/lists/[listname]/config.pck if it >> exists, but even if it does, it may be bad too. > >Thanks for the terrible news :-/ Is my [completely off the cuff] >understanding of the config file correct that it just holds the settings >from the config pages? If so, is there any reason I cannot "create" a new >list (after moving the existing one) with the same name and then sub the >new config.pck for the old corrupted one? Assuming you don't use some kind of custom member adaptor, the config.pck also contains all the list membership information. You can try running 'strings' on the various config.pck* files to see if you can extract useful information that way. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From measl at mfn.org Sun Oct 31 06:56:06 2010 From: measl at mfn.org (J.A. Terranson) Date: Sun, 31 Oct 2010 00:56:06 -0500 (CDT) Subject: [Mailman-Users] Mailman DOA after power outage crash. In-Reply-To: References: Message-ID: On Sat, 30 Oct 2010, Mark Sapiro wrote: > J.A. Terranson wrote: > > > >> /usr/mailman/lists/[listname]/config.pck.tmp.. file and > >> try moving that to /usr/mailman/lists/[listname]/config.pck if it > >> exists, but even if it does, it may be bad too. > > > >Thanks for the terrible news :-/ Is my [completely off the cuff] > >understanding of the config file correct that it just holds the settings > >from the config pages? If so, is there any reason I cannot "create" a new > >list (after moving the existing one) with the same name and then sub the > >new config.pck for the old corrupted one? > > > Assuming you don't use some kind of custom member adaptor, the > config.pck also contains all the list membership information. > > You can try running 'strings' on the various config.pck* files to see > if you can extract useful information that way. Everything seems to be in there: I see all the settings, plus it looks like all the subscribers are there as well. It's going to be *really* painfull manually restoring all ~1200 addresses and their information, but I suppose it will have to do. Whats really odd is that only one (of approx 30 lists) was corrupted, and when I compare the output of the corrupted vs known goos files, they look roughly identical. Clearly they aren't, but... Is there any way to tell "where" mailman thinks the corruption begins or is it just the absence of a clean flag somewhere that I am hosed on? //Alif -- "Never belong to any party, always oppose privileged classes and public plunderers, never lack sympathy with the poor, always remain devoted to the public welfare, never be satisfied with merely printing news, always be drastically independent, never be afraid to attack wrong, whether by predatory plutocracy or predatory poverty." Joseph Pulitzer, 1907 Speech From dnewman at networktest.com Sat Oct 30 22:11:49 2010 From: dnewman at networktest.com (David Newman) Date: Sat, 30 Oct 2010 13:11:49 -0700 Subject: [Mailman-Users] non-delivery to virtual domain Message-ID: <4CCC7C05.7040900@networktest.com> (Apologies for re-raising a topic I asked about here a couple of years ago. The instructions on Sourceforge have changed a bit since then.) New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual domains. Mail sent to/from virtual domains works fine. Different story with Mailman. Although postfix says a message addressed to a list is "sent" to all addresses, subscribers from virtual domains on this server do not receive the message. Subscribers on other domains not on this server do receive the message. There's no indication of trouble in the Mailman logs or in maillog. I've followed the setup instructions here, doing section 6.1.2 before 6.1.1 (given the link about doing virtual stuff first): http://mailman.sourceforge.net/mailman-install/postfix-virtual.html http://mailman.sourceforge.net/mailman-install/postfix-integration.html I've pasted the config files below. Thanks in advance for clues on getting Mailman to deliver to virtual addresses on this server. dn server hostname: mail.domain1.tld virtual domains: domain1.tld # (not its real name!) domain2.tld domain3.tld ----- from /etc/postfix/main.cf: .. myhostname = mail.domain1.tld mydomain = domain1.tld mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain .. alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases virtual_alias_maps = proxy:mysql:/etc/postfix/sql/forwardings.cf proxy:mysql:/etc/postfix/sql/email2email.cf hash:/usr/local/mailman/data/domain1-tld hash:/usr/local/mailman/data/virtual-mailman ----- from /usr/local/mailman/Mailman/mm_cfg.py: MTA = 'Postfix' MAILMAN_SITE_LIST = 'mailman' DEFAULT_EMAIL_HOST = 'domain1.tld' DEFAULT_URL_HOST = 'mail.domain1.tld' DEFAULT_URL_PATTERN = 'https://%s/mailman/' PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' IMAGE_LOGOS = '/icons/' POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias' POSTFIX_MAP_CMD = '/usr/local/sbin/postmap' POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'domain2.tld', 'domain3.tld' ] # Clear the Defaults.py VIRTUAL_HOSTS entry VIRTUAL_HOSTS.clear() add_virtualhost('DEFAULT_EMAIL_HOST', 'DEFAULT_URL_HOST') add_virtualhost('domain2.tld', 'domain2.tld') add_virtualhost('domain3.tld', 'domain3.tld') ----- /usr/local/mailman/data/aliases # The ultimate loop stopper address mailman-loop: /usr/local/mailman/data/owner-bounces.mbox # STANZA START: mailman # CREATED: Sat Oct 30 11:23:37 2010 mailman: "|/usr/local/mailman/mail/mailman post mailman" mailman-admin: "|/usr/local/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/local/mailman/mail/mailman join mailman" mailman-leave: "|/usr/local/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/local/mailman/mail/mailman owner mailman" mailman-request: "|/usr/local/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/local/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mailman" # STANZA END: mailman # STANZA START: s # CREATED: Sat Oct 30 11:35:12 2010 s: "|/usr/local/mailman/mail/mailman post s" s-admin: "|/usr/local/mailman/mail/mailman admin s" s-bounces: "|/usr/local/mailman/mail/mailman bounces s" s-confirm: "|/usr/local/mailman/mail/mailman confirm s" s-join: "|/usr/local/mailman/mail/mailman join s" s-leave: "|/usr/local/mailman/mail/mailman leave s" s-owner: "|/usr/local/mailman/mail/mailman owner s" s-request: "|/usr/local/mailman/mail/mailman request s" s-subscribe: "|/usr/local/mailman/mail/mailman subscribe s" s-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe s" # STANZA END: s ----- /usr/local/etc/mailman/data/domain1-tld: domain1.tld IGNORE @domain1.tld @mail.domain1.tld ----- /usr/local/mailman/data/virtual-mailman: # LOOP ADDRESSES START mailman-loop at domain1.tld mailman-loop # LOOP ADDRESSES END # STANZA START: s # CREATED: Sat Oct 30 11:35:12 2010 s at domain1.tld s s-admin at domain1.tld s-admin s-bounces at domain1.tld s-bounces s-confirm at domain1.tld s-confirm s-join at domain1.tld s-join s-leave at domain1.tld s-leave s-owner at domain1.tld s-owner s-request at domain1.tld s-request s-subscribe at domain1.tld s-subscribe s-unsubscribe at domain1.tld s-unsubscribe # STANZA END: s ----- From mark at msapiro.net Sun Oct 31 16:43:20 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 Oct 2010 08:43:20 -0700 Subject: [Mailman-Users] Mailman DOA after power outage crash. In-Reply-To: Message-ID: J.A. Terranson wrote: > >On Sat, 30 Oct 2010, Mark Sapiro wrote: > >> You can try running 'strings' on the various config.pck* files to see >> if you can extract useful information that way. > >Everything seems to be in there: I see all the settings, plus it looks >like all the subscribers are there as well. It's going to be *really* >painfull manually restoring all ~1200 addresses and their information, but >I suppose it will have to do. > >Whats really odd is that only one (of approx 30 lists) was corrupted, and >when I compare the output of the corrupted vs known goos files, they look >roughly identical. Probably that one list was the only one that was being or had 'recently' been updated when the power was removed. >Clearly they aren't, but... Is there any way to tell >"where" mailman thinks the corruption begins or is it just the absence of >a clean flag somewhere that I am hosed on? Mailman doesn't have a clue as to what the problem is. The file is a Python pickle and all Mailman knows is its attempt to cPickle.load() the file threw an exception or didn't return a Python dictionary. See . Also, you may be able to use some of the pickletools functions to help determine what might be wrong with the file and how to fix it, See . Also, see the text at the beginning of the /usr/lib/pythonx.x/pickletools.py file for documentation of the pickle file format. Note that config.pck is a "protocol 1" pickle. The first step would be to run the following Python commands. It is best to run them under withlist as the unpickling process may need access to Mailman. $ /usr/mailman/bin/withlist -i (some output) >>> import cPickle >>> fp = open('/usr/mailman/lists/[listname]/config.pck') >>> xxx = cPickle.load(fp) (some output about the error) >>> (enter control-D here to exit) Then, depending on the error, you might be able to use pickletools or just a dump of the file to see what the problem is. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Sun Oct 31 17:09:41 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 31 Oct 2010 09:09:41 -0700 Subject: [Mailman-Users] non-delivery to virtual domain In-Reply-To: <4CCC7C05.7040900@networktest.com> Message-ID: David Newman wrote: >(Apologies for re-raising a topic I asked about here a couple of years >ago. The instructions on Sourceforge have changed a bit since then.) > >New server runs OpenBSD 4.7, postfix 2.65, mailman 2.1.14, and virtual >domains. Mail sent to/from virtual domains works fine. > >Different story with Mailman. Although postfix says a message addressed >to a list is "sent" to all addresses, subscribers from virtual domains >on this server do not receive the message. Subscribers on other domains >not on this server do receive the message. There's no indication of >trouble in the Mailman logs or in maillog. What exactly does the Postfix log (maillog) say about the delivery to one of these addresses? >I've followed the setup instructions here, doing section 6.1.2 before >6.1.1 (given the link about doing virtual stuff first): > >http://mailman.sourceforge.net/mailman-install/postfix-virtual.html >http://mailman.sourceforge.net/mailman-install/postfix-integration.html This normally only affects delivery TO a list in a virtual domain. If done properly, it should not affect delivery to any non-list address in the virtual domains. >I've pasted the config files below. > >Thanks in advance for clues on getting Mailman to deliver to virtual >addresses on this server. This is almost certainly a Postfix issue rather than a Mailman issue. If there is nothing in Mailman's smtp-failure log, Mailman has delivered the message whith the local virtual recipients included to Postfix and Postfix has accepted it. See additional comments inline below. >server hostname: >mail.domain1.tld > >virtual domains: >domain1.tld # (not its real name!) >domain2.tld >domain3.tld > >----- > >from /etc/postfix/main.cf: > >.. > >myhostname = mail.domain1.tld >mydomain = domain1.tld >mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain > >.. > >alias_maps = hash:/etc/mail/aliases, hash:/usr/local/mailman/data/aliases > >virtual_alias_maps = > proxy:mysql:/etc/postfix/sql/forwardings.cf > proxy:mysql:/etc/postfix/sql/email2email.cf > hash:/usr/local/mailman/data/domain1-tld > hash:/usr/local/mailman/data/virtual-mailman Full output from "postconf -n" might help. >----- > >from /usr/local/mailman/Mailman/mm_cfg.py: > >MTA = 'Postfix' >MAILMAN_SITE_LIST = 'mailman' >DEFAULT_EMAIL_HOST = 'domain1.tld' >DEFAULT_URL_HOST = 'mail.domain1.tld' >DEFAULT_URL_PATTERN = 'https://%s/mailman/' >PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s' >IMAGE_LOGOS = '/icons/' >POSTFIX_ALIAS_CMD = '/usr/local/sbin/postalias' >POSTFIX_MAP_CMD = '/usr/local/sbin/postmap' >POSTFIX_STYLE_VIRTUAL_DOMAINS = [ 'domain2.tld', 'domain3.tld' ] ># Clear the Defaults.py VIRTUAL_HOSTS entry >VIRTUAL_HOSTS.clear() >add_virtualhost('DEFAULT_EMAIL_HOST', 'DEFAULT_URL_HOST') The above is backwards. It should be add_virtualhost('DEFAULT_URL_HOST', 'DEFAULT_EMAIL_HOST') >add_virtualhost('domain2.tld', 'domain2.tld') >add_virtualhost('domain3.tld', 'domain3.tld') However, nothing here affects delivery of mail FROM mailman. >----- > >/usr/local/mailman/data/aliases > > ># The ultimate loop stopper address >mailman-loop: /usr/local/mailman/data/owner-bounces.mbox > ># STANZA START: mailman ># CREATED: Sat Oct 30 11:23:37 2010 >mailman: "|/usr/local/mailman/mail/mailman post mailman" >mailman-admin: "|/usr/local/mailman/mail/mailman admin mailman" >mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman" >mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman" >mailman-join: "|/usr/local/mailman/mail/mailman join mailman" >mailman-leave: "|/usr/local/mailman/mail/mailman leave mailman" >mailman-owner: "|/usr/local/mailman/mail/mailman owner mailman" >mailman-request: "|/usr/local/mailman/mail/mailman request mailman" >mailman-subscribe: "|/usr/local/mailman/mail/mailman subscribe mailman" >mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mailman" ># STANZA END: mailman > ># STANZA START: s ># CREATED: Sat Oct 30 11:35:12 2010 >s: "|/usr/local/mailman/mail/mailman post s" >s-admin: "|/usr/local/mailman/mail/mailman admin s" >s-bounces: "|/usr/local/mailman/mail/mailman bounces s" >s-confirm: "|/usr/local/mailman/mail/mailman confirm s" >s-join: "|/usr/local/mailman/mail/mailman join s" >s-leave: "|/usr/local/mailman/mail/mailman leave s" >s-owner: "|/usr/local/mailman/mail/mailman owner s" >s-request: "|/usr/local/mailman/mail/mailman request s" >s-subscribe: "|/usr/local/mailman/mail/mailman subscribe s" >s-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe s" ># STANZA END: s Likewise, the aliases above only affect delivery TO the mailman and s lists. >----- > >/usr/local/etc/mailman/data/domain1-tld: > >domain1.tld IGNORE >@domain1.tld @mail.domain1.tld This file and its reference in virtual_alias_maps is conflicting as this says domain1.tld is a virtual alias domain and its presence in mydestination says it's not. Also, this is obsolete in Postfix. The current method of specifying to postfix that a domain is a virtual alias domain is to list it in virtual_alias_domains in main.cf. >----- > >/usr/local/mailman/data/virtual-mailman: > ># LOOP ADDRESSES START >mailman-loop at domain1.tld mailman-loop ># LOOP ADDRESSES END > ># STANZA START: s ># CREATED: Sat Oct 30 11:35:12 2010 >s at domain1.tld s >s-admin at domain1.tld s-admin >s-bounces at domain1.tld s-bounces >s-confirm at domain1.tld s-confirm >s-join at domain1.tld s-join >s-leave at domain1.tld s-leave >s-owner at domain1.tld s-owner >s-request at domain1.tld s-request >s-subscribe at domain1.tld s-subscribe >s-unsubscribe at domain1.tld s-unsubscribe ># STANZA END: s And this virtual mapping only affects delivery to the s at domain1.tld list and it's associated admin addresses, but since domain1.tld is not in POSTFIX_STYLE_VIRTUAL_DOMAINS (which is correct because it is in main.cf mydestination which makes it a postfix local domain), why is this list in virtual-mailman at all. >----- -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan