Mailman 3 March 2001 - Mailman-Developers

Hi.
by efernandezor＠antena3tv.es 06 Mar '01

06 Mar '01

2 1

Mailman Install to latest
by Webmaster 05 Mar '01

05 Mar '01

I have Mailman 2.0, would it be fine to install the patch Mailman 2.02 or do I first have to install Mailman 2.0.1 -- ############################### Webmaster webmaster(a)isu.edu Computing & Communications ################################

3 2

Incorrect Headers
by Teo de Hesselle 05 Mar '01

05 Mar '01

It seems that for one of my lists' monthly password reminders, mailman is putting incorrect headers in, making it appear that the reminder is coming from a different list. The list whom this user is subscribed to is called 'researchnet', whereas the headers are claiming that it is coming from the 'bacc' list. This is interfering with mailman's bounce detection, and as a result the bacc admin is receiving all these messages, and is understandably not impressed. I am including the relevant sections below. Has anyone experienced this before? (or should this be addressed to the develepers' list?). Thank you for any help. >Date: Thu, 1 Mar 2001 05:42:46 +1100 (EST) >Message-Id: <200102281842.f1SIgkI07866(a)tsbunix1.itd.uts.edu.au> >Subject: listserv.uts.edu.au mailing list memberships reminder >From: mailman-owner(a)listserv.uts.edu.au >To: r.wiltshire(a)uts.edu.au >X-No-Archive: yes >X-Ack: no >Sender: bacc-admin(a)listserv.uts.edu.au >Errors-To: bacc-admin(a)listserv.uts.edu.au >X-BeenThere: bacc(a)listserv.uts.edu.au >X-Mailman-Version: 2.0 >Precedence: bulk > >This is a reminder, sent out once a month, about your >listserv.uts.edu.au mailing list memberships. It includes your [snip] > >If you have questions, problems, comments, etc, send them to >mailman-owner(a)listserv.uts.edu.au. Thanks! > >Passwords for r.wiltshire(a)uts.edu.au: > >List Password // URL >---- -------- >researchnet(a)listserv.uts.edu.au xxxxxx >http://listserv.uts.edu.au/mailman/options/researchnet/r.wiltshire%40uts.ed >u.au -- Téo de Hesselle Email Administrator Information Technology Division University of Technology, Sydney

1 0

ANNOUNCE Mailman 2.1 alpha 1
by barry＠digicool.com 04 Mar '01

04 Mar '01

I've just uploaded a snapshot tarball of Mailman 2.1 alpha 1 to SourceForge. I'm only announcing it here because if you're not on mailman-developers, you probably shouldn't be trying to install this. This release is intended as a snapshot of several big changes to Mailman, specifically the rewritten qrunner subsystem, and internationalization support. Only motivated developers should consider using this release as I make no guarantees for stability or even installability. APIs may change. Stuff may not work. It might be a PITA to install. Still, it would be cool if people wanting i18n would pull this release down and play with it. I'm interested in any feedback or experiences you might have. I'll be at the Python conference all week so if you're coming, I'd love to talk about it, otherwise don't expect any responses until I get back. I strongly recommend you do not use this release for production systems (if you even can :). This release also contains the important bug fixes from Mailman 2.0.1 and 2.0.2. You can get the tarball from the Mailman SourceForge pages: http://sourceforge.net/project/showfiles.php?group_id=103 You will need Python 2.0 or better, and my mimelib 0.2 package or better. http://www.python.org/2.0 http://barry.wooz.org/software/Code/mimelib-0.2.tar.gz Enjoy, -Barry 2.1 alpha 1 (04-Mar-2001) - Python 2.0 or newer required. Also required is `mimelib' a new library for handling MIME documents. This will be bundled in future releases, but for now, you must download and install it (using Python's distutils) from http://barry.wooz.org/software/Code/mimelib-0.2.tar.gz You need mimelib 0.2 or better. - Redesigned qrunner subsystem. Now there are multiple message queues, and considerable flexibility in file formats for integration with external systems. The current crop of queues include: archive -- for posting messages to an archiver commands -- for incoming email commands and bounces in -- for list-destined incoming email news -- for messages outgoing to a nntp server out -- for messages outgoing to a smtp server shunt -- for messages that trigger unexpected exceptions in Mailman virgin -- for messages that are generated by Mailman cron/qrunner is now a long running script that forks off sub-runners for each of the above queues. qrunner still plays nice with cron, but it is expected to be started by init at some point in the future. Some support exists for parallel processing of messages in the queues. - Support for internationalization support merged in. Original work done by Juan Carlos Rey Anaya and Victoriano Giralt. I've tested about 90% of the web side, 50% of the email, and 50% of the command line / cron scripts. New scripts: bin/newlang, bin/rmlang - New delivery script `auto' for automatic integration with the Postfix MTA. - A bunch of new bounce detectors. Changes ported from Mailman 2.0.2 and 2.0.1: - A fix for a potential privacy exploit where a clever list administrator could gain access to user passwords. This doesn't allow them to do much more harm to the user then they normally could, but they still shouldn't have access to the passwords. - In the admindb page, don't complain when approving a subscription of someone who's already on the list (SF bug #222409 - Thomas Wouters). Also, quote for HTML the Subject: text printed for held messages, otherwise messages with e.g. "Subject: </table>" could royally screw page formatting. - Docstring fix bin/newlist to remove mention of "immediate" argument (Thomas Wouters). - Fix for bin/update when PREFIX != VAR_PREFIX (SF bug #229794 -- Thomas Wouters). - Bug fix release, namely fixes a buglet in bin/withlist affecting the -l and -r flags; also a problem that can cause qrunner to stop processing mail after disk-full events (SourceForge bug 127199).

1 0

Auto-rejecting spam
by Mikael Djurfeldt 03 Mar '01

03 Mar '01

Hi, I'm a list administrator using Mailman 2.0. My list is sometimes pretty heavily bombarded with spam. I can get 95% of it held by enabling holding of postings with indirect headers (requiring that the list name occurs in the To: or Cc: fields), however, since this spam filtering never hitherto has caught an innocent valid poster, I'd like Mailman to automatically reject this kind of spams without invoking me, the list administrator. So, I'm asking for a new privacy option to enable automatic rejection of postings with indirect headers and/or matching a list of regexps. (I'm not on this list, so I'd be grateful if you include me in the reply.) Best regards, /mdj

1 0

ANNOUNCE Mailman 2.0.2 (important privacy patch)
by barry＠digicool.com 03 Mar '01

03 Mar '01

I've just uploaded the Mailman 2.0.2 release to SourceForge. This is a bug fix release that also fixes a potential privacy hole, which could allow a list administrator to get access to user passwords. Even with those passwords, I believe there's little additional harm that a list admin could do, but still they probably shouldn't have access to those passwords. There are a few other important fixes in this release, so I recommend that all sites running Mailman 2.0 or 2.0.1 should upgrade. As usual I'm releasing this as both a complete tarball and as a patch against Mailman 2.0.1. If you grab the patchfile, you'll want to cd into your 2.0 source, and apply it like so: % patch -p1 < mailman-2.0.1-2.0.2.diff Currently only http://mailman.sourceforge.net is updated, but the list.org and gnu.org sites should be updated soon. The release information on SF is at http://sourceforge.net/project/shownotes.php?release_id=25955 My thanks to Thomas Wouters for his help! Enjoy, -Barry P.S. I'm not sure if I'll have time to release a 2.1 alpha of the I18N stuff before I leave for the Python9 conference. If we get the expected foot of snow between Sunday and Monday, it's a possibility. ;) [From the NEWS file] 2.0.2 (03-Mar-2001) Security fix: - A fix for a potential privacy exploit where a clever list administrator could gain access to user passwords. This doesn't allow them to do much more harm to the user then they normally could, but they still shouldn't have access to the passwords. Bug fixes: - In the admindb page, don't complain when approving a subscription of someone who's already on the list (SF bug #222409 - Thomas Wouters). Also, quote for HTML the Subject: text printed for held messages, otherwise messages with e.g. "Subject: </table>" could royally screw page formatting. - In Netscape.py bounce processor, don't bomb out on ill-formed messages (no semi-colon separating parameters), otherwise mail delivery could grind to a halt. Bug reported by Kambiz Aghaiepour. - Docstring fix bin/newlist to remove mention of "immediate" argument (Thomas Wouters). - Fix for bin/update when PREFIX != VAR_PREFIX (SF bug #229794 -- Thomas Wouters).

2 3

A day or so ago I posted about the /tmp filling up with new
by room_maildev＠bbs.pixel.citadel.org 03 Mar '01

03 Mar '01

A day or so ago I posted about the /tmp filling up with newsgroup files. Since I mentioned it here that hasn't happened again, so I can't track what the problem was. I didn't make any changes, here, or anything, so I have NO idea what was going on. I haven't even rebooted anything. *shrug* Now I'm more confused than I was before, but it all seems to be working. At least for now. I guess all I had to do was complain about it. :)

2 1

>Gating from news to mail happens by cron/gate_news. Gatin
by room_maildev＠bbs.pixel.citadel.org 02 Mar '01

02 Mar '01

>Gating from news to mail happens by cron/gate_news. Gating from mail >to news happens by the ToUsenet.py handler run by the qrunner. >Neither should be able to create root owned files (if they were owned >by user or group `mailman', then I'd be more suspecting of a Mailman >problem). Yes, I tend to agree. No it's configured and set up properly, all the ownerships are by mailman/mailman. I hadn't thought about the fact that root owned those files, so I'll do a little more digging when I figure out what's been happening and post back with more details if I can't. Thanks for your help and prompt replies!

2 1

>Hmm, I see none of these on mail.python.org which gates
by room_maildev＠bbs.pixel.citadel.org 02 Mar '01

02 Mar '01

>Hmm, I see none of these on mail.python.org which gates >comp.lang.python and comp.lang.python.announce (in both directions). >Python's nntplib doesn't appear to create any temp files, so I don't >think it's coming from there, and I'm /sure/ Mailman doesn't create >any temp files. > >Is your usenet software on the same machine as Mailman? Could those >files be created by your news s/w? Who is the user and group owner of >those files? > >-Barry > -rw-r--r-- 1 root root 389120 Feb 27 18:01 filezSQFHI But your question is valid, and I hadn't thoughtof it. The gatewaying stuff I have left in the mailman crontab and there's not anyway it should be able to create those files as 'root', unless the wrapper's doing it. In any event, I have no idea what's causing this. As for 'usenet software' I'm not using anything but the gatewaying software. The usenet server's not on the same machine, it's at a different ISP...and again, like I said, each of those files is specifically a file full of each usenet posting that I have gatewayed. I'm stumped.

2 1

(no subject)
by room_maildev＠bbs.pixel.citadel.org 02 Mar '01

02 Mar '01

I posted this to the mailman-users group, but either I'm the only one having this problem, or people just don't know: I'm having an issue with 2.0.1 and news gatewaying. It works fine, importing usenet news into e-mail and sending it out, however /tmp is filling up with: 389120 Feb 27 20:46 filew5MNZN There are literally hundreds of these files and almost all of then are that same size. Does anyone know why this is ocurring? When I check the files each one is the same (I use diff) and they all seem to contain every post from each newsgroup I'm gatewaying. Any help would be appreciated. I didn't see anything in the archives on this. Thanks!

2 1