Mailman 3 June 2002 - Mailman-Developers

Re: [Mailman-Developers] Mailman password and administrative reminders
by Dan Mick 14 Aug '03

14 Aug '03

? This very message came to me with the following header: Errors-To: mailman-developers-admin(a)python.org All my bounces come to the list admin address, set in the admin webpage, in the second field of General Options. Do you have that set to something, and bounces still come to root? > 2. Bounces are sent to the poor postmaster instead of a -admin address. > I'm not entirely certain, but I think an Errors-To: header or something > like that in all Mailman messages might allow one to distribute that load > somewhat.

8 11

External subscriber lists in 2.1
by J C Lawrence 23 Aug '02

23 Aug '02

Barry, In 2.1 when used with external subscriber storage (eg SQL), will the new equivalent of qrunner request and load the entire subscriber DB onto the heap prior to broadcast? <<Yeah, I'm cheating and being lazy on not checking the source myself>> Reason: This poses scaling problems for lists with very large numbers of subscribers. I'd suggest paging thru the set in blocks. ObExcuse: Chap on -users asking about millions of subscribers. -- 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.

3 4

MM2.1 CVS: broken configure script
by Matthias Klose 11 Jul '02

11 Jul '02

mailman checks for the installation directories during configury. IMO this wrongly assumes, that - the build machine is the target machine - the directories already exist during configuration - you don't use a temporary installation directory 2.1b2 works ok. Found this while making experimental Debian packages. Matthias ./configure --prefix=/usr/lib/mailman \ --with-var-prefix=/var/lib/mailman \ --with-username=list \ --with-groupname=list \ --with-mail-gid=daemon --with-cgi-gid=www-data creating cache ./config.cache checking for --with-python... no checking for python... /usr/bin/python checking Python interpreter... /usr/bin/python checking Python version... 2.1.3 checking for a BSD compatible install... /usr/bin/install -c checking whether make sets ${MAKE}... yes checking for true... /bin/true checking for --without-gcc... no checking for gcc... gcc checking whether the C compiler (gcc ) works... yes checking whether the C compiler (gcc ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking whether #! works in shell scripts... yes checking for --with-var-prefix... /var/lib/mailman checking for --with-username... list checking for list UID... 38 checking for --with-groupname... list checking for list GID... 38 checking permissions on /var/lib/mailman... configure: error: ***** Installation directory /var/lib/mailman is not configured properly! ***** Directory doesn't exist: /var/lib/mailman make: *** [configure-stamp] Error 1

2 1

suggestion for configure
by Ron Jarrell 11 Jul '02

11 Jul '02

Add a --with-fqdn and --with-url or equivalent. The current cvs snapshot can't guess my fqdn on my production box, and it's used now to build a web of interconnected addresses, as well as populate the VIRTUAL_HOSTS table, so I had to do a bunch of deleting and repairing in mm_cfg. I can, if I *remember*, which I've already forgotten once, fix it when I build by setting FQDN and URL environment variables, so that configure picks those up by default, but I have a habit of just looking at config.status to see how I ran configure the last time. Having an explicit configure switch would be nice.

2 1

messages/nl/LC_MESSAGES/mailman.mo
by Jon Parise 01 Jul '02

01 Jul '02

>From the latest CVS sources: install: nl/LC_MESSAGES/mailman.mo: No such file or directory *** Error code 71 It doesn't look like mailman.mo has been checked in for the Dutch translation. -- Jon Parise (jon(a)csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member

3 2

Bug in CVS
by Dan Mick 30 Jun '02

30 Jun '02

Bouncer.py refers to BYUNKNOWN instead of UNKNOWN. Here's the fix: Index: Bouncer.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Bouncer.py,v retrieving revision 2.30 diff -u -r2.30 Bouncer.py --- Bouncer.py 28 May 2002 03:02:23 -0000 2.30 +++ Bouncer.py 18 Jun 2002 16:14:38 -0000 @@ -216,7 +216,7 @@ {MemberAdaptor.BYBOUNCE: 'BYBOUNCE', MemberAdaptor.BYUSER: 'BYUSER', MemberAdaptor.BYADMIN: 'BYADMIN', - MemberAdaptor.BYUNKNOWN: 'BYUNKNOWN'}.get( + MemberAdaptor.UNKNOWN: 'UNKNOWN'}.get( reason, 'invalid value')) return # Send the next notification

2 1

shunt / unshunt
by Danny Terweij 29 Jun '02

29 Jun '02

Hi, What are the files in the shunt dir? When i do bin/unshunt then there is somthing happen, it sends a mail out and the shunt dir is growing. Danny Terweij MM21b2

2 10

Splitting long header lines and the "bug demonstration"
by barry＠zope.com 28 Jun '02

28 Jun '02

I know what is causing http://mail.python.org/pipermail-21/mailman-developers/2002-June/012093.html It's the email package, and specifically it's Generator's behavior when splitting long lines, i.e. Generator._split_header(). I actually think that method is terminally broken because it has a ascii bias. I doubt it would even work for long lines of encoded text. The good news is that we have a perfectly fine line splitter that understands encoded headers and does the RFC-correct thing. It's called Header.encode(). The bad news is that Header.encode() isn't parameter aware and making _split_header() call it will cause some messages to not generate idempotently. If your code is expecting the splitting done by _split_header(), your code will break. Interestingly enough, only 4 unit tests fail when I make this change. In particular, it means that a header like X-Foobar-Spoink-Defrobnit: wasnipoop; giraffes="very-long-necked-animals"; spooge="yummy"; hippos="gargantuan"; marshmallows="gooey" will not get split like X-Foobar-Spoink-Defrobnit: wasnipoop; giraffes="very-long-necked-animals"; spooge="yummy"; hippos="gargantuan"; marshmallows="gooey" but instead will get split like X-Foobar-Spoink-Defrobnit: wasnipoop; giraffes="very-long-necked-animals"; spo oge="yummy"; hippos="gargantuan"; marshmallows="gooey" I can obviously fix the test cases, but will this break your code if I make this change? It should fix the nasty Mailman problem. I'm wondering if I need to make some accomodations for _split_header()'s old behavior. -Barry

3 4

article.html (MM2.1b2)
by Danny Terweij 28 Jun '02

28 Jun '02

Hi, I have found a problem in the article.html from the templates. When a table is used (<table>), then it is ignoring to parse the %(xxx)s commands. Instead of parsing them, it just shows the %(command)s on the web page. Danny Terweij.

1 0

[ mailman-Patches-510415 ] Improve MIME header handling
by noreply＠sourceforge.net 28 Jun '02

28 Jun '02

Patches item #510415, was opened at 2002-01-30 00:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_i… Category: Pipermail Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-28 15:26 Message: Logged In: YES user_id=105527 Thanks, now this is clear. I'll try the beta ASAP :-) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-06-28 06:01 Message: Logged In: YES user_id=12800 k-fish, Martin was actually referring to the revision of one of the files in the Mailman 2.1 distribution. MM2.1 is in beta testing now and will officially support internationalization. The MM2.0.x does not. I'm closing this patch since as Martin says, it's already applied! ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-20 00:21 Message: Logged In: YES user_id=105527 Ok, I could have had a look at the patch header more closely, sorry. Thanks for your answer though, I wasn't aware of 2.14 being existent at all, since 2.0.9 seems to be the latest version being officially avilable... Anyway, my problem with german Umlauts being screwed up was solved by running arch manually, somehow the Umlauts seems to be only messed up when the archiver is run automatically... And rather than backporting (especially now, since my special problem was solved so easily ;) I would love to see a newer version of mailman being released officially... Thanks again for you answer! ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-06-19 20:17 Message: Logged In: YES user_id=21627 The patch applies to version 2.13 of HyperArch.py, just as the patch header says. It was current for the mailman CVS at the time of its creation. It has been applied to the mailman CVS by now (as 2.14), so it is now useless. Feel free to back-port it to mailman 2.0.8 if you want. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 07:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_i…

1 0