Mailman 3 March 2000 - Mailman-Developers

Re: [Mailman-Developers] About MailMan site...
by Dan Mick March 31, 2000

March 31, 2000

Thomas Tschoepke Soares wrote: > I am trying to install mailman here but there are some problems... > > So, I have been trying to download the newer beta version but the domain > www.list.org even resolv at a ping command! This is surely a transient failure; www.list.org has been pretty reliable for me. But you're right; I can't get DNS for it either, and I can't ping its nameservers. The technical contact for the domain is aware and is working on the problem; they have a network outage.

1 0

About MailMan site...
by Thomas Tschoepke Soares March 31, 2000

March 31, 2000

Hi! I am trying to install mailman here but there are some problems... So, I have been trying to download the newer beta version but the domain www.list.org even resolv at a ping command! Could you provide an alternative place from where to get this prog? Or, even better, how about to include it in the sourceforge portal? Thank you, regards Thomas. | Thomas Tschoepke Soares | // Mate do | ttsoares(a)cedep.ifch.ufrgs.br |(~~~//~~) estrivo bendito! |--UIN:961141-------------------------------| \ / Amargo que |The fact is a secondary aspect of reality. | `_/' a gente bebe...

1 0

Re: [Mailman-Developers] A suggestion
by J C Lawrence March 30, 2000

March 30, 2000

On Thu, 30 Mar 2000 17:23:26 +0200 (CEST) Marek Obuchowicz <elephant(a)pld.org.pl> wrote: > I couldn't find the possibility of removing headers in mailman. > Removing 'Recieved' headers is ofen used by majordomo users (like > me in the past). I host one list and I'd like to hide senders' > Message-Id. Eeek! Bad! Bad! > How can I do it? Use a procmail filter inserted before the mailman script invocations. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

1 0

A suggestion
by Marek Obuchowicz March 30, 2000

March 30, 2000

Hi! Sorry if i am writing to wrong address, but i couldn't find a better one :) I couldn't find the possibility of removing headers in mailman. Removing 'Recieved' headers is ofen used by majordomo users (like me in the past). I host one list and I'd like to hide senders' Message-Id. How can I do it? Greets, Marek -- __ Marek "Suonik" Obuchowicz, elephant(a)pld.org.pl /'_)___ Member of GNU generation, PLD project and "H" ( \ ____|\ http://www.projcom.com.pl/ http://www.pld.org.pl/ // || Home Page: http://suonik.art.pl/ (pgp-key is there)

2 1

admin approval and list archive
by Thomas Wouters March 27, 2000

March 27, 2000

There seems to be a bug in the pipermail archiving in combination with admin aproved messages. The bug is that, in the archive mbox, 'From ' lines will be missing from messages which have been passed through admin approval, which means that they will be considered part of the previous message or, if there is no previous message, that the mbox is invalid and no archive will be built. This happens because of one or two buglets, one in the mailbox standard module, and one possibly in the rfc822 module or otherwise in Mailman. When holding a message, the code uses 'str(msg)' (where msg is a rfc822.Message instance) to dump the pending message to a file. Unfortunately, rfc822.Message.__str__() only dumps the normal mail headers and the body, and *not* the 'From ' line, which is stored in rfc822.Message.unixfrom. I dont really think that is a bug in the rfc822 module, as the 'From ' line is not rfc822 but a sendmail (i think) addon for its own use, but it needs to be worked around in any case. The simple fix is attached. In the course of tracking this bug I also found out that the mailbox standard module drops the 'From ' line entirely, before it passes the message to the rfc822.Message constructor. At first I thought that this caused the problem, but now I'm not entirely sure, and I'm not in a position to test it at the moment. This is a bug though, but not in Mailman, and I already sent a fix for it to the python patches list. If anyone is willing to test this, and the above fix doesn't work on its own, grab the mailbox.py fix from the patches mailarchive. And, er, my apologies for this large a rant on this small a bug, it's late and I'm overworked, not spending enough time with python ;) PS: there'll probably be some offset in this patch, my cvs tree is still cluttered with unshared hacks ;) even if it fails, though, I'm confident most people will be able to apply it by hand ;) -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

2 2

Post to every list, just in case...
by Nigel Metheringham March 27, 2000

March 27, 2000

Having been away for a few days I've experienced a sense of things repeating on a short loop whilst reading my mail this morning. One particular thread was cross posted over 3 different mailman lists, although it appears to have been moderated out of one of them at least. So would it be possible for list people to have a little more discipline regarding the posting of messages across lists. Additionally do we need to consider:- 1. Hierarchical lists - ie moderated announce lists that post into other lists, with decent support for building a union of subscribers - maybe rather than subscribing x-users & x-developers to ax-nnounce, a way of telling the list to pull in these lists' subscribers too. 2. Filtering on lists to detect cross posting and do something... 3. An idea of what "something" should be :-) Nigel. -- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]

1 0

French traduction of the templates
by Matthieu CAMUS (IUP MIME - 96000937) March 27, 2000

March 27, 2000

Hello, I'm a frenchy student in Computers Sciences and a true fan of Linux. For the needs of a project I used mailman. I have done the french traduction of the templates files in the /etc/mailman directory. I don't know how to do the traduction in the others files (eg *.py). There is a special function named get-text or something like that for the python's files ? Joined to this email the tar.gz of my traduction. Cordialy, Matthieu Camus e-mail: matthieu.camus(a)univ-lemans.fr

2 1

lock lifetime
by Ricardo Kustner March 25, 2000

March 25, 2000

One of the changes I have to make for my server is to increase the lock lifetime. I suspect that other people who don't have a speedy server either, might get the same problems as me... so maybe it should be mentioned in the install docs and/or moved to a global variable in mm_cfg.py... Below is an excerpt of a message from Thomas who fixed this for me.... For my server I've changed this to 300. "... In any case, you can easily try it out; in Mailman/MailList.py, on or around line 282, there should be a 'lifetime = 60', inside the constructor for the maillists' lockfile. Changing the '60' in, say, '600', should give you better mileage, at least until your machine gets so heavily loaded that a simple admin request takes ten full minutes to process ;) " Ricardo. --

4 4

subscription approval
by Ricardo Kustner March 25, 2000

March 25, 2000

Hi, Today I was subscribing to a list on securityportal.com, which is running LISTSERV... and then I noticed they have a nice way of approving your subscription: you can visit and URL which contains a unique hash that authorizes your request. actually I've been using the same technique for a chatroom signup procedure on our website and it's fairly easy to make... (since i was able to make it ;) ) the big plus of this is that if most of your list subscribers aren't too technical, it's much easier for them to subscribe... anybody can click on the link which their microsoft or AOL browser conviently convert to a hyperlink... (too often I see mails send to the admin with texts like "hi.. my auth code is 923482.. please subscribe me") this could also make unsubscribing very easy... just add a link at the bottom of the mail... and once visited the user gets the choice to unsubscribe (with or without supplying a password?) anyway, i know this wont make it to 2.0, but I hope this could be a nice feature for the next version... Ricardo. --

1 0

[ANNOUNCE] Mailman 2.0 beta 1
by Barry A. Warsaw March 24, 2000

March 24, 2000

I've just uploaded the Mailman 2.0 beta 1 tarball to www.list.org. I decided to name the new version "2.0" because of the architectural changes that have been made. See the excerpt from the NEWS file below for details of what's changed since version 1.1. Two important things to take note of. You will need Python 1.5.2 to run this version of Mailman. Also, if you are upgrading from Mailman 1.x you will need to read the UPGRADING file for instructions. I don't plan to make wider release announcements until 2.0 final is ready to go, but I also don't expect the beta cycle to be very long. We'll see! Enjoy, -Barry -------------------- snip snip -------------------- - A new bundled auto-responder has been added. You can now configure an autoresponse text for each list's primary addresses: listname(a)yourhost.com -- the general posting address listname-request@... -- the automated "request bot" address listname-admin@... -- the human administrator address - The standard UI now includes three logos at the bottom of the page: Dragon's Mailman logo, the Python Powered logo, and the GNU logo. All point to their respective home pages. - It is now possible to set the Reply-To: field on lists to an arbitrary address. NOTE: Reply-To: munging is generally considered harmful! However for some read-only lists, it is useful to direct replies to a parallel discussion list. - There is a new message delivery architecture which uses a pipeline processor for incoming and internally generated messages. Mailman no longer contains a bundled bulk-mailer; instead message delivery is handled completely by the MTA. Most MTAs give a high enough priority to connections from the localhost that mail will not be lost because of system load, but this is not guaranteed (or handled) by Mailman currently. Be careful also if your smtpd is on a different host than the Mailman host. In practice, mail lossage has not be observed. For this reason cron/run_queue is no longer needed (see the UPGRADING file for details). Also, you can choose whether you want direct smtp delivery, or delivery via the command line to a sendmail-compatible daemon. You can also easily add your own delivery module. See Mailman/Defaults.py for details. - A similar pipeline architecture for the parsing of bounce messages has been added. Most common bounce formats are now handled, including Qmail, Postfix, and DSN. It is now much easier to add new bounce detectors. - The approval pending architecture has also been revamped. Subscription requests and message posts waiting for admin approval are no longer kept in the config.db file, but in a separate requests.db file instead. - Finally made consistent the use of Sender:/From:/From_ in the matching of headers for such things as member-post-only. Now, if USE_ENVELOPE_SENDER is true, Sender: will always be chosen over From:, however the default has been changed to USE_ENVELOPE_SENDER false so that From: is always chosen over Sender:. In both cases, if no header is found, From_ (i.e. the envelope sender is used). Note that the variable is now misnamed! Most people want From: matching anyway and any are easily spoofable. - New scripts bin/move_list, bin/config_list - cron/upvolumes_yearly, cron/upvolumes_monthly, cron/archive, cron/run_queue all removed. Edit your crontab if you used these scripts. Other scripts removed: contact_transport, deliver, dumb_deliver. - Several web UI improvements, especially in the admin page. - Remove X-pmrqc: headers to prevent return reciepts for Pegasus mail users. - Security patch when using external archivers. - Honor "X-Archive: No" header by not putting this message in the archive. - Changes to the log file format. - The usual bug fixes.

5 6