Re: [Mailman-Users] Mailman Borks on Large Attachments
Prior to Mailman 2.1.9, the error would have occurred once and the message would have been lost. Beginning in 2.1.9, a queue file backup/recovery mechanism was implemented which allowed messages that were in process when a crash occurred to be recovered, but the problem here is that if the message itself causes the crash, a loop occurs such as you experienced. This is addressed in 2.1.10b3 by counting the number of times a .bak file has been recovered and moving it aside after 3 tries. It would be wonderful if you could install the latest Mailman/Queue/Switchboard.py from http://codebrowse.launchpad.net/~mailman-coders/mailman/2.1/files and see if this mitigates the problem. Ok, I will definitely try this. Yes, it does solve the problem of processing on the lists stopping completely. I'll keep that file in my Mailman! Thank-you. Now to just work out the root cause of the memory errors ... Lachlan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman Borks on Large Attachments
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Feb 5, 2008, at 6:23 AM, Lachlan Michael wrote: Now to just work out the root cause of the memory errors ... It's important to remember that Python's email parsing code sucks the entire message text into memory and keeps large attachments in memory after parsing too. There could be a number of problems associated with this, including a memory leak that causes the raw text to be kept even after parsing, or that the attachment is just to big to be kept in memory after parsing. There have been talks over the years about how to modify the email package's api's so that it would be possible to store large attachments in a separate file outside of core memory, but this has yet to be done. Now would be a good time to look into it again, if we have any hopes of getting something like this into Python 2.6 and 3.0. However, this isn't the right place to discuss such changes -- those should happen on Python's email sig: http://www.python.org/sigs/email-sig Cheers, - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHqFHa2YZpQepbvXERAtYvAJ9C0dNZQrePE/ICqlF1uXuYffNvHwCcDvVz 3lpV5w9yQqJfq8WaN9bVkww= =pmiS -END PGP SIGNATURE- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outgoing qrunner stops working and outgoing mails get stuck
For some reason my previous posts never reached the mailing list, so I repost it here, sorry for the delay: Mark Sapiro ha scritto: Jan 27 13:34:57 2008 (2154) [EMAIL PROTECTED] smtp to test for 1 recips, completed in 55.860 seconds Jan 27 13:37:21 2008 (2154) [EMAIL PROTECTED] smtp to test for 1 recips, completed in 63.191 seconds This is highly suspicious. The times above are the time from start to finish of the SMTP interaction with Qmail. These times, particularly the last few are HUGE. Why? After a look at the log of the smtp server (see below), I can guess that the reason might be an high load on the system due to intense spamassassin activity: at the time of the error there were 20 connections (the maximum number of allowable concurrent connections) to the server, which, considering the traffic of our server, highlights a spamming session. Is it possible that the reason for the outgoing runner to stop is related to this huge time or to the system load? Somewhere around here (13:37:21 minus 00:01:03.191) OutgoingRunner started SMTP delivery of the post to Qmail. Here is the log from the smtp server for that time, in case it can help: (qmail is patched to check the 'rcpt to' against a valid addresses list before accepting a message and to reject during the smtp conversation the mails which achieve a very high spamassassin spam score) 2008-01-27 13:36:00.396206500 qmail-smtpd: validrcptto RCPT TO: [EMAIL PROTECTED] 2008-01-27 13:36:00.396215500 qmail-smtpd: validrcptto found: @MYDOMAIN 2008-01-27 13:36:03.361324500 X-Antivirus-MYDOMAIN-1.25-st-qms: We have reasons to believe this mail is SPAM 2008-01-27 13:36:03.613234500 X-Antivirus-MYDOMAIN-1.25-st-qms: We have reasons to believe this mail is SPAM 2008-01-27 13:36:04.365972500 tcpserver: end 27763 status 256 2008-01-27 13:36:04.365978500 tcpserver: status: 19/20 2008-01-27 13:36:04.365979500 tcpserver: status: 20/20 2008-01-27 13:36:04.365981500 tcpserver: pid 27919 from 202.156.55.133 2008-01-27 13:36:04.365983500 tcpserver: ok 27919 MYDOMAIN:MYDOMAINIP:25 cm133.gamma55.maxonline.com.sg:202.156.55.133::1794 2008-01-27 13:36:04.546585500 tcpserver: end 27792 status 256 2008-01-27 13:36:04.546590500 tcpserver: status: 19/20 2008-01-27 13:36:04.546592500 tcpserver: status: 20/20 2008-01-27 13:36:04.546593500 tcpserver: pid 27920 from 211.158.55.6 2008-01-27 13:36:05.498585500 tcpserver: ok 27920 MYDOMAIN:MYDOMAINIP:25 :211.158.55.6::2133 2008-01-27 13:36:05.498591500 tcpserver: end 27920 status 256 2008-01-27 13:36:05.498593500 tcpserver: status: 19/20 2008-01-27 13:36:05.498594500 tcpserver: status: 20/20 2008-01-27 13:36:05.498596500 tcpserver: pid 27921 from 221.146.194.29 2008-01-27 13:36:05.498598500 tcpserver: ok 27921 MYDOMAIN:MYDOMAINIP:25 :221.146.194.29::1074 2008-01-27 13:36:05.498600500 tcpserver: end 27921 status 256 2008-01-27 13:36:05.498601500 tcpserver: status: 19/20 2008-01-27 13:36:05.499279500 tcpserver: status: 20/20 2008-01-27 13:36:05.499286500 tcpserver: pid 27922 from 89.76.17.147 2008-01-27 13:36:05.499287500 tcpserver: ok 27922 MYDOMAIN:MYDOMAINIP:25 chello089076017147.chello.pl:89.76.17.147::62209 2008-01-27 13:36:06.977693500 X-Antivirus-MYDOMAIN-1.25-st-qms: We have reasons to believe this mail is SPAM 2008-01-27 13:36:07.045020500 qmail-smtpd: validrcptto RCPT TO: [EMAIL PROTECTED] 2008-01-27 13:36:07.045025500 qmail-smtpd: validrcptto found: [EMAIL PROTECTED] 2008-01-27 13:36:08.709515500 tcpserver: end 27764 status 256 2008-01-27 13:36:08.709521500 tcpserver: status: 19/20 2008-01-27 13:36:08.709523500 tcpserver: status: 20/20 2008-01-27 13:36:08.709526500 tcpserver: pid 27939 from 58.8.90.161 2008-01-27 13:36:08.709528500 tcpserver: ok 27939 MYDOMAIN:MYDOMAINIP:25 ppp-58-8-90-161.revip2.asianet.co.th:58.8.90.161::23932 2008-01-27 13:36:09.239802500 qmail-smtpd: validrcptto RCPT TO: [EMAIL PROTECTED] 2008-01-27 13:36:09.239808500 qmail-smtpd: validrcptto found: @MYDOMAIN 2008-01-27 13:36:11.326256500 qmail-smtpd: validrcptto RCPT TO: [EMAIL PROTECTED] 2008-01-27 13:36:11.382459500 qmail-smtpd: validrcptto found: @MYDOMAIN 2008-01-27 13:36:12.198188500 X-Antivirus-MYDOMAIN-1.25-st-qms: We have reasons to believe this mail is SPAM 2008-01-27 13:36:13.033921500 tcpserver: end 27835 status 0 2008-01-27 13:36:13.033926500 tcpserver: status: 19/20 2008-01-27 13:36:13.033927500 tcpserver: status: 20/20 2008-01-27 13:36:13.033929500 tcpserver: pid 27954 from 221.146.194.29 2008-01-27 13:36:13.033931500 tcpserver: ok 27954 MYDOMAIN:MYDOMAINIP:25 :221.146.194.29::1264 2008-01-27 13:36:13.033933500 tcpserver: end 27858 status 256 2008-01-27 13:36:13.033934500 tcpserver: status: 19/20 2008-01-27 13:36:13.033936500 tcpserver: status: 20/20 2008-01-27 13:36:13.033937500 tcpserver: pid 27956 from 211.158.55.6 2008-01-27 13:36:13.598710500 tcpserver: ok 27956 MYDOMAIN:MYDOMAINIP:25 :211.158.55.6::1232 2008-01-27 13:36:13.989282500 tcpserver: end 27954 status 256 2008-01-27 13:36:13.989290500 tcpserver: status:
Re: [Mailman-Users] Outgoing qrunner stops working and outgoing mails get stuck
SP ha scritto:
Ok, thanks: I will patch mailman immediately and post here the 'error'
log as soon as the error appears again.
Here the relevant part of mailman 'error' log (the time of the last sent
message is 22.29 and the time of the first message which gets stuck in
qfiles/out is 22.30):
Feb 03 22:26:03 2008 qrunner(20175): connect: ('localhost', 25)
Feb 03 22:26:03 2008 qrunner(20175): connect: ('localhost', 25)
Feb 03 22:26:03 2008 qrunner(20175): reply: '220 MYDOMAIN ESMTP\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: retcode (220); Msg: MYDOMAIN
ESMTP
Feb 03 22:26:03 2008 qrunner(20175): connect: MYDOMAIN ESMTP
Feb 03 22:26:03 2008 qrunner(20175): send: 'ehlo www.MYDOMAIN\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250-MYDOMAIN\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250-AUTH LOGIN CRAM-MD5
PLAIN\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250-AUTH=LOGIN CRAM-MD5
PLAIN\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250-STARTTLS\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250-PIPELINING\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250 8BITMIME\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: retcode (250); Msg: MYDOMAIN
AUTH LOGIN CRAM-MD5 PLAIN
AUTH=LOGIN CRAM-MD5 PLAIN
STARTTLS
PIPELINING
8BITMIME
Feb 03 22:26:03 2008 qrunner(20175): send: 'mail
FROM:[EMAIL PROTECTED]\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250 ok\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: retcode (250); Msg: ok
Feb 03 22:26:03 2008 qrunner(20175): send: 'rcpt
TO:[EMAIL PROTECTED]\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '250 ok\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: retcode (250); Msg: ok
Feb 03 22:26:03 2008 qrunner(20175): send: 'data\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: '354 go ahead\r\n'
Feb 03 22:26:03 2008 qrunner(20175): reply: retcode (354); Msg: go ahead
Feb 03 22:26:03 2008 qrunner(20175): data: (354, 'go ahead')
Feb 03 22:26:03 2008 qrunner(20175): send: 'Return-Path:
[EMAIL PROTECTED]\r\nDelivered-To: [EMAIL PROTECTED]:
(qmail 3364 invoked by uid 511); 3 Feb 2008 22:26:02 +0100\r\nDate: 3
Feb 2008 22:26:02 +0100\r\nMessage-ID:
[EMAIL PROTECTED]\r\nFrom: [EMAIL PROTECTED]:
[EMAIL PROTECTED]: [Test] Test Sun Feb 3 22:26:02 CET
2008\r\nX-BeenThere: [EMAIL PROTECTED]:
2.1.9\r\nPrecedence: list\r\nList-Id:
test.MYDOMAIN\r\nList-Unsubscribe:
http://MYDOMAIN/mailman/listinfo/test,\r\n\tmailto:[EMAIL
PROTECTED]\r\nList-Archive:
http://MYDOMAIN/pipermail/test\r\nList-Post:
mailto:[EMAIL PROTECTED]\r\nList-Help:
mailto:[EMAIL PROTECTED]\r\nList-Subscribe:
http://MYDOMAIN/mailman/listinfo/test,\r\n\tmailto:[EMAIL
PROTECTED]\r\nMIME-Version:
1.0\r\nContent-Type: text/plain;
charset=iso-8859-1\r\nContent-Transfer-Encoding:
quoted-printable\r\nSender: [EMAIL PROTECTED]:
[EMAIL PROTECTED] Feb 3 22:26:02 CET
2008\r\n___\r\nTest mailing
[EMAIL PROTECTED]://MYDOMAIN/mailman/listinfo/test\r\n.\r\n'
Feb 03 22:26:06 2008 qrunner(20175): reply: '250 ok 1202073966 qp
3369\r\n'
Feb 03 22:26:06 2008 qrunner(20175): reply: retcode (250); Msg: ok
1202073966 qp 3369
Feb 03 22:26:06 2008 qrunner(20175): data: (250, 'ok 1202073966 qp 3369')
Feb 03 22:26:06 2008 qrunner(20175): send: 'quit\r\n'
Feb 03 22:26:06 2008 qrunner(20175): reply: '221 MYDOMAIN\r\n'
Feb 03 22:26:06 2008 qrunner(20175): reply: retcode (221); Msg: MYDOMAIN
Feb 03 22:29:40 2008 qrunner(20175): connect: ('localhost', 25)
Feb 03 22:29:40 2008 qrunner(20175): connect: ('localhost', 25)
Feb 03 22:30:18 2008 qrunner(20175): reply: '220 MYDOMAIN ESMTP\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: retcode (220); Msg: MYDOMAIN
ESMTP
Feb 03 22:30:18 2008 qrunner(20175): connect: MYDOMAIN ESMTP
Feb 03 22:30:18 2008 qrunner(20175): send: 'ehlo www.MYDOMAIN\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: '250-MYDOMAIN\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: '250-AUTH LOGIN CRAM-MD5
PLAIN\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: '250-AUTH=LOGIN CRAM-MD5
PLAIN\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: '250-STARTTLS\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: '250-PIPELINING\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: '250 8BITMIME\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: retcode (250); Msg: MYDOMAIN
AUTH LOGIN CRAM-MD5 PLAIN
AUTH=LOGIN CRAM-MD5 PLAIN
STARTTLS
PIPELINING
8BITMIME
Feb 03 22:30:18 2008 qrunner(20175): send: 'mail
FROM:[EMAIL PROTECTED]\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: '250 ok\r\n'
Feb 03 22:30:18 2008 qrunner(20175): reply: retcode (250); Msg: ok
Feb 03 22:30:18 2008 qrunner(20175): send: 'rcpt
TO:[EMAIL PROTECTED]\r\n'
Feb 03 22:30:19 2008 qrunner(20175): reply: '250 ok\r\n'
Feb 03 22:30:19 2008 qrunner(20175): reply: retcode (250); Msg: ok
Feb 03 22:30:19 2008 qrunner(20175): send: 'data\r\n'
Feb 03 22:30:20 2008 qrunner(20175): reply: '354 go ahead\r\n'
Feb 03 22:30:20 2008 qrunner(20175):
Re: [Mailman-Users] Mailman Cron question FIXED
Marvin Raab wrote: Thanks for the response. Yup, it does. So, I should simply comment out all lines in the crontab.in file? I said: To resolve the problem, I had root use: crontab -u mailman -e and manually edited the file; removing the mailman field In Fedora 8 using yum to install, it appears that stopping and restarting the mailman service does not copy the crontab.in file to the mailman user's crontab. Mark Sapiro said: But does it copy it to /etc/cron.d/mailman? If so, you will be running duplicates of all the cron jobs which will result in duplicate password reminders and admin notices and other problems. No. What you should do is remove your hand installed mailman crontab crontab -u mailman -r and let your yum installed package work as it was intended to. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Still Lost
I'm not very technical so I need some more help please. Step me through in terms that are for dummies like me. I'll try to explain: I have 20+ Mailing Lists setup with each containing a unique set of individuals who are to receive email sent to the list. Some indididuals need the ability to send email to all mailing lists, while others should only be authorized to some of them. Here is where I'm confused. For each of my lists, I need for certain individuals to be able to be able to submit to the mailing list but only those that I define. In the Privacy Section/Sender Filters/All mailing list administration do I set the By default, should new list member postings be moderated? to No then add the list on individuals to the List of non-member addresses whose postings should be automatically accepted. I guess the name 'non-member' is where I'm confused or should I do something different? In an email from Brad Knowles, he stated: If they are not subscribers, then they need to be on the whitelist. But I cannot find a whitelist anywhere. I'm getting a lot of heat from our Boy Scout Troop's Leaders and need to get this functional as soon as possible. Thanks ahead of time Jacsdad aka Thomas J Casey Upon his retirement, a former NASCAR Winston Cup Champion was quoted: the Older I get... the Better I was -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Scripts Associated with Log File Rotation
Hi There,
I have been studying the mailman code this morning to find a way to do some
processing when the mailman logs are rotated. My goal is to process the
data in /var/log/mailman/subscribe.1 and /var/log/mailman/bounce.1 just
after they are rotated. I reviewed the file /etc/logrotate.d/mailman on my
RHEL system which seems to control rotating the logs - below is a copy of
the file for reference.
/var/log/mailman/bounce /var/log/mailman/digest /var/log/mailman/error
/var/log/mailman/post /var/log/mailman/smtp /var/log/mailman/smtp-failure
/var/log/mailman/qrunner /var/log/mailman/locks /var/log/mailman/fromusenet
/var/log/mailman/subscribe /var/log/mailman/vette {
missingok
sharedscripts
postrotate
/usr/lib/mailman/bin/mailmanctl reopen /dev/null 21 || true
endscript
}
I have a couple of question about doing what I need to without breaking
anything:
(1) The time stamps of the log files on my system are not all the same.
The time stamp of /var/log/mailman/subscribe.1 and /var/log/mailman/bounce.1
are not even on the same day. This implies that rotation for these files is
happening at different times. I'm concerned about making one change to the
logrotate.d file above - like adding a line to the postrotate section - as a
result.
(2) My first concern leads me to break subscribe and bounce into separate
entries in the logrotate.d file. Is the solution to what I am trying to
accomplish as simple as the following:
a. Append the existing logrotate.d file to itself two times - resulting
in a file that has three logrotate sections
b. Delete bounce and subscribe from the first section
c. Delete all but bounce from the second section add my script to run
against bounce.1 just before endscript
d. Delete all but subscribe from the third section add my script to
run against subscribe.1 just before endscript.
e. This implies mailmanctl will run three times for each invocation of
logrotate - it only runs once with the distribution file due to
sharedscripts. Is this OK?
Thanks for your assistance with this helping me not break anything as I
make this enhancement to our production system, Greg
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Scripts Associated with Log File Rotation
Greg Sims wrote: I have a couple of question about doing what I need to without breaking anything: (1) The time stamps of the log files on my system are not all the same. The time stamp of /var/log/mailman/subscribe.1 and /var/log/mailman/bounce.1 are not even on the same day. This implies that rotation for these files is happening at different times. No it doesn't. All it says is that at the time subscribe and bounce were renamed to subscribe.1 and bounce.1, the time stamps on those files were different. I'm concerned about making one change to the logrotate.d file above - like adding a line to the postrotate section - as a result. (2) My first concern leads me to break subscribe and bounce into separate entries in the logrotate.d file. You don't need to do this at all. Your concern is based on an erroneous assumption. Just add your processing of the *.1 files after the mailmanctl reopen line. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Scripts Associated with Log File Rotation
I updated the /etc/logrotate.d/mailman file as you suggested. Thanks! Greg -Original Message- From: Mark Sapiro [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 05, 2008 9:33 AM To: Greg Sims; mailman-users@python.org Subject: Re: [Mailman-Users] Scripts Associated with Log File Rotation Greg Sims wrote: I have a couple of question about doing what I need to without breaking anything: (1) The time stamps of the log files on my system are not all the same. The time stamp of /var/log/mailman/subscribe.1 and /var/log/mailman/bounce.1 are not even on the same day. This implies that rotation for these files is happening at different times. No it doesn't. All it says is that at the time subscribe and bounce were renamed to subscribe.1 and bounce.1, the time stamps on those files were different. I'm concerned about making one change to the logrotate.d file above - like adding a line to the postrotate section - as a result. (2) My first concern leads me to break subscribe and bounce into separate entries in the logrotate.d file. You don't need to do this at all. Your concern is based on an erroneous assumption. Just add your processing of the *.1 files after the mailmanctl reopen line. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Porting from a 2.1.5 installation to 2.1.7
Hi, I am retiring a server running Mailman 2.1.5 and need to port everything to a server running 2.1.7 (Fedora Core distribution). Can I take the lists directory and simply copy it from one server to another (i.e., is the format of the various files the same)? Is there anything else that needs to be copied? Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outgoing qrunner stops working and outgoingmails get stuck
ippaso wrote: After a look at the log of the smtp server (see below), I can guess that the reason might be an high load on the system due to intense spamassassin activity: at the time of the error there were 20 connections (the maximum number of allowable concurrent connections) to the server, which, considering the traffic of our server, highlights a spamming session. Is it possible that the reason for the outgoing runner to stop is related to this huge time or to the system load? Yes, but I have some thoughts based on the smtplib debugs to which I'll reply next. Somewhere around here (13:37:21 minus 00:01:03.191) OutgoingRunner started SMTP delivery of the post to Qmail. Here is the log from the smtp server for that time, in case it can help: (qmail is patched to check the 'rcpt to' against a valid addresses list before accepting a message and to reject during the smtp conversation the mails which achieve a very high spamassassin spam score) This appears to be the reason for the large delays when the load is high. If at all possible, you should not be spam scanning outgoing mail from Mailman as all such mail is either a Mailman notice or a post which was already scanned on the way in. In my case for example, I have tight control over my server, so I don't spam scan any outgoing mail at all. snip What if anything is in Mailman's error and smtp-failure logs? The only entry from 'error' log (when I copied the logs for the previous post it wasn't here yet...): Jan 27 14:17:58 2008 (2154) Cannot connect to SMTP server localhost on port smtp And here from 'smtp-failure' Jan 27 14:17:58 2008 (2154) Low level smtp error: (4, 'Interrupted system call'), msgid: [EMAIL PROTECTED] Was this at the time that you restarted Mailman? -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] adding REL=nofollow in Mailman's archives
As some of the mailing lists I administer experience a steady flow of spam, I was looking for a way to add REL=nofollow attribute to Mailman's messages. As I didn't find a way to do it in Mailman, and I don't know enough of Python, I decided to write a simple Perl script which does it. This is one of my first bites at Perl, so be gentle: http://wpkg.org/REL=%22nofollow%22_and_Mailman For some, REL=nofollow may be controversial, though. -- Tomasz Chmielewski -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outgoing qrunner stops working and outgoingmails get stuck
ippaso wrote:
SP ha scritto:
Ok, thanks: I will patch mailman immediately and post here the 'error'
log as soon as the error appears again.
Here the relevant part of mailman 'error' log (the time of the last sent
message is 22.29 and the time of the first message which gets stuck in
qfiles/out is 22.30):
snip
The following are the connect to start sending the last message
successfully sent.
Feb 03 22:32:14 2008 qrunner(20175): connect: ('localhost', 25)
Feb 03 22:32:14 2008 qrunner(20175): connect: ('localhost', 25)
Qmail is busy here too. Reply to connect takes 41 seconds.
Feb 03 22:32:55 2008 qrunner(20175): reply: '220 MYDOMAIN ESMTP\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: retcode (220); Msg: MYDOMAIN
ESMTP
And the connect succeeded and we begin to send.
Feb 03 22:32:55 2008 qrunner(20175): connect: MYDOMAIN ESMTP
Feb 03 22:32:55 2008 qrunner(20175): send: 'ehlo www.MYDOMAIN\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250-MYDOMAIN\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250-AUTH LOGIN CRAM-MD5
PLAIN\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250-AUTH=LOGIN CRAM-MD5
PLAIN\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250-STARTTLS\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250-PIPELINING\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250 8BITMIME\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: retcode (250); Msg: MYDOMAIN
AUTH LOGIN CRAM-MD5 PLAIN
AUTH=LOGIN CRAM-MD5 PLAIN
STARTTLS
PIPELINING
8BITMIME
Feb 03 22:32:55 2008 qrunner(20175): send: 'mail
FROM:[EMAIL PROTECTED]\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250 ok\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: retcode (250); Msg: ok
Feb 03 22:32:55 2008 qrunner(20175): send: 'rcpt
TO:[EMAIL PROTECTED]\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '250 ok\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: retcode (250); Msg: ok
Feb 03 22:32:55 2008 qrunner(20175): send: 'data\r\n'
Feb 03 22:32:55 2008 qrunner(20175): reply: '354 go ahead\r\n'
Feb 03 22:32:56 2008 qrunner(20175): reply: retcode (354); Msg: go ahead
Feb 03 22:32:56 2008 qrunner(20175): data: (354, 'go ahead')
Feb 03 22:32:56 2008 qrunner(20175): send: 'Return-Path:
[EMAIL PROTECTED]\r\nDelivered-To: [EMAIL PROTECTED]:
(qmail 4288 invoked by uid 511); 3 Feb 2008 22:29:12 +0100\r\nDate: 3
Feb 2008 22:29:12 +0100\r\nMessage-ID:
[EMAIL PROTECTED]\r\nFrom: [EMAIL PROTECTED]:
[EMAIL PROTECTED]: [Test] Test Sun Feb 3 22:29:12 CET
2008\r\nX-BeenThere: [EMAIL PROTECTED]:
2.1.9\r\nPrecedence: list\r\nList-Id:
test.MYDOMAIN\r\nList-Unsubscribe:
http://MYDOMAIN/mailman/listinfo/test,\r\n\tmailto:[EMAIL
PROTECTED]\r\nList-Archive:
http://MYDOMAIN/pipermail/test\r\nList-Post:
mailto:[EMAIL PROTECTED]\r\nList-Help:
mailto:[EMAIL PROTECTED]\r\nList-Subscribe:
http://MYDOMAIN/mailman/listinfo/test,\r\n\tmailto:[EMAIL
PROTECTED]\r\nMIME-Version:
1.0\r\nContent-Type: text/plain;
charset=iso-8859-1\r\nContent-Transfer-Encoding:
quoted-printable\r\nSender: [EMAIL PROTECTED]:
[EMAIL PROTECTED] Feb 3 22:29:12 CET
2008\r\n___\r\nTest mailing
[EMAIL PROTECTED]://MYDOMAIN/mailman/listinfo/test\r\n.\r\n'
Above, we send the message at 22:32:56. We do not receive the reply
below until 22:33:23. Presumably, Qmail spent most of the 27 seconds
doing the spam scanning.
Feb 03 22:33:23 2008 qrunner(20175): reply: '250 ok 1202074403 qp
5450\r\n'
Feb 03 22:33:23 2008 qrunner(20175): reply: retcode (250); Msg: ok
1202074403 qp 5450
Feb 03 22:33:23 2008 qrunner(20175): data: (250, 'ok 1202074403 qp 5450')
Feb 03 22:33:23 2008 qrunner(20175): send: 'quit\r\n'
Feb 03 22:33:23 2008 qrunner(20175): reply: '221 MYDOMAIN\r\n'
Feb 03 22:33:23 2008 qrunner(20175): reply: retcode (221); Msg: MYDOMAIN
Now, the message is sent and accepted and we try to connect again to
send the next message.
Feb 03 22:33:23 2008 qrunner(20175): connect: ('localhost', 25)
Feb 03 22:33:23 2008 qrunner(20175): connect: ('localhost', 25)
But we receive no reply to our connect and no timeout either, so we are
still waiting.
I'm not sure where the problem is, but it is outside Mailman. The
underlying Python smtplib has issued a tcp/ip connect request to
localhost, port 25 and is waiting for some kind of response, i.e., a
response from the process listening on localhost:25, a tcp/ip refusal
or a tcp/ip timeout. None of these things occur, so we just wait.
I have no idea whether this is an OS issue, a networking issue or a
Qmail issue, but there should eventually be a reply or a timeout.
Again at the moment of the failure the system load was high since there
were about 20 simultaneous connections to the smtp server, and
consequently many spamassassins processes, and from the mailman 'smtp'
log again it took many time to deliver the last few messages:
Feb 03 22:25:10 2008 (20175) [EMAIL PROTECTED] smtp
to test for 1 recips, completed in 3.815 seconds
Feb 03
Re: [Mailman-Users] Porting from a 2.1.5 installation to 2.1.7
Rob Tanner wrote: I am retiring a server running Mailman 2.1.5 and need to port everything to a server running 2.1.7 (Fedora Core distribution). Can I take the lists directory and simply copy it from one server to another (i.e., is the format of the various files the same)? Is there anything else that needs to be copied? There are many threads on this in the archives of the mailman-users list. The FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp points to a few of them. In short, for 2.1.5 to 2.1.7, you can move the lists/ directory and Mailman will transparently update config.pck formats as necessary as lists are accessed. Note the following: If you move the lists/*/request.pck files, you also need to move any data/heldmsg-* files. OTOH, you can ignore any held messages on the old server, in which case, it's better to not move the request.pck files. If you want to move archives, you can move the entire archives/private/ directory. You don't really need to worry about archives/public/ as the symlinks therein will be recreated on the new system as the lists are accessed, but if you want to move archives/public/, make sure that you move the symlinks and not the directories they point to. If you want to be selective about which archives to move, make sure that you move both the archives/private/listname/ and the archives/private/listname.mbox/ directories for each list. You also have to deal with MTA aliases on the new server if the MTA uses aliases for Mailman. If the domain names for web and email will be the same on the new server, that's all. If not, you need to run fix_url to update the lists. Also, in this case, it might be better to just move the archives/private/listname.mbox/ directories and rebuild the archives with bin/arch --wipe so that the listinfo links in the archives will have the correct host name. If you are going to rebuild archives, it is good to first check the archives/private/listname.mbox/listname.mbox file with bin/cleanarch. See: bin/arch --help bin/cleanarch --help http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.069.htp -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Disable monthly Memberships EMail
Is there a way to turn off the monthly Memberships Reminder EMail. I have an announcements list and don't want any additional EMail. I have searched on Google and the Archives, for this but all I see is how to turn off the Password Reminder, which is already off. Thanks for your help. --- Victor M.J. Ryden -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Disable monthly Memberships EMail
Victor M.J. Ryden wrote: Is there a way to turn off the monthly Memberships Reminder EMail. I have an announcements list and don't want any additional EMail. I have searched on Google and the Archives, for this but all I see is how to turn off the Password Reminder, which is already off. The password reminder is the only Monthly reminder that Mailman sends. It is the mail with Subject: hostname mailing list memberships reminder. If you have set send_reminders to No on the list's General Options page, reminders will not be sent for that list, but a list member may be sent a reminder for other lists in the same installation. If you control the Mailman server, you can remove the mailpasswds entry from Mailman's crontab, and no reminders will ever be sent for any list. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Porting from a 2.1.5 installation to 2.1.7
That was very very helpful. Thanks! -- Rob Mark Sapiro said the following on 02/05/2008 01:22 PM: Rob Tanner wrote: I am retiring a server running Mailman 2.1.5 and need to port everything to a server running 2.1.7 (Fedora Core distribution). Can I take the lists directory and simply copy it from one server to another (i.e., is the format of the various files the same)? Is there anything else that needs to be copied? There are many threads on this in the archives of the mailman-users list. The FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp points to a few of them. In short, for 2.1.5 to 2.1.7, you can move the lists/ directory and Mailman will transparently update config.pck formats as necessary as lists are accessed. Note the following: If you move the lists/*/request.pck files, you also need to move any data/heldmsg-* files. OTOH, you can ignore any held messages on the old server, in which case, it's better to not move the request.pck files. If you want to move archives, you can move the entire archives/private/ directory. You don't really need to worry about archives/public/ as the symlinks therein will be recreated on the new system as the lists are accessed, but if you want to move archives/public/, make sure that you move the symlinks and not the directories they point to. If you want to be selective about which archives to move, make sure that you move both the archives/private/listname/ and the archives/private/listname.mbox/ directories for each list. You also have to deal with MTA aliases on the new server if the MTA uses aliases for Mailman. If the domain names for web and email will be the same on the new server, that's all. If not, you need to run fix_url to update the lists. Also, in this case, it might be better to just move the archives/private/listname.mbox/ directories and rebuild the archives with bin/arch --wipe so that the listinfo links in the archives will have the correct host name. If you are going to rebuild archives, it is good to first check the archives/private/listname.mbox/listname.mbox file with bin/cleanarch. See: bin/arch --help bin/cleanarch --help http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.069.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] getting python errorss with check_perms
Hi, Running this as root so that it can fix any perm problems, but I'm getting what I assume to be python errors: [EMAIL PROTECTED] mailman]# bin/check_perms -f Traceback (most recent call last): File bin/check_perms, line 382, in module checkarchives() File bin/check_perms, line 216, in checkarchives print _(\ NameError: global name '_' is not defined I get the same errors without the '-f' argument. Any ideas? Thanks, Rob -- Rob Tanner UNIX Services Manager Linfield College, McMinnville OR -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] getting python errorss with check_perms
Rob Tanner wrote: Running this as root so that it can fix any perm problems, but I'm getting what I assume to be python errors: [EMAIL PROTECTED] mailman]# bin/check_perms -f Traceback (most recent call last): File bin/check_perms, line 382, in module checkarchives() File bin/check_perms, line 216, in checkarchives print _(\ NameError: global name '_' is not defined I get the same errors without the '-f' argument. Any ideas? You said in another thread that you're migrating to a Fedora Core system. Are you using the Fedora rpm packages of Mailman? This looks like a bug in one of the patches that is applied in the Fedora/Red Hat rpms. If you're using the rpms, what version of Fedora are you running, and what is the version and release of the mailman package? The changes I'm thinking of were discussed at https://bugzilla.redhat.com/132495 -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ There will always be death and taxes, but death doesn't get worse every year. pgpW1OywAjmpd.pgp Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] getting python errorss with check_perms
Todd, I think the bug URL you gave me is a wrong URL. Bug 132495 is a Japanese encoding bug and its status is closed (which I presume means fixed). That doesn't sound like the problem I'm seeing. In answer to your questions, the Fedora release is Fedora release 7 (Moonshine) and the mailman package installed is mailman-2.1.9-5.1 (output of rpm -qa). I just no checked, and there is not a more current package to download via yum. -- Rob Todd Zullinger said the following on 02/05/2008 04:34 PM: Rob Tanner wrote: Running this as root so that it can fix any perm problems, but I'm getting what I assume to be python errors: [EMAIL PROTECTED] mailman]# bin/check_perms -f Traceback (most recent call last): File bin/check_perms, line 382, in module checkarchives() File bin/check_perms, line 216, in checkarchives print _(\ NameError: global name '_' is not defined I get the same errors without the '-f' argument. Any ideas? You said in another thread that you're migrating to a Fedora Core system. Are you using the Fedora rpm packages of Mailman? This looks like a bug in one of the patches that is applied in the Fedora/Red Hat rpms. If you're using the rpms, what version of Fedora are you running, and what is the version and release of the mailman package? The changes I'm thinking of were discussed at https://bugzilla.redhat.com/132495 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/rtanner%40linfield.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] getting python errorss with check_perms
Rob Tanner wrote: I think the bug URL you gave me is a wrong URL. Bug 132495 is a Japanese encoding bug and its status is closed (which I presume means fixed). That doesn't sound like the problem I'm seeing. Read further down in the comment thread. It talks about the _() i18n function being changed to C_(). However, lines 37 to 48 of our check_perms are try: import paths except ImportError: print '''Could not import paths! This probably means that you are trying to run check_perms from the source directory. You must run this from the installation directory instead. ''' raise from Mailman import mm_cfg from Mailman.mm_cfg import MAILMAN_USER, MAILMAN_GROUP from Mailman.i18n import _ Is this what your's looks like? -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Outgoing qrunner stops working and outgoing mails get stuck
On 2/5/08, ippaso wrote: Here is the log from the smtp server for that time, in case it can help: (qmail is patched to check the 'rcpt to' against a valid addresses list before accepting a message and to reject during the smtp conversation the mails which achieve a very high spamassassin spam score) You really want to avoid doing any kind of anti-spam check for outgoing mail from Mailman. All those checks should be done on input, and should not need to be done on output. Moreover, you really don't want to do any kind of recipient address validation, if the recipient in question is not local to your network -- that could easily be mistaken by remote sites for a spammer trying to verify his mailing list. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Still Lost
On 2/5/08, Thomas J Casey wrote: In an email from Brad Knowles, he stated: If they are not subscribers, then they need to be on the whitelist. But I cannot find a whitelist anywhere. Go to the web mail admin interface for your list. Go to the Privacy options... sub-page, then to Sender filters. The second field on the page should be labeled accept_these_nonmembers with a description of List of non-member addresses whose postings should be automatically accepted. That's your whitelist. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] getting python errorss with check_perms
Rob Tanner wrote: I think the bug URL you gave me is a wrong URL. Bug 132495 is a Japanese encoding bug and its status is closed (which I presume means fixed). That doesn't sound like the problem I'm seeing. The bug summary may not sound like what you're seeing, but the patch that was applied to correct the initial problem does redefine _() and can cause the sort of errors you're seeing. I know this because I ran into some places where the patch was incomplete and caused just such a problem for me. :) In answer to your questions, the Fedora release is Fedora release 7 (Moonshine) and the mailman package installed is mailman-2.1.9-5.1 (output of rpm -qa). I just no checked, and there is not a more current package to download via yum. There may still be problems with the patch, as the maintainer noted in the last comment. The bug is closed with the resolution rawhide, which means that the latest updated patch may not have been pushed to F7 (I haven't looked closely, though you can by looking at the Fedora CVS: http://cvs.fedoraproject.org/viewcvs/rpms/mailman/) There does happen to be an update that is in the updates-testing repository, and the patch in question has been updated in that version (mailman-2.1.9-5.3.i386.rpm). You can download that directly or enable the updates-testing repo to install it with yum like so: yum --enablerepo=updates-testing update mailman This package should hit the standard updates repo very soon as it fixes CVE-2006-3636 (multiple cross-site scripting vulnerabilities). -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Artificial Intelligence is no match for Natural Stupidity pgp7zwrZ5Z3dH.pgp Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Turning off confirmation
I'm running a mail list that is used for emergency notification, and many people subscribe using their cellphones. Because of this, sending a confirmation email isn't really the easiest way for the users to subscribe. Also, I don't really think that approving everyone would be feasible for me. Is there a way to turn off the confirmation/approval process for new subscribers? Thanks, Robert Everson -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Turning off confirmation
Robert Everson wrote: I'm running a mail list that is used for emergency notification, and many people subscribe using their cellphones. Because of this, sending a confirmation email isn't really the easiest way for the users to subscribe. Also, I don't really think that approving everyone would be feasible for me. Is there a way to turn off the confirmation/approval process for new subscribers? It is not recommended, but if you want to do it, and if you have sufficient access to the Mailman server, you can put ALLOW_OPEN_SUBSCRIBE = Yes in mm_cfg.py, and then you will be offered None as one of the choices for subscribe_policy. Keep in mind that in addition to making things easier for your PDA subscribers, this will also allow your worst enemy to subscribe multiple people to your list and when these people start receiving messages from the list and replying to the list with take me off this list and complaining to their ISPs that you are a source of spam, you will ultimately have to close the list. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] getting python errorss with check_perms
Rob Tanner writes: File bin/check_perms, line 216, in checkarchives print _(\ NameError: global name '_' is not defined This is the conventional equivalent to GNU gettext used by most Python programs. Find the definition of '_' which will either look like def _(x): # code here or like _ = gettext (or some other name that looks like it might be a function that translates an English string into some other language). Then replace it with def _(x): return x and win (unless you really want to see the messages in a language other than the original, which is almost certainly Englishwink). -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] getting python errorss with check_perms
Todd, That update took case of it. Thanks. -- Rob On 02/05/2008 05:56 PM, Todd Zullinger wrote: Rob Tanner wrote: I think the bug URL you gave me is a wrong URL. Bug 132495 is a Japanese encoding bug and its status is closed (which I presume means fixed). That doesn't sound like the problem I'm seeing. The bug summary may not sound like what you're seeing, but the patch that was applied to correct the initial problem does redefine _() and can cause the sort of errors you're seeing. I know this because I ran into some places where the patch was incomplete and caused just such a problem for me. :) In answer to your questions, the Fedora release is Fedora release 7 (Moonshine) and the mailman package installed is mailman-2.1.9-5.1 (output of rpm -qa). I just no checked, and there is not a more current package to download via yum. There may still be problems with the patch, as the maintainer noted in the last comment. The bug is closed with the resolution rawhide, which means that the latest updated patch may not have been pushed to F7 (I haven't looked closely, though you can by looking at the Fedora CVS: http://cvs.fedoraproject.org/viewcvs/rpms/mailman/) There does happen to be an update that is in the updates-testing repository, and the patch in question has been updated in that version (mailman-2.1.9-5.3.i386.rpm). You can download that directly or enable the updates-testing repo to install it with yum like so: yum --enablerepo=updates-testing update mailman This package should hit the standard updates repo very soon as it fixes CVE-2006-3636 (multiple cross-site scripting vulnerabilities). -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/rtanner%40linfield.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
