Mailman 3 May 2002 - Mailman-Developers

[ mailman-Feature Requests-224058 ] Wishlist: New Header X-Subscribed-as:
by noreply＠sourceforge.net 03 May '02

03 May '02

Feature Requests item #224058, was opened at 2000-12-01 11:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224058&group_id… Category: mail delivery Group: None >Status: Closed >Resolution: Out of Date Priority: 3 Submitted By: Eduardo Marcel Maçan (emacan) Assigned to: Nobody/Anonymous (nobody) Summary: Wishlist: New Header X-Subscribed-as: Initial Comment: I run a very busy and large list with mailman and frequently face the following problem: Many people subscribe using and e-mail redirector, or changes jobs/provider leaving a mail redirection in the former address. When the new mailbox is full, or worst, when it is not valid anymore we get e-mails bouncing from an Address not subscribed to the list. The offending address cannot be taken care automatically by mailman, and most of the times the list administrator cannot find it by using list_members or by browsing logs, because he does not necessarily has access to the server running his mailing list (Browsing all users in the web interface is not effective in this case, specially for large mailing lists). Other similar situation is that some large ISPs use internal e-mail routing rules to map address(a)somewhere.com to things like user1342(a)state.somewhere.com for an example, and errors usually return to list-admin in the second form. By using a header similar to X-Subscribed-as: email(a)somewhere.com in the message headers we could easily identify such offending e-mails, and maybe even take actions automatically. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:07 Message: Logged In: YES user_id=12800 Mailman 2.1 will (optionally) support verp and personalized messages. Yes, it increases the load on the mail server. With verp/personalization enabled, MM2.1 does not add a separate X-Subscribed-As: header, but I also don't think it's necessary, since the subscribed address is encoded in the envelope sender, so it should always be extractable both automatically and manually. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2001-10-06 08:22 Message: Logged In: NO The thing about the incerased Load is only partly true. On the one Hand qmail threads a message to several people already as several seperate messages at least concerning SMTP handling, on the other hand a lot of features whished for mailman really really need per subscriber messages. * VERP * Easy unsubscribe * Customized Messages , "Dear Mx. X," --drt(a)un.bewaff.net ---------------------------------------------------------------------- Comment By: Cord Beermann (cord) Date: 2001-08-16 15:43 Message: Logged In: YES user_id=50101 If you don't want to add such a header it would be nice if Mailman sends one bounce through to the List-admin, so he/she can deal with it. Yet there are only log-entries which can only be vied by someone with an acoount on the computer. Cord ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2001-02-26 03:25 Message: Logged In: YES user_id=34209 The problem with this is that it requires sending each message seperately. Mailman currently does it in bulk, which for big lists greatly (and I mean *greatly*) reduces the load on both the Mailman machine and the SMTP server that it uses, not to mention mailservers that host a lot of the subscribers to that list. Still, might be worth doing optionally, if both the site owner and the list owner (and possibly the subscriber themselves, though maybe not :) enable it. (Not a mailman developer, just a user giving his opinion ;) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=224058&group_id…

1 0

[ mailman-Feature Requests-548321 ] Listproc archive to Mailman Conversion
by noreply＠sourceforge.net 03 May '02

03 May '02

Feature Requests item #548321, was opened at 2002-04-24 17:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=548321&group_id… Category: None Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Listproc archive to Mailman Conversion Initial Comment: Is it possible. we have a listproc archive and we would like to convert it to mailman format. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 01:03 Message: Logged In: YES user_id=12800 If the listproc archive is in Unix mailbox format then yes. If it's in a different format recognized by Python mailbox module then it might be possible with a little bit of Python hacking. As it is, this question is better asked on the mailman-users(a)python.org mailing list. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=548321&group_id…

1 0

[ mailman-Bugs-550524 ] archiving with invalid dates
by noreply＠sourceforge.net 03 May '02

03 May '02

Bugs item #550524, was opened at 2002-04-30 03:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id… Category: None Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Michael Kallas (valshaq) Assigned to: Nobody/Anonymous (nobody) Summary: archiving with invalid dates Initial Comment: If you look at http://mail.gnu.org/mailman/listinfo/help-hurd you'll notice there are mails archived into future archives (because of faked timestamps). I think this should not happen, either deleting it instead (SPAM) or archiving it into the current archive. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:40 Message: Logged In: YES user_id=12800 Dan's right, there are knobs you can twiddle so this doesn't happen. Thanks Dan! ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 23:15 Message: Logged In: YES user_id=10725 The list item clobber_date has been present in Mailman for a very long time, to address this issue. There's a GUI item for it. Have you experimented with setting clobber_date? Or alternatively, if you're using 2.1, see settings in Defaults.py about dates in archives. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id…

1 0

Re: Re: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL
by bob＠nleaudio.com 03 May '02

03 May '02

Actually, alias_database only appears to affect the "newaliases" command, and really isn't needed for what Mailman is doing, as I believe Mailman is using the "postalias" command to create the .db file, isn't it? Bob > >> On Wed, May 01, 2002 at 03:52:37PM -0700, Dan Mick wrote: >> > What is this supposed to do? "postalias <a private alias file>" >> > appears to simply create an alias.dir/alias.pag pair in that >> > same directory, but not affect the Postfix delivery at all. >> > Is this a Postfix version skew problem? Is it expected >> > that postalias actually "installs" the aliases somehow? >> > It doesn't seem like that's the case. >> >> You have to setup your /etc/postfix/main.cf like this: >> >> alias_maps = dbm:/etc/postfix/aliases, >> dbm:/usr/local/mailman/aliases.mailman >> >> alias_database = dbm:/etc/postfix/aliases, >> dbm:/usr/local/mailman/aliases.mailman >> >> Then, I just do "postalias aliases.mailman" when I change >> ~mailman/aliases.mailman > >Well, that makes sense, but without that extra bit of "alias_maps" >configuration, the Problem/Solution as written doesn't make >much sense. > >I'm sure it's fixed for 2.1 with the README.POSTFIX file, but 2.0.10 >users are rightfully confused by that entry. > >Also, INSTALL in 2.1 has that partially-useful Problem/Solution >entry; even though it has been updated to point to README.POSTFIX, >it probably shouldn't come off like it solves that problem. > > > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers(a)python.org >http://mail.python.org/mailman/listinfo/mailman-developers >

2 1

[ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr
by noreply＠sourceforge.net 03 May '02

03 May '02

Bugs item #517192, was opened at 2002-02-13 16:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad(a)pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:08 Message: Logged In: YES user_id=12800 monkeymaster, please try the patch, or include a Python 2.2.1 session that shows the bug still exists. I believe this bug report should be marked closed. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 23:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 18:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 12:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('Mr. Bad', 'mr.bad(a)pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 15:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad <mr.bad(a)pigdog.org> I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle <picklejr(a)someplace.foo> This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 14:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@<wherever>" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id…

1 0

[ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr
by noreply＠sourceforge.net 03 May '02

03 May '02

Bugs item #517192, was opened at 2002-02-13 16:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad(a)pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-03 00:07 Message: Logged In: YES user_id=12800 BTW, I'm attaching the patch to Python 2.1.3's rfc822.py that I plan on checking in momentarily. This backports the Python 2.2.1 patch for the problem, and with this, my 2-line example below also succeeds for Python 2.1.3. If there's ever a Python 2.1.4, this patch will be part of it. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-02 23:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 18:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 12:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('Mr. Bad', 'mr.bad(a)pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 15:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad <mr.bad(a)pigdog.org> I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle <picklejr(a)someplace.foo> This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 14:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@<wherever>" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id…

1 0

[ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr
by noreply＠sourceforge.net 03 May '02

03 May '02

Bugs item #517192, was opened at 2002-02-13 21:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad(a)pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-03 03:18 Message: Logged In: YES user_id=10725 I can echo that Python 2.2 doesn't have the parseaddr problem. monkeymaster, can you try Barry's two-line experiment and see if that works or fails? ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 22:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 16:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('Mr. Bad', 'mr.bad(a)pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 19:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad <mr.bad(a)pigdog.org> I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle <picklejr(a)someplace.foo> This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 19:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@<wherever>" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id…

1 0

[ mailman-Bugs-550524 ] archiving with invalid dates
by noreply＠sourceforge.net 03 May '02

03 May '02

Bugs item #550524, was opened at 2002-04-30 07:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Michael Kallas (valshaq) Assigned to: Nobody/Anonymous (nobody) Summary: archiving with invalid dates Initial Comment: If you look at http://mail.gnu.org/mailman/listinfo/help-hurd you'll notice there are mails archived into future archives (because of faked timestamps). I think this should not happen, either deleting it instead (SPAM) or archiving it into the current archive. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-03 03:15 Message: Logged In: YES user_id=10725 The list item clobber_date has been present in Mailman for a very long time, to address this issue. There's a GUI item for it. Have you experimented with setting clobber_date? Or alternatively, if you're using 2.1, see settings in Defaults.py about dates in archives. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id…

1 0

[ mailman-Patches-551327 ] Makefile fix so that errors propagate
by noreply＠sourceforge.net 03 May '02

03 May '02

Patches item #551327, was opened at 2002-05-02 05:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel Resare (noa) Assigned to: Nobody/Anonymous (nobody) Summary: Makefile fix so that errors propagate Initial Comment: While I was trying to build mailman-2.1b1 as an rpm i encountered problems with my python installation that made the build in misc fail. Unfortunately, the error didn't propagate to the toplevel make process so it took some time to track down. The attached patch simply propagates any errors from make subprocesses to the topelevel make in an automake like fashion. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-02 21:54 Message: Logged In: YES user_id=12800 I think a more comprehensive solution might be necessary. I introduced a delivery mistake (calling it email-2.0.3 in misc/Makefile.in) and the build process didn't stop. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id…

1 0

Re: [Mailman-Developers] Postfix instructions in 2.0.10's INSTALL
by Dan Mick 03 May '02

03 May '02

> On Wed, May 01, 2002 at 03:52:37PM -0700, Dan Mick wrote: > > What is this supposed to do? "postalias <a private alias file>" > > appears to simply create an alias.dir/alias.pag pair in that > > same directory, but not affect the Postfix delivery at all. > > Is this a Postfix version skew problem? Is it expected > > that postalias actually "installs" the aliases somehow? > > It doesn't seem like that's the case. > > You have to setup your /etc/postfix/main.cf like this: > > alias_maps = dbm:/etc/postfix/aliases, > dbm:/usr/local/mailman/aliases.mailman > > alias_database = dbm:/etc/postfix/aliases, > dbm:/usr/local/mailman/aliases.mailman > > Then, I just do "postalias aliases.mailman" when I change > ~mailman/aliases.mailman Well, that makes sense, but without that extra bit of "alias_maps" configuration, the Problem/Solution as written doesn't make much sense. I'm sure it's fixed for 2.1 with the README.POSTFIX file, but 2.0.10 users are rightfully confused by that entry. Also, INSTALL in 2.1 has that partially-useful Problem/Solution entry; even though it has been updated to point to README.POSTFIX, it probably shouldn't come off like it solves that problem.

2 1

Prompt Enhancement Request.
by Phil Barnett 02 May '02

02 May '02

What would be the chance of enhancing the following text in the membership modificiation page? I find a lot of people using this option to 'unsubscribe' from the list. I think this would happen less often if there was a better description with a pointer that this is not an unsubscribe function. ------------------- Disable mail delivery Turn this on if you want mail to not be delivered to you for a little while.

3 3

[ mailman-Bugs-540978 ] eMailadress too long ?
by noreply＠sourceforge.net 02 May '02

02 May '02

Bugs item #540978, was opened at 2002-04-08 14:56 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id… Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Markus Mandalka (mandalka) Assigned to: Nobody/Anonymous (nobody) Summary: eMailadress too long ? Initial Comment: I have a list antiatomforum(a)lists.kommunikationssystem.de and others with long names. It seems that mailman can not handle with such long names, because in the subscribe-mail (which you have to answer to be in the list) the first columns are some things from the header (unsubscribe: xxx(a)lists.xxx and so on). Whith names like atest(a)lists.kommunikationssystem.de it works. ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-02 16:27 Message: Logged In: YES user_id=531451 I've found it. A fast fix for is to comment lines 149-150 in Mailman/Handlers:/CookHeaders.py: --- CookHeaders.py 2002-05-02 14:51:36.000000000 +0200 +++ CookHeaders.py.new 2002-05-02 16:12:09.000000000 +0200 @@ -146,8 +146,8 @@ # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded, but is at least text-MUA friendly. The # adding of 2 is for the colon-space separator. - if len(h) + 2 + len(v) > 78: - v = CONTINUATION.join(v.split(', ')) +# if len(h) + 2 + len(v) > 78: +# v = CONTINUATION.join(v.split(', ')) msg[h] = v # Always delete List-Archive header, but only add it back if the list is # actually archiving Tested with Mailman 2.1b1, Source Mage GNU/Linux 2.4.18, Postfix 1.1.7. I know there should be a better way, but I'm not a Python programmer at all. :) ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-12 00:03 Message: Logged In: YES user_id=12800 I've confirmed this bug, but don't have a fix for it right now. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=540978&group_id…

1 0

[ mailman-Patches-551327 ] Makefile fix so that errors propagate
by noreply＠sourceforge.net 02 May '02

02 May '02

Patches item #551327, was opened at 2002-05-02 09:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel Resare (noa) Assigned to: Nobody/Anonymous (nobody) Summary: Makefile fix so that errors propagate Initial Comment: While I was trying to build mailman-2.1b1 as an rpm i encountered problems with my python installation that made the build in misc fail. Unfortunately, the error didn't propagate to the toplevel make process so it took some time to track down. The attached patch simply propagates any errors from make subprocesses to the topelevel make in an automake like fashion. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=551327&group_id…

1 0

[ mailman-Bugs-550314 ] Sending to multiple lists chooses one.
by noreply＠sourceforge.net 02 May '02

02 May '02

Bugs item #550314, was opened at 2002-04-29 11:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Posner (jposnersails) Assigned to: Nobody/Anonymous (nobody) Summary: Sending to multiple lists chooses one. Initial Comment: When I send a single message addressed as multiple lists on to 'TO:' line, each recipient receives exactly one copy. If a single user is a memeber of more than one list, he receives the copy to a "seemingly" random list. I am new to this version (just upgraded from 1.x) and have not seen this problem before. Thanks. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-05-01 22:52 Message: Logged In: NO If your users run Cyrus, or some similar mail system, messages with duplicate message-IDs are only stored once. This may, or may not, be relevant. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-01 14:54 Message: Logged In: YES user_id=10725 Just tested with close-to-current 2.1CVS; it works for me. Two test lists, one post with both lists on To: line, I get two copies as expected. What version are you running? It might be worth checking the archives to see if the message got to both places; maybe one list is broken. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id…

1 0

Uncaught runner exception: 'NoneType' object
by totschnig.michael＠uqam.ca 02 May '02

02 May '02

Hello an error related to NoneType objects having no attributes has already been reported on this list. I get such an error only when I create a new list, only the mail sent to mailman-owner enumerating the new aliases to add seems to get caught in this. Should I test the patch Barry sent in message <15534.7944.843739.720556(a)anthem.wooz.org> to solve this problem? My MTA is sendmail. Thanks, Michael Apr 30 00:41:51 2002 (602) Uncaught runner exception: 'NoneType' object has no attribute 'Load' Apr 30 00:41:51 2002 (602) Traceback (most recent call last): File "/var/Mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/var/Mailman/Mailman/Queue/Runner.py", line 155, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/Mailman/Mailman/Queue/OutgoingRunner.py", line 58, in _dispose mlist.Load() AttributeError: 'NoneType' object has no attribute 'Load'

2 1

I bit the bullet
by barry＠zope.com 02 May '02

02 May '02

The MailCommandHandler.py module was just completely unmaintainable, so I bit the bullet and replaced it over the last several nights. The framework we've got now is much more extensible, flexible, and maintainable. Basically, each command is implemented in its own module inside the Mailman/Commands directory. You can add new commands by adding a file like cmd_<commandname>.py to the directory. You can delete commands by removing the files (e.g. Marc might want to remove cmd_lists.py :). See the existing files for examples. Through some clever programming, you can limit commands on a per-list, per-domain, per-sender, or per-message basis. Now the only cruft left is Pipermail <wink>. Hopefully over the next several days, I can get back to answering mmdev email, fixing bugs and getting beta2 out. Please start to use the SF trackers for all bugs you find in MM2.1, and all patches against the MM2.1 codebase. My inbox is overflowing, and I'm afraid of missing important bugs and patches. Cheers, -Barry

1 1

a bug?
by Simone Piunno 02 May '02

02 May '02

The site language of my installation is 'it'. Creating a new list with the only permitted language as 'en' I have a list with ['en','it'] (which makes sense) and the preferred language marked as 'it', (which is wrong) Cheers

2 1

Postfix instructions in 2.0.10's INSTALL
by Dan Mick 02 May '02

02 May '02

2.0.10's INSTALL file has this section: Problem: I use Postfix for my MTA and the mail wrapper programs are logging complaints about the wrong GID. Solution: Create a separate aliases file for Postfix in its main.cf config file under the variable "alias_maps". Put the file somewhere in Mailman's home directory, or somewhere else where the user mailman has write access to it; *as user mailman* call Postfix's "postalias" on the alias file. % postalias <the alias file> Also as user mailman, run % python -c'import os; print os.getgid()' This should print out the group id that Mailman should be configured to expect when the mail wrapper programs are run. Call it "thegid". Rebuild Mailman with % ./configure --with-mail-gid=thegid What is this supposed to do? "postalias <a private alias file>" appears to simply create an alias.dir/alias.pag pair in that same directory, but not affect the Postfix delivery at all. Is this a Postfix version skew problem? Is it expected that postalias actually "installs" the aliases somehow? It doesn't seem like that's the case. (There was a question on mailman-users that prompted me to wonder what this meant.)

3 2

Re: [Mailman-Developers] Prompt Enhancement Request.
by Dan Mick 01 May '02

01 May '02

Suggestions? It's always been pretty obvious to me, so I'm no good as a test case. > What would be the chance of enhancing the following text in the > membership modificiation page? > > I find a lot of people using this option to 'unsubscribe' from the > list. I think this would happen less often if there was a better > description with a pointer that this is not an unsubscribe function. > > ------------------- > > Disable mail delivery > > Turn this on if you want mail to not be delivered to you for a little > while. > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers

1 0

[ mailman-Bugs-550314 ] Sending to multiple lists chooses one.
by noreply＠sourceforge.net 01 May '02

01 May '02

Bugs item #550314, was opened at 2002-04-29 18:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Posner (jposnersails) Assigned to: Nobody/Anonymous (nobody) Summary: Sending to multiple lists chooses one. Initial Comment: When I send a single message addressed as multiple lists on to 'TO:' line, each recipient receives exactly one copy. If a single user is a memeber of more than one list, he receives the copy to a "seemingly" random list. I am new to this version (just upgraded from 1.x) and have not seen this problem before. Thanks. ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-05-01 21:54 Message: Logged In: YES user_id=10725 Just tested with close-to-current 2.1CVS; it works for me. Two test lists, one post with both lists on To: line, I get two copies as expected. What version are you running? It might be worth checking the archives to see if the message got to both places; maybe one list is broken. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id…

1 0

[ mailman-Patches-543945 ] easily disable display of sponsorlogos
by noreply＠sourceforge.net 01 May '02

01 May '02

Patches item #543945, was opened at 2002-04-15 04:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id… Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) Summary: easily disable display of sponsorlogos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- >Comment By: Adi Fairbank (adifairbank) Date: 2002-05-01 20:58 Message: Logged In: YES user_id=515566 I will port the patch to 2.1 once I get a chance to upgrade. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 20:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id…

1 0

[ mailman-Patches-413257 ] patch to allow for mass unsubscribes
by noreply＠sourceforge.net 01 May '02

01 May '02

Patches item #413257, was opened at 2001-04-02 23:08 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=413257&group_id… Category: command line scripts Group: None >Status: Closed Resolution: None Priority: 5 Submitted By: Marc Merlin (marcmerlin) Assigned to: Nobody/Anonymous (nobody) Summary: patch to allow for mass unsubscribes Initial Comment: It allows you to unsubscribe Emails from all your mailing lists at once. I ran it on 10,000+ lists on sourceforge, and it ran in less than 10mn, which beats my wrapper shell script by one order of magnitude or two. (the patch adds a special list name '_alllists_') Here's what it looks like: usw-sf-list1:/var/local/mailman/bin# time ./remove_members -f /tmp/badmails _alllists_ User `gb(a)viscomvisual.com' removed from list `berlin-fresco' User `jprice(a)chiinc.com' removed from list `foxgui-announce' User `bmcgroarty(a)high-voltage.com' removed from list `freenet-announce' User `Wilhelm.Pastoors(a)vetmed.uni-giessen.de' removed from list `gump-develop' User `oscu(a)sina.com' removed from list `linux-usb-devel' User `mehdi-laurent.akkar(a)fr.delarue.com' removed from list `madchat-annonces' User `ras(a)colltech.com' removed from list `sendpage-devel' User `mkimball(a)pdi.com' removed from list `utah-glx-cvs' User `mkimball(a)pdi.com' removed from list `utah-glx-dev' User `mkimball(a)pdi.com' removed from list `utah-glx-users' User `brianp(a)pdi.com' removed from list `vacm-develop' User `guido(a)comlog.nl' removed from list `wxwindows-users' User `frekytah(a)jono.com' removed from list `solar-empire-developer' User `dan(a)dar.net' removed from list `xemacs-winnt' real 7m26.294s user 1m9.120s sys 1m10.640s ---------------------------------------------------------------------- >Comment By: Marc Merlin (marcmerlin) Date: 2002-05-01 20:57 Message: Logged In: YES user_id=6500 This was rewritten and integrated in mailman 2.1 cvs ---------------------------------------------------------------------- Comment By: Marc Merlin (marcmerlin) Date: 2001-12-12 17:11 Message: Logged In: YES user_id=6500 Ooops, wrong file. Uploading the real diff. ---------------------------------------------------------------------- Comment By: Marc Merlin (marcmerlin) Date: 2001-12-12 17:09 Message: Logged In: YES user_id=6500 New version of the patch against mailman cvs ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=413257&group_id…

1 0

[ mailman-Patches-543943 ] removes redundant "<BODY " tag
by noreply＠sourceforge.net 01 May '02

01 May '02

Patches item #543943, was opened at 2002-04-15 04:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id… Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: removes redundant "<BODY " tag Initial Comment: In htmlformat.Document.Format(), an extra "<BODY " tag is appended. Looks like a typo. ---------------------------------------------------------------------- >Comment By: Adi Fairbank (adifairbank) Date: 2002-05-01 20:56 Message: Logged In: YES user_id=515566 Sorry, I just attached the patch. Don't know if it's relevant for MM2.1.. I haven't installed that yet. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 20:47 Message: Logged In: YES user_id=12800 No patch was attached. Is this still relevant for MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id…

1 0

[ mailman-Patches-543943 ] removes redundant "<BODY " tag
by noreply＠sourceforge.net 01 May '02

01 May '02

Patches item #543943, was opened at 2002-04-15 04:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id… Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: removes redundant "<BODY " tag Initial Comment: In htmlformat.Document.Format(), an extra "<BODY " tag is appended. Looks like a typo. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 20:47 Message: Logged In: YES user_id=12800 No patch was attached. Is this still relevant for MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id…

1 0

[ mailman-Patches-543945 ] easily disable display of sponsorlogos
by noreply＠sourceforge.net 01 May '02

01 May '02

Patches item #543945, was opened at 2002-04-15 04:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id… Category: Web UI Group: Mailman 2.0.x Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: easily disable display of sponsorlogos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 20:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id…

1 0

[ mailman-Patches-543943 ] removes redundant "<BODY " tag
by noreply＠sourceforge.net 01 May '02

01 May '02

Patches item #543943, was opened at 2002-04-15 00:22 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id… Category: Web UI Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: removes redundant "<BODY " tag Initial Comment: In htmlformat.Document.Format(), an extra "<BODY " tag is appended. Looks like a typo. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 16:47 Message: Logged In: YES user_id=12800 No patch was attached. Is this still relevant for MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543943&group_id…

1 0

[ mailman-Patches-543945 ] easily disable display of sponsor
by noreply＠sourceforge.net 01 May '02

01 May '02

logos Patches item #543945, was opened at 2002-04-15 00:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id… Category: Web UI Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) Summary: easily disable display of sponsor logos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 16:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id…

1 0

[ mailman-Patches-543945 ] easily disable display of sponsor
by noreply＠sourceforge.net 01 May '02

01 May '02

logos Patches item #543945, was opened at 2002-04-15 00:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id… Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Adi Fairbank (adifairbank) Assigned to: Nobody/Anonymous (nobody) >Summary: easily disable display of sponsor logos Initial Comment: Creates a new boolean configuration variable in Defaults.py called DISABLE_SPONSOR_LOGOS (to be overridden in mm_cfg.py) which quickly disables display of sponsor logos. You no longer need to hack htmlformat.py. Patch is against version 2.0.8. ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-05-01 16:43 Message: Logged In: YES user_id=12800 No file is attached. Did you forget to check the "upload & attach file" checkbox? Do you feel like porting your patch to MM2.1? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=543945&group_id…

1 0

[ mailman-Bugs-214205 ] e-mail<->usenet gateway Reply-To header (PR#303)
by noreply＠sourceforge.net 01 May '02

01 May '02

Bugs item #214205, was opened at 2000-09-11 22:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id… Category: nntp/news Group: None Status: Open Resolution: None Priority: 4 Submitted By: Nobody/Anonymous (nobody) Assigned to: Barry Warsaw (bwarsaw) Summary: e-mail<->usenet gateway Reply-To header (PR#303) Initial Comment: Jitterbug-Id: 303 Submitted-By: orion(a)tribble.dyndns.org Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT) Version: 2.0beta4 OS: Debian linux potato I'm running a plain e-mail<->usenet gateway. When someone replies to a usenet post through the list, his e-mail client sets an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to improperly thread messages. I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line 82: # if the message is a reply to a previous post, change the header so # that newsreaders can thread it properly if msg.getheader('in-reply-to'): msg.headers.append('References: %s\n' % msg.getheader('in-reply-to')) del msg['in-reply-to'] I'm happy to say that this solved the problem. (before you laugh at me, take note that I never looked at python before.) ==================================================================== Audit trail: None ---------------------------------------------------------------------- Comment By: Giovanni Lopedote (giuans) Date: 2002-05-01 14:34 Message: Logged In: YES user_id=531451 What a coincidence! I had the same problem and I looked into the code, then modified it to work properly. The coincidence is that my patch is *identical* to yours. So, for sure it works :-) ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2000-09-27 23:00 Message: RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2000-09-19 18:48 Message: This sounds like the email client in question is broken. Mine for example, correctly inserts References: headers and the news readers properly thread the messages. I'm not inclined to cater to broken email or news clients. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_id…

1 0