Mailman 3 November 2007 - 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-Bugs-1834569 ] core dump when list admin is set to be the list bounce addr
by SourceForge.net Nov. 27, 2007

Nov. 27, 2007

Bugs item #1834569, was opened at 2007-11-19 15:48 Message generated for change (Settings changed) made by gjmurphy You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&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.0.x >Status: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: gjmurphy (gjmurphy) Assigned to: Nobody/Anonymous (nobody) Summary: core dump when list admin is set to be the list bounce addr Initial Comment: A list manager here decided that the list admin email address should be set to the list bounce address. Later, a message was sent to this address informing the admin that there were requests pending approval/whatever. Mailman then accepted this message and attempted to parse it as a bounce message which, obviously, failed. This failure was then send to the list administrator informing them that a bounce message could not be parsed. This was repeated until python coredumped the bounce queuerunner process. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-11-19 21:38 Message: Logged In: YES user_id=1123998 Originator: NO Fixed in Mailman 2.1.10. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&group_…

1 0

[ mailman-Bugs-1834569 ] core dump when list admin is set to be the list bounce addr
by SourceForge.net Nov. 19, 2007

Nov. 19, 2007

Bugs item #1834569, was opened at 2007-11-19 06:48 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&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.0.x Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: gjmurphy (gjmurphy) Assigned to: Nobody/Anonymous (nobody) Summary: core dump when list admin is set to be the list bounce addr Initial Comment: A list manager here decided that the list admin email address should be set to the list bounce address. Later, a message was sent to this address informing the admin that there were requests pending approval/whatever. Mailman then accepted this message and attempted to parse it as a bounce message which, obviously, failed. This failure was then send to the list administrator informing them that a bounce message could not be parsed. This was repeated until python coredumped the bounce queuerunner process. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-11-19 12:38 Message: Logged In: YES user_id=1123998 Originator: NO Fixed in Mailman 2.1.10. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&group_…

1 0

[ mailman-Bugs-1834569 ] core dump when list admin is set to be the list bounce addr
by SourceForge.net Nov. 19, 2007

Nov. 19, 2007

Bugs item #1834569, was opened at 2007-11-19 15:48 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=1834569&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.0.x Status: Open Resolution: None Priority: 5 Private: No Submitted By: gjmurphy (gjmurphy) Assigned to: Nobody/Anonymous (nobody) Summary: core dump when list admin is set to be the list bounce addr Initial Comment: A list manager here decided that the list admin email address should be set to the list bounce address. Later, a message was sent to this address informing the admin that there were requests pending approval/whatever. Mailman then accepted this message and attempted to parse it as a bounce message which, obviously, failed. This failure was then send to the list administrator informing them that a bounce message could not be parsed. This was repeated until python coredumped the bounce queuerunner process. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834569&group_…

1 0

[ mailman-Bugs-1834281 ] Wrong mailto subject/in-reply-to link in the article page
by SourceForge.net Nov. 19, 2007

Nov. 19, 2007

Bugs item #1834281, was opened at 2007-11-19 00:19 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=1834281&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: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: Wrong mailto subject/in-reply-to link in the article page Initial Comment: The Archived article page give an oppotunity to reply or to send comments with the mailto link on the poster (or the list address) with the subject and in-reply-to attributes set. But, the subject should have the 'Re:' prefix like the other messages from the user's MUA, and 'In-Reply-To' should be the message-id of the article not the in-reply-to header value of it. The patch is attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1834281&group_…

1 0

[ mailman-Patches-1220144 ] allow specifying another list in accept_these_nonmembers
by SourceForge.net Nov. 18, 2007

Nov. 18, 2007

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 Private: No 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: 2007-11-18 11:58 Message: Logged In: YES user_id=1123998 Originator: NO Patch will be in 2.1.10. ---------------------------------------------------------------------- Comment By: Charles (libertytrek) Date: 2007-11-18 10:32 Message: Logged In: YES user_id=1881071 Originator: NO Hello, I'm very interested in using this feature, but I'm not very good at adding custom patches... any chance of an update on when this will be added to the core code? Thanks, Charles ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2007-05-04 00:33 Message: Logged In: YES user_id=67709 Originator: NO Because '@' is mandatory in mailman 2.2 listname, I think that '`listname@domain`' is more preferable. Use of '`' is meaning 'evaluate this list member'. I also think we can merge this patch (along with the sibling list patch #1347962) in the next mailman 2.1.10 because release of 2.2 is delayed considerably. Thoughts ? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-12-01 12:30 Message: Logged In: YES user_id=1123998 Originator: NO The patch also applies without change to Mailman 2.1.9. ---------------------------------------------------------------------- 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

[ mailman-Patches-1220144 ] allow specifying another list in accept_these_nonmembers
by SourceForge.net Nov. 18, 2007

Nov. 18, 2007

Patches item #1220144, was opened at 2005-06-14 02:29 Message generated for change (Comment added) made by libertytrek 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 Private: No 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: Charles (libertytrek) Date: 2007-11-18 13:32 Message: Logged In: YES user_id=1881071 Originator: NO Hello, I'm very interested in using this feature, but I'm not very good at adding custom patches... any chance of an update on when this will be added to the core code? Thanks, Charles ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2007-05-04 03:33 Message: Logged In: YES user_id=67709 Originator: NO Because '@' is mandatory in mailman 2.2 listname, I think that '`listname@domain`' is more preferable. Use of '`' is meaning 'evaluate this list member'. I also think we can merge this patch (along with the sibling list patch #1347962) in the next mailman 2.1.10 because release of 2.2 is delayed considerably. Thoughts ? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-12-01 15:30 Message: Logged In: YES user_id=1123998 Originator: NO The patch also applies without change to Mailman 2.1.9. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-07-17 19: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 21: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

[ mailman-Bugs-1833527 ] Fails to send own users mail to them.
by SourceForge.net Nov. 17, 2007

Nov. 17, 2007

Bugs item #1833527, was opened at 2007-11-16 21:04 Message generated for change (Comment added) made by twcook You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&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: Closed Resolution: None Priority: 5 Private: No Submitted By: Tim Cook (twcook) Assigned to: Nobody/Anonymous (nobody) Summary: Fails to send own users mail to them. Initial Comment: In at least version 2.1.9, in at least two separate installations, I do not receive my own posts even though I ensured that the Yes option is selected. Another user on the same mailing list reported the same issue. The only similarity I can find in our email addresses are that they are both quite long. timothywayne.cook(a)gmail.com and serefarikan(a)kurumsalteknoloji.com ---------------------------------------------------------------------- >Comment By: Tim Cook (twcook) Date: 2007-11-16 22:09 Message: Logged In: YES user_id=19267 Originator: YES Thanks. Sorry I missed it in the mailing list archive. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-11-16 22:05 Message: Logged In: YES user_id=1123998 Originator: NO I don't know what the issue is with serefarikan(a)kurumsalteknoloji.com, but with timothywayne.cook(a)gmail.com, this is a gmail 'feature' that ignores the post from the list because it is a duplicate of the message in Sent Mail. This is a gmail issue and Mailman can't do anything about it. This is noted at <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.042.htp> and has been noted several times on mailman-users(a)python.org, e.g., <http://mail.python.org/pipermail/mailman-users/2005-February/042782.html>. If you can provide more information about the issue with serefarikan(a)kurumsalteknoloji.com, we can look into that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&group_…

1 0

[ mailman-Bugs-1833527 ] Fails to send own users mail to them.
by SourceForge.net Nov. 17, 2007

Nov. 17, 2007

Bugs item #1833527, was opened at 2007-11-16 21:04 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&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 Private: No Submitted By: Tim Cook (twcook) Assigned to: Nobody/Anonymous (nobody) Summary: Fails to send own users mail to them. Initial Comment: In at least version 2.1.9, in at least two separate installations, I do not receive my own posts even though I ensured that the Yes option is selected. Another user on the same mailing list reported the same issue. The only similarity I can find in our email addresses are that they are both quite long. timothywayne.cook(a)gmail.com and serefarikan(a)kurumsalteknoloji.com ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-11-16 22:05 Message: Logged In: YES user_id=1123998 Originator: NO I don't know what the issue is with serefarikan(a)kurumsalteknoloji.com, but with timothywayne.cook(a)gmail.com, this is a gmail 'feature' that ignores the post from the list because it is a duplicate of the message in Sent Mail. This is a gmail issue and Mailman can't do anything about it. This is noted at <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.042.htp> and has been noted several times on mailman-users(a)python.org, e.g., <http://mail.python.org/pipermail/mailman-users/2005-February/042782.html>. If you can provide more information about the issue with serefarikan(a)kurumsalteknoloji.com, we can look into that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&group_…

1 0

[ mailman-Bugs-1833527 ] Fails to send own users mail to them.
by SourceForge.net Nov. 17, 2007

Nov. 17, 2007

Bugs item #1833527, was opened at 2007-11-16 21:04 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=1833527&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 Private: No Submitted By: Tim Cook (twcook) Assigned to: Nobody/Anonymous (nobody) Summary: Fails to send own users mail to them. Initial Comment: In at least version 2.1.9, in at least two separate installations, I do not receive my own posts even though I ensured that the Yes option is selected. Another user on the same mailing list reported the same issue. The only similarity I can find in our email addresses are that they are both quite long. timothywayne.cook(a)gmail.com and serefarikan(a)kurumsalteknoloji.com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1833527&group_…

1 0