From barry at canonical.com Thu Apr 1 00:54:26 2010 From: barry at canonical.com (Barry Warsaw) Date: Wed, 31 Mar 2010 22:54:26 -0000 Subject: [Bug 552917] [NEW] Subscribing an already subscribed member via REST should 409 References: <20100331225426.1307.60979.malonedeb@palladium.canonical.com> Message-ID: <20100331225426.1307.60979.malonedeb@palladium.canonical.com> 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. From graham at canonical.com Mon Apr 5 14:59:01 2010 From: graham at canonical.com (Graham Binns) Date: Mon, 05 Apr 2010 12:59:01 -0000 Subject: [Bug 294223] Re: Bugs missing after import from SourceForge References: <20081105162459.21689.48776.malonedeb@palladium.canonical.com> Message-ID: <20100405125902.9245.81521.launchpad@gandwana.canonical.com> ** Project changed: mailman => malone ** Changed in: malone Status: New => In Progress ** Changed in: malone Assignee: (unassigned) => Graham Binns (gmb) -- Bugs missing after import from SourceForge https://bugs.launchpad.net/bugs/294223 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From ralston at pobox.com Wed Apr 7 20:21:11 2010 From: ralston at pobox.com (James Ralston) Date: Wed, 07 Apr 2010 18:21:11 -0000 Subject: [Bug 557493] [NEW] Mailman must not strip DKIM-Signature headers References: <20100407182111.5071.56379.malonedeb@potassium.ubuntu.com> Message-ID: <20100407182111.5071.56379.malonedeb@potassium.ubuntu.com> Public bug reported: I reviewed the discussion that led to the decision to have Mailman strip DomainKey-Signature and DKIM-Signature headers: http://mail.python.org/pipermail/mailman- developers/2006-January/018537.html This may have been the correct action to take in 2006. But since then, the DKIM standard has been finalized (RFC4871), and it contains: 3.5. The DKIM-Signature Header Field The DKIM-Signature header field SHOULD be treated as though it were a trace header field as defined in Section 3.6 of [RFC2822], and hence SHOULD NOT be reordered and SHOULD be prepended to the message. RFC2822 defers to RFC2821, which has been replaced by RFC5321, which states: 4.4. Trace Information An Internet mail program MUST NOT change or delete a Received: line that was previously added to the message header section. SMTP servers MUST prepend Received lines to messages; they MUST NOT change the order of existing lines or insert Received lines in any other location. Ergo, Mailman MUST NOT strip DKIM-Signature headers. Even if Mailman knows that actions it will take with the message will invalidate one or more DKIM-Signature headers, those (now-invalid) signatures MUST be left intact. DKIM-Signature headers must be treated exactly like trace (Received) headers. This isn't simply a case of doing the right thing just for standards compliance: although DKIM states that MTAs can't treat the lack of a DKIM signature any differently than an invalid DKIM signature, the presence of a DKIM-Signature header (even invalid) is a consumable item for MUAs; e.g., a token for Bayesian anti-spam systems. (For example, we currently receive *zero* spam with forged DKIM-Signature headers for our own domain. Zero. Thus, even an invalid DKIM-Signature header is incredibly useful to have.) The fix for this is simple; just remove this line from Mailman/Handlers/CleanseDKIM.py: del msg['dkim-signature'] As for DomainKeys, although the DomainKeys protocol is now historical, RFC4870 states: 3.5.2. Determining Whether an Email Should Be Signed A signer MUST NOT sign an email that already contains a "DomainKey- Signature:" header unless a "Sender:" header has been added that was not included in the original signature. The most obvious case where this occurs is with mailing lists. A signer SHOULD NOT remove an existing "DomainKey-Signature:" header. The difficulty here is that the signer (downstream from Mailman) cannot guarantee that a Sender header was added that was not included in the original signature, but it is forbidden from adding another DomainKey- Signature header if that wasn't the case. I suspect this is why many (most?) DomainKeys signers simply refrain from signing if a DomainKey- Signature header is already present, which is the behavior that Joe Peterson observed, and led to the decision to unconditionally strip all DomainKey-Signature and DKIM-Signature headers. Thus, I think Mailman stripping DomainKey-Signature headers is probably still the best choice; leaving them will all but guarantee that any downstream DomainKey-signer will refrain from generating a DomainKey- Signature. This isn't optimal, of course, but implementation ambiguities like this are why DomainKeys is now historical. But Mailman absolutely needs to cease stripping DKIM-Signature headers. (And really, CleanseDKIM.py should be renamed to CleanseDomainKeys.py.) ** Affects: mailman Importance: Undecided Status: New -- Mailman must not strip DKIM-Signature headers https://bugs.launchpad.net/bugs/557493 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From jan at inquata.com Wed Apr 7 22:16:05 2010 From: jan at inquata.com (Jan-Christoph Borchardt) Date: Wed, 07 Apr 2010 20:16:05 -0000 Subject: [Bug 266630] Re: Search Archives References: <20080905194156.1806.51295.launchpad@forster.canonical.com> Message-ID: <20100407201605.5248.86843.malone@potassium.ubuntu.com> This is still valid because there still is no search function. I just wanted to use one but could not. ** Changed in: mailman Status: Invalid => Confirmed ** Summary changed: - Search Archives + there is no search function for archives -- there is no search function for archives https://bugs.launchpad.net/bugs/266630 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu Apr 8 01:42:24 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 07 Apr 2010 23:42:24 -0000 Subject: [Bug 557493] Re: Mailman must not strip DKIM-Signature headers References: <20100407182111.5071.56379.malonedeb@potassium.ubuntu.com> Message-ID: <20100407234224.32093.35613.malone@soybean.canonical.com> This was fixed in Mailman 2.1.10 by adding the following to Defaults.py along with the code to implement it. # Some list posts and mail to the -owner address may contain DomainKey or # DomainKeys Identified Mail (DKIM) signature headers . # Various list transformations to the message such as adding a list header or # footer or scrubbing attachments or even reply-to munging can break these # signatures. It is generally felt that these signatures have value, even if # broken and even if the outgoing message is resigned. However, some sites # may wish to remove these headers by setting this to Yes. REMOVE_DKIM_HEADERS = No ** Changed in: mailman Status: New => Fix Released ** Changed in: mailman Milestone: None => 2.1-stable -- Mailman must not strip DKIM-Signature headers https://bugs.launchpad.net/bugs/557493 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From barry at canonical.com Thu Apr 8 03:30:36 2010 From: barry at canonical.com (Barry Warsaw) Date: Thu, 08 Apr 2010 01:30:36 -0000 Subject: [Bug 557750] [NEW] Mailman should honor X-Approve and X-Approved References: <20100408013036.30054.67600.malonedeb@soybean.canonical.com> Message-ID: <20100408013036.30054.67600.malonedeb@soybean.canonical.com> 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. From speeves at erikin.com Thu Apr 8 03:48:08 2010 From: speeves at erikin.com (speeves) Date: Thu, 08 Apr 2010 01:48:08 -0000 Subject: [Bug 266631] Re: remove user from all lists References: <20080905194156.1806.41645.launchpad@forster.canonical.com> Message-ID: <20100408014808.5035.44416.malone@potassium.ubuntu.com> As of: ii mailman 1:2.1.11-11 Powerful, web-based mailing list manager There is a --fromall flag, which removes the user from all lists on the server: remove_members --fromall addr1 --fromall Removes the given addresses from all the lists on this system regardless of virtual domains if you have any. This option cannot be used -a/--all. Also, you should not specify a listname when using this option. ** Changed in: mailman Status: Invalid => Fix Released -- remove user from all lists https://bugs.launchpad.net/bugs/266631 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Thu Apr 8 04:08:54 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 08 Apr 2010 02:08:54 -0000 Subject: [Bug 557750] Re: Mailman should honor X-Approve and X-Approved References: <20100408013036.30054.67600.malonedeb@soybean.canonical.com> Message-ID: <20100408020855.15797.84337.launchpad@wampee.canonical.com> ** Changed in: mailman/2.1 Milestone: None => 2.1.14 ** Changed in: mailman/2.1 Assignee: (unassigned) => Mark Sapiro (msapiro) -- 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. From dag at wieers.com Thu Apr 8 10:15:42 2010 From: dag at wieers.com (dag) Date: Thu, 08 Apr 2010 08:15:42 -0000 Subject: [Bug 557750] Re: Mailman should honor X-Approve and X-Approved References: <20100408013036.30054.67600.malonedeb@soybean.canonical.com> Message-ID: <20100408081542.30054.88046.malone@soybean.canonical.com> Original thread: http://mail.python.org/pipermail/mailman- users/2010-April/069232.html For backward compatibility I would support both Approved: and X-Approved: headers. Just in case so that after an upgrade the Approved: header is not shared with the whole mailing-list (exposing your password). The documentation could indicate X-Approved: as being supported and deprecate the usage of Approved: ? -- 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. From barry at canonical.com Thu Apr 8 13:56:55 2010 From: barry at canonical.com (Barry Warsaw) Date: Thu, 08 Apr 2010 11:56:55 -0000 Subject: [Bug 557750] Re: Mailman should honor X-Approve and X-Approved References: <20100408013036.30054.67600.malonedeb@soybean.canonical.com> Message-ID: <20100408115655.9245.19323.malone@gandwana.canonical.com> Sorry, I was time constrained when I submitted the bug. Yes, absolutely we should continue to support the old headers. I don't think we need to deprecate them though. -- 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. From mark at msapiro.net Thu Apr 8 23:51:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 08 Apr 2010 21:51:32 -0000 Subject: [Bug 558106] Re: A MemberAdaptor for LDAP-based membership References: <20100408090607.1687.22727.launchpad@loganberry.canonical.com> Message-ID: <20100408215132.5035.36252.malone@potassium.ubuntu.com> This version (0.5) of LDAPMemberships.py supports mixed case email addresses and properly returns None from the getMemberName method if the member has no 'cn' value in the LDAP database. ** Attachment added: "LDAP MemberAdaptor" http://launchpadlibrarian.net/43476506/LDAPMemberships.py -- A MemberAdaptor for LDAP-based membership https://bugs.launchpad.net/bugs/558106 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Apr 9 00:02:01 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 08 Apr 2010 22:02:01 -0000 Subject: [Bug 558106] Re: A MemberAdaptor for LDAP-based membership References: <20100408090607.1687.22727.launchpad@loganberry.canonical.com> Message-ID: <20100408220202.32181.87871.malone@soybean.canonical.com> This update (0.6) from Chris Nulk adds additional fields from LDAP givenname - givenname/firstname typically, preferredname - preferred name instead of givenname, sn - surname/lastname, fullname - usually first/given name and last/sur name combined, to be consulted in defining the member's real name. ** Attachment added: "LDAP MemberAdaptor, v 0.6" http://launchpadlibrarian.net/43477175/LDAP_Memberships.py -- A MemberAdaptor for LDAP-based membership https://bugs.launchpad.net/bugs/558106 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Apr 9 02:51:55 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 09 Apr 2010 00:51:55 -0000 Subject: [Bug 266554] Re: Integration of Mailman and htdig for archiving References: <20080905193728.32763.34621.launchpad@forster.canonical.com> Message-ID: <20100409005155.1180.12409.malone@palladium.canonical.com> It's not a bug, it's a patch, and it's still relevant. ** Changed in: mailman Status: Invalid => Confirmed -- Integration of Mailman and htdig for archiving https://bugs.launchpad.net/bugs/266554 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Fri Apr 9 02:50:35 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 09 Apr 2010 00:50:35 -0000 Subject: [Bug 266553] Re: Archive indexer control to improve index References: <20080905193726.32763.50718.launchpad@forster.canonical.com> Message-ID: <20100409005036.9043.61830.malone@gandwana.canonical.com> It's not a bug, it's a patch, and it's still relevant. ** Changed in: mailman Status: Invalid => Confirmed -- Archive indexer control to improve index https://bugs.launchpad.net/bugs/266553 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From julian.edwards at canonical.com Mon Apr 12 15:07:59 2010 From: julian.edwards at canonical.com (Julian Edwards) Date: Mon, 12 Apr 2010 13:07:59 -0000 Subject: [Bug 558249] Re: Host based langage selection References: <20100408090833.1687.40185.launchpad@loganberry.canonical.com> Message-ID: <20100412130800.30443.24294.launchpad@gandwana.canonical.com> ** Branch linked: lp:~mvo/launchpad/support-timeframe-kubuntu -- Host based langage selection https://bugs.launchpad.net/bugs/558249 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. From mark at msapiro.net Sun Apr 18 01:53:06 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 17 Apr 2010 23:53:06 -0000 Subject: [Bug 266588] Re: Add SpamAssassin filter to mail pipeline References: <20080905193752.32763.39358.launchpad@forster.canonical.com> Message-ID: <20100417235307.18215.20988.malone@wampee.canonical.com> 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. From mark at msapiro.net Sun Apr 18 01:59:09 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 17 Apr 2010 23:59:09 -0000 Subject: [Bug 557991] Re: SpamAssassin handler References: <20100408090356.1687.6770.launchpad@loganberry.canonical.com> Message-ID: <20100417235909.32126.16461.malone@soybean.canonical.com> 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. From mark at msapiro.net Sun Apr 18 02:25:31 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 18 Apr 2010 00:25:31 -0000 Subject: [Bug 266588] Re: Add SpamAssassin filter to mail pipeline References: <20080905193752.32763.39358.launchpad@forster.canonical.com> Message-ID: <20100418002531.32126.26229.malone@soybean.canonical.com> 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. From mark at msapiro.net Sun Apr 18 02:34:24 2010 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 18 Apr 2010 00:34:24 -0000 Subject: [Bug 266588] Re: Add SpamAssassin filter to mail pipeline References: <20080905193752.32763.39358.launchpad@forster.canonical.com> Message-ID: <20100418003424.23545.58877.malone@potassium.ubuntu.com> 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. From jakub.nadolny at gmail.com Mon Apr 19 18:00:30 2010 From: jakub.nadolny at gmail.com (Jakub Nadolny) Date: Mon, 19 Apr 2010 16:00:30 -0000 Subject: [Bug 566731] Re: there are some misspellings in Polish language templates References: <20100419160030.24517.71148.malonedeb@gandwana.canonical.com> Message-ID: <20100419160032.24517.79398.malone@gandwana.canonical.com> ** Attachment added: "Corrected Polish text templates" http://launchpadlibrarian.net/44828620/corrected-pl-templates-2.1.13.tgz -- 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. From jakub.nadolny at gmail.com Mon Apr 19 18:00:30 2010 From: jakub.nadolny at gmail.com (Jakub Nadolny) Date: Mon, 19 Apr 2010 16:00:30 -0000 Subject: [Bug 566731] [NEW] there are some misspellings in Polish language templates References: <20100419160030.24517.71148.malonedeb@gandwana.canonical.com> Message-ID: <20100419160030.24517.71148.malonedeb@gandwana.canonical.com> 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. From mark at msapiro.net Mon Apr 19 20:41:03 2010 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 19 Apr 2010 18:41:03 -0000 Subject: [Bug 566731] Re: there are some misspellings in Polish language templates References: <20100419160030.24517.71148.malonedeb@gandwana.canonical.com> Message-ID: <20100419184104.23545.88763.launchpad@potassium.ubuntu.com> ** Changed in: mailman Importance: Undecided => Low ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- 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. From josh at joshtriplett.org Thu Apr 29 23:17:25 2010 From: josh at joshtriplett.org (Josh Triplett) Date: Thu, 29 Apr 2010 21:17:25 -0000 Subject: [Bug 571902] [NEW] Side-wide whitelist References: <20100429211726.10929.5747.malonedeb@palladium.canonical.com> Message-ID: <20100429211726.10929.5747.malonedeb@palladium.canonical.com> 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. From josh at joshtriplett.org Thu Apr 29 23:21:44 2010 From: josh at joshtriplett.org (Josh Triplett) Date: Thu, 29 Apr 2010 21:21:44 -0000 Subject: [Bug 571904] [NEW] Aggregated list with subscribers from other lists References: <20100429212144.25029.95715.malonedeb@wampee.canonical.com> Message-ID: <20100429212144.25029.95715.malonedeb@wampee.canonical.com> 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. From mark at msapiro.net Thu Apr 29 23:43:52 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 29 Apr 2010 21:43:52 -0000 Subject: [Bug 571904] Re: Aggregated list with subscribers from other lists References: <20100429212144.25029.95715.malonedeb@wampee.canonical.com> Message-ID: <20100429214352.10929.25776.malone@palladium.canonical.com> The "sibling lists" feature (in particular, regular_include_lists) added in Mailman 2.1.10 can do essentially your first request (accept a list of lists whose members are automatically added to the recipient list of a post to this list) as long as you don't care about digest members. See the section of the FAQ at beginning with "With Mailman 2.1.10 or later" for a bit more on this. Will that satisfy this request? -- 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. From josh at joshtriplett.org Fri Apr 30 00:06:01 2010 From: josh at joshtriplett.org (Josh Triplett) Date: Thu, 29 Apr 2010 22:06:01 -0000 Subject: [Bug 571904] Re: Aggregated list with subscribers from other lists References: <20100429212144.25029.95715.malonedeb@wampee.canonical.com> Message-ID: <20100429220601.17929.38965.malone@potassium.ubuntu.com> That sounds like exactly what we want, yes. I didn't know that feature existed now. :) Thanks! -- 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.