Mailman 3 February 2008 - Mailman-coders

[ mailman-Feature Requests-1104433 ] Configurable per-user/per-subscription subject prefix
by SourceForge.net Feb. 19, 2008

Feb. 19, 2008

Feature Requests item #1104433, was opened at 2005-01-18 04:44 Message generated for change (Comment added) made by scratchmonkey You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 3 Private: No Submitted By: Ross Golder (rossigee) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable per-user/per-subscription subject prefix Initial Comment: I've had a request from a list member who would like us to add a subject prefix to all the lists on our server (mail.gnome.org), as his mail client can't do any kind of automatic filtering. We are obviously reluctant to change the status quo, as many people (e.g. PDA/mobile users) would then respond asking us to remove them. Instead, I decided to file this feature request to make it (per-subscription) configurable. It would have one of three possible values; use the default list setting, override on or override off. This would allow users to please themselves, and in some cases overcome problems caused by limitations in their mailclient. ---------------------------------------------------------------------- Comment By: Kenneth Porter (scratchmonkey) Date: 2008-02-19 21:43 Message: Logged In: YES user_id=29401 Originator: NO It looks like the default subject prefix mangling happens in the main pipeline after the message is accepted, in CookHeaders. Per-user processing (like VERP) appears to be done in the queue runners. I guess OutputRunner would need to be the one to do this, and would need to break up the recipient list into groups based on what per-recipient munging needs to be done. ---------------------------------------------------------------------- Comment By: Kenneth Porter (scratchmonkey) Date: 2008-02-19 16:03 Message: Logged In: YES user_id=29401 Originator: NO Nothing seems to have happened with this in the last 3 years. I just saw this conflict come up again on the Subversion mailing list, and it seems to come up regularly on any list that has the prefixes disabled (my personal preference). Before I start looking at the code, are there any design constraints that argue against implementing this, or implementing it in a particular way? ---------------------------------------------------------------------- Comment By: Ross Golder (rossigee) Date: 2005-01-19 00:43 Message: Logged In: YES user_id=20872 Some lists use prefixes, some don't. Some users that subscribe to many lists want consistency, but we don't want to have to determine and enforce a site-wide policy and deal with all the ensuing arguments. This feature shifts the decision from the list/site managers to the individuals users. Basic headache prevention. The main argument for prefixes seems to be 'I can quickly identify what the mail is about in my inbox', where users haven't got or don't use their client's header filtering features. The main argument against prefixes seems to be 'I just get a screenful of list prefixes when I try to view my list folders', where users are trying to use mail clients in a low screen resolution (e.g. old VGA screen, palm/PDA device, mobile phone, small desktop window whatever). Sorry for misfiling it. Haven't used SF for a while - forgot that feature requests and bugs aren't mixed like in bugzilla. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-18 18:45 Message: Logged In: YES user_id=67709 This should be submitted as Feature Request. BTW, many mailing list users are happy with subject prefixes. Why not GNOME users? ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_…

1 0

[ mailman-Feature Requests-1104433 ] Configurable per-user/per-subscription subject prefix
by SourceForge.net Feb. 19, 2008

Feb. 19, 2008

Feature Requests item #1104433, was opened at 2005-01-18 04:44 Message generated for change (Comment added) made by scratchmonkey You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 3 Private: No Submitted By: Ross Golder (rossigee) Assigned to: Nobody/Anonymous (nobody) Summary: Configurable per-user/per-subscription subject prefix Initial Comment: I've had a request from a list member who would like us to add a subject prefix to all the lists on our server (mail.gnome.org), as his mail client can't do any kind of automatic filtering. We are obviously reluctant to change the status quo, as many people (e.g. PDA/mobile users) would then respond asking us to remove them. Instead, I decided to file this feature request to make it (per-subscription) configurable. It would have one of three possible values; use the default list setting, override on or override off. This would allow users to please themselves, and in some cases overcome problems caused by limitations in their mailclient. ---------------------------------------------------------------------- Comment By: Kenneth Porter (scratchmonkey) Date: 2008-02-19 16:03 Message: Logged In: YES user_id=29401 Originator: NO Nothing seems to have happened with this in the last 3 years. I just saw this conflict come up again on the Subversion mailing list, and it seems to come up regularly on any list that has the prefixes disabled (my personal preference). Before I start looking at the code, are there any design constraints that argue against implementing this, or implementing it in a particular way? ---------------------------------------------------------------------- Comment By: Ross Golder (rossigee) Date: 2005-01-19 00:43 Message: Logged In: YES user_id=20872 Some lists use prefixes, some don't. Some users that subscribe to many lists want consistency, but we don't want to have to determine and enforce a site-wide policy and deal with all the ensuing arguments. This feature shifts the decision from the list/site managers to the individuals users. Basic headache prevention. The main argument for prefixes seems to be 'I can quickly identify what the mail is about in my inbox', where users haven't got or don't use their client's header filtering features. The main argument against prefixes seems to be 'I just get a screenful of list prefixes when I try to view my list folders', where users are trying to use mail clients in a low screen resolution (e.g. old VGA screen, palm/PDA device, mobile phone, small desktop window whatever). Sorry for misfiling it. Haven't used SF for a while - forgot that feature requests and bugs aren't mixed like in bugzilla. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-01-18 18:45 Message: Logged In: YES user_id=67709 This should be submitted as Feature Request. BTW, many mailing list users are happy with subject prefixes. Why not GNOME users? ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1104433&group_…

1 0

[ mailman-Bugs-1186819 ] Bug with non-ascii characters during subscribe
by SourceForge.net Feb. 15, 2008

Feb. 15, 2008

Bugs item #1186819, was opened at 2005-04-20 09:59 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1186819&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 (stable) Status: Open >Resolution: Works For Me Priority: 5 Private: No Submitted By: Aaron (appleaaron) Assigned to: Nobody/Anonymous (nobody) Summary: Bug with non-ascii characters during subscribe Initial Comment: We have users from all over the world that access our mailing lists. Recently we have found an error with users that include their full name if it includes non-ascii characters such as � � and �. Here is the traceback: Traceback (most recent call last): File "/Volumes/ngs/app/listsp/mailman/scripts/driver", line 87, in run_main main() File "/Volumes/ngs/app/listsp/mailman/Mailman/Cgi/ subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/Volumes/ngs/app/listsp/mailman/Mailman/Cgi/ subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/Volumes/ngs/app/listsp/mailman/Mailman/MailList.py", line 887, in AddMember self.internal_name(), who, by) File "/Volumes/ngs/app/listsp/mailman/Mailman/Logging/ Syslog.py", line 40, in write self.write_ex(kind, msg, args, kws) File "/Volumes/ngs/app/listsp/mailman/Mailman/Logging/ Syslog.py", line 58, in write_ex logf.write(msg + '\n') File "/Volumes/ngs/app/listsp/mailman/Mailman/Logging/ StampedLogger.py", line 73, in write Logger.write(self, "%s %s" % (prefix, msg)) File "/Volumes/ngs/app/listsp/mailman/Mailman/Logging/ Logger.py", line 91, in write f.write(msg) UnicodeEncodeError: 'ascii' codec can't encode character '\ue6' in position 51: ordinal not in range(128) Python information: Variable Value sys.version 2.3 (#1, Sep 13 2003, 00:49:11) [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] sys.executable /usr/bin/python sys.prefix /System/Library/Frameworks/Python.framework/ Versions/2.3 sys.exec_prefix /System/Library/Frameworks/ Python.framework/Versions/2.3 sys.path /System/Library/Frameworks/Python.framework/ Versions/2.3 sys.platform darwin ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2008-02-15 10:51 Message: Logged In: YES user_id=1123998 Originator: NO I am unable to duplicate this in recent Mailman. This may be another manifestation of the problem at <http://sourceforge.net/tracker/index.php?func=detail&aid=1235567&group_id=1…> which was fixed in Mailman 2.1.7. If anyone is still seeing this error, can you provide more specifics such as the list's preferred language and the subscriber's preferred language. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1186819&group_…

1 0

[ mailman-Bugs-1893463 ] senddigests: Message instance has no attribute 'get_type'
by SourceForge.net Feb. 14, 2008

Feb. 14, 2008

Bugs item #1893463, was opened at 2008-02-14 11:33 Message generated for change (Comment added) made by gzp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1893463&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 beta >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Gabor Z. Papp (gzp) Assigned to: Nobody/Anonymous (nobody) Summary: senddigests: Message instance has no attribute 'get_type' Initial Comment: Python 2.5.1 mailman 2.1.10b3 compiled everyting from source on Linux. Seems like mailman working fine, except sending out digests. Running senddigest from the cron dir generates the fillowing error and the mbox file left unprocessed: List: moricz: problem processing /var/spool/mailman/lists/moricz/digest.mbox: Message instance has no attribute 'get_type' ---------------------------------------------------------------------- >Comment By: Gabor Z. Papp (gzp) Date: 2008-02-14 14:04 Message: Logged In: YES user_id=59218 Originator: YES Manually compiling and using email-2.5.8 from misc/ in $PREFIX/mailman/pythonlib/ solved the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1893463&group_…

1 0

[ mailman-Bugs-1893463 ] senddigests: Message instance has no attribute 'get_type'
by SourceForge.net Feb. 14, 2008

Feb. 14, 2008

Bugs item #1893463, was opened at 2008-02-14 11:33 Message generated for change (Settings changed) made by gzp You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1893463&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: Gabor Z. Papp (gzp) Assigned to: Nobody/Anonymous (nobody) >Summary: senddigests: Message instance has no attribute 'get_type' Initial Comment: Python 2.5.1 mailman 2.1.10b3 compiled everyting from source on Linux. Seems like mailman working fine, except sending out digests. Running senddigest from the cron dir generates the fillowing error and the mbox file left unprocessed: List: moricz: problem processing /var/spool/mailman/lists/moricz/digest.mbox: Message instance has no attribute 'get_type' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1893463&group_…

1 0

[ mailman-Bugs-1893463 ] senddigest: Message instance has no attribute 'get_type'
by SourceForge.net Feb. 14, 2008

Feb. 14, 2008

Bugs item #1893463, was opened at 2008-02-14 11:33 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=1893463&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: Gabor Z. Papp (gzp) Assigned to: Nobody/Anonymous (nobody) Summary: senddigest: Message instance has no attribute 'get_type' Initial Comment: Python 2.5.1 mailman 2.1.10b3 compiled everyting from source on Linux. Seems like mailman working fine, except sending out digests. Running senddigest from the cron dir generates the fillowing error and the mbox file left unprocessed: List: moricz: problem processing /var/spool/mailman/lists/moricz/digest.mbox: Message instance has no attribute 'get_type' ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1893463&group_…

1 0

[ mailman-Patches-1892861 ] Galician Translation attached
by SourceForge.net Feb. 13, 2008

Feb. 13, 2008

Patches item #1892861, was opened at 2008-02-13 17:21 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=1892861&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: fjrial (fjrial) Assigned to: Nobody/Anonymous (nobody) Summary: Galician Translation attached Initial Comment: Hi: My name is Frco. Javier Rial Rodríguez, galician coordinator of OpenOffice.org and several Mozilla products and IT at Mancomun.org I registered some time ago to translate mailman into galician... and after too much time here it's attached the translation. It's nearly 100% translated... Thanks for this greate software ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1892861&group_…

1 0

[ mailman-Bugs-1879338 ] catch invalid URLs
by SourceForge.net Feb. 5, 2008

Feb. 5, 2008

Bugs item #1879338, was opened at 2008-01-25 08:00 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1879338&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: catch invalid URLs Initial Comment: One finds one can use URLs like http://lists.example.org/admin.cgi/zzz-example.org/zzz/add/vvv/dddd and still visit the administration pages as if one typed in a correct URL. Somewhere in Mailman, something is not checking the URL beyond a certain length or segment. You might say "so what?", but if you allow these to work, soon all kinds of people's typos will end up in documents as being the URL to use to do various tasks, just because they happened to work that day. (Yes, the above example does not bypass password checks.) ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-02-05 23:20 Message: Logged In: YES user_id=1971011 Originator: YES http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.057.htp is an example of a evil looseness. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1879338&group_…

1 0

[ mailman-Bugs-1874279 ] Mass Subscriptions names
by SourceForge.net Feb. 4, 2008

Feb. 4, 2008

Bugs item #1874279, was opened at 2008-01-18 09:33 Message generated for change (Comment added) made by jidanni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Web/CGI Group: 2.1 alpha Status: Open Resolution: None Priority: 5 Private: No Submitted By: jidanni (jidanni) Assigned to: Nobody/Anonymous (nobody) Summary: Mass Subscriptions names Initial Comment: Today we look at members/add, Mass Subscriptions. Please change "Enter one address per line below..." to "Enter Bob Clodsworth <blob(a)example.com> or just blob(a)example.com, one per line:" Else no one can guess how to get names in. P.S., with site language = English, don't dream of entering and UTF-8 or &# 31309 ; stuff. You'll get an error. ASCII is assumed, dangnabit! ---------------------------------------------------------------------- >Comment By: jidanni (jidanni) Date: 2008-02-05 07:40 Message: Logged In: YES user_id=1971011 Originator: YES Yes it's on http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.044.htp but that's no excuse not to mention it on the page itself. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-23 04:36 Message: Logged In: YES user_id=1971011 Originator: YES Holy moly, on the Mass Subscriptions page, if you leave the notify administrator box checked, it _really does_ send one notification for EACH subscriber! Subscribe 50 people, and the administrator gets 50 EMAILs about it, not just one email with the results about all 50 names. Who knows what pleasure is in store on the mass delete page. You have my permission to split this off into a separate bug. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-23 04:29 Message: Logged In: YES user_id=1971011 Originator: YES By the way, on the mass subscription page, if one puts addresses both in the entry box, and in the contents of the file to be read in, one ends up with at least one garbled address... do warn or catch or say on the page that it's OK to use both, then process correctly. I did not test the mass deletions page. ---------------------------------------------------------------------- Comment By: jidanni (jidanni) Date: 2008-01-19 14:56 Message: Logged In: YES user_id=1971011 Originator: YES And even with site language zh_TW, on the mass subscription results page one sees UTF-8 becomes: * 積丹尼 <jidanni(a)jidanni.org> though apparently internally it is still UTF-8 at evidenced on other pages. P.S., the zh_TW 'send me my passwd' email sends raw % mess: 我們歡迎任何問題或建議 ! 請 email 給 %(adminaddr)s. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1874279&group_…

1 0

[ mailman-Patches-1879680 ] Danish translation update for 2.1.10b
by SourceForge.net Feb. 4, 2008

Feb. 4, 2008

Patches item #1879680, was opened at 2008-01-25 15:40 Message generated for change (Settings changed) made by tgc99 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1879680&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: internationalization Group: Mailman 2.1 >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Tom G. Christensen (tgc99) Assigned to: Nobody/Anonymous (nobody) Summary: Danish translation update for 2.1.10b Initial Comment: Here's an update for the danish translation. The work was done against the 2.1 maintenance branch and the diff created with bzr diff -p1 -r1034. ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2008-01-26 17:49 Message: Logged In: YES user_id=1159458 Originator: YES No it is not. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2008-01-25 16:17 Message: Logged In: YES user_id=12800 Originator: NO Is the branch publicly available? I'd like to see if I can bzr merge it! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1879680&group_…

1 0