Mailman 3 May 2011 - 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. 27, 2020

Sept. 27, 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 701558] [NEW] Content filtering leaves a single sub-part in a multipart message.
by Mark Sapiro June 9, 2017

June 9, 2017

Public bug reported: If the original message is multipart but not multipart/alternative and content filtering removes all but one part, the message is left as a multipart message with only the one sub-part instead of being recast as just the sub-part. This can cause msg_header and/or msg_footer to be added as separate parts to a text/plain message instead of being added to the text/plain body part. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Milestone: None => 2.1.15 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Description changed: - If the original message in multipart but not multipart/alternative and + If the original message is multipart but not multipart/alternative and content filtering removes all but one part, the message is left as a multipart message with only the one sub-part instead of being recast as just the sub-part. This can cause msg_header and/or msg_footer to be added as separate - parts to a text/plain message instead if being added to the text/plain + parts to a text/plain message instead of being added to the text/plain body part. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/701558 Title: Content filtering leaves a single sub-part in a multipart message.

3 7

[Bug 576675] [NEW] Content filtering fails to collapse alternatives.
by Mark Sapiro June 9, 2017

June 9, 2017

Public bug reported: Collapsing multipart/alternative parts to just the first alternative only works if the message itself is multipart/alternative, or the multipart/alternative part is at the first sub-level. For example, given this structure: multipart/mixed | multipart/related | | multipart/alternative | | | text/plain | | | text/html | | image/jpeg | application/msword The multipart/alternative part will not be collapsed. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- Content filtering fails to collapse alternatives. https://bugs.launchpad.net/bugs/576675 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 7

[Bug 757062] [NEW] Content filtering can remove the headers from a message/rfc822 part.
by Mark Sapiro June 9, 2017

June 9, 2017

Public bug reported: If Content filtering accepts both message/rfc822 and multipart/alternative MIME parts, and a message/rfc822 part contains a message whose content type is multipart/alternative and collapse_alternatives is Yes, the headers of the message in the message/rfc822 part will be lost. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/757062 Title: Content filtering can remove the headers from a message/rfc822 part.

3 12

[Bug 775294] [NEW] Set lifetime for input forms
by Tokio Kikuchi Sept. 5, 2016

Sept. 5, 2016

*** This bug is a security vulnerability *** Private security bug reported: We may have to set lifetime for input forms because of recent activities on cross-site request forgery (CSRF). The form lifetime is successfully deployed in frameworks like web.py or plone etc. Proposed branch lp:~tkikuchi/mailman/form-lifetime implement lifetime in admin, admindb, options and edithtml interfaces. Other forms like create and rmlist have confirmation by password thus are safe regarding CSRF. The form generation time is set by a hidden parameter whose value is calculated following the mailman cookie algorithm. The default lifetime is set 1 hour in Default.py thus configurable by a site administrator. If a password is set in request, authorization cookie is discarded so the password authentication is forced. Wget tricks to manage list in FAQ can be used as they are now. ** Affects: mailman Importance: Undecided Status: New ** Branch linked: lp:~tkikuchi/mailman/form-lifetime -- You received this bug notification because you are a member of Mailman Coders, which is a direct subscriber. https://bugs.launchpad.net/bugs/775294 Title: Set lifetime for input forms

2 5

[Bug 707295] [NEW] Membership Management Better Search Function
by arky May 23, 2015

May 23, 2015

Public bug reported: In Mailman Membership Management, I would like to option to filter search results by status viz (hide,nomail [reason], ack, not metoo, nodupes, digest, plain) ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/707295 Title: Membership Management Better Search Function

4 3

[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 674352] [NEW] List Moderator Login should check for username
by arky March 12, 2014

March 12, 2014

Public bug reported: List Moderator logins currently prompt for list moderator password only. It would be good idea if prompt for username/password login as well. Mailman: 2.1.9 ** Affects: mailman Importance: Undecided Status: New -- List Moderator Login should check for username https://bugs.launchpad.net/bugs/674352 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 3

[Bug 725498] [NEW] expose message-id to templates
by Thijs Kinkhorst Aug. 5, 2013

Aug. 5, 2013

Public bug reported: As reported by Adrian von Bidder to Debian: Please consider this trivial patch, which exposees message-ids to the templates used for the email archive. See it in action on lists.debian.ch. (I don't think my modification to the templates should be in, but having te message-id exposed would mean I won't have to remember to patch mailman on every update...) (AFAICT mailman adds a Message-Id when an incoming email doesn't have one, so this should never be a problem.) ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman (Debian) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/725498 Title: expose message-id to templates

4 7

[Bug 693134] [NEW] Uncaught bounce from Dovecot when Quota Exceeded
by JorSol June 20, 2013

June 20, 2013

Public bug reported: I have a Debian 5 (Lenny) server with Postfix - Dovecot and Mailman 2.1.11 and 1700+ users. The problem is when Dovecot returns the bounce message about "Quota exceeded", Mailman don't recognize the format: Your message to <user(a)domain.com> was automatically rejected: Quota exceeded It's suposed that Mailman recognize this type of message using the VERP feature, I have "recipient_delimiter = +" in Postfix but Mailman don't detect message coming from Dovecot. /var/log/mailman/bounce: Dec 21 10:58:08 2010 (3214) listnews: bounce message w/no discernable addresses: <dovecot-1292944464-47721-0@mail> Dec 21 10:58:08 2010 (3214) noticias: forwarding unrecognized, message-id: <dovecot-1292944464-47721-0@mail> ** Affects: mailman Importance: Undecided Status: New ** Tags: dovecot mailman postfix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded

4 13

[Bug 736849] [NEW] Sender header change to improve Outlook
by Joseph Brennan Aug. 31, 2012

Aug. 31, 2012

Public bug reported: FAQ 2.3 describes problems with Outlook's ugly display of Sender "on behalf of" From, giving the example as "From listname- bounces(a)mailman.server.com On behalf of fred(a)poster.domain.com". But Outlook prefers to show the real name and hide the Internet address, when a real name is present. Most commonly the From would be "From: Fred Example <fred(a)poster.domain.com>" and as a result Outlook would display "From listname-bounces(a)mailman.server.com On behalf of Fred Example". If Mailman wrote the Sender header with a real name Outlook would show the name there too. For example, if the list name (local part) were inserted, thus "Sender: listname <listname-bounces(a)mailman.server.com>", then Outlook would display "From listname on behalf of Fred Example" which is much better in appearance and still complies with using a Sender header. RFC 2822 allows Sender to contain a real name. sender = "Sender:" mailbox CRLF mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/736849 Title: Sender header change to improve Outlook

3 7

[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 770581] [NEW] The list admin or moderator password can be compromised by sending in an Approved: header
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: If posting to a list is secured by requiring an Approved: or X-Approved: header for a post to be accepted without moderation, the list admin or moderator password can be compromised by sending it in the headers of an email message. There should be a 'poster' password for this purpose only so the consequences of compromise would be less severe. ** Affects: mailman Importance: Wishlist Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/770581 Title: The list admin or moderator password can be compromised by sending in an Approved: header

1 2

[Bug 637652] [NEW] mailman should respect LDFLAGS
by Hanno Böck June 15, 2012

June 15, 2012

Public bug reported: mailman Makefile should respect the LDFLAGS variable. See attached patch. ** Affects: mailman Importance: Undecided Status: New -- mailman should respect LDFLAGS https://bugs.launchpad.net/bugs/637652 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 761232] [NEW] Warnings when setting a list with digest members digestable=No or with non-digest members nondigestable=No do not identify affected members.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: It would be good to identify the affected members in the warning. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/761232 Title: Warnings when setting a list with digest members digestable=No or with non-digest members nondigestable=No do not identify affected members.

1 2

[Bug 745432] [NEW] Email address with leading or trailing space is not accepted by web subscribe.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: If an address is entered on the web listinfo subscribe form with a leading or trailing space, it is rejected with the message "The email address you supplied is not valid. (E.g. it must contain an '@'.)". This is confusing to the user who looks at the address and sees it does contain an '@' and appears valid. Leading and trailing whitespace should be stripped from the address entry. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/745432 Title: Email address with leading or trailing space is not accepted by web subscribe.

1 2

[Bug 739524] [NEW] Administrivia 'who' matches too much
by Joseph Brennan June 15, 2012

June 15, 2012

Public bug reported: Mailman/Utils.py has: 'who': (0, 2), This matches subject and start-of-line with many ordinary-language sentences or headings like 'who are you?' or 'Who is affected:'. I suggest dialing it back to (0, 1) which would have far fewer false positives, or even (0, 0) as it once was. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/739524 Title: Administrivia 'who' matches too much

2 4

[Bug 721015] [NEW] Typo in cron/gate_news usage() definition.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The usage function defined in cron/gate_news defines its first argument as 'status' but then refers to it as 'code'. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/721015 Title: Typo in cron/gate_news usage() definition.

1 1

[Bug 705715] [NEW] @listname entries in *_these_nonmembers are case sensitive.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The listname in @listname entries in *_these_nonmembers should be lower- cased before attempting to instantiate the list. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/705715 Title: @listname entries in *_these_nonmembers are case sensitive.

1 3

[Bug 700528] [NEW] bin/rmlist does not remove the heldmsg-LISTNAME-* files for the list.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: bin/rmlist LISTNAME should remove any data/heldmsg-LISTNAME-* files. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: Triaged ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Milestone: None => 2.1.15 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/700528 Title: bin/rmlist does not remove the heldmsg-LISTNAME-* files for the list.

1 2

[Bug 697161] [NEW] Bug in mm-handler-2.1.10 regarding lists named xxx-admin
by Sebastian Hagedorn June 15, 2012

June 15, 2012

Public bug reported: We're running Mailman 2.1.14 and have recently begun using mm- handler-2.1.10 from the contrib directory as MTA for sendmail. Everything appeared to work fine, but after a few months we were alerted by one of our users that no mail was delivered anymore to one of his lists. The list's name is mathematica-admin. It turns out that mm- handler strips the -admin part and tries to deliver the mail to a list named mathematica, which does not exist. We had a small number of other lists with the same problem. I've created a patch that fixes it and another small issue (a variable is passed to a subroutine, but a global variable is actually used there). ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/697161 Title: Bug in mm-handler-2.1.10 regarding lists named xxx-admin

2 3

[Bug 666181] [NEW] wrong From field in subscription notification to admin
by Ilya Belyy June 15, 2012

June 15, 2012

Public bug reported: Steps to reproduce: Create two mail lists ml01 (hosted on domain dom.1) and ml02 (hosted on domain dom.2) Add user to ml01 $ add_members -a y -r - ml01 lkjhlkhlkh(a)wefqwefqwef.com Subscribed: lkjhlkhlkh(a)wefqwefqwef.com Notification email to the admin of ml01 will look as following: Subject: Ml01 subscription notification From: mailman(a)dom.2 To: mladmin00(a)dom.1 Message-ID: <mailman.1.1287993063.7501.ml01(a)dom.1> Date: Mon, 25 Oct 2010 14:51:03 +0700 Subscribed: lkjhlkhlkh(a)wefqwefqwef.com Apparently, host name of the mail list is not considered when composing the notification message. I've checked 2.1.9 and 2.1.14 - both have the same bug ** Affects: mailman Importance: Undecided Status: New -- wrong From field in subscription notification to admin https://bugs.launchpad.net/bugs/666181 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 3

[Bug 787790] [NEW] Scrubber can return raw message body for multipart message
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: If ARCHIVE_HTML_SANITIZER = 2 in mm_cfg.py, messages which are multipart after content filtering will appear as the raw (undecoded) message body in the plain format digest and in the archive. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/787790 Title: Scrubber can return raw message body for multipart message

2 6

[Bug 779751] [NEW] admindb fail to find message charset
by Tokio Kikuchi June 15, 2012

June 15, 2012

Public bug reported: admindb.py displays held message excerpt but fails to get proper message charset, leading unreadable text excerpts especially for languages using multi-byte code. Attached patch solves this problem by finding the first charset in multipart message, which is used in Decorate.py etc. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/779751 Title: admindb fail to find message charset

2 6

[Bug 774588] [NEW] recent change in Utils.websafe() breaks Japanese (and other double-byte language) texts
by Tokio Kikuchi June 15, 2012

June 15, 2012

Public bug reported: Utils.websafe() escapes characters like < and >. Recent change in this function added 8bit characters like \xbc and \xbe as 'dangerous' characters. This breaks Japanese text display because they appear as a part of double-byte characters. Because these characters are only 'dangerous' for old browsers, I suggest reverting the change or at least making configurable whether the site administrator apply changes or not. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/774588 Title: recent change in Utils.websafe() breaks Japanese (and other double- byte language) texts

2 3

[Bug 770377] [NEW] Mailman should set the 'secure' cookie flag when accessed via https
by Ward Vandewege June 15, 2012

June 15, 2012

Public bug reported: When accessed over https, Mailman should set the 'secure' cookie flag. Please see the attached patch which implements that. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/770377 Title: Mailman should set the 'secure' cookie flag when accessed via https

2 3

[Bug 769318] [NEW] admindb should have 'logout' function
by Tokio Kikuchi June 15, 2012

June 15, 2012

*** This bug is a security vulnerability *** Private security bug reported: Current 2.1 admindb interface have no link (or button) to logout the administrator/moderator. An administrator can logout from mailman from admin interface but a moderator cannot logout without zapping the moderator cookie by browser's function (if it is provided) or terminating the browser. The admindb web page should have a convenient 'logout' link. Another inconvenience in admin logout funciton is that if the site-wide admin is allowed by mm_cfg.ALLOW_SITE_ADMIN_COOKIES then the administrator cannot logout with visiting the 'Logout' link in the admin page. These bugs are fixed by lp:~tkikuchi/mailman/logout-enforcement and the branch was requested to merge into 2.1 series. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is a direct subscriber. https://bugs.launchpad.net/bugs/769318 Title: admindb should have 'logout' function

2 2

[Bug 702516] [NEW] RFC 2047 encoded From: header is not correctly parsed.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: If a real name or comment in a From: or other sender header is RFC 2047 encoded and the decoding contains an unquoted comma or other special, the Message methods get_sender() and get_senders() can return bogus addresses leading to other issues. A patch is attached. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/702516 Title: RFC 2047 encoded From: header is not correctly parsed.

2 4

[Bug 677115] [NEW] Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded.
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: A list moderator receives a held message notification and attempts to approve the message by replying to the third part (second attachment) and including an Approved: <password> line as the first line of the reply. If the moderator's MUA base64 encodes the reply for i18n or other reasons, the Approved: line is not found and the message is discarded. ** Affects: mailman Importance: Undecided Status: New -- Reply to to part 3 of a held message notification containing a Approved: first body line fails if reply is base64 encoded. https://bugs.launchpad.net/bugs/677115 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 670988] [NEW] Missing format character in Spanish translation
by Mark Sapiro June 15, 2012

June 15, 2012

Public bug reported: The Spanish (es) translation of the bin/check_perms message "%(path)s bad group (has: %(groupname)s, expected %(MAILMAN_GROUP)s)" is missing the 's' in '%(path)s'. This prevents check_perms from reporting/fixing group errors and any other problems not found before the first group error. ** Affects: mailman Importance: Undecided Status: New -- Missing format character in Spanish translation https://bugs.launchpad.net/bugs/670988 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 2

[Bug 778088] [NEW] User can set a password with trailing whitespace which prevents login.
by Mark Sapiro May 19, 2012

May 19, 2012

Public bug reported: Both the subscribe CGI and the user options CGI allow setting a password with trailing whitespace, but options login strips the trailing whitespace before validating. Thus, the user can't log in to the options page. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/778088 Title: User can set a password with trailing whitespace which prevents login.

1 1

[Bug 714424] [NEW] Held message user notification should be from -owner, not -bounces
by Mark Sapiro May 19, 2012

May 19, 2012

Public bug reported: If respond_to_post_requests is Yes the notice to the poster of a held post is From: the listname-bounces address. It should be from the listname-owner address. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/714424 Title: Held message user notification should be from -owner, not -bounces

1 1

[Bug 776122] [NEW] Bootstrap phase of setup fails
by Richard Wackerbarth April 7, 2012

April 7, 2012

Public bug reported: When attempting to build MM3 from source, the buildout phase of the bootstrap fails. The code cannot recognize the version number of the MM source. This is because the regular expression in setup.py is looking for the version to be enclosed by ", but the version.py file uses '. ** Affects: mailman Importance: Undecided Status: New ** Tags: mm3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/776122 Title: Bootstrap phase of setup fails

3 2

[Bug 782474] [NEW] Re-design the mailman favicon
by Tokio Kikuchi April 7, 2012

April 7, 2012

Public bug reported: The new mailman logo is very nice and cool. But, the reduced favicon (mm-icon.png) looks rather shabby because of its limited size and resolution. I redesigned the favicon by emphasizing the feature of crescent like lines. I also make it a 'true' windows icon format so you can put it on your desk top and make a link to your mailman site. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/782474 Title: Re-design the mailman favicon

2 4

[Bug 600780] [NEW] Login function needed in rest-client
by Anna April 6, 2012

April 6, 2012

Public bug reported: For a good, working Mailman 3.0 UI we have to handle the passwords for each user (needed when they subscribe/unsubscribe/want to access their settings page but also for the admins and listowners). Hence, we need to implement the possibility to check for passwords in the rest-client (I believe these are saved in the user table in the core DB) and/or a login function. We should probably use https for the psw authentication. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- Login function needed in rest-client https://bugs.launchpad.net/bugs/600780 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 4

[Bug 788309] [NEW] Site configuration customization unnecessarily stored in tree
by Richard Wackerbarth April 6, 2012

April 6, 2012

Public bug reported: The i18n templates for site customization are specified to be in <template_dir>/site/ etc., a part of the tree, rather than being placed in <var_dir> (outside the tree) Solution, move them to <var_dir>/templates/site/ ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/788309 Title: Site configuration customization unnecessarily stored in tree

2 5

[Bug 685261] [NEW] emailed command in subject header is ignored
by Mark Sapiro April 6, 2012

April 6, 2012

Public bug reported: For example, a held message notification to the list owner/moderator contains an attached message/rfc822 part with subject "confirm <token>" and this message can be replied to with or without an "Approved: <password>" header/first body line to accept or discard the held message. The code allows for an MUA possibly inserting 'Re:' or some l10n equivalent in the subject making it "Re: confirm <token>", but if the l10n equivalent contains a non-ascii character, the entire command is ignored and the message continues to be held. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/685261 Title: emailed command in subject header is ignored

2 6

[Bug 778688] [NEW] Invalid entry in owner roster causes infinite loop
by Richard Wackerbarth April 3, 2012

April 3, 2012

Public bug reported: If there is an error in the owners roster, a message sent to that roster bounces to the same list generating another (longer) bounce message which also bounces to the same roster, ad nausium. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/778688 Title: Invalid entry in owner roster causes infinite loop

2 1

[Bug 778687] [NEW] Invalid roster upon initial list creation
by Richard Wackerbarth Sept. 25, 2011

Sept. 25, 2011

Public bug reported: GNU Mailman 3.0.0a7+ (Where's My Thing?) -- bzr=7005 When executing bin/mailman create -domain=True example(a)throwaway.domain, the example-owner get populated with an entry INSERT INTO "address" VALUES(1,'main=true','main=True','',NULL,'2005-08-01 07:49:23',1,2); The roster should be empty. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/778687 Title: Invalid roster upon initial list creation

2 4

[Bug 770328] [NEW] REST qrunner sometimes does not exit after tests exception
by Barry Warsaw Sept. 25, 2011

Sept. 25, 2011

Public bug reported: When the test suite gets an exception in the REST qrunner, it sometimes prevents the qrunner from exiting. The symptom of this is that the next time you try to run the test suite, you'll get an Address In Use error early on. This is because the test suite will try to start a new REST qrunner, which wants to bind to port 9001, but that's already in use by the "zombie" qrunner. The workaround is fairly simple. Just kill -HUP the zombie from the shell. Once it exits, the port gets freed up and the test suite will work again. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/770328 Title: REST qrunner sometimes does not exit after tests exception

1 4

[Bug 787599] [NEW] host_name ancient name for mail_host
by benste Sept. 25, 2011

Sept. 25, 2011

Public bug reported: please update the settings and core to support "mail_host" instead of "host_name" which is confusing in comparision to "web_host" The same thing needs to be done in the REST Api to support this change ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailmanweb Importance: Medium Status: Confirmed ** Also affects: mailmanweb Importance: Undecided Status: New ** Changed in: mailman Status: New => Opinion ** Changed in: mailmanweb Status: New => Opinion -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/787599 Title: host_name ancient name for mail_host

2 4

[Bug 772135] [NEW] The bounce qrunner needs to be enabled
by Barry Warsaw Sept. 25, 2011

Sept. 25, 2011

Public bug reported: The Mailman 3 bounce qrunner isn't really enabled. It needs to be hooked up to scan_message() and tested. ** Affects: mailman Importance: Medium Status: Confirmed ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/772135 Title: The bounce qrunner needs to be enabled

1 2

[Merge] lp:~flo-fuchs/mailman.client/settings into lp:mailman.client
by Florian Fuchs June 20, 2011

June 20, 2011

Florian Fuchs has proposed merging lp:~flo-fuchs/mailman.client/settings into lp:mailman.client. Requested reviews: Barry Warsaw (barry) For more details, see: https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088 Hi, I have added methods to delete mailing lists as well as a _Settings class to read and write list settings. Please feel free to make any changes you want (...and, of course, tell me if you feel this should be done completely differently... ;-) Cheers Florian -- https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088 Your team Mailman Coders is subscribed to branch lp:mailman.client.

3 7

[Bug 667252] [NEW] Mailman 3 Branch, install fails with --prefix specified
by Simon Fraser June 13, 2011

June 13, 2011

Public bug reported: When trying to install mailman outside the Python tree, I get the following error: (I've replaced my home directory with $HOME in the below text) $ whoami srf $ /software/bin/python-2.6.3 setup.py install --prefix=~srf/mailman-install running install Checking .pth file support in /$HOME/mailman-install/lib/python2.6/site-packages/ error: can't create or remove files in install directory The following error occurred while trying to add or remove files in the installation directory: [Errno 2] No such file or directory: '/$HOME/mailman- install/lib/python2.6/site-packages/test-easy-install-20075.pth' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /$HOME/mailman-install/lib/python2.6/site-packages/ This directory does not currently exist. Please create it and try again, or choose a different installation directory (using the -d or --install-dir option). ** Affects: mailman Importance: Undecided Status: New -- Mailman 3 Branch, install fails with --prefix specified https://bugs.launchpad.net/bugs/667252 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 5

[Bug 266263] Re: NNTP gatewaying trashes Message-IDs
by Ike May 30, 2011

May 30, 2011

I solved this problem in another way. Someone wrote for me the SynFU- script: https://github.com/Shirk/SynFU It is a very good script for synchronizing mails between mailing lists and a newsserver. I'm using it on a system with more than 200 mailing lists and up to 1000 postings a day. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266263 Title: NNTP gatewaying trashes Message-IDs

1 0

[Bug 266263] Re: NNTP gatewaying trashes Message-IDs
by Joshua Cranmer May 30, 2011

May 30, 2011

Here is my proposal for what to do: 1. Find all known mailing lists in the to/cc headers, and simultaneously crosspost to those newsgroups 2. Only rewrite a message ID if the news server has one on the server that does not represent this message. This means that all of the problems with message IDs should be limited to people who put the mailing lists in BCCs, or people who are sending to mailing lists on multiple servers that inject into NNTP in different places. I do not yet have a patch for either yet. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266263 Title: NNTP gatewaying trashes Message-IDs

1 0

[Bug 266263] Re: NNTP gatewaying trashes Message-IDs
by Joshua Cranmer May 30, 2011

May 30, 2011

** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266263 Title: NNTP gatewaying trashes Message-IDs

1 0

[Bug 558123] Re: fix for [815297] signatures break
by Mark Sapiro May 27, 2011

May 27, 2011

*** This bug is a duplicate of bug 265967 *** https://bugs.launchpad.net/bugs/265967 ** This bug has been marked a duplicate of bug 265967 Breaking signatures in message/rfc822 attachement! -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558123 Title: fix for [815297] signatures break

1 0

[Bug 266821] Re: privacy hole in password reminder
by Amedee Van Gasse May 23, 2011

May 23, 2011

I am sorry, this appears to be the general Launchpad page for Mailman, not just Ubuntu's version of it. I got confused because a lot of Ubuntu happens on Launchpad, but there are other projects hosted here too. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266821 Title: privacy hole in password reminder

1 0

[Bug 266821] Re: privacy hole in password reminder
by Amedee Van Gasse May 23, 2011

May 23, 2011

The problem isn't plain text emailed passwords. The *real* problem is storing plain text passwords on the server that runs mailman. If that server gets compromised, the attacker has a list of email addresses and passwords. I guess you all heard about the recent problems with Sony's Playstation Network (PSN). One of the biggest problems there was that Sony stored plain text passwords. If you Google for "plain text passwords", you will see thousands of articles that advise against it, and none that recommend it. Storing plain text passwords in a database is a security antipattern. Passwords should always be one-way encrypted (hashed), and preferably well salted. This is a website that shames Plain Text Offenders: http://plaintextoffenders.com/ Mailman should be added to that website, and Ubuntu should add a very clear security warning to Mailman. Other (more secure) mailing list software should be advised, or a more secure (patched) version (MM 2.1, 3.0, whatever) should be used. Canonical/Ubuntu itself currently uses Mailman for it's community mailing lists (ubuntu-users etc...). This should be seriously evaluated. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266821 Title: privacy hole in password reminder

1 0

[Bug 786932] [NEW] Feature request: Option to trust list owners' HTML
by Cedders May 23, 2011

May 23, 2011

Public bug reported: List owners may want to edit the list information or subscribe pages to link to CSS or JS on a main site, to use a standard style or do form validation, for example. The checks against cross-site scripting prevent this, and the text suggesting shell access may be inappropriate. The site admin may trust the list owners, but it may not be desirable for privacy or firewall reasons to give them SSH access to the Mailman server. (previously suggested on bug 266273) It would therefore be very useful to have a global option to turn off the XSS checking as needed. A simple patch is attached to provide this option. I didn't find existing translations for the relevant error messages (in French or Spanish at least). ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/786932 Title: Feature request: Option to trust list owners' HTML

1 1

[Bug 266841] Re: export member list in web interface
by Mark Sapiro May 16, 2011

May 16, 2011

*** This bug is a duplicate of bug 266867 *** https://bugs.launchpad.net/bugs/266867 ** This bug has been marked a duplicate of bug 266867 Membership List for Web Interface * You can subscribe to bug 266867 by following this link: https://bugs.launchpad.net/mailman/+bug/266867/+subscribe -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266841 Title: export member list in web interface

1 0

[Bug 266727] Re: Export list members
by David Sterratt May 16, 2011

May 16, 2011

*** This bug is a duplicate of bug 266867 *** https://bugs.launchpad.net/bugs/266867 ** This bug has been marked a duplicate of bug 266867 Membership List for Web Interface * You can subscribe to bug 266867 by following this link: https://bugs.launchpad.net/mailman/+bug/266867/+subscribe -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266727 Title: Export list members

1 0

[Bug 781487] [NEW] Fails to process Vietnamese Characters in email links
by arky May 12, 2011

May 12, 2011

Public bug reported: Mailman (2.1.9) fails to process emails with Vietnamese charasets. Testcase: 1) http://ngocentre.org.vn/mailman/listinfo/wildtrade 2) Copy Tú(a)gmail.com in Unsubscribe and edit Options and press submit. 3) You will get the following error Error: Illegal Email Address: Tú(a)gmail.com If the email address have words such then mailman spews out 'We've hit a bug' page. Sample Vietname names for testing purpose: Trần Đỗ Huyền Vũ Phương Tú ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/781487 Title: Fails to process Vietnamese Characters in email links

2 1

Re: [Question #157154]: How to disable a list temporarily ?
by Mark Sapiro May 12, 2011

May 12, 2011

Question #157154 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/157154 Status: Open => Answered Mark Sapiro proposed the following answer: Just 'chmod 000 lists/LISTNAME', and when you want to re-enable the list, 'chmod 2775 lists/LISTNAME'. If the list has public archives and you want to disable access to them, 'rm archives/public/LISTNAME*'. When you re-enable the list, these symlinks will be automatically recreated when you access the list. Depending on your MTA, you may want to remove the list's aliases. -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0

[Question #157154]: How to disable a list temporarily ?
by arky May 12, 2011

May 12, 2011

New question #157154 on mailman in Ubuntu: https://answers.launchpad.net/ubuntu/+source/mailman/+question/157154 How do I disable a list temporarily. I don't want to delete it but disallow access to it (via email or HTTP) -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0