Mailman 3 July 2002 - Mailman-Developers

[ mailman-Bugs-585229 ] opening holes by changing permissions?
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #585229, was opened at 2002-07-22 23:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585229&group_i… Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: opening holes by changing permissions? Initial Comment: I was having problems adding a list in Mailman 2.1beta via the web interface, it was giving me an error regarding permissions to the mailman/data/aliases.db file. This is the error I got: ... File "/var/mailman/Mailman/MTA/Postfix.py", line 46, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/mailman/data/aliases (status: 1, Operation not permitted) To fix this I changed the permissions on this file so apache could write to it. chmod a+w aliases.db This did fix the problem of creating and deleting lists via the web interface. Does anyone know if this would open up any security holes? Is there another way to fix the permissions problem that is more logical? Thanks for your help. Paul Marshall ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 11:28 Message: Logged In: YES user_id=12800 You shouldn't need to do this if you've followed the directions in README.POSTFIX. The key issue is that aliases and aliases.db must be group owned by `mailman' and must be group writeable. Since the cgi scripts are setgid mailman Apache should have no problems writing the file. And since Postfix filter prog is also setgid mailman, it should have no problems either. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585229&group_i…

1 0

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #585833, was opened at 2002-07-24 10:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta Status: Closed Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Ousmane Wilane (wilane) Date: 2002-07-24 15:26 Message: Logged In: YES user_id=47556 Oops! After cvs -q up -P -d, The bug stood there with the same traceback. Maybe I'm doing something wrong but don't know what ... :) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 14:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

[ mailman-Bugs-585484 ] virtual domain lists misdirect autoreply
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #585484, was opened at 2002-07-23 12:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585484&group_i… Category: bounce detection Group: None Status: Open Resolution: None Priority: 5 Submitted By: Byron T. Watts (btwatts) Assigned to: Nobody/Anonymous (nobody) Summary: virtual domain lists misdirect autoreply Initial Comment: Using mailman with virtual domain hosting. Bounced messages for a particular list are going to the wrong list administrator (not even on the same domain). The particular notices that I'm seeing misdirected, are the <i>useridi> is on vacation messages. I am not certain whether other messages are being similarly misdirected. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 11:25 Message: Logged In: YES user_id=12800 Sorry, I'll need more information here. Start with the basics: what OS, what MTA, what version of Python, what version of Mailman. How do you have your MTA configured? Have you set up virtual domain support in Mailman properly (differs depending on the version of Mailman you're using). Please include version numbers for all related software. Also if you can provide a reproducible recipe for seeing the bug, or at least attach copies of misdirected messages, these things would help. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585484&group_i…

1 0

[ mailman-Bugs-577685 ] sh syntax problem in configure
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #577685, was opened at 2002-07-05 03:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577685&group_i… Category: configuring/installing Group: 2.0.x >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: sh syntax problem in configure Initial Comment: in 2.0.12 configure script includes a statement: if [ "$?" == "1" ] which should be in a traditional sh: if [ "$?" = "1" ] (Note single =, not double =) configure fails on solaris 8 with double =, while the error was ignored on FreeBSD. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 10:40 Message: Logged In: YES user_id=12800 This shoudl be fixed in the MM2.0.13 candidate patch, recently announced. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-11 18:30 Message: Logged In: YES user_id=12800 Note that that patch is against configure.in, so you'll need to run autoreconf (or just patch configure by hand). Let me know if that's a problem. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-11 18:29 Message: Logged In: YES user_id=12800 Let's try that again with the checkbox checked off. :/ ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-11 18:28 Message: Logged In: YES user_id=12800 Can you please try the attached patch? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=577685&group_i…

1 0

[ mailman-Bugs-585270 ] qrunner fails with RHL7.2 python 1.5.2
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #585270, was opened at 2002-07-23 03:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585270&group_i… Category: mail delivery Group: 2.0.x >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Stuart Prescott (themill) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner fails with RHL7.2 python 1.5.2 Initial Comment: qrunner from mailman-2.0.12 (downloaded and installed from the src tarball) fails with Python 1.5.2 from RHL7.2 python-1.5.2-38. Error message from $prefix/logs/error is attached as is a patch that does seem to fix the problem and allow Mailman to work. (I'm not a Python programmer .. I noramlly use P**L so I'm not sure exactly what or why... please treat my patch with the greatest skepticism!) >From the mailing lists, there are quite a few ppl having problems with the RHL distributions of Python -- is this a compatability thing (that we can argue about whether it's RHL or Mailman that is at fault a la gcc for years to come?) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 10:39 Message: Logged In: YES user_id=12800 This is fixed in the MM2.0.13 candidate patch recently announced. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585270&group_i…

1 0

[ mailman-Bugs-585776 ] no webauthentification possible
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #585776, was opened at 2002-07-24 04:17 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585776&group_i… Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: no webauthentification possible Initial Comment: After updating to 2.1b some of our lists aren`t accessible for admins any more. I`m using the current cvs, but when they try to login mailman crashes: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 82, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 82, in main cgidata.getvalue('adminpw', '')): File "/usr/lib/mailman/Mailman/SecurityManager.py", line 206, in WebAuthenticate ac = self.Authenticate(authcontexts, response, user) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 159, in Authenticate elif crypt and crypt.crypt(response, secret[:2]) == secret: TypeError: argument 2 must be string without null bytes, not str ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 10:26 Message: Logged In: YES user_id=12800 I don't quite understand how you could have gotten a secret with null bytes in it, but I've added a try/except around the crypt() call to ignore this exception. If you get it, it's equivalent to a failed response. For future reference, before upgrading to MM2.1, was USE_CRYPT set to 0 or 1? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585776&group_i…

1 0

[ mailman-Bugs-585833 ] Forward posts held for approval
by noreply＠sourceforge.net 24 Jul '02

24 Jul '02

Bugs item #585833, was opened at 2002-07-24 06:22 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i… Category: mail delivery Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Ousmane Wilane (wilane) Assigned to: Nobody/Anonymous (nobody) Summary: Forward posts held for approval Initial Comment: FWIW I'm using the current cvs. When I forward a mail which was held for approval to my email address (oversized mail in this case) I get the provided traceback in my logs and the mail in shunt q: ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 10:04 Message: Logged In: YES user_id=12800 Fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585833&group_i…

1 0

Candidate Mailman 2.0.13 patch
by barry＠zope.com 24 Jul '02

24 Jul '02

As some of you have noticed, Mailman 2.0.12 has some compatibility problems with Python 1.5.2. In order to correct this, and a few other minor problems, I want to soon release a version 2.0.13. This time, however I'd like to enlist your help. ;) I have uploaded a candidate patch for 2.0.12 -> 2.0.13 at this url: http://sf.net/tracker/index.php?func=detail&aid=585643&group_id=103&atid=30… I would appreciate it if someone (or a few someones) could give this patch a try. I'm essentially running it on python.org/zope.org, however I'm using Python 2.1.3 in my production environment. I have done some limited testing with Python 1.5.2 and this patch and it seems to go okay. I'd especially like to hear from those of you experiencing problems with MailCommandHandler, if you are running MM2.0.12 with Python 1.5.2. Does this patch fix things for you? Does it produce any other tracebacks or warnings in logs/error? Thanks for any feedback you can provide. If I get some positive feedback (or at least, no negative feedback) in a few days, I'd do a formal release. I expect that to be largely similar to this patch, with perhaps some documentation updates, unless other problems are uncovered by your testing. Thanks! -Barry

4 4

Modifying mailman to filter archived messages
by Laurence Berland 24 Jul '02

24 Jul '02

Sent this to Mailman-users earlier, but am now thinking it is more appropriate here... All, I'm trying to modify mailman to simplify some tasks. Currently, sysadmins get various emails from LogWatch every day or so that need to be read through in depth and then saved to some mailbox somewhere. This both takes a lot of time and creates lots of private copies of these messages, which is bad. The simple part of this is to instead have the emails go to a mailman list that these people may or may not choose to subscribe to, so that mailman will archive the messages and let people choose whether or not to receive them without the intervention of others. The tough part is status coding. I've already modified LogWatch (and will modify other email-sending scripts such as our backup scripts) to code certain lines based on whether or not they require attention. Example 0: means "fine" or "green" and 2: means "trouble" or "red". What I'd like mailman to do is trap these strings such as "0:" "1:" etc and replace them with something else. Is there a particularl easy way to do this? If not, where in the code could I conceivably do this. I've been briefly skimming the code, and intend to read through quite a bit of it to figure all this out, but if anyone could at least point me in the right direction it'd make me very happy. Thanks for your help, Laurence Berland ------------------------------------------------------- ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py -------------------------------------------------------

4 7

problems with mailman 2.0.12 qrunner failing to process any messages
by Chris Dagdigian 24 Jul '02

24 Jul '02

Hi folks, First off thanks for making such a great package. I've been using mailman for a few years now to run mailing lists for various open source informatics efforts like biojava.org, biopython.org and bioperl.org. We upgraded to 2.0.12 over the weekend and are now having trouble with mailman. It's basically stopped processing incoming email. From looking at google and various mailing man list archives it seems that my problem is very similar to what some people saw in v2.06 with mailman not being able to gracefully handle some error or bounce situations. The patches discussed however seem to be already in place with mailman 2.0.12 (specifically a change to Boucers/DSN.py). Right now I'm manually moving .msg and .db files into and out of the qfiles directory so that I can at least get some mail out. This will hopefully also give me a small sample of "bad" emails that are triggering the problem. I'm not a python person so I'd appreciate any tips on how to resolve this. Here are the specifics: qrunner is bombing out with an error and leaving lots of unprocessed messages in the qfiles/ directory. The output from the 'error' logfile is as follows: [mailman@pw600a ~/qfiles]$ tail ../logs/error Jul 23 11:10:01 2002 qrunner(8882): Traceback (innermost last): Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 283, in ? Jul 23 11:10:01 2002 qrunner(8882): kids = main(lock) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 253, in main Jul 23 11:10:01 2002 qrunner(8882): keepqueued = dispose_message(mlist, msg, msgdata) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/cron/qrunner", line 157, in dispose_message Jul 23 11:10:01 2002 qrunner(8882): mlist.ParseMailCommands(msg) Jul 23 11:10:01 2002 qrunner(8882): File "/home/mailman/Mailman/MailCommandHandler.py", line 123, in ParseMailCommands Jul 23 11:10:01 2002 qrunner(8882): precedence = msg.get('precedence', '').lower() Jul 23 11:10:01 2002 qrunner(8882): AttributeError : 'string' object has no attribute 'lower Regards, Chris -- Chris Dagdigian, <dag(a)sonsorol.org> Independent life science IT & research computing consulting Office: 617-666-6454, Mobile: 617-877-5498, Fax: 425-699-0193 Work: http://BioTeam.net PGP KeyID: 83D4310E Yahoo IM: craffi

2 4