Mailman 3 February 2003 - Mailman-coders

[ mailman-Patches-687704 ] use external style sheet config option
by SourceForge.net Feb. 17, 2003

Feb. 17, 2003

Patches item #687704, was opened at 2003-02-17 02:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_i… Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None >Priority: 3 Submitted By: Magnus Stenman (snugge) Assigned to: Nobody/Anonymous (nobody) Summary: use external style sheet config option Initial Comment: Adds an optional stylesheet config option to Defaults.py, and adds the place holders for it into the english templates and the cgis. The style sheet is in a separate file, making per site customization less messy when the templates get modified by Mailman developers. Sample style sheet using verdana/arial in 9pt is included. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_i…

1 0

[ mailman-Patches-687704 ] use external style sheet config option
by SourceForge.net Feb. 17, 2003

Feb. 17, 2003

Patches item #687704, was opened at 2003-02-17 02:05 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_i… Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Magnus Stenman (snugge) Assigned to: Nobody/Anonymous (nobody) Summary: use external style sheet config option Initial Comment: Adds an optional stylesheet config option to Defaults.py, and adds the place holders for it into the english templates and the cgis. The style sheet is in a separate file, making per site customization less messy when the templates get modified by Mailman developers. Sample style sheet using verdana/arial in 9pt is included. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=687704&group_i…

1 0

[ mailman-Bugs-672649 ] canonstr -> unicode usernames
by SourceForge.net Feb. 15, 2003

Feb. 15, 2003

Bugs item #672649, was opened at 2003-01-22 19:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_i… Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Donn Cave (donnc) Assigned to: Nobody/Anonymous (nobody) Summary: canonstr -> unicode usernames Initial Comment: Cgi.subscribe.process_form gets a unicode value for fullname, from Utils.canonstr() (return unicode(newstr, charset, 'replace') This came to my attention because it broke OwnerNotification when the email Message couldn't "flatten" itself with the unicode payload. Suspect that's only the beginning of the trouble that will be caused, so I'm hoping we really don't want unicode usernames values as a rule. I fixed it in subscribe.py with fullname = fullname.encode('iso8859-1'), but note that canonstr is used elsewhere like this. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:37 Message: Logged In: YES user_id=67709 If your users choose to input latin-1 charcters in fullname, it will be better to set iso-8859-1as english charset. in mm_cfg.py, def _(s): return s LC_DESCRIPTIONS['en'] = (_('English (USA)'), 'iso-8859-1') del _ ---------------------------------------------------------------------- Comment By: Pat Carr (pcarr) Date: 2003-02-13 04:05 Message: Logged In: YES user_id=710070 I stumbled over the same bug, but in my case it was bailing only in the confirm.py script. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=672649&group_i…

1 0

[ mailman-Bugs-683833 ] Traceback on checkdbs
by SourceForge.net Feb. 15, 2003

Feb. 15, 2003

Bugs item #683833, was opened at 2003-02-10 09:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_i… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None >Priority: 6 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:21 Message: Logged In: YES user_id=67709 increment priority because someone else asked this bug. until merged into CVS. ;-) ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 10:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_i…

1 0

[ mailman-Patches-685788 ] fix for Cc: to cc: weirdness
by SourceForge.net Feb. 15, 2003

Feb. 15, 2003

Patches item #685788, was opened at 2003-02-13 07:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_i… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None >Priority: 6 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix for Cc: to cc: weirdness Initial Comment: http://mail.python.org/pipermail/mailman-users/2003-February/026353.html describe the problem. It is caused by Mailman/Handlers/AvoidDuplicates.py ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-15 11:17 Message: Logged In: YES user_id=67709 I will be incrementing priority every time I point this patch. ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_i…

1 0

[ mailman-Patches-601117 ] add sequencial number in subject prefix
by SourceForge.net Feb. 14, 2003

Feb. 14, 2003

Patches item #601117, was opened at 2002-08-28 05:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_i… Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-14 11:33 Message: Logged In: YES user_id=67709 Hi, I am pleased you like this patch. Here is my current version attached. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_i…

1 0

[ mailman-Patches-601117 ] add sequencial number in subject prefix
by SourceForge.net Feb. 14, 2003

Feb. 14, 2003

Patches item #601117, was opened at 2002-08-28 05:07 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_i… Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: add sequencial number in subject prefix Initial Comment: This patch for 'CookHeaders.py' add an ability to add a sequencial number in the subject prefix. You can define a subject prefix like: [listname %d] Then, the subject line of delivered mail becomes: Subject: [listname 123] Hoge hoge When someone replied this mail, mailman receives a messages with: Subject: Re: [listname 123] Hoge hoge Then, this patch removes [listname \d+] part and deliver it with: Subject: [listname 124] Re: Hoge hoge And next, another person replies with Subject: Re: [listname 124] Re: Hoge hoge Then, (magically!) you get: Subject: [listname 125] Re: Hoge hoge Not with Re: Re: Hoge hoge. Looks like complicated but this patch has been working well with Japanese-enhanced Mailman for more than a year. Without %d, this patch works like current version, I believe. ---------------------------------------------------------------------- Comment By: Fabio Rossetti (fabiorossetti) Date: 2003-02-14 10:02 Message: Logged In: YES user_id=693899 If you need a quick fix to make the patch work with 2.1.1 here's my take (it's the diff file adapted to work with 2.1.1 CookHeaders.py) 17a18 > (sequence version) 221c222,223 < prefix = mlist.subject_prefix --- > prefix = mlist.subject_prefix.strip(); > if not prefix: return 237,243c239,250 < if prefix and subject: < pattern = re.escape(prefix.strip()) < for decodedsubj, charset in headerbits: < if re.search(pattern, decodedsubj, re.IGNORECASE): < # The subject's already got the prefix, so don't change it < return < del msg['subject'] --- > headerstring = '' > fws = '' > cset = None > for (s, c) in headerbits: > headerstring += fws + s > if c == None or c == 'us-ascii': > fws = ' ' > cset = Utils.GetCharSet(mlist.preferred_language) > else: > fws = '' > cset = c > # Note: searching prefix in subject is REMOVED. (seq version) 245a253,275 > else: > subject = headerstring > # If the subject_prefix contains '%d', it is replaced with the > # mailing list sequential number. Also, if the prefix is closed with > # [],(), or {}, the prefix in the responding post subject will be cared. > # sequential number format allows '%05d' like pattern. > p = re.compile('%\d*d') > if p.search(prefix,1): > # prefix have number, so we should search prefix w/number > # in subject. > prefix_pattern = p.sub(r'\s*\d+\s*', prefix) > else: > prefix_pattern = prefix > prefix_pattern = re.sub('([\[\(\{])', '\\\g<1>', prefix_pattern) > subject = re.sub(prefix_pattern, '', subject) > subject = re.compile('(RE:\s*)+', re.I).sub('Re: ', subject, 1) > # and substitute %d in prefix with post_id > try: > prefix = prefix % mlist.post_id > except: > pass > # Note that trailing space was stripped in seq version (TK) > prefix += ' ' 248,262c278,288 < for s, c in headerbits: < # Once again, convert the string to unicode. < if c is None: < c = Charset('iso-8859-1') < if not isinstance(c, Charset): < c = Charset(c) < if not _isunicode(s): < codec = c.input_codec or 'ascii' < try: < s = unicode(s, codec, 'replace') < except LookupError: < # Unknown codec, is this default reasonable? < s = unicode(s, Utils.GetCharSet (mlist.preferred_language), < 'replace') < h.append(s, c) --- > # in seq version, subject header is already concatnated > if not _isunicode(subject): > try: > subject = unicode(subject, cset, 'replace') > except LookupError: > # unknown codec > cset = Utils.GetCharSet(mlist.preferred_language) > subject = unicode(subject, cset, 'replace') > subject = subject.encode(cset) > h.append(subject, cset) > del msg['subject'] ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-12-20 04:31 Message: Logged In: YES user_id=67709 update for 2.1b6+ ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:59 Message: Logged In: YES user_id=67709 I have uploaded the patch with the same name as the old one. Please download the upper one because it's newer. Sorry for the inconvenience. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2002-10-31 05:53 Message: Logged In: YES user_id=67709 Patch ID 625482 (i18n List-Id) and this was merged for 2.1b4+ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_i…

1 0

[ mailman-Bugs-683833 ] Traceback on checkdbs
by SourceForge.net Feb. 13, 2003

Feb. 13, 2003

Bugs item #683833, was opened at 2003-02-10 09:48 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_i… Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback on checkdbs Initial Comment: The checkdbs script of mailman 2.1.1 quits with a traceback: [mailman@styx cron]$ ./checkdbs Traceback (most recent call last): File "./checkdbs", line 136, in ? main() File "./checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "./checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) I tried reverting to mailman 2.1, and everything works fine now. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-02-13 10:25 Message: Logged In: YES user_id=67709 Here is a patch. Please try and feedback. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=683833&group_i…

1 0

[ mailman-Patches-685788 ] fix for Cc: to cc: weirdness
by SourceForge.net Feb. 13, 2003

Feb. 13, 2003

Patches item #685788, was opened at 2003-02-13 07:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_i… >Category: mail delivery >Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix for Cc: to cc: weirdness Initial Comment: http://mail.python.org/pipermail/mailman-users/2003-February/026353.html describe the problem. It is caused by Mailman/Handlers/AvoidDuplicates.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_i…

1 0

[ mailman-Patches-685788 ] fix for Cc: to cc: weirdness
by SourceForge.net Feb. 13, 2003

Feb. 13, 2003

Patches item #685788, was opened at 2003-02-13 07:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_i… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix for Cc: to cc: weirdness Initial Comment: http://mail.python.org/pipermail/mailman-users/2003-February/026353.html describe the problem. It is caused by Mailman/Handlers/AvoidDuplicates.py ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=685788&group_i…

1 0