BERJAYA

[Bug 582522] [NEW] Implement archive delivery via LMTP
by Barry Warsaw May 22, 2026

May 22, 2026

Public bug reported: Dovecot beta supports delivery via LMTP. Mailman 3 should implement a generic archive delivery implementation that delivers via LMTP. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Milestone: None => 3.0.0a6 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => High -- Implement archive delivery via LMTP https://bugs.launchpad.net/bugs/582522 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 5

[Bug 967951] [NEW] The LMTP runner should reject messages with duplicate Message-IDs
by Barry Warsaw May 22, 2026

May 22, 2026

Public bug reported: Subject says it all. Mailman 3 requires unique Message-IDs for posts. ** Affects: mailman Importance: Undecided Status: New ** Tags: easy 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/967951 Title: The LMTP runner should reject messages with duplicate Message-IDs To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967951/+subscriptions

7 13

[Bug 582524] [NEW] Use IMAP CREATE to add folders to IMAP archiver on list creation
by Barry Warsaw May 21, 2026

May 21, 2026

Public bug reported: For every mailing list we expose to IMAP, we'll want to create a few folders. Hook in the IMAP folder creation to the list creation hooks. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Use IMAP CREATE to add folders to IMAP archiver on list creation https://bugs.launchpad.net/bugs/582524 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 2

[Bug 582525] [NEW] Add sieve rules to route messages properly to IMAP server
by Barry Warsaw May 21, 2026

May 21, 2026

Public bug reported: When a message from Mailman gets routed to an IMAP server (e.g. for archiving or administration), we need a sieve rule to do proper routing. E.g. for dovecot. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Add sieve rules to route messages properly to IMAP server https://bugs.launchpad.net/bugs/582525 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 4

[Bug 1252575] [NEW] The Mail<->News gateway doesn't honor moderation or *_these_nonmembers for messages gated from usnet.
by Mark Sapiro May 19, 2026

May 19, 2026

Public bug reported: Messages gated to a list from usenet bypass all the checks in Moderate.py. It is appropriate to bypass generic_nonmember_action because many usenet posts will be from nonmembers of the list, but if the sender is a moderated member or a nonmember matching one of the *_these_nonmembers filters, those things should be honored. ** 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/1252575 Title: The Mail<->News gateway doesn't honor moderation or *_these_nonmembers for messages gated from usnet. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1252575/+subscriptions

5 6

[Bug 1417093] [NEW] list of users approved for any list on the site
by Stephen Turnbull May 19, 2026

May 19, 2026

Public bug reported: Some sites would like to allow a specified list of users to subscribe without administrator approval to any list on the site. For sites with many users, many lists, and a lot of turnover, approving all subscriptions is a lot of work. In many applications it would probably be a better idea to have a member plugin for the enterprise member database, but not all sites will be that sophisticated, or they may worry about the security implications of exposing those databases to Mailman. ** Affects: mailman Importance: Undecided Status: New ** Tags: feature 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/1417093 Title: list of users approved for any list on the site To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1417093/+subscriptions

5 6

[ 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 965532] [NEW] Need a script to upgrade from MM2 to MM3
by Barry Warsaw Dec. 14, 2021

Dec. 14, 2021

Public bug reported: We need a script, documentation, or other procedure to help people migrate from Mailman 2 to Mailman 3. ** 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/965532 Title: Need a script to upgrade from MM2 to MM3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/965532/+subscriptions

8 21

[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 883193] [NEW] Remove the X- prefix from some headers
by Barry Warsaw Jan. 15, 2019

Jan. 15, 2019

Public bug reported: MM3 still uses a lot of X- headers, but some of the X- prefixes can be removed. In general, we can just claim the Mailman- prefix for Mailman specific headers. Candidates include: Mailman-Rule-Hits Mailman-Rule-Misses Mailman-Version Mailman-Approved-At Mailman-LMTP-MailFrom (i.e. X-MailFrom) Mailman-Copy (or remove this header) Mailman-Content-Filter (from X-Content-Filtered-By) Also, fix the outdated comments about add-dup-header in avoid_duplicates.py and verp.py. Probably also get rid of X-List-Administrivia (and possibly reduced_list_headers). These seem unnecessary now. ** 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/883193 Title: Remove the X- prefix from some headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions

3 6

Mailman-coders

February 2015