Mailman-coders September 2018

mailman-coders@python.org

8 discussions

[Bug 1609516] [NEW] [needs-packaging] GNU Mailman v3

by Kẏra

Public bug reported: Mailman 3 is essentially five projects: Mailman Core Postorius - The Web UI for Mailman Mailman Client - The REST API Client HyperKitty - The Archiver for Mailman Mailman Bundler - Installer for Mailman Suite including all above projects URL: https://www.gnu.org/software/mailman/ ** Affects: mailman Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Affects: debian Importance: Unknown Status: Unknown ** Tags: needs-packaging ** Bug watch added: Debian Bug tracker #799292 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799292 ** Also affects: debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799292 Importance: Unknown Status: Unknown ** Also 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/1609516 Title: [needs-packaging] GNU Mailman v3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1609516/+subscriptions

5 months, 1 week

[Bug 544477] [NEW] setting localhost in postfix_lmtp breaks delivery

by Patrick Ben Koetter

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.

1 year

[Bug 1731604] [NEW] VERP fails if the recipient address local part is quoted.

by Mark Sapiro

Public bug reported: We have seen (very rarely) cases where a recipient address has a quoted local part such as "jr."@example.org. This results in a VERPed sender address like list-bounces+"jr."=example.org(a)example.com which is syntactically invalid. The VERPed sender should be "list- bounces+jr.=example.org"@example.com in this case. I.e., the entire VERPed sender local part should be quoted, not just the recipient local part. This also requires BounceRunner to recognize this and restore the original local part. ** 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/1731604 Title: VERP fails if the recipient address local part is quoted. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1731604/+subscriptions

1 year, 6 months

[Bug 1785854] [NEW] TypeError from confirm CGI.

by Mark Sapiro

Public bug reported: We have seen some massive, robotic subscribes and confirmations. In rare cases a TypeError can be thrown. This occurs because in processing, the CGI script retrieves the pending entry more than once. If the initial retrieval returns None, an appropriate message is returned, but if two clients confirm the same token at the same time, both initial retrievals may succeed, but then subsequent processing locks the list and retrieves the data again. The first client to get there processes the confirmation which removes the token. Then when the list is unlocked, the second client gets None for the pending data and throws TypeError when retrieving things from None. ** 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/1785854 Title: TypeError from confirm CGI. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1785854/+subscriptions

1 year, 9 months

[Bug 1774826] [NEW] Feature request: simple captcha

by Oscar Racle

Public bug reported: Suggest to include a simple captcha that (unlike reCAPTCHA) does not involve feeding data to the internet advertising and surveillance industry. This could be a simple arithmetic captcha entirely implemented in python without any contact to 3rd party servers. Such a mechanism should be sufficient to keep out ordinary spambots. ** 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/1774826 Title: Feature request: simple captcha To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1774826/+subscriptions

2 years, 4 months

[Bug 883193] [NEW] Remove the X- prefix from some headers

by Barry Warsaw

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

2 years, 9 months

[Bug 1094696] [NEW] Event notifications on postings

by George Chatzisofroniou

Public bug reported: It looks like there is no way for a MM3 plugin to be signaled for a new posting. It would be great if core could provide a notification to the plugins that have subscribed to this event when a new post occurs. This notification should carry some interesting information, like the number of recipients and the message size. This request is also essential for the MM3-Metrics module (https://launchpad.net/mm3-metrics). ** Affects: mailman Importance: Undecided Status: New ** Tags: events mailman3 metrics modules notification plugins post -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1094696 Title: Event notifications on postings To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1094696/+subscriptions

2 years, 10 months

[Bug 1414352] [NEW] Improve code coverage by adding tests

by Terri

Public bug reported: Mailman Core and Postorius have sets of tests, but could use more extensive test coverage. This bug is meant to be a repeatable bug suitable for new contributors (e.g. prospective Google Summer of Code Students). In short: find a piece of Postorius or Mailman Core that isn't yet tested and write a test (or set of tests) for it. Contributors wishing to work on Mailman Core should look at START.rst and DATABASE.rst for more information about setting up tests. For Postorius, Florian is working on vcrpy test integration, so new tests can use that format. Links to documentation and examples much appreciated to update this bug! ** Affects: mailman Importance: Undecided Status: New ** Affects: postorius Importance: Undecided Status: New ** Tags: beginner-friendly easy mailman3 repeatable test ** Tags added: easy mailman3 ** Also affects: mailman Importance: Undecided Status: New ** Description changed: - Postorius has a set of tests, but it could use more extensive coverage. - This bug is meant to be a repeatable bug suitable for new contributors - (e.g. prospective Google Summer of Code Students). In short: find a - piece of postorius that isn't yet tested and write a test (or set of - tests) for it. + Mailman Core and Postorius have sets of tests, but could use more + extensive test coverage. This bug is meant to be a repeatable bug + suitable for new contributors (e.g. prospective Google Summer of Code + Students). In short: find a piece of Postorius or Mailman Core that + isn't yet tested and write a test (or set of tests) for it. - Florian is working on vcrpy test integration, so new tests can use that - format. + Contributors wishing to work on Mailman Core should look at START.rst + and DATABASE.rst for more information about setting up tests. + + For Postorius, Florian is working on vcrpy test integration, so new + tests can use that format. + + Links to documentation and examples much appreciated to update this bug! ** Tags added: repeatable -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414352 Title: Improve code coverage by adding tests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414352/+subscriptions

2 years, 10 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders September 2018