Mailman-coders July 2006

mailman-coders@python.org

1 participants
24 discussions

[ mailman-Patches-1532081 ] with long lists, findmember option got forgotten

by SourceForge.net

Patches item #1532081, was opened at 2006-08-01 01:04 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=1532081&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 UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: RISKO Gergely (errge) Assigned to: Nobody/Anonymous (nobody) Summary: with long lists, findmember option got forgotten Initial Comment: After the admin do a filtering on members, the generated first letter based URLs don't inherit the filter regex. This patch fixes that bug. Reported in debian as #359721. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1532081&group_…

14 years, 10 months

[ mailman-Feature Requests-403066 ] Auto Approval of subscriptions for certain domains

by SourceForge.net

Feature Requests item #403066, was opened at 2001-01-01 09:27 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_i… 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: Closed Resolution: Accepted Priority: 3 Submitted By: Mark Tearle (mtearle) Assigned to: Mark Sapiro (msapiro) Summary: Auto Approval of subscriptions for certain domains Initial Comment: A patch to enable automatic approval for certain domains, eg people in the example.com are automatically approved all others have to wait for the moderator ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-07-31 18:13 Message: Logged In: YES user_id=3142 New feature request for this patch, seeking feedback. Most of my lists automatically moderate new subscribers, in addition some require admin approval for subsciption, except for domains listed in subscribe_auto_approval. A nice addition to this patch would be to not moderate subscribers whose domains are listed in subscribe_auto_approval. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2006-03-25 22:21 Message: Logged In: YES user_id=1312539 This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2006-03-12 22:12 Message: Logged In: YES user_id=3142 I've successfully applied this against a v2.1.8 system and it works well. Thanks!! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-03-11 13:36 Message: Logged In: YES user_id=1123998 The attached patch is against a 2.1.8a1 installed base (installed because it patches Defaults.py and not Defaults.py.in). It is a modification and extension of the original patch. It implements a new list attribute 'subscribe_auto_approval' which is a list of email addresses and regular expressions matching email addresses whose subscriptions are exempt from admin approval. It implements the original intent if one just uses regexps that match domains. This will go in Mailman 2.2, but it would be nice to get some feedback from people who are interested in this feature and are willing to try the patch. ---------------------------------------------------------------------- Comment By: Thomas Wouters (twouters) Date: 2003-03-11 08:31 Message: Logged In: YES user_id=34209 Is this still necessary with Mailman 2.1, which has more 'automatic' options (as well as 'memberadaptors') ? In any case, the patch is likely heavily out of date by now, I'm moving this to Feature Requests for now. Feel free to respond if you (still) have a need. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_i…

14 years, 10 months

[ mailman-Bugs-1531675 ] ARCHIVE_TO_MBOX=1 broken

by SourceForge.net

Bugs item #1531675, was opened at 2006-07-31 11:23 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=1531675&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: configuring/installing Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ross Golder (rossigee) Assigned to: Nobody/Anonymous (nobody) Summary: ARCHIVE_TO_MBOX=1 broken Initial Comment: While looking into an archiving problem on mail.gnome.org, where we use our own external archiver (ARCHIVE_TO_MBOX was set to 1), Owen Taylor discovered the following bug causing it to ignore this setting: >From /usr/lib/mailman/Mailman/Defaults.py: # ARCHIVE_TO_MBOX #-1 - do not do any archiving # 0 - do not archive to mbox, use builtin mailman html archiving only # 1 - archive to mbox to use an external archiving mechanism only # 2 - archive to both mbox and builtin mailman html archiving - # use this to make both external archiving mechanism work and # mailman's builtin html archiving. the flat mail file can be # useful for searching, external archivers, etc. ARCHIVE_TO_MBOX = 2 Now, while that's not particularly clear, I can certainly see why one might assume that we wanted a setting, of '1', but if you look at the code we see: if mm_cfg.ARCHIVE_TO_MBOX in (1, 2): self.__archive_to_mbox(msg) if mm_cfg.ARCHIVE_TO_MBOX == 1: # Archive to mbox only. return txt = str(msg) # should we use the internal or external archiver? [...] So, ARCHIVE_TO_MBOX=1 skips both the internal *and* external archivers, and archives only to the MBOX files. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1531675&group_…

14 years, 10 months

[ mailman-Feature Requests-1530164 ] Accept senders from another list(s)

by SourceForge.net

Feature Requests item #1530164, was opened at 2006-07-27 23:47 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1530164&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 Submitted By: Paul Williamson (kb5mu) Assigned to: Nobody/Anonymous (nobody) Summary: Accept senders from another list(s) Initial Comment: I'd like to specify that List A is to accept postings from List B and List C. Example: List A is an open discussion group, and List B is a senior manager's group. The managers might not subscribe to the discussion (for lack of time) but they need to be able to post announcements. Indirect reference to another list would be better than the existing facility to add individual addresses to the approved list. When a manager comes or goes or changes email address, his access to List A would automatically follow his status on List B, without administrator action. Indirect reference to another list is better than asking the managers to subscribe to List A but disable mail delivery, because they won't remember to update their List A subscriptions. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-07-28 08:22 Message: Logged In: YES user_id=1123998 See patch 1220144 at https://sourceforge.net/tracker/index.php?func=detail&aid=1220144&group_id=… I think this does what you want. It is a candidate for inclusion in Mailman 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1530164&group_…

14 years, 10 months

[ mailman-Feature Requests-1530164 ] Accept senders from another list(s)

by SourceForge.net

Feature Requests item #1530164, was opened at 2006-07-27 23:47 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=1530164&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 Submitted By: Paul Williamson (kb5mu) Assigned to: Nobody/Anonymous (nobody) Summary: Accept senders from another list(s) Initial Comment: I'd like to specify that List A is to accept postings from List B and List C. Example: List A is an open discussion group, and List B is a senior manager's group. The managers might not subscribe to the discussion (for lack of time) but they need to be able to post announcements. Indirect reference to another list would be better than the existing facility to add individual addresses to the approved list. When a manager comes or goes or changes email address, his access to List A would automatically follow his status on List B, without administrator action. Indirect reference to another list is better than asking the managers to subscribe to List A but disable mail delivery, because they won't remember to update their List A subscriptions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1530164&group_…

14 years, 10 months

[ mailman-Feature Requests-1527758 ] Send rejection text to moderated messages

by SourceForge.net

Feature Requests item #1527758, was opened at 2006-07-24 09:25 Message generated for change (Comment added) made by derekrprice You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1527758&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 Submitted By: Derek Robert Price (derekrprice) Assigned to: Nobody/Anonymous (nobody) Summary: Send rejection text to moderated messages Initial Comment: Per this report http://savannah.gnu.org/support/?func=detailitem&item_id=105465 , it would be nice if a default rejection text could be sent to moderated messages. For instance, most posters to CVS's commit email list are held for moderation, and I would like them to be sent the following notice when the moderator rejects their postings: This list is intended to receive automated commit messages from the CVS repository and is therefore otherwise read-only. Please send user discussion, including help requests, to info-cvs(a)gnu.org and development discussion, including bug reports and patch submissions, to bug-cvs(a)gnu.org. Unfortunately, there does not appear to be an easy way to do this via the list setup. I would be just as happy if the a default "held for moderation" message could be set. Both would be especially nice. ---------------------------------------------------------------------- >Comment By: Derek Robert Price (derekrprice) Date: 2006-07-24 09:32 Message: Logged In: YES user_id=793288 Incidentally, as noted by Sylvain Beucler in the linked savannah.gnu.org support incident, there is already a comment in Handlers/Moderate.py to the effect that the held for moderation message should be configurable. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1527758&group_…

14 years, 10 months

[ mailman-Feature Requests-1527758 ] Send rejection text to moderated messages

by SourceForge.net

Feature Requests item #1527758, was opened at 2006-07-24 09:25 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=1527758&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 Submitted By: Derek Robert Price (derekrprice) Assigned to: Nobody/Anonymous (nobody) Summary: Send rejection text to moderated messages Initial Comment: Per this report http://savannah.gnu.org/support/?func=detailitem&item_id=105465 , it would be nice if a default rejection text could be sent to moderated messages. For instance, most posters to CVS's commit email list are held for moderation, and I would like them to be sent the following notice when the moderator rejects their postings: This list is intended to receive automated commit messages from the CVS repository and is therefore otherwise read-only. Please send user discussion, including help requests, to info-cvs(a)gnu.org and development discussion, including bug reports and patch submissions, to bug-cvs(a)gnu.org. Unfortunately, there does not appear to be an easy way to do this via the list setup. I would be just as happy if the a default "held for moderation" message could be set. Both would be especially nice. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1527758&group_…

14 years, 10 months

[ mailman-Patches-1527537 ] prevent and log subscription spamflood (2.1.8)

by SourceForge.net

Patches item #1527537, was opened at 2006-07-24 11:06 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=1527537&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: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Paul Wise (pabs3) Assigned to: Nobody/Anonymous (nobody) Summary: prevent and log subscription spamflood (2.1.8) Initial Comment: The attached patch for mailman 2.1.8 causes mailman to ignore subscriptions that already exist in pending.pck and request.pck. This prevents people from mass-spamming either the list admin or random email addresses (depending on the configuration of the list). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1527537&group_…

14 years, 10 months

[ mailman-Patches-1220144 ] allow specifying another list in accept_these_nonmembers

by SourceForge.net

Patches item #1220144, was opened at 2005-06-13 23:29 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&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: list administration Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 6 Submitted By: Jim Tittsler (jtittsler) Assigned to: Tokio Kikuchi (tkikuchi) Summary: allow specifying another list in accept_these_nonmembers Initial Comment: Add the capability to logically include the addresses all of the members of another list in the same Mailman installation to accept_these_nonmembers. '@listname' checks the poster's address against the membership of listname. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-07-17 16:09 Message: Logged In: YES user_id=1123998 The 2.1.6 patch also applies without change to Mailman 2.1.7 and 2.1.8. Even though there are minor changes in the patched modules, the patched line numbers and the patch data are unchanged. ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-17 18:37 Message: Logged In: YES user_id=67709 Marking as an Mailman 2.2 new feature candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&group_…

14 years, 11 months

[ mailman-Bugs-1469962 ] Attachments with ' just hang

by SourceForge.net

Bugs item #1469962, was opened at 2006-04-13 10:36 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1469962&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: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: cpkevin (xprt5) Assigned to: Nobody/Anonymous (nobody) Summary: Attachments with ' just hang Initial Comment: If someone sends an email with the character ' in the subject or attachment name mailman hangs. after deleting the ' in the attachment name in /usr/local/cpanel/3rdparty/mailman/lists/list_name/digest.mbox the next message is delivered (but this message isn't delivered!) Apr 11 23:04:22 2006 (60899) Uncaught runner exception: need more than 2 values to unpack This was working fine before a recent upgrade with mailman/python and still works fine on other servers. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-07-16 20:28 Message: Logged In: YES user_id=1123998 The thing I missed in trying to duplicate is the fact that the exception is thrown in decode_rfc2231(). Thus, the problem only occurs with a RFC2231 encoded header, i.e., one with a long filename split into pieces as filename*0="first part of name containing ' character" filename*1="second part of name - etc." The underlying problem is in the Python email library in email/Utils.py. See http://mail.python.org/pipermail/email-sig/2006-July/000293.html for a more complete description and a potential fix. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-04-14 10:39 Message: Logged In: YES user_id=1123998 I am unable to duplicate this error with various versions of Python's email library. I am using an attachment with the header Content-Disposition: attachment; filename="cal'dar.doc" If the one that fails in your case is different from this in any significant way, please post it. ---------------------------------------------------------------------- Comment By: cpkevin (xprt5) Date: 2006-04-14 06:07 Message: Logged In: YES user_id=1501592 Here is the latest traceback Apr 11 23:04:22 2006 (60899) Uncaught runner exception: need more than 2 values to unpack Apr 11 23:04:22 2006 (60899) Traceback (most recent call last): File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/ToDigest.py", line 315, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/Scrubber.py", line 299, in process url = save_attachment(mlist, part, dir) File "/usr/local/cpanel/3rdparty/mailman/Mailman/Handlers/Scrubber.py", line 411, in save_attachment filename = Utils.oneline(msg.get_filename(''), lcset) File "/usr/local/cpanel/3rdparty/mailman/pythonlib/email/Message.py", line 724, in get_filename filename = self.get_param('filename', missing, 'content-disposition') File "/usr/local/cpanel/3rdparty/mailman/pythonlib/email/Message.py", line 607, in get_param for k, v in self._get_params_preserve(failobj, header): File "/usr/local/cpanel/3rdparty/mailman/pythonlib/email/Message.py", line 554, in _get_params_preserve params = Utils.decode_params(params) File "/usr/local/cpanel/3rdparty/mailman/pythonlib/email/Utils.py", line 337, in decode_params charset, language, value = decode_rfc2231(EMPTYSTRING.join(value)) File "/usr/local/cpanel/3rdparty/mailman/pythonlib/email/Utils.py", line 284, in decode_rfc2231 charset, language, s = parts ValueError: need more than 2 values to unpack Apr 11 23:04:22 2006 (60899) SHUNTING: 1144789462.1552839+7ff91a627d48daa19efc8509d86eb3ec869fc909 ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-04-13 20:34 Message: Logged In: YES user_id=1123998 I'm not sure if this is a 2.1.6 bug or a cPanel bug, but it seems to be fine in 2.1.7 since I have now received copies of this bug report, its two updates, the 149967 report and its update (a total of 5 messages) from the mailman-coders(a)python.org Mailman 2.1.7 list, and they all have subject [ mailman-Bugs-1469962 ] Attachments with ' just hang (or the same with 1469967). I.e., the same messages you receive directly from sourceforge.net are also posted to mailman-coders(a)python.org. In any case, if you want to post the full traceback from the error, either here or directly to me, I will try to determine the problem and suggest a fix for 2.1.6. ---------------------------------------------------------------------- Comment By: cpkevin (xprt5) Date: 2006-04-13 19:22 Message: Logged In: YES user_id=1501592 Mailman version is 2.1.6 ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-04-13 18:36 Message: Logged In: YES user_id=1123998 What Mailman/Python version is this? Also see http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1469962&group_…

14 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders July 2006