Mailman-coders November 2004

mailman-coders@python.org

1 participants
61 discussions

[ mailman-Bugs-1062663 ] empty charset in header crashes admindb.py

by SourceForge.net

Bugs item #1062663, was opened at 2004-11-08 21:52 Message generated for change (Comment added) made by idogan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062663&group_… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ricardo Kustner (rixhq) Assigned to: Nobody/Anonymous (nobody) Summary: empty charset in header crashes admindb.py Initial Comment: when a message contains a header like this: Content-Type: text/plain; charset= (note the empty charset) The admindb.py details page page gives an error. Traceback is below. Btw does this mean the charset value in the header is directly mapped to a module name to import? (sounds kinda scary...) I know the real fault is in the message (I'm not sure if the mime stripper caused this or a bad mailer), but maybe mailman shouldn't crash on this. Traceback (most recent call last): File "/usr/local/mailman/scripts/driver", line 87, in run_main main() File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 222, in main show_detailed_requests(mlist, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 545, in show_detailed_requests show_post_requests(mlist, id, info, total, count, form) File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 611, in show_post_requests body = unicode(body, mcset).encode(lcset) File "/usr/lib/python2.2/encodings/__init__.py", line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name ---------------------------------------------------------------------- Comment By: idogan (idogan) Date: 2004-11-30 22:09 Message: Logged In: YES user_id=1169233 I have exactly the same problem: Nov 30 21:53:09 2004 admin(21885): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(21885): [----- Mailman Version: 2.1.5 -----] admin(21885): [----- Traceback ------] admin(21885): Traceback (most recent call last): admin(21885): File "/opt/mailman/scripts/driver", line 87, in run_main admin(21885): main() admin(21885): File "/opt/mailman/Mailman/Cgi/admindb.py", line 163, in main admin(21885): process_form(mlist, doc, cgidata) admin(21885): File "/opt/mailman/Mailman/Cgi/admindb.py", line 711, in process_form admin(21885): forward, forwardaddr) admin(21885): File "/opt/mailman/Mailman/ListAdmin.py", line 159, in HandleRequest admin(21885): forward, addr) admin(21885): File "/opt/mailman/Mailman/ListAdmin.py", line 345, in __handlepost admin(21885): syslog('vette', note) admin(21885): File "/opt/mailman/Mailman/Logging/Syslog.py", line 40, in write admin(21885): self.write_ex(kind, msg, args, kws) admin(21885): File "/opt/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex admin(21885): logf.write(msg + '\n') admin(21885): File "/opt/mailman/Mailman/Logging/StampedLogger.py", line 73, in write admin(21885): Logger.write(self, "%s %s" % (prefix, msg)) admin(21885): File "/opt/mailman/Mailman/Logging/Logger.py", line 91, in write admin(21885): f.write(msg) admin(21885): UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 90: ordinal not in range(128) admin(21885): [----- Python Information -----] admin(21885): sys.version = 2.3.4 (#1, Nov 10 2004, 13:08:40) [C] admin(21885): sys.executable = /opt/csw/bin/python admin(21885): sys.prefix = /opt/csw admin(21885): sys.exec_prefix = /opt/csw admin(21885): sys.path = /opt/csw admin(21885): sys.platform = sunos5 admin(21885): [----- Environment Variables -----] admin(21885): HTTP_COOKIE: eth+admin=2802000000694eddac41732800000031336161396238633262356333316431613335633033383739313330326164303462643162393164 admin(21885): SERVER_SOFTWARE: Apache/2.0.52 (Unix) admin(21885): SCRIPT_NAME: /mailman/admindb admin(21885): SERVER_SIGNATURE: <address>Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443</address> admin(21885): admin(21885): REQUEST_METHOD: POST admin(21885): HTTP_KEEP_ALIVE: 300 admin(21885): SERVER_PROTOCOL: HTTP/1.1 admin(21885): QUERY_STRING: admin(21885): CONTENT_LENGTH: 433 admin(21885): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(21885): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041108 admin(21885): HTTP_CONNECTION: keep-alive admin(21885): HTTP_REFERER: https://lists.dogan.ch/mailman/admindb/eth admin(21885): SERVER_NAME: lists.dogan.ch admin(21885): REMOTE_ADDR: 213.144.141.146 admin(21885): PATH_TRANSLATED: /var/www/lists.dogan.ch/htdocs/eth admin(21885): SERVER_PORT: 443 admin(21885): SERVER_ADDR: 213.144.137.44 admin(21885): DOCUMENT_ROOT: /var/www/lists.dogan.ch/htdocs admin(21885): PYTHONPATH: /opt/mailman admin(21885): SCRIPT_FILENAME: /opt/mailman/cgi-bin/admindb admin(21885): SERVER_ADMIN: ihsan(a)dogan.ch admin(21885): HTTP_HOST: lists.dogan.ch admin(21885): HTTPS: on admin(21885): REQUEST_URI: /mailman/admindb/eth admin(21885): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(21885): GATEWAY_INTERFACE: CGI/1.1 admin(21885): REMOTE_PORT: 64543 admin(21885): HTTP_ACCEPT_LANGUAGE: de,tr;q=0.7,en;q=0.3 admin(21885): CONTENT_TYPE: application/x-www-form-urlencoded admin(21885): HTTP_ACCEPT_ENCODING: gzip,deflate admin(21885): PATH_INFO: /eth Nov 30 21:53:20 2004 admin(21886): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(21886): [----- Mailman Version: 2.1.5 -----] admin(21886): [----- Traceback ------] admin(21886): Traceback (most recent call last): admin(21886): File "/opt/mailman/scripts/driver", line 87, in run_main admin(21886): main() admin(21886): File "/opt/mailman/Mailman/Cgi/admindb.py", line 163, in main admin(21886): process_form(mlist, doc, cgidata) admin(21886): File "/opt/mailman/Mailman/Cgi/admindb.py", line 711, in process_form admin(21886): forward, forwardaddr) admin(21886): File "/opt/mailman/Mailman/ListAdmin.py", line 159, in HandleRequest admin(21886): forward, addr) admin(21886): File "/opt/mailman/Mailman/ListAdmin.py", line 345, in __handlepost admin(21886): syslog('vette', note) admin(21886): File "/opt/mailman/Mailman/Logging/Syslog.py", line 40, in write admin(21886): self.write_ex(kind, msg, args, kws) admin(21886): File "/opt/mailman/Mailman/Logging/Syslog.py", line 58, in write_ex admin(21886): logf.write(msg + '\n') admin(21886): File "/opt/mailman/Mailman/Logging/StampedLogger.py", line 73, in write admin(21886): Logger.write(self, "%s %s" % (prefix, msg)) admin(21886): File "/opt/mailman/Mailman/Logging/Logger.py", line 91, in write admin(21886): f.write(msg) admin(21886): UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 90: ordinal not in range(128) admin(21886): [----- Python Information -----] admin(21886): sys.version = 2.3.4 (#1, Nov 10 2004, 13:08:40) [C] admin(21886): sys.executable = /opt/csw/bin/python admin(21886): sys.prefix = /opt/csw admin(21886): sys.exec_prefix = /opt/csw admin(21886): sys.path = /opt/csw admin(21886): sys.platform = sunos5 admin(21886): [----- Environment Variables -----] admin(21886): HTTP_COOKIE: eth+admin=2802000000694eddac41732800000031336161396238633262356333316431613335633033383739313330326164303462643162393164 admin(21886): SERVER_SOFTWARE: Apache/2.0.52 (Unix) admin(21886): SCRIPT_NAME: /mailman/admindb admin(21886): SERVER_SIGNATURE: <address>Apache/2.0.52 (Unix) Server at lists.dogan.ch Port 443</address> admin(21886): admin(21886): REQUEST_METHOD: POST admin(21886): HTTP_KEEP_ALIVE: 300 admin(21886): SERVER_PROTOCOL: HTTP/1.1 admin(21886): QUERY_STRING: admin(21886): CONTENT_LENGTH: 433 admin(21886): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7 admin(21886): HTTP_USER_AGENT: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041108 admin(21886): HTTP_CONNECTION: keep-alive admin(21886): HTTP_REFERER: https://lists.dogan.ch/mailman/admindb/eth admin(21886): SERVER_NAME: lists.dogan.ch admin(21886): REMOTE_ADDR: 213.144.141.146 admin(21886): PATH_TRANSLATED: /var/www/lists.dogan.ch/htdocs/eth admin(21886): SERVER_PORT: 443 admin(21886): SERVER_ADDR: 213.144.137.44 admin(21886): DOCUMENT_ROOT: /var/www/lists.dogan.ch/htdocs admin(21886): HTTP_PRAGMA: no-cache admin(21886): PYTHONPATH: /opt/mailman admin(21886): SCRIPT_FILENAME: /opt/mailman/cgi-bin/admindb admin(21886): SERVER_ADMIN: ihsan(a)dogan.ch admin(21886): HTTP_HOST: lists.dogan.ch admin(21886): HTTPS: on admin(21886): HTTP_CACHE_CONTROL: no-cache admin(21886): REQUEST_URI: /mailman/admindb/eth admin(21886): HTTP_ACCEPT: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 admin(21886): GATEWAY_INTERFACE: CGI/1.1 admin(21886): REMOTE_PORT: 64543 admin(21886): HTTP_ACCEPT_LANGUAGE: de,tr;q=0.7,en;q=0.3 admin(21886): CONTENT_TYPE: application/x-www-form-urlencoded admin(21886): HTTP_ACCEPT_ENCODING: gzip,deflate admin(21886): PATH_INFO: /eth ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1062663&group_…

16 years, 2 months

[ mailman-Bugs-1075686 ] footer added to quoted-printable mail isn't encoded

by SourceForge.net

Bugs item #1075686, was opened at 2004-11-30 01:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1075686&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Felix Palmen (tentakel) Assigned to: Nobody/Anonymous (nobody) Summary: footer added to quoted-printable mail isn't encoded Initial Comment: When Mailman adds a footer to a mail with Content-Transfer-Encoding quoted-printable, it doesn't encode the footer in quoted-printable, so spaces (and other characters?) are messed up. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1075686&group_…

16 years, 2 months

[ mailman-Patches-1071669 ] Danish message catalog update

by SourceForge.net

Patches item #1071669, was opened at 2004-11-23 13:44 Message generated for change (Comment added) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_… Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tom G. Christensen (tgc99) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Danish message catalog update Initial Comment: Bring the Danish message catalog in line with Release_2.1-maint. - All fuzzy translations have been fixed - All missing translations have been added - Misc updates to existing translations ---------------------------------------------------------------------- >Comment By: Tom G. Christensen (tgc99) Date: 2004-11-29 10:01 Message: Logged In: YES user_id=1159458 Patch updated to apply cleanly on top of CVS as of 2004-11-29 08:49+100. It also fixes two new fuzzies. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1071669&group_…

16 years, 3 months

[ mailman-Feature Requests-1074197 ] Web interface to sync_members

by SourceForge.net

Feature Requests item #1074197, was opened at 2004-11-27 08:53 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=1074197&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Matthew Saltzman (cumthsc) Assigned to: Nobody/Anonymous (nobody) Summary: Web interface to sync_members Initial Comment: It would be useful to extend the Membership Management page to support sync_members. We use mailman to run a number of members-only lists for a professional society. The membership database is kept on a separate system, and lists of current members are produced for the various lists at regular intervals. It would be easier for our non-technical office staff to keep the mailing list memberships in sync with the main database if they could upload the member list through the Web rather than having to upload the file with FTP and use sudo and shell commands to do the synching. We could mass-delete and mass-subscribe, but it would be more convenient to do it in one step. Also, for some of the lists, new members should receive notification that they have been subscribed, but carry-over members should not get such notification. The only way to do that with add_members is to add in two steps or to make two files with members to be deleted and members to be added, leaving the carry-over members subscribed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1074197&group_…

16 years, 3 months

[ mailman-Patches-1073556 ] fix for some malicious messages

by SourceForge.net

Patches item #1073556, was opened at 2004-11-26 15:22 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1073556&group_… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: fix for some malicious messages Initial Comment: Some malicious messages (most of them are spam or auto-generated messages) cause shunting. - Message containing null byte(s) bound for -request address. - Message with message/delivery-status part and without text/plain part bound for -confirm address or list address. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1073556&group_…

16 years, 3 months

[ mailman-Bugs-1069319 ] Digests not sent

by SourceForge.net

Bugs item #1069319, was opened at 2004-11-19 10:34 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_… Category: mail delivery Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Tom Allen (djpeanut) Assigned to: Nobody/Anonymous (nobody) Summary: Digests not sent Initial Comment: Hi, I run a very active mailing list with digest mode enabled as the default for all members. The digest were set to send daily when not empty and did so from the 5th Oct to the 25th Oct without any problems. However, at this point the digests inexplicably stopped being sent automatically. No settings were changed. I've checked all the settings in the digest page but they are fine, and the only way I can get a digest to send is to do it manually. I am running version 2.1.5. Nearly a hundred other mailing lists are running on the machine and to my knowledge, they are all unaffected. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-26 01:44 Message: Logged In: YES user_id=67709 Then, make sure the cron(d) process is running. ---------------------------------------------------------------------- Comment By: Tom Allen (djpeanut) Date: 2004-11-21 23:30 Message: Logged In: YES user_id=701435 I have heard that this problem is actually affecting all mailing lists on the server. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-19 13:29 Message: Logged In: YES user_id=67709 Looks like one of the messages stored in lists/<listname>/digest.mbox is causing a error and stop the digest processing. If you can find the cause of error, you can edit the mbox file and issue cron/senddigest command, I think. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1069319&group_…

16 years, 3 months

[ mailman-Bugs-1064494 ] Accessing list web page - bug report

by SourceForge.net

Bugs item #1064494, was opened at 2004-11-11 14:00 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1064494&group_… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Ralphabf (mudd47) Assigned to: Nobody/Anonymous (nobody) Summary: Accessing list web page - bug report Initial Comment: Bug in Mailman version 2.1.4 Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 68, in run_main immediate=1) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py ", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 49, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 67, in __get_f 1) File "/usr/lib/python2.3/codecs.py", line 566, in open file = __builtin__.open(filename, mode, buffering) IOError: [Errno 13] Permission denied: '/var/lib/mailman/logs/error' ------------------------------------------------------ -------------------------- Python information: Variable Value sys.version 2.3.3 (#2, Feb 17 2004, 11:45:40) [GCC 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------ -------------------------- Environment variables: Variable Value SERVER_SOFTWARE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache- AdvancedExtranetServer/2.0.48 (Mandrake Linux/6.7.100mdk) Server at hyndan.gbg.abf.se Port 80 REQUEST_METHOD GET PATH_INFO /mailman SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) HTTP_CONNECTION Keep-Alive SERVER_NAME hyndan.gbg.abf.se REMOTE_ADDR 62.127.120.98 PATH_TRANSLATED /var/www/html/mailman SERVER_PORT 80 SERVER_ADDR 192.168.1.111 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/admin SERVER_ADMIN root@localhost HTTP_HOST hyndan.gbg.abf.se REQUEST_URI /mailman/admin/mailman HTTP_ACCEPT */* GATEWAY_INTERFACE CGI/1.1 REMOTE_PORT 16872 HTTP_ACCEPT_LANGUAGE sv HTTP_ACCEPT_ENCODING gzip, deflate ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-26 01:36 Message: Logged In: YES user_id=67709 It says "Permission denied: '/var/lib/mailman/logs/error'" . Check your logs directory permission by bin/check_perms and fix. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1064494&group_…

16 years, 3 months

[ mailman-Bugs-1072750 ] Error after cancel invitation

by SourceForge.net

Bugs item #1072750, was opened at 2004-11-24 20:21 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072750&group_… Category: (un)subscribing Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: schmartin (schmartin) Assigned to: Nobody/Anonymous (nobody) Summary: Error after cancel invitation Initial Comment: Bug in Mailman version 2.1.5c2 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/www/mailman/scripts/driver", line 87, in run_main main() File "/var/www/mailman/Mailman/Cgi/confirm.py", line 114, in main subscription_cancel(mlist, doc, cookie) File "/var/www/mailman/Mailman/Cgi/confirm.py", line 312, in subscription_cancel userdesc = mlist.pend_confirm(cookie)[1] File "/var/www/mailman/Mailman/Pending.py", line 141, in pend_confirm assert self.Locked() AssertionError Python information: Variable Value sys.version 2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 Environment variables: Variable Value PATH_INFO /leiterrunde CONTENT_LENGTH 116 CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://www.postfuchs.de/mailman/confirm/leiterrunde/06ca753186f732c16d5ad6b… SCRIPT_FILENAME /var/www/mailman/cgi-bin/confirm PYTHONPATH /var/www/mailman SERVER_SOFTWARE Apache/2.0.48 (RedHat 9/Server4You) SERVER_ADMIN root@localhost SCRIPT_NAME /mailman/confirm REQUEST_METHOD POST HTTP_HOST www.postfuchs.de HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING PATH_TRANSLATED /var/www/mailman/leiterrunde REQUEST_URI /mailman/confirm/leiterrunde HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.3) Gecko/20040910(248152) HTTP_CONNECTION keep-alive SERVER_NAME www.postfuchs.de REMOTE_ADDR 217.83.83.186 REMOTE_PORT 2178 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 UNIQUE_ID sv-CND5L0I0AADkk-u8AAAAG SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate SERVER_ADDR 62.75.208.141 DOCUMENT_ROOT /var/www/mailman ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-11-26 01:31 Message: Logged In: YES user_id=67709 This bug was already fixed in CVS Release_2_1-maint tree (See bug ID 981188). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1072750&group_…

16 years, 3 months

[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option

by SourceForge.net

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: Closed 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:40 Message: Logged In: YES user_id=33248 Whatever. There's obviously no point in debating it, since you think it is so terribly horrible and I don't see the problem with helping users, regardless of what "standards" would like to impose on us. So I'll try to mark this closed, and we can get on with our lives. ---------------------------------------------------------------------- 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…

16 years, 3 months

[ mailman-Feature Requests-923122 ] reply_goes_to_list allow poster+list option

by SourceForge.net

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…

16 years, 3 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders November 2004