Mailman-coders January 2004

mailman-coders@python.org

1 participants
74 discussions

[ mailman-Bugs-872733 ] Changing topics_bodylines_limit value undefines topics
by SourceForge.net 08 Jan '04

08 Jan '04

Bugs item #872733, was opened at 2004-01-07 18:14 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=872733&group_i… Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Peter Smith (peters) Assigned to: Nobody/Anonymous (nobody) Summary: Changing topics_bodylines_limit value undefines topics Initial Comment: If you change the value for "topics_bodylines_limit" at the "Mailing list Configuration Help topics_bodylines_limit Option" screen and then click "Submit", the defined topics will be reset. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=872733&group_i…

1 0

[ mailman-Patches-872068 ] Decorate.py patch
by SourceForge.net 07 Jan '04

07 Jan '04

Patches item #872068, was opened at 2004-01-07 00:46 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=872068&group_i… Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 7 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Decorate.py patch Initial Comment: Here is a patch which was defered and not included in 2.1.4 for Decorate.py. This fixes most of the footer-in-the-attachment problem by 1. convert header, body and footer into unicode 2. then concatnate them 3. try encode with the list charset 4. if fail, encode with the message charset 5. if both attempts fail, make the footer attachment. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=872068&group_i…

1 0

[ mailman-Bugs-871830 ] Small logging error in "subscribe" log
by SourceForge.net 06 Jan '04

06 Jan '04

Bugs item #871830, was opened at 2004-01-06 18:32 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=871830&group_i… Category: None Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Stig Sandbeck Mathisen (shub-internet) Assigned to: Nobody/Anonymous (nobody) Summary: Small logging error in "subscribe" log Initial Comment: Looks like there is a small logging error in the "subscribe" logging. The log lines look like this: Jan 06 18:31:52 2004 (9728) online-driftsmeldinger-ost: pending Stig Sandbeck Mathisen <ssm(a)fnord.no> 148.122.46.12 Jan 06 18:32:15 2004 (3682) online-driftsmeldinger-ost: new "ssm(a)fnord.no" <Stig Sandbeck Mathisen>, via email confirmation On the second line, the name and the address should change place, address should be inside <>. and name inside "" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871830&group_i…

1 0

[ mailman-Patches-630339 ] create list with multiple owners
by SourceForge.net 06 Jan '04

06 Jan '04

Patches item #630339, was opened at 2002-10-29 18:03 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_i… Category: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 3 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: create list with multiple owners Initial Comment: Create list with multiple list owners, by 'create' CGI script and 'newlist' command line script. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2004-01-06 16:28 Message: Logged In: YES user_id=529503 Update for 2.1.4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_i…

1 0

[ mailman-Patches-818601 ] "Announcement-only" (read only) list
by SourceForge.net 06 Jan '04

06 Jan '04

Patches item #818601, was opened at 2003-10-06 22:07 Message generated for change (Comment added) made by hatukanezumi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_i… Category: Web UI Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: "Announcement-only" (read only) list Initial Comment: Documents say that Mailman "supports a wide range of mailing list types, such as general discussion lists and announce-only lists". It's exactly true. But some people wish really "announcement-only" feature. By `Announcement-only' feature: o Posting by e-mail is not allowed at all. All messages to posting address are forwarded to owners and no other users won't receive it. o Web interface is provided so that only specified users ("posters") can post messages to list. For example for `mail magazine' publishers, `announcement-only' list is safer (Oooops! I've approved the SPAM!) and let them be free from moderation tasks. Changes on codes: o New CGI script `post'. o New handler `Posttop' which switches messages bound to list to owners (only on annnouncement-only list). o New `announcement_only' configuration directive. o Some modifications of templates. Notice: By now this is buggie (both in Python and English). Comments and Fixes are welcome. ---------------------------------------------------------------------- >Comment By: Hatuka*nezumi (hatukanezumi) Date: 2004-01-06 16:20 Message: Logged In: YES user_id=529503 Update for 2.1.4. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-29 19:39 Message: Logged In: YES user_id=529503 rel.1.0. o Confusing "announcement-only" has been changed to "read-only". o New admin category. ---------------------------------------------------------------------- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-10-09 23:51 Message: Logged In: YES user_id=529503 rel.0.2. * Posttop handler now placed after Hold handler so that spam discarding and auto-response are capable. * Global pipelone processing are ommitted when: -------------------------------------- SpamDetect : [A] and [W] Approve : [W] ReplyBot : [W] Moderate : [A] Hold : - administrivia : [A] - too many recips : [A] - implicit dest. : [A] - suspicious headers : [A] and not [W] - message size : [A] and not [W] - news moderation : [A] and not [W] Posttop : (if [A], may be switched to owner pipeline.) AvoidDuplicates : [A] ------------------------------ [A]: list is announcement-only. [W]: message is posted from Web (by `poster'). * Additional modification to templates. * Some admin option categories are hidden. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=818601&group_i…

1 0

[ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership
by SourceForge.net 05 Jan '04

05 Jan '04

Patches item #871062, was opened at 2004-01-05 12:09 Message generated for change (Comment added) made by fubarobfusco You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- >Comment By: K. A. Krueger (fubarobfusco) Date: 2004-01-05 12:18 Message: Logged In: YES user_id=944208 Er. SF ate the indentation on my "extend.py" example in the patch description. All of the lines after "def extend(list):" are meant to be indented once. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i…

1 0

[ mailman-Patches-871062 ] A MemberAdaptor for LDAP-based membership
by SourceForge.net 05 Jan '04

05 Jan '04

Patches item #871062, was opened at 2004-01-05 12:09 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=871062&group_i… Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: K. A. Krueger (fubarobfusco) Assigned to: Nobody/Anonymous (nobody) Summary: A MemberAdaptor for LDAP-based membership Initial Comment: This is a module, LDAPMemberships, which extends MemberAdaptor to support membership lists based on a search in an enterprise LDAP directory. With this module, you can make mailing lists which, rather than having a list of member addresses stored in the list, query your LDAP server for member addresses whenever necessary. For instance, if you wish to have a mailing list of all the Vice Presidents in your company, you can express this as an LDAP search: "(title=Vice President*)" and create a mailing list which performs this search and delivers mail to the resulting user accounts when a message is sent to it. This way, rather than manually adding new Vice Presidents to the mailing list, you can simply have Human Resources update the LDAP records, and the change will immediately take effect for the mailing list. Mailman lists with LDAP-based membership can still have moderators, list policies, and the other usual features of Mailman lists. There are a few missing features; notably: 1. There is no bounce processing. 2. There are no per-user preferences. 3. The Web interface still allows you to try setting user preferences, but if you do you will get a stack thrown at you. (Only the "readable" interface of MemberAdaptor is implemented.) 4. The LDAP settings of a list (e.g. LDAP server and search string) are only administrable by editing its "extend.py" file, not over the Web. 5. There is no digest mode. To use this module, you must have the "ldap" Python module installed (aka "python-ldap"). Then just put LDAPMemberships.py in the "Mailman" directory (~mailman/Mailman), create a new list, and write an "extend.py" file in the list directory like so: ##### from Mailman.LDAPMemberships import LDAPMemberships def extend(list): ldap = LDAPMemberships(list) ldap.ldapsearch = "(title=Vice President*)" # members search string ldap.ldapserver = "ldap.example.net" # your enterprise LDAP server ldap.ldapbasedn = "dc=Example dc=net" # your LDAP base DN ldap.ldapbinddn = '' # a bind DN which can read people's 'mail' field ldap.ldappasswd = '' # the password for the bind DN list._memberadaptor = ldap ##### This module has been tested at my site and is in production on a Mailman 2.1.2 installation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=871062&group_i…

1 0

[ mailman-Bugs-871050 ] Uncought runner exception: Empty module name
by SourceForge.net 05 Jan '04

05 Jan '04

Bugs item #871050, was opened at 2004-01-05 11:03 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=871050&group_i… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Fernando Barajas (fbarajas) Assigned to: Nobody/Anonymous (nobody) Summary: Uncought runner exception: Empty module name Initial Comment: Hi! I run several lists on mailman, and all of the lists are working OK, but suddently one of them (named fc_general) stopped working, and I get the following in logs/error every time I try to post to the fc_general list: Jan 05 11:03:48 2004 (8451) Uncaught runner exception: Empty module name Jan 05 11:03:48 2004 (8451) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 89, in process send_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 130, in send_digests send_i18n_digests(mlist, mboxfp) File "/home/mailman/Mailman/Handlers/ToDigest.py", line 303, in send_i18n_dige sts msg = scrubber(mlist, msg) File "/home/mailman/Mailman/Handlers/Scrubber.py", line 308, in process t = t.encode(charset, 'replace') File "/var/tmp/python2-2.2.3- root/usr/lib/python2.2/encodings/__init__.py", li ne 51, in search_function ValueError: Empty module name Jan 05 11:03:48 2004 (8451) SHUNTING: 1073322225.130398+2e61b88872c9af343bce1927 de7443b7500f2622 The rest of my lists work correctly. I was using 2.1.2, but today I upgraded to 2.1.4 and it's still failing. What can I do? Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&group_i…

1 0

[ mailman-Bugs-726736 ] qrunner hung by spam
by SourceForge.net 04 Jan '04

04 Jan '04

Bugs item #726736, was opened at 2003-04-24 08:01 Message generated for change (Comment added) made by lindahl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- Comment By: Greg Lindahl (lindahl) Date: 2004-01-04 22:37 Message: Logged In: YES user_id=57593 It's not the reporter's place to close a bug report -- thanks for the fix, but the Mailman owners have to close the bug. I'm afraid that the mailman community doesn't spend much time keeping their sourceforge bug list clean. I've given a couple of other people the fix, it's an extremely common situation today. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-01-04 15:54 Message: Logged In: YES user_id=113859 Greg, maybe you should close the bug in addition to send another email to the mailman lists to ask for an 2.0.14 release. An alternative would be to make a patch release, this bug certainly is critical for 2.0.x. On the other hand it most likely does not affect 2.1.x. ---------------------------------------------------------------------- Comment By: Greg Lindahl (greglindahl) Date: 2003-08-06 00:13 Message: Logged In: YES user_id=612574 Thanks -- I see that you fixed all of them in your patch. This should be added to the 2.0.X series. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 17:41 Message: Logged In: YES user_id=113859 I've submitted a patch for this to the patch tracker 783651 https://sourceforge.net/tracker/index.php?func=detail&aid=783651&group_id=1… ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 17:32 Message: Logged In: YES user_id=113859 I also encountered that bug once at a site of a friend. Take a look at Mailman/Bouncers/Postfix.py and especially the line with boundary = msg.getparam('boundary') this can result in boundary being "None" which is then not treated properly. So add the following check below this with the correct indentation: if not boundary: return None If I remember correctly this was handled completely differently in Mailman 2.1 so I believe that this bug is limited to Mailman 2.0.x. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_i…

1 0

[ mailman-Bugs-726736 ] qrunner hung by spam
by SourceForge.net 04 Jan '04

04 Jan '04

Bugs item #726736, was opened at 2003-04-24 10:01 Message generated for change (Comment added) made by ber You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_i… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 8 Submitted By: Greg Lindahl (greglindahl) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner hung by spam Initial Comment: I realized no mail had gone out for 6 days, and saw that qrunner was barfing on SOMETHING. This is with Mailman 2.0.6. Even though I'm behind the times, I'd bet this bug could be in 2.1.X -- I just don't know enough Python to see what's going on. I blew away a bunch of files in my qfiles directory; I didn't save the bad message. Apr 24 00:39:01 2003 qrunner(2397): Traceback (innermost last): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 282, in ? Apr 24 00:39:01 2003 qrunner(2397): kids = main(lock) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 252, in main Apr 24 00:39:01 2003 qrunner(2397): keepqueued = dispose_message(mlist, msg, msgdata) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/cron/qrunner", line 121, in dispose_message Apr 24 00:39:01 2003 qrunner(2397): if BouncerAPI.ScanMessages(mlist, mimemsg): Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages Apr 24 00:39:01 2003 qrunner(2397): addrs = func(msg) Apr 24 00:39:01 2003 qrunner(2397): File "/home/mailman/Mailman/Bouncers/Postfix.py", line 39, in process Apr 24 00:39:01 2003 qrunner(2397): more = mfile.next() Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 121, in next Apr 24 00:39:01 2003 qrunner(2397): while self.readline(): pass Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 93, in readline Apr 24 00:39:01 2003 qrunner(2397): if marker == self.section_divider(sep): Apr 24 00:39:01 2003 qrunner(2397): File "/usr/lib/python1.5/multifile.py", line 157, in section_divider Apr 24 00:39:01 2003 qrunner(2397): return "--" + str Apr 24 00:39:01 2003 qrunner(2397): TypeError : illegal argument type for built-in operation ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2004-01-04 16:54 Message: Logged In: YES user_id=113859 Greg, maybe you should close the bug in addition to send another email to the mailman lists to ask for an 2.0.14 release. An alternative would be to make a patch release, this bug certainly is critical for 2.0.x. On the other hand it most likely does not affect 2.1.x. ---------------------------------------------------------------------- Comment By: Greg Lindahl (greglindahl) Date: 2003-08-06 02:13 Message: Logged In: YES user_id=612574 Thanks -- I see that you fixed all of them in your patch. This should be added to the 2.0.X series. ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:41 Message: Logged In: YES user_id=113859 I've submitted a patch for this to the patch tracker 783651 https://sourceforge.net/tracker/index.php?func=detail&aid=783651&group_id=1… ---------------------------------------------------------------------- Comment By: Bernhard Reiter (ber) Date: 2003-08-05 19:32 Message: Logged In: YES user_id=113859 I also encountered that bug once at a site of a friend. Take a look at Mailman/Bouncers/Postfix.py and especially the line with boundary = msg.getparam('boundary') this can result in boundary being "None" which is then not treated properly. So add the following check below this with the correct indentation: if not boundary: return None If I remember correctly this was handled completely differently in Mailman 2.1 so I believe that this bug is limited to Mailman 2.0.x. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=726736&group_i…

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders January 2004