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