Mailman 3 March 2002 - Mailman-Developers

Re: [Mailman-Developers] big list
by Dan Mick 08 Mar '02

08 Mar '02

> >>>>> "NM" == Nigel Metheringham > >>>>> <Nigel.Metheringham(a)dev.InTechnology.co.uk> writes: > > NM> Ideally you would make a copy in memory, ship it down the > NM> delivery pipeline, then work on the next copy... really only > NM> need a few copies actually in python memory at once (pretty > NM> much just the number of outgoing delivery streams). > > That's what I have in mind. > > NM> Of course as the MTA catches these its going to make a queue > NM> file on disk for each one unless you can do this funky passing > NM> the VERP stuff down the pipeline stuff thats been mentioned on > NM> the list before. > > It would be really cool if we could get a bunch of MTA authors > together (I only care about the open source ones <wink>) to define a > protocol for letting the MTA doing the stitching. I think Postfix, > and probably Exim support a way to do this for the envelope sender, > but the really interesting bits happen when the body of the message > can be personalized. The outgoing MTA's the most efficient place to > do this, but you have to get it the information it needs to chew on. BTW, I'm doing this for the From VERPing with Postfix, and it's working out really well for me. The changes are really small and well-contained, and my bounce processing is *really* working better now (I never ever have a missed bounce): Index: Mailman/Handlers/SMTPDirect.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/SMTPDirect.py,v retrieving revision 2.11 diff -u -r2.11 SMTPDirect.py --- Mailman/Handlers/SMTPDirect.py 16 Dec 2001 06:23:14 -0000 2.11 +++ Mailman/Handlers/SMTPDirect.py 8 Mar 2002 23:28:20 -0000 @@ -75,6 +75,9 @@ # do that here?) del msg['sender'] del msg['errors-to'] + # DJM - do this unconditionally since we're VERPing as below + del msg['sender'] + del msg['errors-to'] # Get the flat, plain text of the message msgtext = msg.as_string(unixfrom=0) # Time to split up the recipient list. If we're VERPing then each chunk @@ -270,7 +273,9 @@ if not getattr(conn, 'sock', 0): conn.connect(mm_cfg.SMTPHOST, mm_cfg.SMTPPORT) # Send the message - refused = conn.sendmail(envsender, recips, msgtext) + # DJM - do Postfix VERPing + refused = conn.sendmail(envsender, recips, msgtext,\ + mail_options=["XVERP"]) except smtplib.SMTPRecipientsRefused, e: refused = e.recipients # MTA not responding, or other socket problems, or any other kind of Index: Mailman/Queue/BounceRunner.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Queue/BounceRunner.py,v retrieving revision 2.8 diff -u -r2.8 BounceRunner.py --- Mailman/Queue/BounceRunner.py 7 Mar 2002 16:54:39 -0000 2.8 +++ Mailman/Queue/BounceRunner.py 8 Mar 2002 23:28:21 -0000 @@ -111,6 +111,8 @@ continue # not a bounce to our list # All is good addr = '%s@%s' % mo.group('mailbox', 'host') + syslog('bounce', 'VERP bounce from %s header for addr %s', + header, addr) except IndexError: syslog('error', "VERP_REGEXP doesn't yield the right match groups: %s",

2 1

Big archives
by Nigel Metheringham 08 Mar '02

08 Mar '02

The exim list has been running since 1996, migrated to mailman in 99, and has all the arhives online at http://www.exim.org/pipermail/exim-users/ I've had comments from people that this page is now too slow to load - since I roll the archives weekly (high traffic list) there are around 300 lines of basic archive index in the html table. I don't like the idea of migrating chunks out, but maybe some means of handling large archive chunks would be useful. It is of course an archiver rather than a mailman issue, so a new wonderfully enhanced pipermail is the answer :-) Nigel -- [ Nigel Metheringham Nigel.Metheringham(a)InTechnology.co.uk ] [ - Comments in this message are my own and not ITO opinion/policy - ]

2 1

[Bug] Digest volume increments daily
by Les Niles 08 Mar '02

08 Mar '02

In 2.1a4, and AFAICT the current cvs tree, the digest volume number gets incremented daily regardless of the configured rate. This is because the test for the frequency of update is combined with the test for whether to actually update, causing the default branch -- update daily -- to be executed most of the time. Here's a patch that fixes this. -les --------------------------------------------------------------------- *** Mailman/Handlers/ToDigest.py.orig Sun Jan 6 23:04:03 2002 --- Mailman/Handlers/ToDigest.py Thu Mar 7 06:27:09 2002 *************** *** 97,111 **** timetup = time.localtime(mlist.digest_last_sent_at) now = time.localtime(time.time()) freq = mlist.digest_volume_frequency ! if freq == 0 and timetup[0] < now[0]: ! bump = 1 # Yearly ! elif freq == 1 and timetup[1] <> now[1]: # Monthly, but we take a cheap way to calculate this. We assume # that the clock isn't going to be reset backwards. ! bump = 1 ! elif freq == 2 and (timetup[1] % 4 <> now[1] % 4): # Quarterly, same caveat ! bump = 1 elif freq == 3: # Once again, take a cheap way of calculating this weeknum_last = int(time.strftime('%W', timetup)) --- 97,114 ---- timetup = time.localtime(mlist.digest_last_sent_at) now = time.localtime(time.time()) freq = mlist.digest_volume_frequency ! if freq == 0: ! if timetup[0] < now[0]: ! bump = 1 # Yearly ! elif freq == 1: # Monthly, but we take a cheap way to calculate this. We assume # that the clock isn't going to be reset backwards. ! if timetup[1] <> now[1]: ! bump = 1 ! elif freq == 2: # Quarterly, same caveat ! if (timetup[1] % 4 <> now[1] % 4): ! bump = 1 elif freq == 3: # Once again, take a cheap way of calculating this weeknum_last = int(time.strftime('%W', timetup))

1 0

migration from Majordomo to Mailman
by Heiko Rommel 08 Mar '02

08 Mar '02

Hi, just in case somebody finds it usefull I'm including a perl script that will largely easy the migration from Majordomo to Mailman 2.0 - especially if you have more than a few lists. The process of migration is only half-automatic since there are a bunch of params in Majordomo which have no exact counterpart in Mailman. On the other hand, there are some new params in Mailman which had to be set to a default value. The script is far from being perfect - but it worked from me and the 208 lists I had to migrate ;-) Heiko Rommel phone +49-911-740 53 696 SuSE GmbH fax +49-911-741 77 55 Deutschherrnstr. 15-19 mail rommel(a)suse.de 90429 Nuernberg www http://www.suse.de/ Germany

2 2

[PATCH] Always add footer for us-ascii lists
by Ben Gertzfield 08 Mar '02

08 Mar '02

This patch solves Dan Mick's problem where people posting with the charset iso-8859-1 or utf-8 were not having the footer added to the list, which was set to use us-ascii. Since all the charsets we support are strictly supersets of us-ascii, I think it's always safe to add the footer to plain text messages of any charset when the list's charset is us-ascii. (No, UTF-16 will not be supported with this change. But it wouldn't have been supported with the old system anyway..) Tested patch follows, against Mailman CVS. -- Brought to you by the letters P and I and the number 11. "You have my pills!" Debian GNU/Linux maintainer of Gimp and Nethack -- http://www.debian.org/ Index: Decorate.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/Decorate.py,v retrieving revision 2.10 diff -u -r2.10 Decorate.py --- Decorate.py 23 Feb 2002 06:46:16 -0000 2.10 +++ Decorate.py 8 Mar 2002 01:44:35 -0000 @@ -61,12 +61,18 @@ # matches the charset of the list's preferred language. This is a # suboptimal solution, and should be solved by allowing a list to have # multiple headers/footers, for each language the list supports. + # + # Also, if the list's preferred charset is us-ascii, we can always + # safely add the header/footer to a plain text message since all + # charsets Mailman supports are strict supersets of us-ascii -- + # no, UTF-16 emails are not supported yet. mcset = msg.get_param('charset', 'us-ascii') lcset = Utils.GetCharSet(mlist.preferred_language) msgtype = msg.get_type('text/plain') # BAW: If the charsets don't match, should we add the header and footer by # MIME multipart chroming the message? - if not msg.is_multipart() and msgtype == 'text/plain' and mcset == lcset: + if (not msg.is_multipart() and msgtype == 'text/plain' and + (lcset == 'us-ascii' or mcset == lcset)): payload = header + msg.get_payload() + footer msg.set_payload(payload) elif msg.get_type() == 'multipart/mixed':

1 0

Can you set a list's password via the command line?
by James Madill 08 Mar '02

08 Mar '02

In moving the 175 mailing lists from one machine (version 2.0.1) to another (version 2.0.8), all of the list passwords are no longer working. Is there a way to set a list's password via the command line? I'd hate to have to manually set each one & send it to the list admin(s). -- James o o o o o o o . . . _______________________ _______=======_T___ o _____ |James Madill | |Duke Univ Med Ctr| >.][__n_n_| D[ ====|____ |james.madill(a)duke.edu| | (919) 286-6384 | (________|__|_[____/____]_|_____________________|_|_________________| _/oo O-O-O ` oo oo 'o^o^o o^o^o` 'o^o o^o` -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- <http://www.duke.edu/~madil001/>

2 1

forwarded message from Hye-Shik Chang
by barry＠zope.com 07 Mar '02

07 Mar '02

Do we have anybody who could do a Korean translation for Mailman? -Barry

1 0

forwarded message from Lisa M. Opus Goldstein
by barry＠zope.com 07 Mar '02

07 Mar '02

Here's a great way to help with Mailman even if you don't fancy yourself a hacker. Documentation, as always, lags far behind. I'd be happy to work with someone (or perhaps a group of someones), on the technical side, but a good technical writer I'm not. -Barry

1 0

Attachments
by Rodolfo Pilas 07 Mar '02

07 Mar '02

I had MM 2.1a4+ from CVS downloaded February 07,2002. Today I upload to the latest version of CVS and I have just seen the following problems: SUBJECT: Subject line that said [Test] label now say ¡Test¿ (I used MM with Spanish language) ATTACHMENT I do not receive attachments, MM brokes attachment: This is a source of last part of the header an complete message (without text, only with attachment) that I receive: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-VDRv7n6c29BFJBk4/S1O"; charset="es" Content-Transfer-Encoding: 8bit X-Evolution-Source: imap://rodolfo.pilas@mydomain.com/ --=-VDRv7n6c29BFJBk4/S1O-- That's all! As soon as I re-install the CVS version of Feb.07 all return to the normal way. -- Rodolfo Pilas Quien los puso a estos tipos donde estan, rodolfo(a)pilas.net Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, ICQ #17461636 Quien les paga para que hagan lo que haran http://xtralinux.org -=# Apocalipsis Now % Cuarteto de Nos #=- Public GnuPG key: http://www.keyserver.net 1024D/57153363 2001-06-02 key fingerprint = DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363

1 0

Unsubscribe confirmation message
by Rodolfo Pilas 07 Mar '02

07 Mar '02

[MM 2.1a4+ uptdated from CVS today] When I sent a message to test-leave(a)mydomain.com I receive a confirmation of unsubscription, but the message macros have not been replaced propertly. -----Mensaje reenviado----- From: test-request(a)mydomain.com To: rodolfo.pilas(a)mydomain.com Subject: confirm 7b48481651194c40f4c1488e7d8ad16499e45d0a Date: 07 Mar 2002 14:44:12 -0300 Mensaje de confirmación para la anulación de la subscripción a la lista de distribución %(listname)s Se ha recibido una solicitud %(remote) para quitar su dirección de correo electrónico "%(email)s" de la lista de distribución %(listaddr)s. Para confirmar que quiere borrarse de esta lista de distribución, solo tiene que responder este mensaje, manteniendo intacta la cabecera del asunto (Subject). O visite esta página web: %(confirmurl)s O incluya la línea siguiente -- y solo la línea siguiente -- en un mensaje dirijido a %(requestaddr)s: confirm %(cookie)s Responder este mensaje debería funcionar con la mayoría de los programas de correo electrónico, porque normalmente dejan de una forma válida la línea del Asunto (el texto adicional Re: en el asunto es correcto) Si no desea borrarse de esta lista de distribución, solo tiene que ignorar este mensaje. Si piensa que alguien quiere borrarle de la lista malintencionadamente o si tiene cualquier otra cuestión, mándelas al administrador de la lista a la dirección %(listadmin)s.

1 0