Mailman 3 July 2006 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Aug. 19, 2022

Aug. 19, 2022

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[ mailman-Patches-1532081 ] with long lists, findmember option got forgotten
by SourceForge.net July 31, 2006

July 31, 2006

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_…

1 0

[ mailman-Feature Requests-403066 ] Auto Approval of subscriptions for certain domains
by SourceForge.net July 31, 2006

July 31, 2006

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…

1 0

[ mailman-Bugs-1531675 ] ARCHIVE_TO_MBOX=1 broken
by SourceForge.net July 31, 2006

July 31, 2006

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_…

1 0

[ mailman-Feature Requests-1530164 ] Accept senders from another list(s)
by SourceForge.net July 28, 2006

July 28, 2006

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_…

1 0

[ mailman-Feature Requests-1530164 ] Accept senders from another list(s)
by SourceForge.net July 27, 2006

July 27, 2006

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_…

1 0

[ mailman-Feature Requests-1527758 ] Send rejection text to moderated messages
by SourceForge.net July 24, 2006

July 24, 2006

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_…

1 0

[ mailman-Feature Requests-1527758 ] Send rejection text to moderated messages
by SourceForge.net July 24, 2006

July 24, 2006

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_…

1 0

[ mailman-Patches-1527537 ] prevent and log subscription spamflood (2.1.8)
by SourceForge.net July 23, 2006

July 23, 2006

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_…

1 0

[ mailman-Patches-1220144 ] allow specifying another list in accept_these_nonmembers
by SourceForge.net July 17, 2006

July 17, 2006

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_…

1 0