Mailman 3 November 2004 - Mailman-coders

[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option
by SourceForge.net 25 Nov '04

25 Nov '04

Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl(a)freefriends.org ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:32 Message: Logged In: YES user_id=18417 The problem is that this idea is likely to cause a number of programs to break, probably pretty badly. I think this is a very bad idea. We don't want to be doing things to encourage people to break the standards, especially since most people who would use this option would not understand the true scope of the problem. Using two "Reply-to:" headers doesn't resolve this issue, either. If you want to munge the "Reply-to:" header to point back to the list, then Mailman gives you the ability to do that. It's a bad idea, for the reasons laid out in the FAQ, but you do have that capability. ---------------------------------------------------------------------- Comment By: karl berry (kberry) Date: 2004-11-25 18:20 Message: Logged In: YES user_id=33248 I'm trying to help my users avoid a fairly common mistake, not engage in arguments about standards. Fine, Reply-to: list, poster may not work for the population of some lists. So those lists won't enable it. Meanwhile, it will help some people and lists, and there's no other way to accomplish the behavior (that I know of). It's trivial to add and a tiny change in the user interface. I am not asking for per-user control of this, which is what the FAQ entry you cited mostly discusses. Obviously some compromise has already been made with the "reply-to considered harmful" stance. (For which I am very thankful, because it is very useful.) ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See <http://www.python.org/cgi-bin/ faqw-mm.py?req=show&file=faq03.048.htp> for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=10… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i…

1 0

[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option
by SourceForge.net 25 Nov '04

25 Nov '04

Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by kberry You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl(a)freefriends.org ---------------------------------------------------------------------- >Comment By: karl berry (kberry) Date: 2004-11-25 18:20 Message: Logged In: YES user_id=33248 I'm trying to help my users avoid a fairly common mistake, not engage in arguments about standards. Fine, Reply-to: list, poster may not work for the population of some lists. So those lists won't enable it. Meanwhile, it will help some people and lists, and there's no other way to accomplish the behavior (that I know of). It's trivial to add and a tiny change in the user interface. I am not asking for per-user control of this, which is what the FAQ entry you cited mostly discusses. Obviously some compromise has already been made with the "reply-to considered harmful" stance. (For which I am very thankful, because it is very useful.) ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See <http://www.python.org/cgi-bin/ faqw-mm.py?req=show&file=faq03.048.htp> for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=10… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i…

1 0

[ mailman-Patches-951167 ] patch for #923122 reply_goes_to_list allow poster+list ...
by SourceForge.net 25 Nov '04

25 Nov '04

Patches item #951167, was opened at 2004-05-10 10:36 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=951167&group_i… Category: mail delivery Group: None Status: Open Resolution: None Priority: 5 Submitted By: URA Hiroshi (ura) Assigned to: Nobody/Anonymous (nobody) Summary: patch for #923122 reply_goes_to_list allow poster+list ... Initial Comment: This is patch for #923122 reply_goes_to_list allow poster+list option. http://sourceforge.net/tracker/index.php?func=detail&aid=923122&group_id=10… The patch introduces a new variable `add_poster_to_reply_to' per list. If `add_poster_to_reply_to' is `Yes' and poster isn't member of list, address to poster is added to Reply-To header. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:19 Message: Logged In: YES user_id=18417 The "Reply-to:" header is only supposed to include one address. The handling of multiple addresses in this header is undefined, and some clients may handle that correctly, while others almost certainly won't. I don't think that this patch is a good idea. Ultimately, all problems with "Reply-To:" are clients problems, see <http: //www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.048.htp>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=951167&group_i…

1 0

[ mailman-Feature Requests-1041963 ] Members of sub-lists can't post to umbrella list
by SourceForge.net 25 Nov '04

25 Nov '04

Feature Requests item #1041963, was opened at 2004-10-07 03:37 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041963&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Evan Prodromou (evanprodromou) Assigned to: Nobody/Anonymous (nobody) Summary: Members of sub-lists can't post to umbrella list Initial Comment: Consider list1 and list2 on the same Mailman server. The admin creates a third list, list3, to act as an umbrella list for both lists. If the admin configures list3 so that only list members can post, members of list1 or list2 can't post to the list. This is a FAQ'd problem with a workaround: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.005.htp The problem should be fixed so that the workaround isn't needed. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 18:18 Message: Logged In: YES user_id=18417 I think that this issue is addressed by Jim Tittsler's patch at <http:// starship.python.net/crew/jwt/mailman/#listinclusion>. I'm trying now to see if this has been uploaded to the Mailman SourceForge Patch tracker, and if not I'll try to get Jim to upload it himself. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-10-13 13:09 Message: Logged In: YES user_id=67709 This is more a feature request than a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041963&group_…

1 0

[ mailman-Feature Requests-893870 ] allow signed postings from non-subscribers
by SourceForge.net 25 Nov '04

25 Nov '04

Feature Requests item #893870, was opened at 2004-02-10 04:51 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=893870&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ben Elliston (elliston) Assigned to: Nobody/Anonymous (nobody) Summary: allow signed postings from non-subscribers Initial Comment: It would be great if Mailman could permit posting from non-subscribers if the incoming message can be verified based on a per-list or site-wide GPG keyring. If per-list keyring could have a GPG key of the list owner, who in turn can sign keys of people they trust to post to the list. Furthermore, such posters could subscribe by email without needing to confirm. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:28 Message: Logged In: YES user_id=18417 Mailman has nothing to do with PGP. It can allow messages to include certain MIME bodypart types which would include signatures, but that would not include having the server validate those signatures. If you want tighter integration between Mailman and PGP, that's a separate matter, and should probably be a different RFE. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=893870&group_i…

1 0

[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option
by SourceForge.net 25 Nov '04

25 Nov '04

Feature Requests item #923122, was opened at 2004-03-25 14:01 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: karl berry (kberry) Assigned to: Nobody/Anonymous (nobody) Summary: reply_goes_to_list allow poster+list option Initial Comment: Right now, the reply_goes_to_list option allows (a) poster, (b), list, and (c) explicit. How about (d) poster AND list? That is, insert/override a reply-to: header containing both the list name, and the original reply-to (if present, else From: address). For extra credit, omit the original poster if they are a list member. This would be very useful for a number of lists I maintain, where 90% of the traffic is among the list members (hence having a simple reply go to the list), yet a few messages come in from the outside world (hence including the original poster's address). I'm using mailman 2.1.4 on GNU/Linux. Thanks, karl(a)freefriends.org ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:26 Message: Logged In: YES user_id=18417 I don't think this is possible. "Reply-to:" goes back to one address, not two. The action of having multiple "Reply-to:" headers is also undefined, and some clients may work the way you want, while others may work in ways you do not. Pretty much everything to do with "Reply-to:" is really a client problem, and needs to be solved there. See <http://www.python.org/cgi-bin/ faqw-mm.py?req=show&file=faq03.048.htp> for details. ---------------------------------------------------------------------- Comment By: URA Hiroshi (ura) Date: 2004-05-10 10:44 Message: Logged In: YES user_id=1007264 I uploaded the patch by different method. see following URL: http://sourceforge.net/tracker/index.php?func=detail&aid=951167&group_id=10… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=923122&group_i…

1 0

[ mailman-Feature Requests-1070016 ] Better way to manage google & co
by SourceForge.net 25 Nov '04

25 Nov '04

Feature Requests item #1070016, was opened at 2004-11-20 14:20 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1070016&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Peer Heinlein (pheinlein) Assigned to: Nobody/Anonymous (nobody) Summary: Better way to manage google & co Initial Comment: It`s possible to disallow google to index a public web-archive of a mailinglist by a robots.txt. But it would be much nicer if a admin could change this behavior in the MM-admin-config-interface. If a flag like "robots_allow_index" is set to NO, pipermail should add a HTML-Header <META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"> to each html-page generated by pipermail. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2004-11-25 15:16 Message: Logged In: YES user_id=18417 Actually, on another project I'm working on, we've found that robots.txt doesn't seem to stop Google. They index the page anyway. It would definitely be nice if we could find other ways to stop them from doing that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1070016&group_…

1 0

[ mailman-Feature Requests-1073232 ] Reject/discard decisions before hold...
by SourceForge.net 25 Nov '04

25 Nov '04

Feature Requests item #1073232, was opened at 2004-11-25 15:15 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1073232&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Reject/discard decisions before hold... Initial Comment: Folks, It would be really nice if Mailman could intelligently make reject/ discard decisions before looking at decisions which would result in a "hold" action. For example, if the list is configured for a maximum message size of 40KB and reject any message over that size, but postings from non-members are held for moderation, then it would be nice if a non-member posting a message over 40KB in size got an auto- reject for being too large as opposed to being held for moderation because it's from a non-member. Same for discard -- make these decisions before looking at ones that could result in a "hold". This would make the lives of moderators and list server managers much nicer, since a lot of spam could be rejected or discarded outright, and we'd never need to see it or deal with it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1073232&group_…

1 0

[ mailman-Bugs-1072217 ] CookieError on addresses with plus and/or equal signs
by SourceForge.net 25 Nov '04

25 Nov '04

Bugs item #1072217, was opened at 2004-11-24 01:16 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072217&group_… Category: Web/CGI Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Juanma Barranquero (lektu) Assigned to: Nobody/Anonymous (nobody) Summary: CookieError on addresses with plus and/or equal signs Initial Comment: The Web/CGI interface to mailmain allows the user to set addresses where the "name" part includes "+" and "=" chars, but chokes afterwards when trying to log in again with such addresses (which are, I think, perfectly fine). For example, I registererd to the mod_python list as xxx(a)yyy.com; after a while I changed it to xxx+list=mod-python(a)yyy.com, which worked all right. But trying to access the web interface brings: Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/options.py", line 226, in main password, user): File "/var/mailman/Mailman/SecurityManager.py", line 226, in WebAuthenticate print self.MakeCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 240, in MakeCookie c[key] = binascii.hexlify(marshal.dumps((issued, mac))) File "/usr/lib/python2.3/Cookie.py", line 581, in __setitem__ self.__set(key, rval, cval) File "/usr/lib/python2.3/Cookie.py", line 574, in __set M.set(key, real_value, coded_value) File "/usr/lib/python2.3/Cookie.py", line 453, in set raise CookieError("Illegal key value: %s" % key) CookieError: Illegal key value: mod_python+user+xxx+list=mod-python--at--yyy.com [etc, etc] ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-25 12:46 Message: Logged In: YES user_id=67709 I've just fixed this in CVS (Release_2_1-maint). SecurityManager.py revision 2.20.2.5 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072217&group_…

1 0

[ mailman-Bugs-1070692 ] Uncaught runner exception: frexp() result out of range
by SourceForge.net 24 Nov '04

24 Nov '04

Bugs item #1070692, was opened at 2004-11-22 00:28 Message generated for change (Comment added) made by pokemoen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1070692&group_… Category: mail delivery Group: 2.1 beta >Status: Deleted Resolution: None Priority: 5 Submitted By: Pokemoen (pokemoen) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception: frexp() result out of range Initial Comment: debian, x86, mailman Version: 2.1.5-4, python 2.3.4-13 after upgrading mailman, when sending a mail (from a svn-hook or mutt) i get the folling error : (taken from /var/log/mailman/error) ----------------------------------------------------------------------- Nov 22 01:08:15 2004 (15323) Uncaught runner exception: frexp() result out of range Nov 22 01:08:15 2004 (15323) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/ToOutgoing.py", line 55, in process outq.enqueue(msg, msgdata, listname=mlist.internal_name()) File "/var/lib/mailman/Mailman/Queue/Switchboard.py", line 129, in enqueue cPickle.dump(data, fp, protocol) SystemError: frexp() result out of range Dec 13 21:05:24 1901 (15323) SHUNTING: 1101082094.6941769+f15ffd34953b7dac540e2bfd3f041d0c8adcb9c1 ----------------------------------------------------------------------- this happens also after a purge & reinstall, also checkout the cool date on the last line :) ---------------------------------------------------------------------- >Comment By: Pokemoen (pokemoen) Date: 2004-11-24 23:15 Message: Logged In: YES user_id=1021709 python seems to have magicly fixed itself and i can't reproduce it anymore. please ignore until it comes up again. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1070692&group_…

1 0