Mailman 3 May 2002 - Mailman-Developers

Re: [Mailman-Developers] Another stupid question
by J C Lawrence May 22, 2002

May 22, 2002

On Wed, 22 May 2002 13:22:53 -0400 Jay R Ashworth <jra(a)baylink.com> wrote: > I seem to have managed to get CVS installed and running (and finally > ironed out my DNS issues), but for some reason, my installation thinks > it has no name: invitation messages come from "MAILER-DAEMON" with no > domain, and the List headers are for "test1@" Odds are good this is an MTA config problem. Send mail from both the CLI (`mail`) and telnetting to localhost. See what default host is given on From: etc and then fix as appropriate. Make sure you try with unqualified addresses (ie UID only), with partially qualified domains, and FQDNs to see the exact behaviour. > Do I have to reinstall *again*? Almost certainly not. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

[ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo
by noreply＠sourceforge.net May 22, 2002

May 22, 2002

Bugs item #558633, was opened at 2002-05-21 13:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- Comment By: Donal Hunt (redgiant) Date: 2002-05-22 16:40 Message: Logged In: YES user_id=551025 It actually gets worse! I finally figured out what has been crashing my machine for the past few days... and it's related to this bug i think. To reproduce: Create a moderated mailing list. eg test(a)hostanme.com Send a mail from your mailman user (eg su to mailman id and type: echo "test" | mail -s "test" test(a)hostname.com (where test(a)hostname.com is your moderated mailing list)) The mail gets sent to the mailing list and held for approval (mailman(a)hostname.com isn't a subscriber). A message gets sent back to mailman(a)hostname.com saying the message is held for approval (which mailman tries to post to the mailman list). At this stage stuff starts to stop working on the machine (smtp, telnet and syslogd mainly). What I've got from stracing syslogd (I originally thought it was a syslogd problem) and a mail from root are below: The thing is not that mailman is going to be sending mails to lists locally, but more someone could spoof a mail and DOS your machine. not nice!!! From what I've seen (evidence below) - there isn't a fight between the two lists 0 but i may be wrong. Quick fix: set "respond_to_post_requests" to No. System info: Suse Linux 7.0, Syslogd 1.3-3, Mailman 2.1b (cvs - may 9th) If this has been fixed already or is a seperate bug I apologise in advance for the long comment. ----------------------------------------------------------------------------------------------- <mailman(a)hostname.dcu.ie>: Command died with status 1: "/usr/local/mailman/mail/wrapper post mailman" Reporting-MTA: dns; hostname.dcu.ie Arrival-Date: Wed, 22 May 2002 16:02:45 +0100 (IST) Final-Recipient: rfc822; mailman(a)hostname.dcu.ie Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 1: "/usr/local/mailman/mail/wrapper post mailman" Received: from hostname.dcu.ie (localhost [127.0.0.1]) by hostname.dcu.ie (Postfix) with ESMTP id DB02D5DFEA for <mailman(a)hostname.dcu.ie>; Wed, 22 May 2002 16:02:45 +0100 (IST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Your message to Test2 awaits moderator approval From: test2-bounces(a)hostname.dcu.ie To: mailman(a)hostname.dcu.ie Message-ID: <mailman.16.1022079764.11428.test2(a)hostname.dcu.ie> Date: Wed, 22 May 2002 16:02:44 +0100 X-BeenThere: test2(a)hostname.dcu.ie X-Mailman-Version: 2.1b2+ Precedence: bulk List-Id: <test2.hostname.dcu.ie> X-List-Administrivia: yes Sender: test2-bounces(a)hostname.dcu.ie Errors-To: test2-bounces(a)hostname.dcu.ie ----------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------- writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"hostname", 7}, {" ", 1}, {"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6) = ?ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) --- time(NULL) = 1022032087 rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, [], SA_RESTART}, 8) = 0 alarm(30) = 0 sigreturn() = ? (mask now []) writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"hostname", 7}, {" ", 1},{"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6) = ?ERESTARTSYS (To be restarted) --- SIGALRM (Alarm clock) --- time(NULL) = 1022032117 rt_sigaction(SIGALRM, {0x405304, [], SA_RESTART}, {0x405304, [],SA_RESTART}, 8) = 0 alarm(30) = 0 sigreturn() = ? (mask now []) writev(1, [{"May 22 02:36:40", 15}, {" ", 1}, {"linux28", 7}, {" ", 1}, {"local[6728]: fatal: execvp /usr/"..., 85}, {"\r\n", 2}], 6 <unfinished ----------------------------------------------------------------------------------------------- ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-22 03:38 Message: Logged In: YES user_id=12800 Norbert Bollow gives this very good idea: Rate limiting can do a lot to prevent things from getting out of hand. For example, respond at most ten times to essentially the same request from the same email address. On any given day, when Mailman gets the tenth message from the same email address without valid commands, it could reply "This is the tenth message of this type today from you. It order to avoid problems like mail loops between email robots, any further messages of this type will be ignored today. Please try again tomorrow." And then any further messages from that address with no valid commands will be just discarded. Similarly, Mailman would reply only to ten subscription requests for the same list from the same user on any given day. And only to ten unsubscription requests for the same list from the same user on any given day. And only to ten requests to change the subscription options in the same way. Etc. Since most loops (with the exception of some bounce loops) iterate more quickly than ten times per day, this will kill most loops between robots before they create serious problems. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 21:47 Message: Logged In: YES user_id=12800 Heh, I think this is a general problem when you get two email robots talking to each other! In MM2.1cvs the robot will refuse to respond to a message marked Precedence: bulk|junk|list -- but it looks like that wouldn't have even helped in this case (since the Majordomo server isnt' setting that header ;/ ) The only other solution I can think of is to add a config variable which is a blacklist of known addresses (regexps) that Mailman should not respond too. You'd still get into the robot infloop the first time, but at least you'd have a hope of avoiding subsequent replybot storms for the same address. ---------------------------------------------------------------------- Comment By: Nigel Metheringham (nigel) Date: 2002-05-21 13:03 Message: Logged In: YES user_id=31288 and other file ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id…

1 0

confirmation strings don't seem to work with mm 2.1b2+
by Marc MERLIN May 22, 2002

May 22, 2002

I'm using a CVS tree updated last week. I got this mail (because my spamassassin is boucing the mails, and the list mostly gets spams). No big deal, except that the URL tells me the confirmation string is incorrect and even if I re-enter it in the "Otherwise, re-enter your confirmation string." page, it still doesn't work. What can I do to help debug this/provide more info? ----- Forwarded message from web-team-request(a)svlug.org ----- From: web-team-request(a)svlug.org To: merlin(a)svlug.org X-List-Administrivia: yes Subject: confirm 834fdd960d02e8e77409e82c626b698f96fb434a X-Spam-Status: No, hits=0.6 required=7.0 tests=NO_REAL_NAME version=2.20 X-Spam-Level: Your membership in the mailing list web-team has been disabled due to excessive bounces. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. To re-enable your membership, you can simply respond to this message (leaving the Subject: line intact), or visit the confirmation page at http://lists.svlug.org/lists/confirm/web-team/834fdd960d02e8e77409e82c626b6… You can also visit your membership page at http://lists.svlug.org/lists/options/web-team/merlin%40svlug.org (...) ----- End forwarded message ----- -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

1 0

Mailman problem with Python upgrade
by Kory Wheatley May 22, 2002

May 22, 2002

I've install mailman 2.0.11 on Red Hat 7.2 and it was working fine until I upgrade to Python 2.1. Once I upgraded to this version everything seemed fine for 5 hours. I was able to receive messages from my mailing lists at our University. The Web Interface administrator options for the lists all worked fine. Then messages started piling in "qfiles" and it would not send anymore messages out. I moved them out of the queue and started moving them back in one at a time and then again the messages seemed to be sent properly, but then they started piling back up in the qfiles directory again . Here is the errors I received in the "error" logfile. I'm not totally efficient on Python yet, so I would like some help I would appreciate it. (Quite a few messages on CORRUPTED ARCHIVES and module regex not found) ERROR LOG FILE May 21 10:20:01 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:01 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:20:01 2002 qrunner(31161): import HyperArch May 21 10:20:01 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:20:01 2002 qrunner(31161): from Mailman import EncWord May 21 10:20:01 2002 qrunner(31161): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:20:01 2002 qrunner(31161): import base64 May 21 10:20:01 2002 qrunner(31161): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:20:01 2002 qrunner(31161): import binascii May 21 10:20:01 2002 qrunner(31161): ImportError: No module named binascii May 21 10:20:01 2002 (31161) CORRUPT ARCHIVE FOR LIST: libstaff May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: relief May 21 10:20:02 2002 qrunner(31161): Traceback (most recent call last): May 21 10:20:02 2002 qrunner(31161): File "/home/mailman/Mailman/Archiver/Archiver.py", line 220, in ArchiveMail May 21 10:20:02 2002 qrunner(31161): h = HyperArch.HyperArchive(self) May 21 10:20:02 2002 qrunner(31161): AttributeError: 'Mailman.Archiver.HyperArch' module has no attribute 'HyperArchive' May 21 10:20:02 2002 (31161) CORRUPT ARCHIVE FOR LIST: ultimate May 21 10:22:01 2002 qrunner(31203): Traceback (most recent call last): May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:22:01 2002 qrunner(31203): import HyperArch May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:22:01 2002 qrunner(31203): from Mailman import EncWord May 21 10:22:01 2002 qrunner(31203): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:22:01 2002 qrunner(31203): import base64 May 21 10:22:01 2002 qrunner(31203): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:22:01 2002 qrunner(31203): import binascii May 21 10:22:01 2002 qrunner(31203): ImportError: No module named binascii May 21 10:22:01 2002 (31203) CORRUPT ARCHIVE FOR LIST: korymail May 21 10:28:01 2002 qrunner(31258): Traceback (most recent call last): May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:28:01 2002 qrunner(31258): import HyperArch May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:28:01 2002 qrunner(31258): from Mailman import EncWord May 21 10:28:01 2002 qrunner(31258): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:28:01 2002 qrunner(31258): import base64 May 21 10:28:01 2002 qrunner(31258): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:28:01 2002 qrunner(31258): import binascii May 21 10:28:01 2002 qrunner(31258): ImportError: No module named binascii May 21 10:28:01 2002 (31258) CORRUPT ARCHIVE FOR LIST: ccaus May 21 10:34:00 2002 qrunner(31303): Traceback (most recent call last): May 21 10:34:00 2002 qrunner(31303): File "/home/mailman/Mailman/Archiver/Archiver.py", line 219, in ArchiveMail May 21 10:34:01 2002 qrunner(31303): import HyperArch May 21 10:34:01 2002 qrunner(31303): File "/home/mailman/Mailman/Archiver/HyperArch.py", line 47, in ? May 21 10:34:01 2002 qrunner(31303): from Mailman import EncWord May 21 10:34:01 2002 qrunner(31303): File "/home/mailman/Mailman/EncWord.py", line 21, in ? May 21 10:34:01 2002 qrunner(31303): import base64 May 21 10:34:01 2002 qrunner(31303): File "/tmp/32444-i386/install/usr/lib/python2.1/base64.py", line 7, in ? May 21 10:34:01 2002 qrunner(31303): import binascii May 21 10:34:01 2002 qrunner(31303): ImportError: No module named binascii 3:26:01 2002 qrunner(32122): Traceback (most recent call last): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 283, in ? May 21 13:26:01 2002 qrunner(32122): kids = main(lock) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 253, in main May 21 13:26:01 2002 qrunner(32122): keepqueued = dispose_message(mlist, msg, msgdata) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/cron/qrunner", line 121, in dispose_message May 21 13:26:01 2002 qrunner(32122): if BouncerAPI.ScanMessages(mlist, mimemsg): May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 57, in ScanMessages May 21 13:26:01 2002 qrunner(32122): mod = __import__('Mailman.Bouncers.'+modname) May 21 13:26:01 2002 qrunner(32122): File "/home/mailman/Mailman/Bouncers/Catchall.py", line 34, in ? May 21 13:26:01 2002 qrunner(32122): import regsub May 21 13:26:01 2002 qrunner(32122): File "/usr/lib/python2.1/regsub.py", line 20, in ? May 21 13:26:01 2002 qrunner(32122): import regex May 21 13:26:01 2002 qrunner(32122): ImportError : No module named regex Kory Wheatley Idaho State University

1 0

[ mailman-Bugs-558988 ] bad performance for big queue dirs
by noreply＠sourceforge.net May 22, 2002

May 22, 2002

Bugs item #558988, was opened at 2002-05-22 03:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Norbert Bollow (bollow) Assigned to: Nobody/Anonymous (nobody) Summary: bad performance for big queue dirs Initial Comment: Many filesystems (e.g. the popular ext2) have horrible performance when there are many files in the same directory. The queue system should be modified to avoid this situation. As a test case, try adding 20,000 test address in such a way that Mailman will try to send a welcome message to each of them. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558988&group_id…

1 0

[ mailman-Feature Requests-558896 ] allow multiple values for invoking group
by noreply＠sourceforge.net May 22, 2002

May 22, 2002

Feature Requests item #558896, was opened at 2002-05-21 18:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=558896&group_id… >Category: None >Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nalin Dahyabhai (nsdahya1) Assigned to: Nobody/Anonymous (nobody) Summary: allow multiple values for invoking group Initial Comment: When building binary packages (for example, when you don't know ahead of time which MTA is going to be used, and the different MTAs run under different GIDs), it's sometimes useful to be able to specify multiple unprivileged GIDs which are to be allowed to run the wrapped scripts. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 23:03 Message: Logged In: YES user_id=12800 I'm changing this to a feature request. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=558896&group_id…

1 0

[ mailman-Bugs-558633 ] Blocked queue after fight with Majordomo
by noreply＠sourceforge.net May 22, 2002

May 22, 2002

Bugs item #558633, was opened at 2002-05-21 08:01 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nigel Metheringham (nigel) Assigned to: Nobody/Anonymous (nobody) Summary: Blocked queue after fight with Majordomo Initial Comment: On Mailman 2.0.8 (was honestly going to upgrade today!). It appears that a couple of messages were boucing between the mailman request addresses and a Majordomo server, with more error transcript being added to the message on each bounce. This then appeared to completely block the qrunner. Removing the 2 huge messages from the qfiles directory fixed it. Broken message qfiles attached. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 22:38 Message: Logged In: YES user_id=12800 Norbert Bollow gives this very good idea: Rate limiting can do a lot to prevent things from getting out of hand. For example, respond at most ten times to essentially the same request from the same email address. On any given day, when Mailman gets the tenth message from the same email address without valid commands, it could reply "This is the tenth message of this type today from you. It order to avoid problems like mail loops between email robots, any further messages of this type will be ignored today. Please try again tomorrow." And then any further messages from that address with no valid commands will be just discarded. Similarly, Mailman would reply only to ten subscription requests for the same list from the same user on any given day. And only to ten unsubscription requests for the same list from the same user on any given day. And only to ten requests to change the subscription options in the same way. Etc. Since most loops (with the exception of some bounce loops) iterate more quickly than ten times per day, this will kill most loops between robots before they create serious problems. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-21 16:47 Message: Logged In: YES user_id=12800 Heh, I think this is a general problem when you get two email robots talking to each other! In MM2.1cvs the robot will refuse to respond to a message marked Precedence: bulk|junk|list -- but it looks like that wouldn't have even helped in this case (since the Majordomo server isnt' setting that header ;/ ) The only other solution I can think of is to add a config variable which is a blacklist of known addresses (regexps) that Mailman should not respond too. You'd still get into the robot infloop the first time, but at least you'd have a hope of avoiding subsequent replybot storms for the same address. ---------------------------------------------------------------------- Comment By: Nigel Metheringham (nigel) Date: 2002-05-21 08:03 Message: Logged In: YES user_id=31288 and other file ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558633&group_id…

1 0

Replybot change proposed
by barry＠zope.com May 22, 2002

May 22, 2002

I propose that the Replybot not send responses to any message marked "Precedence: bulk" unless there is a corresponding "X-Ack: yes" header. I also propose that the -request robot discard all similarly formatted messages. I think this will drastically cut down on the number of bogus replybot storms, and vulnerability of robot addresses being subscribed. There's not much we can do about broken replybots, but we can at least guard against properly written ones. Does anybody have any objections? -Barry

5 15

[ mailman-Bugs-558909 ] Auto-responsder doesn't send response.
by noreply＠sourceforge.net May 21, 2002

May 21, 2002

Bugs item #558909, was opened at 2002-05-21 23:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Donal Hunt (redgiant) Assigned to: Nobody/Anonymous (nobody) Summary: Auto-responsder doesn't send response. Initial Comment: Auto-response mail never gets sent on -admin and -owner addresses. Set the autorespond_admin and autorespond_admin_text properties on the auto-responder page of the admin page for the list. Sending mail to either <listname>-admin@host or <listname>-owner@host results in the admin receiving the email but no auto-response is sent to the sender. Found on Mailman CVS (May 9th). Up to my eyes at present so haven't got a chance to dig deeper yet. Will do so middle of next week if needed. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=558909&group_id…

1 0

[ mailman-Patches-558898 ] allow multiple values for invoking group
by noreply＠sourceforge.net May 21, 2002

May 21, 2002

Patches item #558898, was opened at 2002-05-21 18:11 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558898&group_id… Category: command line scripts Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Nalin Dahyabhai (nsdahya1) Assigned to: Nobody/Anonymous (nobody) Summary: allow multiple values for invoking group Initial Comment: Per bug #558896, a patch which converts the allowed gid into an array of allowed gids which can be set at compile-time. Might not be complete enough, but it seems to work for me. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=558898&group_id…

1 0