Mailman 3 April 2010 - 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

[Bug 544477] [NEW] setting localhost in postfix_lmtp breaks delivery
by Patrick Ben Koetter Sept. 26, 2020

Sept. 26, 2020

Public bug reported: Setting localhost in postfix_lmtp works against Postfix defaults and breaks delivery. Reason: The Postfix lmtp client only uses dns queries by default to search for hostnames. If the DNS server does not provide an answer for "localhost" delivery from the lmtp client to mailman fails. Solution: Provide "127.0.0.1" instead of "localhost". This does not require DNS and is even faster because it saves DNS lookups. Example: hey2(a)mailman.state-of-mind.de lmtp:[localhost.localdomain]:8024 ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 7

[Bug 514625] [NEW] Mailman 3 member functions should "guess" address membership
by Stephen Turnbull May 23, 2015

May 23, 2015

Public bug reported: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.domain.tld" is subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." ** Affects: mailman Importance: Undecided Status: New ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and - address>. [ ] Add <unknown> address as an alias for <member>." + address>. [ ] Add <unknown address> as an alias for <member>." ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against - the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is - subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same + the member database. For example, if "turnbull(a)sk.domain.tld" is + subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." -- Mailman 3 member functions should "guess" address membership https://bugs.launchpad.net/bugs/514625 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 5

[Bug 543618] [NEW] test breaks if existing mailman.cfg is found
by Patrick Ben Koetter March 24, 2015

March 24, 2015

Public bug reported: The test program reports an error if it detects an existing mailman.cfg: Failure in test test_current_working_directory (mailman.tests.test_configfile.TestConfigFileSearch) Traceback (most recent call last): File "/usr/lib/python2.6/unittest.py", line 279, in run testMethod() File "/root/mailman/src/mailman/tests/test_configfile.py", line 107, in test_current_working_directory self.assertEqual(found, config_file) File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: '/etc/mailman.cfg' != u'/tmp/tmpVfAIyB/home/alex/mailman/hacking/mailman.cfg' I believe it should not do this. It should either silently ignore the difference or use the test mailman.cfg or ... but not break. ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 518517] [NEW] Add the equivalent of postconf(1)
by Barry Warsaw April 22, 2014

April 22, 2014

Public bug reported: Postfix has a very handy command called postconf(1) which lets you dump all or one Postfix configuration variable. It would be very handy for Mailman 3 to have something similar. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Also affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged -- Add the equivalent of postconf(1) https://bugs.launchpad.net/bugs/518517 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

5 19

[Bug 500955] [NEW] Templates for AST use inconsistent DOCTYPE
by Matt Selsky June 15, 2012

June 15, 2012

Public bug reported: Most of the templates use a DOCTYPE of HTML 4.01 Transitional, but the AST templates use HTML 3.2. The patch updates the DOCTYPES for the AST templates. ** Affects: mailman Importance: Undecided Status: New -- Templates for AST use inconsistent DOCTYPE https://bugs.launchpad.net/bugs/500955 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 500952] [NEW] Extra escape characters in DOCTYPE
by Matt Selsky June 15, 2012

June 15, 2012

Public bug reported: The DOCTYPE header for 2 files in the sk templates contain extra escape characters around the quote marks. ** Affects: mailman Importance: Undecided Status: New -- Extra escape characters in DOCTYPE https://bugs.launchpad.net/bugs/500952 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 501739] [NEW] Approved: header not always removed
by Mark Sapiro Sept. 21, 2010

Sept. 21, 2010

Public bug reported: Approve follows SpamDetect in the default pipeline. If SpamDetect or another custom or reordered handler preceding Approve holds a post containing an Approve(d): header or pseudo-header, and that post is approved, the Approve(d): header or pseudo-header will not be removed from the delivered message. ** Affects: mailman Importance: Undecided Status: New -- Approved: header not always removed https://bugs.launchpad.net/bugs/501739 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 514050] [NEW] listinfo.html templates have a misplaced form start tag
by Mark Sapiro Sept. 21, 2010

Sept. 21, 2010

Public bug reported: The tag <MM-Subscribe-Form-Start> which generates the <form> tag for the subscribe form is in the <td> entry for the language form. This generates invalid HTML which is a problem for at least some browsers. There is also no DOCTYPE directive and other misplaced tags that cause validation errors. ** Affects: mailman Importance: Undecided Status: New -- listinfo.html templates have a misplaced form start tag https://bugs.launchpad.net/bugs/514050 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 566731] [NEW] there are some misspellings in Polish language templates
by Jakub Nadolny Sept. 20, 2010

Sept. 20, 2010

Public bug reported: Some files in Polish language templates for mailman 2.1 have misspellings and/or language mistakes. I attach corrected versions for 2.1.13. ** Affects: mailman Importance: Undecided Status: New -- there are some misspellings in Polish language templates https://bugs.launchpad.net/bugs/566731 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 3

[Bug 545772] [NEW] An error in Simplified Chinese translation
by LI Rui Bin Sept. 20, 2010

Sept. 20, 2010

Public bug reported: See the patches. ** Affects: mailman Importance: Undecided Status: New -- An error in Simplified Chinese translation https://bugs.launchpad.net/bugs/545772 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 5

[Bug 530654] [NEW] Active button on /cgi-bin/mailman/confirm is 'cancel'
by Stefan Ritter Sept. 20, 2010

Sept. 20, 2010

Public bug reported: Hi, when someone come to the confirm page and enter his/her email-address, the active button should be 'submit', not 'cancel'. Several people want to press the enter-key to send the data, and in this case, he/she cancel the progress. Regards, Stefan ** Affects: mailman Importance: Undecided Status: New -- Active button on /cgi-bin/mailman/confirm is 'cancel' https://bugs.launchpad.net/bugs/530654 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 2

[Bug 529100] [NEW] Initial 'emptyarchive' page can have wrong host name in listinfo page link
by Mark Sapiro Sept. 20, 2010

Sept. 20, 2010

Public bug reported: Because of the processing sequence in bin/newlist and Mailman/Cgi/create.py The initial archive index page for a new list is built with a link to the listinfo page with host name DEFAULT_URL_HOST instead of the host name supplied to newlist with -u or the host name of the create web page. ** Affects: mailman Importance: Undecided Status: New -- Initial 'emptyarchive' page can have wrong host name in listinfo page link https://bugs.launchpad.net/bugs/529100 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 2

[Bug 557750] [NEW] Mailman should honor X-Approve and X-Approved
by Barry Warsaw Sept. 20, 2010

Sept. 20, 2010

Public bug reported: >From mailman-users: It appears that while the Approved: header is standard in Usenet for posting to moderated groups, it's use for email and email lists has never been standardized (RFC 2076, Sec 3.4). Thus, your point is well taken. ** Affects: mailman Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailman/2.1 Importance: Undecided Status: Confirmed ** Affects: mailman/3.0 Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed ** Also affects: mailman/2.1 Importance: Undecided Status: New ** Also affects: mailman/3.0 Importance: Undecided Status: New ** Changed in: mailman/2.1 Status: New => Confirmed ** Changed in: mailman/3.0 Status: New => Confirmed ** Changed in: mailman/3.0 Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman/3.0 Milestone: None => 3.0.0a6 -- Mailman should honor X-Approve and X-Approved https://bugs.launchpad.net/bugs/557750 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 533468] [NEW] admindb interface applies action to not yet seen messages from user.
by Mark Sapiro Sept. 20, 2010

Sept. 20, 2010

Public bug reported: If the moderator has retrieved the admindb overview page and another message arrives and is held from a user who already has one or more held messages displayed on the page, and the moderator applies an action or the default "discard all messages marked Defer" to that user's messages, the same action will be applied to the newly arrived message even though it wasn't displayed. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: New -- admindb interface applies action to not yet seen messages from user. https://bugs.launchpad.net/bugs/533468 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 2

[Bug 526143] [NEW] List-Post header should be retained in MIME digest messages
by Mark Sapiro Sept. 20, 2010

Sept. 20, 2010

Public bug reported: The List-Post header should be retained by default in messages in the MIME format digest to facilitate 'reply list' with MUAs that have that feature. ** Affects: mailman Importance: Undecided Status: New -- List-Post header should be retained in MIME digest messages https://bugs.launchpad.net/bugs/526143 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 5

[Bug 552917] [NEW] Subscribing an already subscribed member via REST should 409
by Barry Warsaw Sept. 20, 2010

Sept. 20, 2010

Public bug reported: 409 Conflict is probably a better HTTP response code for the REST API when trying to subscribe an already subscribed member. Add some content body to explain the situation. ** Affects: mailman Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailman/3.0 Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed ** Tags: mailman3 ** Changed in: mailman Milestone: None => 3.0.0a6 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Status: New => Confirmed ** Tags added: mailman3 ** Also affects: mailman/3.0 Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed -- Subscribing an already subscribed member via REST should 409 https://bugs.launchpad.net/bugs/552917 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 4

[Bug 543627] [NEW] mailman command does not initialize directory structure on first run
by Patrick Ben Koetter Sept. 20, 2010

Sept. 20, 2010

Public bug reported: Contrary to "src/mailman/docs/START.txt" which says Run the ``bin/mailman info`` command to see which configuration file Mailman will use, and where it will put its database file. The first time you run this, Mailman will also create any necessary run-time directories and log files. neither the mailman command alone nor running it with option "info" creates the initial directory structure. If you go with the default settings in mailman.cfg you probably won't notice because you are within the correct directory structure. But if you set "var_dir: /opt/mailman" in e.g. /etc/mailman.cfg things break. I believe fixing this would also fix ticket #543620. ** Affects: mailman Importance: Undecided Status: New -- mailman command does not initialize directory structure on first run https://bugs.launchpad.net/bugs/543627 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 2

[Bug 497968] [NEW] Need a 'no-daemonize' option for '/bin/mailman start'
by Steve Burling June 19, 2010

June 19, 2010

Public bug reported: The version of Mailman distributed with Apple's Mac OS X Server has a hacked up mailmanctl, primarily to support not daemonizing in the launchd environment. (I think). Their hack is ugly, and it'd be nice if it was made unnecessary. ** Affects: mailman Importance: Undecided Status: New -- Need a 'no-daemonize' option for '/bin/mailman start' https://bugs.launchpad.net/bugs/497968 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 5

[Bug 571904] [NEW] Aggregated list with subscribers from other lists
by Josh Triplett May 12, 2010

May 12, 2010

Public bug reported: On our site (http://lists.psas.pdx.edu) we have a list (psas-team) which automatically includes the subscribers from any other PSAS mailing list (except psas-announce). This makes it easy to have a list for each team and a list for anyone on any team. We use a custom script to aggregate the subscribers regularly. Ideally we'd like native support for this in mailman instead; we'd like to create a list and say "automatically include the subscribers of the following lists as subscribers to this list". (Bonus if we can say "all lists of the form psas-* except for psas-announce".) We'd also like the ability for people to subscribe directly to psas-team, without having to subscribe to one of the other lists; currently we use a fake list psas-misc to feed people into psas- team, but this seems like a hack. ** Affects: mailman Importance: Undecided Status: New -- Aggregated list with subscribers from other lists https://bugs.launchpad.net/bugs/571904 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 571902] [NEW] Side-wide whitelist
by Josh Triplett April 29, 2010

April 29, 2010

Public bug reported: Many lists only allow subscribers to post. On these lists, people often subscribe so they can post, but disable delivery so they don't receive all the (potentially high-volume) list traffic. In general, someone who has gone to the trouble of subscribing to one list at a site often qualifies to post to any list at that site, but mailman does not make it trivial to implement such a policy. A few mailman installations have custom patches for this. I'd like to have the ability to trivially (as in "check a checkbox") implement the following policy with mailman: - Allow posting from anyone subscribed to any list on this site, or whitelisted for any list on this site. This would also, as a side effect, allow a dummy list to serve as a place to subscribe for whitelisting purposes only. (See http://lists.debian.org/whitelist/ for an example of such a list.) I can imagine that some people might want to specify a specific list for use in whitelisting, rather than any list on the site, though I personally don't care about that variation. ** Affects: mailman Importance: Undecided Status: New -- Side-wide whitelist https://bugs.launchpad.net/bugs/571902 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 266588] Re: Add SpamAssassin filter to mail pipeline
by Mark Sapiro April 17, 2010

April 17, 2010

Attached is a patch to the spamd.py in comment #17. The intent of this patch is to catch a "[Errno 104] Connection reset by peer" exception as reported at http://mail.python.org/pipermail/mailman- users/2010-April/069283.html and which apparently occurs because of a SpamAssassin timeout, and handle it as other spamd communication errors are handled so the message isn't shunted. ** Patch added: "spamd.py patch to fix shunting when SA times out." http://launchpadlibrarian.net/44642273/spamd.patch -- Add SpamAssassin filter to mail pipeline https://bugs.launchpad.net/bugs/266588 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 266588] Re: Add SpamAssassin filter to mail pipeline
by Mark Sapiro April 17, 2010

April 17, 2010

The patch in comment #19 is garbled. Here it is attached as a file. ** Patch added: "SpamAssassin.py patch" http://launchpadlibrarian.net/44641726/SpamAssassin.patch -- Add SpamAssassin filter to mail pipeline https://bugs.launchpad.net/bugs/266588 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 557991] Re: SpamAssassin handler
by Mark Sapiro April 17, 2010

April 17, 2010

See https://bugs.launchpad.net/mailman/+bug/266588 which is the LP incarnation of SF patch 534577. That item has more up to date and complete code than this one. -- SpamAssassin handler https://bugs.launchpad.net/bugs/557991 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 266588] Re: Add SpamAssassin filter to mail pipeline
by Mark Sapiro April 17, 2010

April 17, 2010

It's not a bug, it's a patch, and it's still relevant. ** Changed in: mailman Status: Invalid => Confirmed -- Add SpamAssassin filter to mail pipeline https://bugs.launchpad.net/bugs/266588 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0