Mailman 3 June 2007 - Mailman-Users

Re: [Mailman-Users] Low level smtp error: Server not connected
by Leonard Jacobs June 4, 2007

June 4, 2007

> > On 5/29/07, Barry Warsaw wrote: > > >/ Does anybody else use Postfix 2.4? > / > Actually, I'm pretty sure we are currently using it on the NTP Public > Services Project pages at ntp.isc.org, which is the project I had > gotten involved in years ago, prior to getting involved in Mailman. > I got on this mailing list in order to help me figure out if it would > be a good idea to switch from Majordomo to Mailman, and I haven't > looked back since. > > Currently, these are the two primary open source projects where I > spend most of my time. > > > If you want to give it a test, I could install the latest postfix 2.5 > experimental or non-production patch releases on the python.org mail > servers, so that we can give the newer code a try. ;) > > > Seriously, I am quite convinced that the problem here is a > mis-configuration between Mailman and postfix, and that neither > program is necessarily "at fault". > > -- > Brad Knowles <brad at shub-internet.org <http://mail.python.org/mailman/listinfo/mailman-users>>, Consultant & Author > LinkedIn Profile: <http://tinyurl.com/y8kpxu> > Slides from Invited Talks: <http://tinyurl.com/tj6q4> Still having problems with Maioman via Postfix 2.4, so I just upgraded to the stable patch 2.4.3. My edited mm_cfg.py file: MTA = 'Postfix' DEFAULT_URL_HOST = 'lists.shambhala.com' DEFAULT_EMAIL_HOST = 'lists.shambhala.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) OWNERS_CAN_ENABLE_PERSONALIZATION = 1 SMTPPORT = 25 SMTPHOST = '192.168.1.130' [user]# ifconfig | grep 130 inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0 [user]# postconf | grep version mail_version = 2.4.3 Yes, I have stopped & restarted Mailman after each mm_cfg.py change and no, there are no anti-virus or other rejections with postfix. Additionally I am not running SELinux on this box. After my recent Postfix upgrade to 2.4.3, my logs/smtp-failure contains: Jun 03 23:54:13 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308(a)shambhala.com> Jun 03 23:54:19 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308(a)shambhala.com> Jun 03 23:54:20 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308(a)shambhala.com> Jun 03 23:54:21 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308(a)shambhala.com> Now one clue that might be relevant is that when creating test lists and testing sending messages to beta users of these lists, all works fine. But as soon as the list contains the actual number of users, in one case 5,100 members, in another 350 members, the mailings to the subscribers fail with the error as listed above. And there is no obvious throttling on the Postfix MTA. Think I should try downgrading to an earlier version of Postfix? It does seem like a recent upgrade of Postfix may have broken the connection that once did exist. Any other thoughts or suggestions would be appreciated. Thanks. --- [This E-mail scanned for viruses by Declude EVA]

2 1

Re: [Mailman-Users] multiple header_filter_rules?
by David R Bosso June 3, 2007

June 3, 2007

--On Friday, June 1, 2007 11:32 AM -0700 Mark Sapiro <msapiro(a)value.net> wrote: > David R Bosso wrote: >> --On May 22, 2007 4:53:05 PM -0700 Mark Sapiro <msapiro(a)value.net> wrote: >> >>> David R Bosso wrote: >>>> >>>> I have 2 rules set up. For a given test message, Rule 1 does not >>>> match, and Rule 2 does. If I have Rule 1 set to discard, and Rule 2 >>>> set to Hold, the message is discarded. If I make the single change >>>> of setting Rule 2 to Defer, then the message is accepted. >>> >>> Can you provide the contents of header_filter_rules, ideally from the >>> output of >>> >>> bin/dumpdb lists/<listname>/config.pck >> >> 'header_filter_rules': [ ( '^Return-Path: >> (?!(<dbosso(a)lsit\\.ucsb\\.edu>))', >> 3, >> False), >> ('^Subject: test', 7, False)], >> >>> and a copy of >>> the test message that illustrates the problem. >> >> A mail from me (rule 1 does not match), with the subject "test". > > > Sorry for the long delay in following up. I have tried to duplicate this > and I can't. I have the exact header_filter_rules as above and I send a > message from me (also doesn't match rule 1) with 'Subject: test' and it > is held by rule 2. [whoops. sent this to the list with the wrong address the first time] Rule 1 is (I thought) Match Return-Path:, only if it's not followed by dbosso(a)lsit.ucsb.edu. This should discard for any Return Path but my email address, did you modify it to match yours, or do I have the (?!...) syntax wrong? -David > I have tested with both the current SpamDetect.py rev 8146 and the 2.1.9 > base rev 7750 with the same result. See > <http://mailman.svn.sourceforge.net/viewvc/mailman/branches/Release_2_1-m > aint/mailman/Mailman/Handlers/SpamDetect.py?view=log> for more including > the source of these. > > -- > Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan

3 3

Problem with googlemail
by Patrick Krusenotto June 2, 2007

June 2, 2007

Hello altogether, My Name is Patrick and I am new to this list. I have got a serious problem with googlemail that I could'nt solve myself yet. I installed the mailman on top of exim on a suse virtual server under http://iqool.de/mailman It works perfect with all the accounts I tested it with. But there is one exception : Mailman does not get any mailings through my googlemail account. While all the administrative mailman-mails are coming through, all the member mailings are absorbed. The googlemail server gives no error. It just eats the mails and seems to throw them to /dev/null I tried over and over again, but had no success. I was very surprised, that I do not have any Problems to receive mails from mailman-users(a)python.org. Can anyone give me hint? Is there a special configuration, that is needed to let googlemail deliver the mails? Thank you very much for your help. Patrick

2 2

Re: [Mailman-Users] Pipermail --> MHonArc error
by Richard Barrett June 2, 2007

June 2, 2007

Karl I just noticed the posting that you made to mailman-users. I think that what is triggering the exception is the way you are running arch. When you run arch the first time with the --wipe option, the existing HTML archive content is deleted and the new HTML archive content is generated by MHonArc from the list's .mbox content, assuming you have set the list to use mhonarc as it archive page generator. When you then run arch a second time without the the --wipe option you are telling MHonArc to generate HTML archive content from the same .mbox with the same content as on the previous run with the -- wipe option. But MHonArc does not find any new messages to add to the HTML archive as it is being handed the same messages again. Normally, MHonArc "optimises out" "duplicate" messages (based on Message-id: I believe). I think that when it finds nothing to add to the HTML archive it closes the pipe connection back to the Mailman process prematurely, leading to the exception. I will publish a revised MHonArc/Mailman integration patch to handle this condition but in the meantime you should be able avoid the problem by not running arch with the same input .mbox as on a previous run. No loss, as the second run of arch serves no useful purpose. Regards Richard On Tue May 1 21:56:17 CEST 2007 you posted the following to the mailman-users list: I am trying to convert a list from the Pipermail archiver to MhonArc. I can run /bin/arch --wipe listname successfully. I get this error when generating the MhonArc archive with /bin/arch listname Pickling archive state into /data/mailman/archives/private/listname/pipermail.pck Traceback (most recent call last): File "./arch", line 202, in ? main() File "./arch", line 190, in main archiver.processUnixMailbox(fp, start, end) File "/data/mailman/Mailman/Archiver/pipermail.py", line 576, in processUnixMailbox self.mhonarcProcessUnixMailbox(input, start, end) File "/data/mailman/Mailman/Archiver/pipermail.py", line 706, in mhonarcProcessUnixMailbox status = mhonarch_process.close() IOError: [Errno 32] Broken pipe If I switch back to Pipermail it will run successfully. It looks too that I miss March and April 2007 archives when trying to convert to MHonArc, but Pipermail generates them. Would this point to an problem in the .mbox file? --Karl

1 0

Re: [Mailman-Users] Maximum template size?
by Carter Braxton June 2, 2007

June 2, 2007

"Mark Sapiro" <msapiro(a)value.net> wrote: > The problem is the non-substitution '%' characters in your template. Ouch, this is another one of those "D'oh!" moments! Should have seen that, thanks for pointing it out. Is there a way to escape the "%" sign to prevent substitution? (I'm not very familiar with Python, have been a C programmer for 25 years.) Also, I was wondering, what is the reason for using the hex code "%40" instead of "@" in the URLs provided to users? -- Carter Braxton cbraxton(a)iname.com (Note: Any ads appended here are from my email service.) = AMP Violin Lessons on DVD Studio Lessons on DVD for Beginners and Intermediates. http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=452d3305c117066abeb6338…

2 1

How do I change the footer and owner email address?
by Me Myself June 1, 2007

June 1, 2007

I'm using cpanel and RHL. The URL at the bottom of the mailman mailings (that's supposed to go to our mailman page) is incorrect and produces a 404. Emails also that are supposed to go to mailman-owner are going to our web host postmaster instead. How do I correct this? Thanks in advance.

2 1

Does Mailman require a MySQL database?
by Me Myself June 1, 2007

June 1, 2007

Wasn't sure as the install was done automatically in cpanel. Thanks.

3 2

(no subject)
by Jens Andersson June 1, 2007

June 1, 2007

unsubscribe

1 0

multiple header_filter_rules?
by David R Bosso June 1, 2007

June 1, 2007

Howdy, I'm seeing the following oddity with header_filter_rules. I have 2 rules set up. For a given test message, Rule 1 does not match, and Rule 2 does. If I have Rule 1 set to discard, and Rule 2 set to Hold, the message is discarded. If I make the single change of setting Rule 2 to Defer, then the message is accepted. Any idea why the Action for Rule 1 is being used when Rule 2 is hit? Can anyone else reproduce this? Am I misunderstanding something about Rule processing order? Using Mailman 2.1.9 Thanks. -David

2 4

OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/testing.mbox'
by Noah June 1, 2007

June 1, 2007

Hi, Okay I give up. I am attempting to create a mail list called testing but I receive the error below. What are the proper permissions for /usr/local/mailman/archives/private/ ? # ls -dl /usr/local/mailman/archives/private/ drwxr-s--x 131 mailman mailman 3072 Feb 28 16:18 /usr/local/mailman/archives/private/ ---- snip ---- May 31 20:40:33 2007 admin(27921): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(27921): [----- Mailman Version: 2.1.9 -----] admin(27921): [----- Traceback ------] admin(27921): Traceback (most recent call last): admin(27921): File "/usr/local/mailman/scripts/driver", line 101, in run_main admin(27921): main() admin(27921): File "/usr/local/mailman/Mailman/Cgi/create.py", line 56, in main admin(27921): process_request(doc, cgidata) admin(27921): File "/usr/local/mailman/Mailman/Cgi/create.py", line 190, in process_request admin(27921): mlist.Create(listname, owner, pw, langs, emailhost) admin(27921): File "/usr/local/mailman/Mailman/MailList.py", line 493, in Create admin(27921): self.InitVars(name, admin, crypted_password) admin(27921): File "/usr/local/mailman/Mailman/MailList.py", line 404, in InitVars admin(27921): baseclass.InitVars(self) admin(27921): File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 96, in InitVars admin(27921): os.mkdir(self.archive_dir()+'.mbox', 02775) admin(27921): OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/testing.mbox' admin(27921): [----- Python Information -----] ---- snip ---

2 2