Mailman 3 August 2007 - Mailman-coders

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

19 Aug '22

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-1783633 ] allow add_member to offer confirmation
by SourceForge.net 28 Aug '07

28 Aug '07

Patches item #1783633, was opened at 2007-08-28 20:55 Message generated for change (Settings changed) made by novalis_dt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&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: Mailman 2.1 >Status: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: David Turner (novalis_dt) Assigned to: Nobody/Anonymous (nobody) Summary: allow add_member to offer confirmation Initial Comment: Adds a -c option to add_member to allow it to be used to subscribe members with confirmation. ---------------------------------------------------------------------- Comment By: David Turner (novalis_dt) Date: 2007-08-28 20:56 Message: Logged In: YES user_id=83137 Originator: YES Oops. This duplicates #1765041 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…

1 0

[ mailman-Patches-1783633 ] allow add_member to offer confirmation
by SourceForge.net 28 Aug '07

28 Aug '07

Patches item #1783633, was opened at 2007-08-28 20:55 Message generated for change (Comment added) made by novalis_dt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&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: Mailman 2.1 Status: Open >Resolution: Duplicate Priority: 5 Private: No Submitted By: David Turner (novalis_dt) Assigned to: Nobody/Anonymous (nobody) Summary: allow add_member to offer confirmation Initial Comment: Adds a -c option to add_member to allow it to be used to subscribe members with confirmation. ---------------------------------------------------------------------- >Comment By: David Turner (novalis_dt) Date: 2007-08-28 20:56 Message: Logged In: YES user_id=83137 Originator: YES Oops. This duplicates #1765041 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…

1 0

[ mailman-Patches-1783633 ] allow add_member to offer confirmation
by SourceForge.net 28 Aug '07

28 Aug '07

Patches item #1783633, was opened at 2007-08-28 20:55 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=1783633&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: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: David Turner (novalis_dt) Assigned to: Nobody/Anonymous (nobody) Summary: allow add_member to offer confirmation Initial Comment: Adds a -c option to add_member to allow it to be used to subscribe members with confirmation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…

1 0

[ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py
by SourceForge.net 24 Aug '07

24 Aug '07

Patches item #1776178, was opened at 2007-08-17 13:53 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&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.2 / 3.0 >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-08-24 10:07 Message: Logged In: YES user_id=1869522 Originator: YES The patches will make Mailman working but unstoppable. It looks to be a python's problem with handling signals in threads. I'm closing this ticket until the issues got solved. ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:04 Message: Logged In: YES user_id=1869522 Originator: YES I'm adding updated patch for Mailman 2.2 and a new patch for Mailman 3. I've moved the python-inotify parts in conditionals, so if inotify is not present in the system, everything should work as in the unpatched version. File Added: mailman3-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:00 Message: Logged In: YES user_id=1869522 Originator: YES File Added: mailman-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-17 14:36 Message: Logged In: YES user_id=1869522 Originator: YES Yes, you're right... I didn't realize that inotify is Linux specific. I will add a configure script option -- this should solve the Linux-only problem and make the python-inotify dependency optional. Also I will take a look at Mailman 3 and try to create a patch for it as well. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 14:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…

1 0

[ mailman-Bugs-1778960 ] Empty Bounces
by SourceForge.net 22 Aug '07

22 Aug '07

Bugs item #1778960, was opened at 2007-08-21 19:54 Message generated for change (Comment added) made by ninja_k You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&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: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Lange (ninja_k) Assigned to: Nobody/Anonymous (nobody) Summary: Empty Bounces Initial Comment: I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA. All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well. Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents. The logs show: Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a ... I'm not quite sure what is going on, but I am fairly certain that this is a bug. ---------------------------------------------------------------------- >Comment By: Nick Lange (ninja_k) Date: 2007-08-22 05:23 Message: Logged In: YES user_id=411568 Originator: YES To answer your questions (apparently I can't quote your message, my apologies) 1. No auto responders are in use. I will attempt to sanitize and post up some courier logs for you tomorrow. 2. While I haven't gone as far as to capture individual messages in transit, the attached "messages" are completely empty, yes. With consideration to one, I'll try to enable some kind of tracing on the programs as they are executed when I get into work... ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-08-21 23:46 Message: Logged In: YES user_id=1123998 Originator: NO > ... I'm not quite sure what is going on, but I am fairly certain that this > is a bug. Maybe, but not necessarily. What do your Courier logs show? It is even possible that one of your list members has a misconfigured autoresponder of some kind. In any case, Mailman is receiving this empty bounce message, and something (presumably outside Mailman) is sending it. > If I turn on Uncaught bounce > notification, the message that is forwarded has no contents. What are the headers of this message, or are there no headers either? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…

1 0

[ mailman-Bugs-1778960 ] Empty Bounces
by SourceForge.net 21 Aug '07

21 Aug '07

Bugs item #1778960, was opened at 2007-08-21 12:54 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&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: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Lange (ninja_k) Assigned to: Nobody/Anonymous (nobody) Summary: Empty Bounces Initial Comment: I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA. All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well. Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents. The logs show: Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a ... I'm not quite sure what is going on, but I am fairly certain that this is a bug. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-08-21 16:46 Message: Logged In: YES user_id=1123998 Originator: NO > ... I'm not quite sure what is going on, but I am fairly certain that this > is a bug. Maybe, but not necessarily. What do your Courier logs show? It is even possible that one of your list members has a misconfigured autoresponder of some kind. In any case, Mailman is receiving this empty bounce message, and something (presumably outside Mailman) is sending it. > If I turn on Uncaught bounce > notification, the message that is forwarded has no contents. What are the headers of this message, or are there no headers either? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…

1 0

[ mailman-Bugs-1778960 ] Empty Bounces
by SourceForge.net 21 Aug '07

21 Aug '07

Bugs item #1778960, was opened at 2007-08-21 19:54 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=1778960&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: bounce detection Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Nick Lange (ninja_k) Assigned to: Nobody/Anonymous (nobody) Summary: Empty Bounces Initial Comment: I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA. All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well. Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents. The logs show: Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a ... I'm not quite sure what is going on, but I am fairly certain that this is a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…

1 0

[ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py
by SourceForge.net 21 Aug '07

21 Aug '07

Patches item #1776178, was opened at 2007-08-17 13:53 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&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.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:04 Message: Logged In: YES user_id=1869522 Originator: YES I'm adding updated patch for Mailman 2.2 and a new patch for Mailman 3. I've moved the python-inotify parts in conditionals, so if inotify is not present in the system, everything should work as in the unpatched version. File Added: mailman3-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:00 Message: Logged In: YES user_id=1869522 Originator: YES File Added: mailman-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-17 14:36 Message: Logged In: YES user_id=1869522 Originator: YES Yes, you're right... I didn't realize that inotify is Linux specific. I will add a configure script option -- this should solve the Linux-only problem and make the python-inotify dependency optional. Also I will take a look at Mailman 3 and try to create a patch for it as well. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 14:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…

1 0

[ mailman-Patches-1776178 ] Use inotify instead of polling in Runner.py
by SourceForge.net 21 Aug '07

21 Aug '07

Patches item #1776178, was opened at 2007-08-17 13:53 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&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.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: Use inotify instead of polling in Runner.py Initial Comment: Hi, the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible. The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed. --ts ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-08-21 10:00 Message: Logged In: YES user_id=1869522 Originator: YES File Added: mailman-inotify.patch ---------------------------------------------------------------------- Comment By: Tomas Smetana (tsmetana) Date: 2007-08-17 14:36 Message: Logged In: YES user_id=1869522 Originator: YES Yes, you're right... I didn't realize that inotify is Linux specific. I will add a configure script option -- this should solve the Linux-only problem and make the python-inotify dependency optional. Also I will take a look at Mailman 3 and try to create a patch for it as well. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2007-08-17 14:16 Message: Logged In: YES user_id=12800 Originator: NO IIUC, inotify is a Linux-only thing so this would have to be optional. I haven't looked at the patch, but I would target this for Mailman 3 instead of 2.2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…

1 0