Mailman 3 February 2015 - 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 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

[Bug 1094696] [NEW] Event notifications on postings
by George Chatzisofroniou Dec. 23, 2018

Dec. 23, 2018

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

4 6

[Bug 1414352] [NEW] Improve code coverage by adding tests
by Terri Dec. 23, 2018

Dec. 23, 2018

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

8 14

[Bug 1251495] [NEW] Lists with topics enabled can throw unexpected keyword argument 'Delete' exception.
by Mark Sapiro Nov. 29, 2017

Nov. 29, 2017

Public bug reported: Code added to Tagger.py in 2.1.16 to support the from_is_list Wrap Message option contained a misspelling. ** Affects: mailman Importance: High 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/1251495 Title: Lists with topics enabled can throw unexpected keyword argument 'Delete' exception. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1251495/+subscriptions

5 16

[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 978351] [NEW] Content Filtering *_filename_extension matches are case sensitive.
by Mark Sapiro June 9, 2017

June 9, 2017

Public bug reported: If the case of the filename extension in the message doesn't agree with that in *_filename_extension, they won't match. Matching should be case insensitive. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Affects: mailman/2.1 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Released ** Affects: mailman/3.0 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Tags: mailman3 ** Also affects: mailman/3.0 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Released ** Also affects: mailman/2.1 Importance: Undecided Status: New ** Changed in: mailman/3.0 Status: Fix Released => In Progress ** Changed in: mailman/3.0 Milestone: mailman-2.1 => 3.0.0b2 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/978351 Title: Content Filtering *_filename_extension matches are case sensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/978351/+subscriptions

3 5

[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 1104498] [NEW] Member contact requests
by Kẏra April 1, 2016

April 1, 2016

Public bug reported: When configured to hide email addresses. a mailman user should be able to contact someone else by using a request contact form a profile page representing a user. This form would email the recipient of the request a short message explaining who is trying to get in contact, and the email address of the user requesting contact. ** Affects: mailman Importance: Undecided Status: New ** Tags: wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1104498 Title: Member contact requests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1104498/+subscriptions

6 6

[Bug 1279980] [NEW] Some forms in list admin interfaces use absolute links in form action
by Vitor Choi Feitosa Feb. 15, 2016

Feb. 15, 2016

Public bug reported: Some forms in admin interface, like the one on list member management -- https://HOSTNAME/mailman/admin/somelist/members -- , use absolute links as the form action url. POST data then gets transmitted in the clear because that absolute link points to http instead of https address. I'm running mailman 2.1.14 ** 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/1279980 Title: Some forms in list admin interfaces use absolute links in form action To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1279980/+subscriptions

3 9

[Merge] lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client
by Rajeev S Feb. 3, 2016

Feb. 3, 2016

Rajeev S has proposed merging lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli/+merge/23… GSoC project "Mailman CLI" The branch contains the Mailman CLI shell as well as the command line tools built as a part of the GSoC 2014, Under the mentors Stephen J Turnbull, Abhilash Raj and Barry Warsaw. -- https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli/+merge/23… Your team Mailman Coders is requested to review the proposed merge of lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client.

1 3

[Bug 889829] [NEW] setup takes zope interface 3.5.1, but needs 3.8.0
by Harry Enke July 31, 2015

July 31, 2015

Public bug reported: separate installation of zope interface 3.8.0 fixes the issue, afterwards mailman 3.0.0.8a OS: Scientific Linux 6.1, Python 2.6.6 ** 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/889829 Title: setup takes zope interface 3.5.1, but needs 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889829/+subscriptions

3 7

[Bug 1414298] [NEW] ILanguageManager should be exposed as a REST resource
by Sumana Harihareswara June 8, 2015

June 8, 2015

Public bug reported: Expose ILanguageManager as a REST resource, so that Postorius can use it to learn what languages a system supports, and thus provide list administrators with options for a list's preferred language. Refer to src/mailman/model/docs/languages.rst -- I imagine this will probably use a getUtility call to say, getUtility(ILanguageManager) Background, based on my conversation with Barry yesterday (I may have gotten some things wrong): The system knows it supports certain languages. This is set in a config file that only the site administrator can change -- a change in the config file requires a mailman restart in order to take effect. The Language Manager is per system. The Language Manager is a utility, like the user manager (that is, essentially a singleton in the system; interfaces that have multiple implementations are not utilities). When the system boots up, it registers implementations of interfaces. These are ZopeInterfaces, as we use the Zope component architecture, ZCA. ** Affects: mailman Importance: Undecided Status: New ** Affects: postorius Importance: Undecided Status: New ** Tags: i18n mailman3 mailman3-suite-blocker ** Also affects: postorius Importance: Undecided Status: New ** Tags added: i18n mailman3-suite-blocker -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414298 Title: ILanguageManager should be exposed as a REST resource To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414298/+subscriptions

4 8

[Bug 1414176] [NEW] better list-data export and import via XML, maybe web
by Sumana Harihareswara June 8, 2015

June 8, 2015

Public bug reported: Provide a better list-data export and import mechanism via XML. *Possibly* allow for data export via the web. This requires discussion and deciding which parts to implement in Postorius and/or HyperKitty. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Affects: postorius Importance: Undecided Status: New ** Tags: mailman3 ** Also affects: postorius 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/1414176 Title: better list-data export and import via XML, maybe web To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414176/+subscriptions

3 4

[Bug 1414169] [NEW] gather and surface admin statistics
by Sumana Harihareswara June 8, 2015

June 8, 2015

Public bug reported: Improve admin statistics gather (# of posts sent, # bounced, # of domains accessed, which lists are quiet and which are busy) and make these available via the REST interface so Postorius can use them. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414169 Title: gather and surface admin statistics To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414169/+subscriptions

2 3

[Bug 1196608] [NEW] Better theming
by Kẏra June 8, 2015

June 8, 2015

Public bug reported: Using Bootstrap ** 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/1196608 Title: Better theming To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1196608/+subscriptions

3 4

[Bug 1104507] [NEW] Web feeds
by Kẏra June 8, 2015

June 8, 2015

Public bug reported: Mailman should create atom/rss web feeds from lists as well as individual posts (threads) or searches. ** 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/1104507 Title: Web feeds To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1104507/+subscriptions

4 5

[Bug 1036207] [NEW] mailman.client hangs accessing moderation queue
by Stephen Turnbull June 8, 2015

June 8, 2015

Public bug reported: Here's what I did as recorded in Terminal.app: steve@turnbull:~/src/Mailman3/mailman.client$ python Python 2.7.3rc2 (default, Apr 22 2012, 22:30:17) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import os >>> import time >>> import subprocess >>> from mailman.client import Client >>> c = Client('http://localhost:8001/3.0', 'restadmin', 'restpass') >>> dump(c.system) Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'dump' is not defined >>> c.lists [<List "mm3-test(a)turnbull.sk.tsukuba.ac.jp">] >>> c.domains [<Domain "turnbull.sk.tsukuba.ac.jp">] >>> print c.domains[0].url_host turnbull.sk.tsukuba.ac.jp >>> print c.domains[0].mail_host turnbull.sk.tsukuba.ac.jp >>> l = c.lists[0] >>> l.fqdn_listname u'mm3-test(a)turnbull.sk.tsukuba.ac.jp' >>> c.get_list('mm3-test(a)turnbull.sk.tsukuba.ac.jp') <List "mm3-test(a)turnbull.sk.tsukuba.ac.jp"> >>> c.get_list(u'mm3-test(a)turnbull.sk.tsukuba.ac.jp') <List "mm3-test(a)turnbull.sk.tsukuba.ac.jp"> >>> c.members [<Member "turnbull(a)sk.tsukuba.ac.jp" on "mm3-test(a)turnbull.sk.tsukuba.ac.jp">] >>> print c.members[0].self_link http://localhost:8001/3.0/members/230487102891977069915270988864921324936 >>> print c.members[0].link Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: '_Member' object has no attribute 'link' >>> print c.users[0] <User "None" (323817100493882819169277267745120573853)> >>> print c.users [<User "None" (323817100493882819169277267745120573853)>] >>> print c.users[0].addresses <mailman.client._client._Addresses object at 0x7f6b849c7a10> >>> print c.users[0].addresses[0] Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: '_Addresses' object does not support indexing >>> for a in print c.users[0].addresses: File "<stdin>", line 1 for a in print c.users[0].addresses: ^ SyntaxError: invalid syntax >>> for a in c.users[0].addresses: ... print a ... turnbull(a)sk.tsukuba.ac.jp >>> for a in sorted(l.settings): ... print a + ': ' + string(l.settings[a]) ... Traceback (most recent call last): File "<stdin>", line 2, in <module> NameError: name 'string' is not defined >>> for a in sorted(l.settings): ... print a + ': ' + str(l.settings[a]) ... acceptable_aliases: [] admin_immed_notify: True admin_notify_mchanges: False administrivia: True advertised: True allow_list_posts: True anonymous_list: False autorespond_owner: none autorespond_postings: none autorespond_requests: none autoresponse_grace_period: 90d autoresponse_owner_text: autoresponse_postings_text: autoresponse_request_text: bounces_address: mm3-test-bounces(a)turnbull.sk.tsukuba.ac.jp collapse_alternatives: True convert_html_to_plaintext: False created_at: 2012-08-09T03:16:21.186456 default_member_action: defer default_nonmember_action: hold description: digest_last_sent_at: None digest_size_threshold: 30.0 display_name: Mm3-test filter_content: False fqdn_listname: mm3-test(a)turnbull.sk.tsukuba.ac.jp generic_nonmember_action: 1 http_etag: "b8b4e1df6bc8d8ee33f363927022d0bcc86569bb" include_rfc2369_headers: True join_address: mm3-test-join(a)turnbull.sk.tsukuba.ac.jp last_post_at: None leave_address: mm3-test-leave(a)turnbull.sk.tsukuba.ac.jp list_name: mm3-test mail_host: turnbull.sk.tsukuba.ac.jp next_digest_number: 1 no_reply_address: noreply(a)turnbull.sk.tsukuba.ac.jp owner_address: mm3-test-owner(a)turnbull.sk.tsukuba.ac.jp post_id: 1 posting_address: mm3-test(a)turnbull.sk.tsukuba.ac.jp posting_pipeline: default-posting-pipeline reply_goes_to_list: no_munging request_address: mm3-test-request(a)turnbull.sk.tsukuba.ac.jp scheme: http send_welcome_message: True volume: 1 web_host: turnbull.sk.tsukuba.ac.jp welcome_message_uri: mailman:///welcome.txt >>> dir() ['Client', '__builtins__', '__doc__', '__name__', '__package__', 'a', 'c', 'l', 'os', 'subprocess', 'time'] >>> dir(Client) ['__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__hash__', '__init__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'create_domain', 'delete_domain', 'delete_list', 'domains', 'get_domain', 'get_list', 'get_user', 'lists', 'members', 'preferences', 'system', 'users'] >>> dir(Client.system) ['__class__', '__delattr__', '__delete__', '__doc__', '__format__', '__get__', '__getattribute__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__set__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', 'deleter', 'fdel', 'fget', 'fset', 'getter', 'setter'] >>> dir(l) ['__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__hash__', '__init__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', '_connection', '_get_info', '_info', '_url', 'accept_message', 'defer_message', 'delete', 'discard_message', 'display_name', 'fqdn_listname', 'get_member', 'held', 'list_name', 'mail_host', 'members', 'moderate_message', 'reject_message', 'settings', 'subscribe', 'unsubscribe'] >>> l._connection.__doc__ u'A connection to the REST client.' >>> l.held.__doc__ ^CTraceback (most recent call last): File "<stdin>", line 1, in <module> File "mailman/client/_client.py", line 350, in held 'lists/{0}/held'.format(self.fqdn_listname), None, 'GET') File "mailman/client/_client.py", line 114, in call response, content = Http().request(url, method, data, headers) File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1543, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1293, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1263, in _conn_request response = conn.getresponse() File "/usr/lib/python2.7/httplib.py", line 1030, in getresponse response.begin() File "/usr/lib/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib/python2.7/httplib.py", line 365, in _read_status line = self.fp.readline() File "/usr/lib/python2.7/socket.py", line 430, in readline data = recv(1) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/email/message.py", l\ ine 226, in _enqueue virginq.enqueue(self, **str_keywords) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/switchboard.py"\ , line 123, in enqueue msgsave = cPickle.dumps(_msg, protocol) After the above I tried a couple of things, like printing l.held (with no further attribute). These also hung for a few seconds and I interrupted with ^C. Eventually it failed with an error about not being connected to Mailman. I thought Mailman had crashed, but when I tried shutting down Mailman using bin/mailman, it seemed to shut down normally. ** 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/1036207 Title: mailman.client hangs accessing moderation queue To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1036207/+subscriptions

3 4

[Bug 1006345] [NEW] Anonymous subscription via confirmation email
by Robert Niederreiter June 8, 2015

June 8, 2015

Public bug reported: Currently it is not possible to subscribe as anonymous user. ** Affects: postorius Importance: Undecided Status: New ** Tags: anonymous confirmation subscription ui -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1006345 Title: Anonymous subscription via confirmation email To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1006345/+subscriptions

7 16

[Bug 1104497] [NEW] User profile pages
by Kẏra June 8, 2015

June 8, 2015

Public bug reported: Mailman users should have a profile page that is common to all the lists in the instance. The profile should store all the user's personal information (if any), and lists all of the posts by that user. ** Affects: mailman Importance: Undecided Status: New ** Tags: wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1104497 Title: User profile pages To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1104497/+subscriptions

5 5

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

May 23, 2015

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

4 5

[Bug 1414187] [NEW] user permission to override a post size limitation
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: A user permission: the user is allowed to override the list's post sizes limit (slightly different from the bug# 1414182 "ignore size in future" permission/privilege). From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. Original note: "I don't know if this is a reasonable request or not, but if yes, could each user be allowed an override for post sizes (slightly different from above "ignore size in future" request)?" ** 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/1414187 Title: user permission to override a post size limitation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414187/+subscriptions

2 1

[Bug 1414185] [NEW] Increase user permission granularity w.r.t. size limitations and implicit addressing
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Increase user permission granularity with regards to user's ability to ignore size limitations and use implicit addressing. Bug 1414183 and Bug 1414182 depend on this. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414185 Title: Increase user permission granularity w.r.t. size limitations and implicit addressing To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414185/+subscriptions

2 1

[Bug 1414183] [NEW] option on moderation request to allow user to use implicit addressing in future
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Add checkbox to moderation requests with option "Allow this user to use implicit addressing in the future" From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414183 Title: option on moderation request to allow user to use implicit addressing in future To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414183/+subscriptions

2 1

[Bug 1414182] [NEW] option on moderation request to allow user to ignore size limitations in future
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Add checkbox to moderation requests with option "Allow this user to ignore size limitations in the future" From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414182 Title: option on moderation request to allow user to ignore size limitations in future To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414182/+subscriptions

2 1

[Bug 1414181] [NEW] Include message headers in discard notifications
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Include message headers in discard notifications - currently it isn't always possible to tell who sent a message that's been discarded, which makes it a bit pointless sending a notification. It would be nice to include brief headers in the first message part. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414181 Title: Include message headers in discard notifications To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414181/+subscriptions

3 2

[Bug 1414180] [NEW] discard stagnant messages from bounces or shunt queues
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Discard messages that have been in the bounces or shunt queues for a long time. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414180 Title: discard stagnant messages from bounces or shunt queues To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414180/+subscriptions

2 1

[Bug 1414179] [NEW] Fix the bounce probe problem, & make bounce processing more efficient
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: "Fix the bounce probe problem, and make bounce processing more efficient. Right now, it sucks." From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414179 Title: Fix the bounce probe problem, & make bounce processing more efficient To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414179/+subscriptions

2 1

[Bug 1414178] [NEW] Partition queue directories into hashed subdirectories
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Partition queue directories into hashed subdirectories so that all queue files do not live in the same directory (which increases contention on the directory inodes and reduces overall performance). From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 performance -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1414178 Title: Partition queue directories into hashed subdirectories To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414178/+subscriptions

2 1

[Bug 1414177] [NEW] for Postfix, switch to non-Postfix mailbox store
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: For Postfix, switch to http://www.postfix.org/VIRTUAL_README.html#in_virtual_other Non-Postfix mailbox store: separate domains, non-UNIX accounts virtual domains and maildir delivery by default. Delivery mechanics for other MTAs may or may not change. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414177 Title: for Postfix, switch to non-Postfix mailbox store To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414177/+subscriptions

2 1

[Bug 1414174] [NEW] add audit trail for user management changes
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Add audit trail for user subscriptions. Who added them? What checks were made? From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414174 Title: add audit trail for user management changes To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414174/+subscriptions

2 1

[Bug 1414173] [NEW] delete double messages in digest option
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: The 'digest option' needs to be improved to delete 'double messages' From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414173 Title: delete double messages in digest option To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414173/+subscriptions

2 1

[Bug 1414171] [NEW] Better feedback to users who have bounced
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Provide better feedback to users who have bounced. May include making message ID of member's last bounced message available via API so Postorius can use it. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414171 Title: Better feedback to users who have bounced To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414171/+subscriptions

2 1

[Bug 1414170] [NEW] Caps for list member count and outgoing messages per time slice
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Caps for list member count and outgoing messages per time slice. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414170 Title: Caps for list member count and outgoing messages per time slice To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414170/+subscriptions

2 1

[Bug 1414163] [NEW] use LMTP process to do checks & dispose messages earlier
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Hook into the LMTP process http://wiki.mailman.psf.io/DEV/LMTP%20process so that messages can be disposed of as early as possible. Check potential senders and recipients at LTMP time to check, e.g., "are you sending to a list that does not exist or that you do not have permission to post to?" From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414163 Title: use LMTP process to do checks & dispose messages earlier To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414163/+subscriptions

2 2

[Bug 1414159] [NEW] suppress backscatter bounces when SPF headers don't match
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Suppress backscatter bounces when http://www.openspf.org SPF headers do not match. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414159 Title: suppress backscatter bounces when SPF headers don't match To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414159/+subscriptions

2 1

[Bug 1414157] [NEW] integrate spam defense into Mailman core
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Possibly integrate http://www.spambayes.org Spambayes or http://www.spamassassin.org SpamAssassin or http://pyzor.org pyzor into Mailman core. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414157 Title: integrate spam defense into Mailman core To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414157/+subscriptions

2 1

[Bug 1414156] [NEW] Switch to $strings (i.e. `string.Template` instances) for all i18n substitutions
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Switch to $strings (i.e. `string.Template` instances) for all i18n substitutions. We should be able to mechanically update all existing translations. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414156 Title: Switch to $strings (i.e. `string.Template` instances) for all i18n substitutions To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414156/+subscriptions

2 2

[Bug 1414155] [NEW] Language variants (e.g. en_UK)
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Mailman should support language variants (e.g. en_UK). From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414155 Title: Language variants (e.g. en_UK) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414155/+subscriptions

2 2

[Bug 1414154] [NEW] switch to external translation system
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Finish the transition to an externally managed translation system. This is necessary for the Mailman 3.0 release. Right now someone has to send new translations to Mark and he has to do a new release with new catalogs; see http://wiki.mailman.psf.io/DEV/Internationalization and http://wiki.mailman.psf.io/DEV/i18nhowto for more info. We have some notes at http://wiki.mailman.psf.io/DEV/Managing%20Translations about what we want in the future. It must be free software (this is why we cannot use Transifex). The workflow Barry would love: a developer can develop their software, marking all strings for localisation. Someone can take the trunk branch and run a tool to extract all the strings and provide Mailman developers with GNU gettext catalogs, or make them available in a branch, or on the web, so Mailman maintainers can check them out. There exists enough distributed machinery that we should be able to do this in a disconnected way. (From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series.) ** 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/1414154 Title: switch to external translation system To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414154/+subscriptions

5 6

[Bug 1414151] [NEW] Rosters should not be public by default
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Rosters should not be public by default. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414151 Title: Rosters should not be public by default To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414151/+subscriptions

2 1

[Bug 1414149] [NEW] option to allow verified nonmembers to post to a list
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Add an option to allow ''verified'' non-members to post to the list. A verified non-member is someone who posts to the list and responds in the affirmative to a confirmation message. A verified member can post in the future (think Gmane http://www.gmane.org ). From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. May be a duplicate of bug 558029. ** 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/1414149 Title: option to allow verified nonmembers to post to a list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414149/+subscriptions

2 1

[Bug 1414147] [NEW] juggling for recipients in headers
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: Strip nodup recipients from both the `To` and `Cc` headers, and juggle recipient headers so that the list address is always in the `To` field. This might address the other major complaint against no-reply-to- munging, recipient proliferation. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414147 Title: juggling for recipients in headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414147/+subscriptions

2 1

[Bug 1414143] [NEW] Use subprocess module instead of things like os.popen()
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: In src/mailman/handlers/mime_delete.py we have: cmd = os.popen(config.HTML_TO_PLAIN_TEXT_COMMAND .... We should use the subprocess module instead http://www.python.org/doc/current/lib/module-subprocess.html in cases like this. From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414143 Title: Use subprocess module instead of things like os.popen() To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414143/+subscriptions

2 1

[Bug 1414141] [NEW] Convert the last of the string exceptions in Errors.py to class exceptions
by Sumana Harihareswara May 23, 2015

May 23, 2015

Public bug reported: From http://wiki.mailman.psf.io/DEV/Mailman%203.0?action=diff&rev2=30&rev1=28 -- a TODO for the Mailman 3.x series. ** 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/1414141 Title: Convert the last of the string exceptions in Errors.py to class exceptions To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1414141/+subscriptions

2 1

[Bug 1351312] [NEW] Message acceptance options not working
by John Naggets May 23, 2015

May 23, 2015

Public bug reported: I am testing the two following list config parameters: default_nonmember_action default_member_action and actually the following options do not work: Reject (with notification) and Discard (no notification) It looks like currently only the hold for moderator and accept options are working. Is it possible that these two are not ready yet in the beta4 version of mailman? Furthermore the approval mail to the moderator contains in its body as reason XXX: Reason: XXX I guess this also needs adapting. ** 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/1351312 Title: Message acceptance options not working To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1351312/+subscriptions

2 1

[Bug 1333902] [NEW] Mailman 3.0 goes awry when handling messages in an unexpected format
by NotTheEvilOne May 23, 2015

May 23, 2015

Public bug reported: Hi, This bug report is little bit inaccurate. I had the following situation. I sent a message to Mailman 3 from mutt. I think that this message had no unixfrom header in "email.message.Message". The log file showed an exception thrown at "mailman/cure/runner.py". The exception "AttributeError: class MIMEMultipart has no attribute 'sender'" was caused because "_process_one_file()" of "runner.py" accesses "mailman.email.message.Message.sender" without any validation. The loaded, pickled file contained a "MIMEMultipart" object, the other one a "email.message.Message" as far as I can remember. I have attached a patch that ensures that "runner.py" is handling the expected Mailman "Message" instance but I think this was not the root of the problem. Hope it helps anyway. Best regards and keep up the good work on Mailman 3 ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Patch added: "Ensure runner.py handles a Mailman "Message" instance" https://bugs.launchpad.net/bugs/1333902/+attachment/4138396/+files/0003-mai… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1333902 Title: Mailman 3.0 goes awry when handling messages in an unexpected format To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1333902/+subscriptions

2 1

[Bug 1332922] [NEW] Mailman 3.0 REST API does not support e-mails with uppercase letters
by NotTheEvilOne May 23, 2015

May 23, 2015

Public bug reported: Hi, the following test case resulted in: HTTP/1.0 500 Internal Server Error Username: MyTest e-mail: MyTest(a)domain.invalid 1. Create user curl -v -H "Accept: application/json" -H "Content-type: application/x-www-form-urlencoded" -X POST -d 'email=MyTest@domain.invalid&display_name=MyTest@domain.invalid' http://localhost:8001/3.0/users -> 201 Created DB address contains email "mytest(a)domain.invalid" and _original "MyTest(a)domain.invalid" curl -v -H "Accept: application/json" -H "Content-type: application/x -www-form-urlencoded" -X POST -d 'list_id=some_list.domain.invalid&role=member&subscriber=MyTest(a)domain.invalid' http://localhost:8001/3.0/members -> 500 Internal Server Error No log file contain any exception or error message Workaround available: Using lower-case letters result in a success curl -v -H "Accept: application/json" -H "Content-type: application/x-www-form-urlencoded" -X POST -d 'list_id=some_list.domain.invalid&role=member&subscriber=mymest(a)domain.invalid' http://localhost:8001/3.0/members ** 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/1332922 Title: Mailman 3.0 REST API does not support e-mails with uppercase letters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1332922/+subscriptions

3 2

[Bug 1307644] [NEW] Remove IMailingList.moderator_password
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: This attribute is obsolete and should be removed. ** Affects: mailman Importance: Undecided Assignee: Barry Warsaw (barry) 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/1307644 Title: Remove IMailingList.moderator_password To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1307644/+subscriptions

2 1

[Bug 1292958] [NEW] Precedence: bulk header on subscription confirmation requests can cause request to be mis-classified
by Mark Sapiro May 23, 2015

May 23, 2015

Public bug reported: This may be an issue with gmail and possibly elsewhere. See <https://mail.python.org/pipermail/mailman-users/2014-March/076294.html> ** 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/1292958 Title: Precedence: bulk header on subscription confirmation requests can cause request to be mis-classified To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1292958/+subscriptions

3 2

[Bug 1285496] [NEW] A test in src/mailman/model/docs/registration.rst fails if Python default encoding is UTF-8
by Mark Sapiro May 23, 2015

May 23, 2015

Public bug reported: The Invalid email addresses section in the doctests in src/mailman/model/docs/registration.rst attempts to register various invalid email addresses and checks that they are rejected. In particular, the test >>> registrar.register(mlist, '\xa0(a)example.com') Traceback (most recent call last): ... InvalidEmailAddressError: \xa0(a)example.com will fail if python's sys.getdefaultencoding() returns 'UTF-8' because the invalid address is reported with the UTF-8 encoding of nonbreaking space rather than \xa0. ** 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/1285496 Title: A test in src/mailman/model/docs/registration.rst fails if Python default encoding is UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1285496/+subscriptions

2 1

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

May 23, 2015

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

4 5

[Bug 1197473] [NEW] moderating usenet->mailman posts
by Karl Berry May 23, 2015

May 23, 2015

Public bug reported: In http://www.mail-archive.com/mailman-users%40python.org/msg62889.html, I explained the (very strong) desirability of having posts made from Usenet to Mailman be subject to normal moderation rules instead of automatically and unconditionally approved. (In short, to not let Usenet spam through to the mailing lists without any checking.) In his reply, http://www.mail-archive.com/mailman- users%40python.org/msg62890.html, Mark gave a simple one-line change (that is working fine so far as we can tell). When I asked, Mark told me that the change couldn't be made for mailman 2.1, since it would need to be a user option and thus have i18n impact, so suggested that I post it here, tagged mailman3, which I hope I've done here. Happy hacking, Karl ** 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/1197473 Title: moderating usenet->mailman posts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1197473/+subscriptions

3 2

[Bug 1190582] [NEW] Add some common filters to REST API resources that expose collections
by Florian Fuchs May 23, 2015

May 23, 2015

Public bug reported: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test(a)example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there are x unadvertised lists in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest ** Description changed: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test(a)example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there are x unadvertised list in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept - a number of common filter params which are used for the WHERE clause of + a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both ** Description changed: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test(a)example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there - are x unadvertised list in the result, the page will only show 10 - x + are x unadvertised lists in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1190582 Title: Add some common filters to REST API resources that expose collections To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1190582/+subscriptions

2 1

[Bug 1170726] [NEW] The LMTP server needs to check acceptable aliases
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: The LMTP server currently does a sanity check on the To field of the incoming message, to ensure that it is addressed to a valid mailing list. This check ignores acceptable aliases, but it should honor them. ** 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/1170726 Title: The LMTP server needs to check acceptable aliases To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1170726/+subscriptions

4 3

[Bug 1170388] [NEW] the tomoderators argument to "send" is ignored
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: searching all the code (mailman-3.0.0b3) (with ack) for "tomoderators" returns this: $ ack -ai tomoderators src/mailman/bin/checkdbs.py 202: msg.send(mlist, **{'tomoderators': True}) src/mailman/chains/hold.py 241: nmsg.send(mlist, **dict(tomoderators=True)) src/mailman/app/moderator.py 228: msg.send(mlist, tomoderators=True) 299: msg.send(mlist, tomoderators=True) I can't see where this option is actually used. In practice, the moderation notification sent from hold.py in line 241 just goes to everyone in the mailing list, not the moderators. ** 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/1170388 Title: the tomoderators argument to "send" is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1170388/+subscriptions

2 3

[Bug 1104505] [NEW] Web posting interface
by Kẏra May 23, 2015

May 23, 2015

Public bug reported: There should be an interface for posting to a list from the Web UI ** Affects: mailman Importance: Undecided Status: New ** Tags: wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1104505 Title: Web posting interface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1104505/+subscriptions

4 5

[Bug 1104484] [NEW] Link to post in email footer
by Kẏra May 23, 2015

May 23, 2015

Public bug reported: With the new web UI, there should be a feature to have message footers include a link to the message in the web UI ** Affects: mailman Importance: Undecided Status: New ** Tags: wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1104484 Title: Link to post in email footer To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1104484/+subscriptions

4 4

[Bug 1096812] [NEW] Threading issues in mailman 3.0.0b2
by David Bell May 23, 2015

May 23, 2015

Public bug reported: I am seeing concurrency issues when using mailman 3 in a threaded application server. Reading the Storm documentation it states that "Store objects are not threadsafe. [...] Therefore, the best policy is usually to create a Store object for each thread which needs one" (https://storm.canonical.com/Manual#Working_with_multiple_threads) In mailman/database/base.py:141 I see a Store being created and cached. As recommended in the storm docs, Stores should not be cached. ** 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/1096812 Title: Threading issues in mailman 3.0.0b2 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1096812/+subscriptions

3 2

[Bug 1096066] [NEW] mailman raises exception if passed message not contains text/plain message part
by Robert Niederreiter May 23, 2015

May 23, 2015

Public bug reported: If message sent to mailman not contains a text/plain message part (i.e. only text/html), an error is raised and the message gets swallowed. I fixed this this way in my setup: === modified file 'src/mailman/rules/approved.py' --- src/mailman/rules/approved.py 2012-07-02 20:08:58 +0000 +++ src/mailman/rules/approved.py 2013-01-04 13:31:09 +0000 @@ -73,6 +73,8 @@ stripped = False for part in typed_subpart_iterator(msg, 'text', 'plain'): break + if not part: + return False payload = part.get_payload(decode=True) if payload is not None: charset = part.get_content_charset('us-ascii') regards, robert ** 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/1096066 Title: mailman raises exception if passed message not contains text/plain message part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1096066/+subscriptions

3 2

[Bug 1023681] [NEW] bin/mailman -C config start does not work with a relativ config path
by AlexanderS May 23, 2015

May 23, 2015

Public bug reported: During testing I encountered, that bin/mailman is not working correctly if you supply a relative path as -C argument. For the main process the path is converted into a absolute path during startup but the bin/master process is getting the relative filename but maybe a different working directory. The attached patch fixes that behavior by supplying the generated absolute pathname to the new process. ** 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/1023681 Title: bin/mailman -C config start does not work with a relativ config path To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1023681/+subscriptions

4 4

[Bug 998949] [NEW] Admin notice of held subscription is not fully in list's preferred language.
by Mark Sapiro May 23, 2015

May 23, 2015

Public bug reported: When admin_immed_notify is Yes and subscribe_policy is approve, the Subject: of the notice to the admin is in the user's preferred language rather than the list's preferred language and it may not be properly RFC 2047 encoded. ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman/2.1 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Affects: mailman/3.0 Importance: Undecided Status: New ** Tags: mailman3 ** Also affects: mailman/2.1 Importance: Undecided Status: New ** Also affects: mailman/3.0 Importance: Undecided Status: New ** Tags added: mailman3 ** Changed in: mailman/2.1 Importance: Undecided => Medium ** Changed in: mailman/2.1 Status: New => In Progress ** Changed in: mailman/2.1 Milestone: None => 2.1.15 ** Changed in: mailman/2.1 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/998949 Title: Admin notice of held subscription is not fully in list's preferred language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/998949/+subscriptions

3 4

[Bug 987031] [NEW] archival hashes can be shortened
by Jeff Breidenbach May 23, 2015

May 23, 2015

Public bug reported: The draft for archival hashes for mailman specifies 32 character, base 32 encoding. We can get away with 13 characters which expects the first collision at around 50 billion messages. The the wikipedia charts in their "birthday attack" article. It's not like an occasional collision is a big deal and this is not a security issue. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** 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/987031 Title: archival hashes can be shortened To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987031/+subscriptions

2 1

[Bug 856004] [NEW] "OperationalError: database is locked" encountered under very light load while using REST API
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: I've seen this error twice while running integration tests (of our own application) that access Mailman 3 using the API. The load on Mailman is very light, as all requests made to the API are serial, never in parallel. Of course the various processing queues in MM3 are separate processes and could be doing work concurrently. The platform is Centos 6. Traceback (most recent call last): File "/usr/lib64/python2.6/wsgiref/handlers.py", line 93, in run self.result = application(self.environ, self.start_response) File "/home/sgoss/mailman_clone/src/mailman/rest/wsgiapp.py", line 63, in __call__ config.db.commit() File "/home/sgoss/mailman_clone/src/mailman/database/stock.py", line 70, in commit self.store.commit() File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/store.py", line 122, in commit self._connection.commit() File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 126, in commit self.raw_execute("COMMIT", _end=True) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/database.py", line 321, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/database.py", line 366, in _check_disconnect return function(*args, **kwargs) OperationalError: database is locked The backend here is SQLite, which falls over very quickly under concurrent load. If the goal here is to create a stable mailing list server, maybe SQLite is a poor default. ** 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/856004 Title: "OperationalError: database is locked" encountered under very light load while using REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/856004/+subscriptions

3 8

[Bug 827547] [NEW] KeyError in "virgin" runner.
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: Not sure what caused this error that showed up in mailman.log: Aug 16 10:54:50 2011 (31400) Uncaught runner exception: u'foo.example.com' Aug 16 10:54:50 2011 (31400) Traceback (most recent call last): File "/home/sgoss/mailman_clone/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/runners/virgin.py", line 37, in _dispose process(mlist, msg, msgdata, 'virgin') File "/home/sgoss/mailman_clone/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/pipeline/cook_headers.py", line 360, in process process(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/pipeline/cook_headers.py", line 202, in process listinfo = mlist.script_url('listinfo') File "/home/sgoss/mailman_clone/src/mailman/model/mailinglist.py", line 243, in script_url return urljoin(self.domain.base_url, target + '/' + self.fqdn_listname) File "/home/sgoss/mailman_clone/src/mailman/model/mailinglist.py", line 227, in domain return getUtility(IDomainManager)[self.mail_host] File "/home/sgoss/mailman_clone/src/mailman/model/domain.py", line 142, in __getitem__ raise KeyError(email_host) KeyError: u'foo.example.com' ** 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/827547 Title: KeyError in "virgin" runner. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/827547/+subscriptions

3 8

[Bug 1191911] [NEW] [feature-request] calendar appointments support
by Alexander Adolf May 23, 2015

May 23, 2015

Public bug reported: This is an feature proposal/enhancement request. I am running standardisation groups, and often schedule conference calls, Web meetings, etc. To invite the working group members, I add a mailman list as an invitee to the calendar appointment on my calendar. That way, everybody on the list gets and invitation, and also update emails are delivered when I drag the appointment around on my calendar. Everyone stays in sync. Nice. I don't care who of the list members actually accepts the appointment, because the dates are fixed by other means beforehand (e.g. doodle.com). But of course I never see any accept/decline responses. This causes my calendaring app to consider the appointments as "unconfirmed" since none of the invitees has confirmed their participation. I hence have to manually edit such appointments in order to make them show up as "confirmed, busy". To alleviate this. it would be awesome if mailman could optionally be configured to automatically respond to the sender of an email containing a calendar appointment, and accept the invitation. Maybe this could fit in the content filtering section? That way, mailman operated lists would confirm their attendance on behalf of their members, and the calendar appointment on the organiser's calendar would have the proper status. ** Affects: mailman Importance: Undecided Status: New ** Tags: feature-request -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1191911 Title: [feature-request] calendar appointments support To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1191911/+subscriptions

3 3

[Bug 1082495] [NEW] Support bracketed prefixes in subject as filters
by Gordon P. Hemsley May 23, 2015

May 23, 2015

Public bug reported: Many large mailing lists use bracketed prefixes in subjects as a way to filter messages into smaller buckets, allowing some subscribers to read all mail sent to the list while allowing others to filter messages (in their mail client) to read only the messages they are interested in. For example, the W3C's www-style mailing list uses these tags to filter messages based on which CSS spec they refer to. Thus, a subject line that begins "[css3-fonts]" will be assumed to be about only the css3-fonts spec, with a target audience of only those interested in that particular spec and not, say, the css3-flexbox spec (whose subject lines would be prefixed with "[css3-flexbox]"). To handle this, the Mailman archive interface would provide an option to filter only on particular prefixes (as well as messages that don't have any prefixes), allowing a user of the archive to use it as they otherwise would, but filtering the output such that they only see the messages they want to see, instead of the whole archive. In addition, it would be helpful to allow mailing lists to automatically prefix subject lines when the message is sent to an e-mail address using a plus alias. For example, sending mail to www-style+css3-fonts(a)w3.org would prefix the subject line of the message with "[css3-fonts]" in the message sent to subscribers and in the archive, whereas sending mail to www- style+css3-flexbox(a)w3.org would prefix the message with "[css3-flexbox]". It should also be allowed to have multiple prefixes on a message, and having such messages be treated as if they had any prefix individually. In terms of plus aliasing, there are two ways to handle it: (1) allow aliases to specify multiple prefixes in a plus alias using some separator (e.g. a comma: www-style+css3-fonts,css3-flexbox(a)w3.org); or (2) detecting and intercepting when a single message was sent to multiple e-mail addresses with different plus aliases for a single mailing list (e.g. sending the same e-mail to both www- style+css3-fonts(a)w3.org and www-style+css3-flexbox(a)w3.org), treating it as a single message with multiple subject prefixes when sent to subscribers or stored in the archive. Now, I understand that this is likely a huge undertaking, but I think it would go a long way to helping users with large and diverse mailing lists. ** 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/1082495 Title: Support bracketed prefixes in subject as filters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1082495/+subscriptions

6 9

[Bug 1070064] [NEW] Add a 'policy' command
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: It would be kind of nice for MM3 to implement a 'policy' command. If you issue this email command, you would receive a response containing an admin supplied policy text. This response should adhere to the general grace period timeouts, and the text should be retrieved via the generalized url retrieval and caching machinery. This way, the same policy text could be retrievable via email command or web ui. There should be a way to request policy documents in multiple languages. ** Affects: mailman Importance: Wishlist Status: New ** Tags: mailman3 ** Changed in: mailman Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1070064 Title: Add a 'policy' command To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1070064/+subscriptions

2 1

[Bug 956384] [NEW] Continuous integration and real-world testing
by Andrea Crotti May 23, 2015

May 23, 2015

Public bug reported: This is not a real bug, I would just like to start a discussion about what can be done to set up a continuos integration system. Is there any Jenkins server which can be used? Another thing which I was thinking is if we have some real tests on real systems with various MTA such as Postfix/Exim. I haven't tried it yet but it seems that http://vagrantup.com/ and puppet could really be very nice tools for the job. And we could then 1. fire up a VM 2. install the different MTAs 3. create some complicated mailing lists and check that everything works correctly Other ideas? ** 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/956384 Title: Continuous integration and real-world testing To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/956384/+subscriptions

3 4

[Bug 1076152] [NEW] Review RFC 6783 for any needed changes
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: http://www.rfc-editor.org/rfc/rfc6783.txt Mailing Lists and Non-ASCII Addresses This needs to be reviewed for relevance to Mailman 3, likely with separate bugs for any needed changes. ** Affects: mailman Importance: Low Status: Triaged ** 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/1076152 Title: Review RFC 6783 for any needed changes To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1076152/+subscriptions

2 1

[Bug 1035061] [NEW] setup.py build_sphinx is broken
by Stephen Turnbull May 23, 2015

May 23, 2015

Public bug reported: Like this: steve@turnbull:~/src/Mailman3/mailman-trunk$ python setup.py build_sphinx usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'build_sphinx' For more information (version, configuration, and build log), see Bug #1035057. ** 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/1035061 Title: setup.py build_sphinx is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035061/+subscriptions

4 4

[Bug 1035021] [NEW] Referring people to launchpad for lazr.config docs is rude
by Stephen Turnbull May 23, 2015

May 23, 2015

Public bug reported: I suggest snarfing their docs, and rewriting them from a user's point of view. Feel free to assign it to me. :-) ** 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/1035021 Title: Referring people to launchpad for lazr.config docs is rude To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035021/+subscriptions

3 3

[Bug 1004056] [NEW] ability to add administrator via command line
by Jeff Marshall May 23, 2015

May 23, 2015

Public bug reported: How do I add another person as an administrator to either a single >list or to my full mailman installation? I don't see this in either >Postorius or the command line tools. It would be useful to have a command line interface for adding extra administrators to a mailing list. It could either be added: 1) to the existing 'members' subcommand as an additional option on the --add command (like --admin --add blah(a)blah.com) 2) to the existing 'members' subcommand as a separate post-add step (step 1: --add blah(a)blah.com step 2: --admin blah(a)blah.com to add admin rights to that existing subscriber) 3) a new subcommand #2 seems like a reasonable approach. #1 is limited because you could only give admin rights when first adding a user. ** 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/1004056 Title: ability to add administrator via command line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1004056/+subscriptions

3 2

[Bug 975708] [NEW] Switch to the `requests` package
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: The `requests` package <http://pypi.python.org/pypi/requests/0.11.1> was all the rage at Pycon 2012. Seems like it could replace the use of several similar packages like httplib2, urllib2, etc. For future investigation. ** Affects: mailman Importance: Low Status: Triaged ** 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/975708 Title: Switch to the `requests` package To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975708/+subscriptions

2 1

[Bug 975707] [NEW] Investigate something like ZeroMQ
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: At Pycon, we talked about the need for the core to potentially push data to Postorius, HyperKitty, and other components. It makes much more sense for the core to be capable of publishing events and data to a messaging system like ZeroMQ, which those other components could subscribe to. This is a placeholder for future investigation. ** Affects: mailman Importance: Low Status: Triaged ** 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/975707 Title: Investigate something like ZeroMQ To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975707/+subscriptions

2 1

[Bug 975705] [NEW] Rip out or redesign the topic system
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: At Pycon, it was observed that the topic system as it exists in mm2.1 isn't really all that useful. Terri had some thoughts about that in regards to work that Systers did. This is mostly a placeholder for future ideas and to get it out of my TODO list. :) ** Affects: mailman Importance: Low Status: Triaged ** 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/975705 Title: Rip out or redesign the topic system To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975705/+subscriptions

4 4

[Bug 975703] [NEW] -d should (maybe) be the default for `bin/mailman create`
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: `bin/mailman create` has a -d option which says to create the domain of the new mailing list's posting address if it doesn't already exist. At Pycon it was observed that it was kind of silly to always have to specify -d and that maybe it should be the default. The reason I didn't do that was because of typos, which would be a bit of work to undo. Maybe once we have list renaming exposed, this would be useful. But I'm still not sure. ** Affects: mailman Importance: Low Status: Triaged ** 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/975703 Title: -d should (maybe) be the default for `bin/mailman create` To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975703/+subscriptions

2 1

[Bug 975702] [NEW] Implement a pipeline in other runners
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: Stephen observed that it might be useful to implement a pipeline of handlers (even chain processing?) for other runners such as archive, bounce, and command. This is probably not something for 3.0 final, thus I'm marking it triaged,low. But it's an interesting idea and may lead to other useful refactoring. ** Affects: mailman Importance: Low Status: Triaged ** 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/975702 Title: Implement a pipeline in other runners To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975702/+subscriptions

3 2

[Bug 973790] [NEW] 'approved' rule should not modify the message
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: In Mailman 3, technically rules should not have side effects. The 'approved' rule breaks this because it removes the Approved header (and other supported headers) from the message. There should instead be a handler that does the header cleaning, and the rule should not do this. >From an implementation standpoint, the same code can be used in both the handler and in the rule. You can use a slightly different API wrapper and use a flag to indicate whether the header should be removed or not. OTOH, some clever refactoring might make better sense. ** 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/973790 Title: 'approved' rule should not modify the message To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/973790/+subscriptions

3 3

[Bug 967954] [NEW] IMessageStore should be exposed as a top level REST resource
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: At the simplest, it should support GET on a Message-ID or X-Message-ID- Hash value and return the bytes of the stored message, or 404. ** 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/967954 Title: IMessageStore should be exposed as a top level REST resource To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967954/+subscriptions

2 3

[Bug 953531] [NEW] Add graphs of the overall architecture
by Andrea Crotti May 23, 2015

May 23, 2015

Public bug reported: Adding to the documentation some graphs in graphviz format. ** 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/953531 Title: Add graphs of the overall architecture To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/953531/+subscriptions

4 5

[Bug 937154] [NEW] bin/disabled.py is nonfunctional
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: The bin/disabled.py script needs tests, documentation, and fixing in Mailman 2. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Tags: mailman3 ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Milestone: None => 3.0.0b1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/937154 Title: bin/disabled.py is nonfunctional To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/937154/+subscriptions

4 8

[Bug 889635] [NEW] Per-list configurable message headers for digests
by Joseph Fall May 23, 2015

May 23, 2015

Public bug reported: Digest messages are sent out with a partial set of headers for each message. The list of headers kept for each plain-text digested message is configured by the setting: PLAIN_DIGEST_KEEP_HEADERS = [ 'Message', 'Date', 'From', 'Subject', 'To', 'Cc', 'Message-ID', 'Keywords', 'Content-Type', ] My users are very perplexed and frustrated by the e-mail headers included in the digest - in particular, the Message-ID and Content-Type are meaningless, and the To header is repetitive. All this "noise" clutters up the content and makes the digest harder to read. Given that this is a plain-text digest, with the headers listed in the message body, I don't really see an RFC issue here? Yet they can only be configured using a list-wide override in mm_cfg.py I would be willing to work on this to allow a list admin to override the plain digest headers using the web interface, but want to hear from the development team if this is a patch they would be willing to consider before I invest the time. thanks. ** 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/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions

4 7

[Bug 885715] [NEW] Mailman should add a Received header
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: When the LMTP runner or any other injection vector receives a message, it should add a Received header to indicate the time at which Mailman got the message. Use case: there is a spam filter between the incoming MTA and Mailman, and the message sits in the spam filter for a while before its administrator accepts the message. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** 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/885715 Title: Mailman should add a Received header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/885715/+subscriptions

2 3

[Bug 869347] [NEW] bin/test script fails unless zope.testrunner is pip installed
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: I am running Mailman 3 in a virtualenv with most of its package dependencies installed through pip. In this particular configuration, if I run `buildout`, the test script that is created cannot seem to load zope.testrunner properly: $ bin/test -vv Traceback (most recent call last): File "bin/test", line 35, in <module> import zope.testrunner ImportError: No module named testrunner The workaround is to remove the eggs folder, pip install zope.testrunner, and then re-run buildout. ** 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/869347 Title: bin/test script fails unless zope.testrunner is pip installed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869347/+subscriptions

3 3

[Bug 837700] [NEW] Issues with users subscribed via their preferred address
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: You can subscribe an address to a mailing list, and you can subscribe a user to a mailing list, if the user has a preferred address. There are two problems with this. * You can actually end up getting doubly subscribed (i.e. same address with the same role). Normally, the subscription mechanism prevents you from subscribing the same address with the same role more than once, or the same user with the same role more than once. However, if you subscribe once by the address, and once by the user whose preferred address is that same address, the double subscription occurs. * The Member repr() doesn't distinguish between a member that's subscribed via explicit address, and one that's subscribed via preferred address. This means that the above will appear as a double address subscription, when it's really not. Are these substantial problems that need to be fixed? Almost certainly the second one does, but I haven't come up with an elegant repr() for the case of a user subscribed with their preferred address. ** Affects: mailman Importance: Low 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/837700 Title: Issues with users subscribed via their preferred address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/837700/+subscriptions

2 2

[Bug 793669] [NEW] feature request. change the 'list my other subscriptions' to also report if the other subscriptions are enabled or disabled
by Laura Creighton May 23, 2015

May 23, 2015

Public bug reported: I have a large number of subscriptions to mailing lists on python.org. Delivery is disabled on most of them. This is exactly how I want it -- I don't want to keep up with the day to day matters of the list, but I do want to be able to re-anable delivery and discuss things there should the need arise without having to create a new account. However, when I go on vacation, what I want to do is also disable a few high volume lists that I normally want to read every day. Thus what I would really like to see is which lists are currently enabled, so I can decide which one(s) if any I want to disable for the vacation. I don't want to disable the low-volume ones. Given that I am going to have to re-enable the lists I want to read when I get back one by one, I want the number of lists that get temporarily disabled to be as small as possible. And I want to be able to email me the short list of what they were so I can remember which ones to turn on again. Interestingly, the text of the message indicates a usability misunderstanding, and a grammatical error. The text reads: You can view a list of all the other mailing lists at python.org for which you are a member. Use this if you want to make the same membership option changes to this other subscriptions. It should be 'these other subscriptions'. And the people who want to make the same membership option changes to all the lists they are subscribed to on a site are precisely the users who don't need the feature. They can blindly go off and change things globally. If the number of lists they are subscribed to on that site is 1 -- i.e. they do not have any other subscriptions -- then saying to do things globally will do no harm. The reason you might want to look is to check because you might _not_ want to do things globally. And once you are dealing with that case, things you do not want to do globally, then of course you want to see the current settings that you have. But for my use case, all I care about is changing delivery status. All the other options I either never change, or want to change globally. I suspect that most people use mailing lists in this way, where the only thing they need to worry about is changes due to vacation, but I haven't conducted any polls to test this theory. This request sent to the tracker because the automated mail I recevied when some moderator refused to accept my mail to mailman-dev with this feature request, with the message 'why don't you just disable delivery globally and then reset them globally when you return' said that this was the place for feature requests and not the mailing list. Hope this request is clearer and explains why globally disabling is not what I want to do. Thank you ** 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/793669 Title: feature request. change the 'list my other subscriptions' to also report if the other subscriptions are enabled or disabled

4 9

[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 881320] [NEW] Mailman 3 translations
by Vincent Fretin May 23, 2015

May 23, 2015

Public bug reported: In mailman 3.0.0a8, the locales directory contains actually mailman 2 translations. The unsubscribe mail is not translated into French because the msgids are different between mailman2 and mailman3. Do you have a script to generate a pot file and sync the po files? I had to generate myself the French mo file from the po. It's maybe a good idea to include mo files in the sdist, or generate mo files at mailman startup. ** 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/881320 Title: Mailman 3 translations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881320/+subscriptions

4 5

[Bug 1042828] [NEW] UI web URLs should be per-mailinglist
by Richard Wackerbarth May 23, 2015

May 23, 2015

Public bug reported: The web URL needs to be attached to the individual mailing lists and not to the email domain. However, for ease of configuration, and following DRY principals, default values should be derived from the list hierarchy. As an example use case, consider: The mail server is run by an umbrella organization. Each of the groups under the umbrella has its own website. Some of those might be co-hosted from the same server, but others could be elsewhere. Each group wants it to appear as if they are "stand alone", providing UI access to the mailing list functions from their individual websites rather than from that of the umbrella organization. ** 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/1042828 Title: UI web URLs should be per-mailinglist To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1042828/+subscriptions

3 5

[Bug 987019] [NEW] special case archive@mail-archive.com
by Jeff Breidenbach May 23, 2015

May 23, 2015

Public bug reported: As discussed, confusion can arise between the archiving module for mailman, and the manual mechanism of adding the archiving subscriber. Do something, perhaps involving ban lists, to keep us out of trouble. (I don't really know what is most sensible. I'd always imagined the archiving module would simply be adding the special subscriber address, but that's not the way it turned out.) ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** 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/987019 Title: special case archive(a)mail-archive.com To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987019/+subscriptions

3 2

[Bug 985149] [NEW] Add List-Post value to permalink hash input
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: Currently, we define the X-Message-ID-Hash as the base32 encoding of the sha1 hash of the Message-ID content (sans angle brackets as defined in RFC 5322). The suggestion is made that List-Post value should be added to this hash so as to be able to distinguish cross-posted messages. This should be fine, and pretty easy. My only concern is that the header name is now a misnomer. I wonder, is it worth coming up with a better header? Now's the time to do it since it's likely that there are almost no consumers of this standard. What about `Permalink-Hash` ? ** Affects: mailman Importance: High 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/985149 Title: Add List-Post value to permalink hash input To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/985149/+subscriptions

4 7

[Bug 982555] [NEW] LMTP should reject unknown lists in RCPT-stage
by Bernhard Schmidt May 23, 2015

May 23, 2015

Public bug reported: At the moment the LMTP runner rejects mails to non-existing lists after the DATA stage. # telnet localhost 8024 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.svr02.mucip.net Python LMTP runner 1.0 MAIL FROM: <berni(a)birkenwald.de> 250 Ok RCPT TO: <thislistdoesnotexist(a)birkenwald.de> 250 Ok DATA 354 End data with <CR><LF>.<CR><LF> Message-ID: <bal(a)blubb.de> as . 550 Requested action not taken: mailbox unavailable It should reject invalid addresses in the RCPT TO stage, this way it could easily be used with Postfix' feature "reject_unverified_recipient" to avoid accepting and then bouncing messages. ** 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/982555 Title: LMTP should reject unknown lists in RCPT-stage To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/982555/+subscriptions

4 3

[Bug 975711] [NEW] Store the list style in the mailinglist table
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: It seems useful to record the list style that was used to create the mailing list. Maybe this could be used later to propagate changes in the style to lists that were created with it. The problem is that the style machinery is way to over-engineered. There's actually a priority system for applying a style to a mailing list. This should be simplified anyway, and then we could store the style name in the database. It makes no sense to do this with the complicated scheme currently used. ** Affects: mailman Importance: High 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/975711 Title: Store the list style in the mailinglist table To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975711/+subscriptions

2 1

[Bug 975670] [NEW] Documentation fails to specifying sphinx requirement
by Richard Wackerbarth May 23, 2015

May 23, 2015

Public bug reported: Sphinx is required to build the documentation. However, it is not automatically installed and the installation documentation fails to instruct that it be installed before building the online docs. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** 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/975670 Title: Documentation fails to specifying sphinx requirement To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975670/+subscriptions

5 6

[Bug 965520] [NEW] Improve installation documentation
by Barry Warsaw May 23, 2015

May 23, 2015

Public bug reported: This page: http://packages.python.org/mailman/src/mailman/docs/START.html describes how to install, configure, and start Mailman 3. It's a bit sparse and out-of-date. For example, it doesn't describe all the locations that mailman.cfg is search for. It also doesn't describe installing and running mm3 in a virtualenv. This would make a nice bite-sized bug for someone wanting to contribution to Mailman. ** Affects: mailman Importance: Undecided Status: New ** Tags: documentation easy mailman3 ** Tags removed: bite-size ** Tags added: easy -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/965520 Title: Improve installation documentation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/965520/+subscriptions

6 12

[Bug 881316] [NEW] RuntimeError: maximum recursion depth exceeded while pickling an object
by Vincent Fretin May 23, 2015

May 23, 2015

Public bug reported: With mailman 3.0.0a8. I got the following traceback from a html mail with html signature+image from Outlook, Oct 14 09:21:31 2011 (17579) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/chains/hold.py", line 245, in _process nmsg.send(mlist, **dict(tomoderators=True)) File "/home/zope/mailman/src/mailman/email/message.py", line 198, in send self._enqueue(mlist, **_kws) File "/home/zope/mailman/src/mailman/email/message.py", line 216, in _enqueue virginq.enqueue(self, **str_keywords) File "/home/zope/mailman/src/mailman/core/switchboard.py", line 133, in enqueue msgsave = cPickle.dumps(_msg, protocol) RuntimeError: maximum recursion depth exceeded while pickling an object It's really an obscure issue for me. I resolved it by adding sys.setrecursionlimit(10000) in src/mailman/core/switchboard.py before msgsave = cPickle.dumps(_msg, protocol) line 134 and doing bin/mailman unshunt fixed the issue. By default sys.getrecursionlimit() returns 1000. If you want to have a test email to reproduce, I can ask my customer to send an email to a test mailing-list. ** 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/881316 Title: RuntimeError: maximum recursion depth exceeded while pickling an object To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881316/+subscriptions

4 6

[Bug 881312] [NEW] Properly decode payload
by Vincent Fretin May 23, 2015

May 23, 2015

Public bug reported: With mailman 3.0.0a8 in src/mailman/runners/command.py, there is an issue with body = part.get_payload(decode=True) if you send a mail to test-unsubscribe(a)example.com, with accents in the mail, in the signature for example, you get a body string encoded in iso-8859-1. When you try to concatenate iso-8859-1 string with unicode, this the case when the mail body with "Unprocessed:" and "Ignored:" is generated, you get a UnicodeDecodeError ascii. The code should be modified to correctly decode the mail body like it is done in src/mailman/pipeline/decorate.py mcset = msg.get_content_charset() or 'us-ascii' unicode(msg.get_payload(decode=True), mcset) There are similar issues in src/mailman/rules/administrivia.py with the line: if line == '': where it give you a warning because it compare an iso to an empty unicode. and in src/mailman/rules/approved.py where it simply crashes: Oct 18 17:54:41 2011 (18207) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 65, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/zope/mailman/src/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in position 14: invalid continuation byte Currently, mailman is unusable for another language than English, like French. ** 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/881312 Title: Properly decode payload To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881312/+subscriptions

4 6

[Bug 826861] [NEW] doctests failing on Centos 6 due to "unprintable" error objects
by Stephen A. Goss May 23, 2015

May 23, 2015

Public bug reported: On Centos 6 (64 bit), the following tests fail due to what looks like some kind of Python object printing quirk with the version that ships with RHEL 6 and derivatives: src/mailman/model/docs/membership.txt src/mailman/model/docs/users.txt The errors all look like this: File "/home/sgoss/mailman_clone/src/mailman/model/docs/membership.txt", line 296, in membership.txt Failed example: gwen_member.address = new_address Differences (ndiff with -expected +actual): Traceback (most recent call last): - ... - UnverifiedAddressError: gperson(a)example.com + File "/usr/lib64/python2.6/doctest.py", line 1248, in __run + compileflags, 1) in test.globs + File "<doctest membership.txt[68]>", line 1, in <module> + gwen_member.address = new_address + File "/home/sgoss/mailman_clone/src/mailman/model/member.py", line 116, in address + raise UnverifiedAddressError(new_address) + UnverifiedAddressError: <unprintable UnverifiedAddressError object> The system reports Python version 2.6.5. This error does not seem to occur with Python 2.7 on Ubuntu 11.04. One possibility is that for some reason when it comes to printing out those error objects, Python doesn't have a default encoding scheme for representing the embedded unicode strings in that particular context (email address in the above example). ** 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/826861 Title: doctests failing on Centos 6 due to "unprintable" error objects To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/826861/+subscriptions

3 7

[Merge] lp:~abompard/mailman/default_languages into lp:mailman
by Aurélien Bompard May 7, 2015

May 7, 2015

Aurélien Bompard has proposed merging lp:~abompard/mailman/default_languages into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~abompard/mailman/default_languages/+merge/216401 This branch adds the default languages that were defined in Mailman 2.1. -- https://code.launchpad.net/~abompard/mailman/default_languages/+merge/216401 Your team Mailman Coders is requested to review the proposed merge of lp:~abompard/mailman/default_languages into lp:mailman.

2 2

[Merge] lp:~abompard/mailman/pgsql_upgrade into lp:mailman
by Aurélien Bompard May 7, 2015

May 7, 2015

Aurélien Bompard has proposed merging lp:~abompard/mailman/pgsql_upgrade into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~abompard/mailman/pgsql_upgrade/+merge/227289 As explained on http://www.mail-archive.com/mailman-developers%40python.org/msg14659.html, the schema upgrade of 20130406 is missing the PostgreSQL part. This branch adds it in a new migration. -- https://code.launchpad.net/~abompard/mailman/pgsql_upgrade/+merge/227289 Your team Mailman Coders is requested to review the proposed merge of lp:~abompard/mailman/pgsql_upgrade into lp:mailman.

2 4

[Merge] lp:~mgill25/mailman/branch2 into lp:mailman
by Manish Gill May 5, 2015

May 5, 2015

Manish Gill has proposed merging lp:~mgill25/mailman/branch2 into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #1165589 in GNU Mailman: "Switchboard fails to log the error message with some exceptions." https://bugs.launchpad.net/mailman/+bug/1165589 For more details, see: https://code.launchpad.net/~mgill25/mailman/branch2/+merge/158359 Bug #1165589 fix -- https://code.launchpad.net/~mgill25/mailman/branch2/+merge/158359 Your team Mailman Coders is requested to review the proposed merge of lp:~mgill25/mailman/branch2 into lp:mailman.

2 1

[Bug 1165589] [NEW] Switchboard fails to log the error message with some exceptions.
by Mark Sapiro May 5, 2015

May 5, 2015

Public bug reported: The Switchboard.finish() method logs an error when attempting to preserve or unlink the .bak file throws an EnvironmentError exception, but the actual error message from the exception isn't logged. This missing information can be quite helpful. ** 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/1165589 Title: Switchboard fails to log the error message with some exceptions. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1165589/+subscriptions

5 9

[Bug 1191796] [NEW] ScriptOptions class can be removed
by Barry Warsaw May 3, 2015

May 3, 2015

Public bug reported: This convenience class is used in fewer places and can probably be removed for use of standard argparse. ** Affects: mailman Importance: Low Status: Triaged ** 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/1191796 Title: ScriptOptions class can be removed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1191796/+subscriptions

3 3

[Bug 1004044] [NEW] BrowserID system does not keep me logged in
by Jeff Marshall April 28, 2015

April 28, 2015

Public bug reported: The BrowserID system on Postorius logs me out all the time, even after just a few page views. I'm constantly having to hit the sign-in button again. If I am trying to perform an administrative function I have to do it very quickly after signing in or else I'm logged out again. There's no error when I get logged out. It simply loses my logged-in state. Creating a superuser account via the command line and logging in that way works flawlessly without any unexpected logouts. The problem is isolated to BrowserID login only. Mac OS X: 10.7.3 Chrome: 19.0.1084.46 (all default settings on the browser) ** Affects: postorius Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004044 Title: BrowserID system does not keep me logged in To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004044/+subscriptions

2 1

[Bug 1004049] [NEW] Held messages show display message body
by Jeff Marshall April 28, 2015

April 28, 2015

Public bug reported: The Held Messages page on Postorius only shows the subject line of the messages. It seems like the body of the message will also be important for reviewing the held message. According to Barry the body of the message, as a text blob, should be accessible via the REST API: http://packages.python.org/mailman/src/mailman/rest/docs/moderation.html ** Affects: postorius Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004049 Title: Held messages show display message body To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004049/+subscriptions

5 8

[Bug 1004051] [NEW] Accepting Held messages results in stack trace
by Jeff Marshall April 28, 2015

April 28, 2015

Public bug reported: I get an error dump whenever I accept a held message on Postorius. The message does get accepted and sends ok. But this error dump is displayed each time: Exception Type: AttributeError Exception Value: 'module' object has no attribute 'successful' Exception Location: /home/marshman/mailman/postorius/src/postorius/views.py in accept_held_message, line 405 ** Affects: postorius Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004051 Title: Accepting Held messages results in stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004051/+subscriptions

2 5

[Bug 1025709] [NEW] When logging in through BrowserID or django.contrib.auth: Create new MM user if none exists
by Florian Fuchs April 28, 2015

April 28, 2015

Public bug reported: Currently user data held by Postorius is not neccessarily connected to Mailman. Once logged in, it should be checked if the user already exists in MM and a new user should be added to via the API if necessary. ** Affects: postorius Importance: Undecided Status: New ** Description changed: Currently user data held by Postorius is not neccessarily connected to - Mailman. Once logged in, it should be checked if the user exists in MM - and add a new user if necessary. + Mailman. Once logged in, it should be checked if the user already exists + in MM and a new user should be added to via the API if necessary. -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1025709 Title: When logging in through BrowserID or django.contrib.auth: Create new MM user if none exists To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1025709/+subscriptions

1 1

[Bug 1027496] [NEW] Check code against pep8 conventions
by Florian Fuchs April 28, 2015

April 28, 2015

Public bug reported: It's a dirty job, but someone's gotta do it. ** Affects: postorius Importance: Undecided Status: In Progress ** Changed in: postorius Status: New => In Progress ** Changed in: postorius Milestone: None => 1.0.0a2 ** Branch linked: lp:~flo-fuchs/postorius/pep8 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1027496 Title: Check code against pep8 conventions To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1027496/+subscriptions

1 2

[Bug 1203359] [NEW] IArchiver.archive_message implementations return None
by Stephen Turnbull April 28, 2015

April 28, 2015

Public bug reported: The Interface sez: def archive_message(mlist, msg): """Send the message to the archiver. :param mlist: The IMailingList object. :param msg: The message object. :returns: The url string or None if the message's archive url cannot be calculated. """ but none of prototype, MHonArch, and mailarchive return anything. I think the Interface should be changed to say ":returns: 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/1203359 Title: IArchiver.archive_message implementations return None To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1203359/+subscriptions

3 3

[Bug 1425359] [NEW] 500 error code shown by postorius instead of 409 error code
by Ankush Sharma April 28, 2015

April 28, 2015

Public bug reported: When a new mailman subscriber is created with the email of an already existing mailman subscriber or user a `409` code with a message `user already exists` is returned by the postorius but when the same email but now case sensitive is used a `500` code with message `server error code` is returned. The latter should also return a `409` instead of `500` as it is misleading. Although the mailman core is giving `AssertionError: User should have had linked address` in both the cases`. ** 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/1425359 Title: 500 error code shown by postorius instead of 409 error code To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1425359/+subscriptions

3 9

[Bug 1423756] [NEW] Ability to define user as domainowner or serverowner
by Andrew Stuart April 28, 2015

April 28, 2015

Public bug reported: I had an idea about rounding out the Mailman permissions model, interested in hearing thoughts on it. Obviously there has been considerable discussion on this topic before. Mailman already carries much of the information needed for determining user permissions to Mailman resources. Only two things are missing: 1: the ability to define a user as being a “serverowner” 2: the ability to define a user as being a “domainowner” (You’ll need to look at this email in plain text to see the table properly). The Mailman permissions model currently looks like this: resource_type roles resource_id user_identifier where to find permission --------------------------------------------------------------------------------------------------------- user userowner n/a UUID (defined in user record) list listowner list_id subscriber (defined in list member record) list listmember list_id subscriber (defined in list member record) list listmoderator list_id subscriber (defined in list member record) list listnonmember list_id subscriber (defined in list member record) I am suggesting adding two further permissions to the existing permissions model, which would look like this: resource_type roles resource_id user_id where to find permission --------------------------------------------------------------------------------------------------------- server serverowner n/a UUID (not currently defined in Mailman) domain domainowner mail_host UUID (not currently defined in Mailman) To implement, it would need to be possible to define as user as being a ‘serverowner’, and also to be able to define a user as being a ‘domainowner’ for any given domain. It should be possible to define multiple user with the serverowner role and it should be possible to define multiple users with the domain owner role. If it were possible to do so within the Mailman core then there would be a completely usable permissions model entirely within Mailman, and no need to store any additional permissions data outside Mailman. The permissions model would allow definition of user access to any Mailman resource including domains and servers. The interpretation of the permissions would still be up to the application that consumes the REST API, as is currently the case. There would need to be methods available via the REST API to: set domainowner role for a user set serverowner role for a user delete domainowner role from a user delete serverowner role from a user find if a specific user holds domainowner find if a specific user holds serverowner role find all domainowners for a domain find all serverowners ** Affects: mailman Importance: Undecided Status: New ** Tags: enhancement 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/1423756 Title: Ability to define user as domainowner or serverowner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1423756/+subscriptions

3 19

[Bug 1420083] [NEW] Provide a reserved url for clearing out the uid table
by Barry Warsaw April 28, 2015

April 28, 2015

Public bug reported: While testing the authenticating REST proxy, it is necessary to clear out the uid table. In normal operation, we never delete rows from this table, to ensure that uids are never duplicated. However, when a user is deleted in the proxy test suite, its uid entry is never cleaned up. This thread discusses several options: http://thread.gmane.org/gmane.mail.mailman.devel/19733 Yet another option would be to expose <api>/reserved/uids/orphans and if you DELETE that resource, all uids not associated with users will be removed from the table. It's a bit crufty in that I think we may be abusing the DELETE method (since <api>/reserved/uids/orphans will still exist after the successful operation), but since this is a testing-only method, I think it's fine. Not sure we need to implement GET, or subresources, but we could if it turns out we need that for testing purposes. Also, DELETEing .../orphans means that the ill effects of accidentally calling this on a real server are minimized. At worst, uids could be reused, but that's unlikely given our use of uuid4(). ** Affects: mailman Importance: High Status: Triaged ** 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/1420083 Title: Provide a reserved url for clearing out the uid table To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1420083/+subscriptions

2 5

[Bug 1419519] [NEW] REST API delete user function does not delete every 2nd linked address
by Andrew Stuart April 28, 2015

April 28, 2015

Public bug reported: The following series of curl commands creates a user with an email address of ‘z(a)example.xn--org-to0a, and then links 10 additional addresses to z(a)example.org curl -X POST --data "email=z(a)example.org&display_name=z" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users curl -X POST --data "email=z1(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z2(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z3(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z4(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z5(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z6(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z7(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z8(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z9(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses curl -X POST --data "email=z10(a)example.org" --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org/addresses A sqlite3 dump of the database shows the following in the addresses table: INSERT INTO "address" VALUES(11,'z(a)example.org',NULL,'z',NULL,'2015-02-08 10:50:37.241724',5,17); INSERT INTO "address" VALUES(12,'z1(a)example.org',NULL,'',NULL,'2015-02-08 10:52:08.928901',5,19); INSERT INTO "address" VALUES(13,'z2(a)example.org',NULL,'',NULL,'2015-02-08 10:52:36.308978',5,20); INSERT INTO "address" VALUES(14,'z3(a)example.org',NULL,'',NULL,'2015-02-08 10:52:43.947229',5,21); INSERT INTO "address" VALUES(15,'z4(a)example.org',NULL,'',NULL,'2015-02-08 10:52:49.598934',5,22); INSERT INTO "address" VALUES(16,'z5(a)example.org',NULL,'',NULL,'2015-02-08 10:52:54.406450',5,23); INSERT INTO "address" VALUES(17,'z6(a)example.org',NULL,'',NULL,'2015-02-08 10:52:59.295078',5,24); INSERT INTO "address" VALUES(18,'z7(a)example.org',NULL,'',NULL,'2015-02-08 10:53:04.892381',5,25); INSERT INTO "address" VALUES(19,'z8(a)example.org',NULL,'',NULL,'2015-02-08 10:53:10.497119',5,26); INSERT INTO "address" VALUES(20,'z9(a)example.org',NULL,'',NULL,'2015-02-08 10:53:16.450507',5,27); INSERT INTO "address" VALUES(21,'z10(a)example.org',NULL,'',NULL,'2015-02-08 10:53:24.021368',5,28); All good at this stage. No problems. The following curl command deletes user ‘z(a)example.xn--org-to0a curl --verbose -X DELETE --header "authorization: Basic cmVzdGFkbWluOnJlc3RwYXNz" http://localhost:8001/3.0/users/z@example.org Strangely, a sqlite3 dump of the database now shows the following in the addresses table: INSERT INTO "address" VALUES(12,'z1(a)example.org',NULL,'',NULL,'2015-02-08 10:52:08.928901',NULL,19); INSERT INTO "address" VALUES(14,'z3(a)example.org',NULL,'',NULL,'2015-02-08 10:52:43.947229',NULL,21); INSERT INTO "address" VALUES(16,'z5(a)example.org',NULL,'',NULL,'2015-02-08 10:52:54.406450',NULL,23); INSERT INTO "address" VALUES(18,'z7(a)example.org',NULL,'',NULL,'2015-02-08 10:53:04.892381',NULL,25); INSERT INTO "address" VALUES(20,'z9(a)example.org',NULL,'',NULL,'2015-02-08 10:53:16.450507',NULL,27); So 6 of the addresses that should have been deleted were deleted, but 5 remain. The linked address deletion seems to be skipping addresses for some reason. It appears the problem is caused by the delete address functionality mutating the iterator of user addresses. This appears to fix the problem, which is in rest/users.py def on_delete(self, request, response): """Delete the named user, all her memberships, and addresses.""" if self._user is None: not_found(response) return for member in self._user.memberships.members: member.unsubscribe() user_manager = getUtility(IUserManager) addresses_for_deletion = [] for address in self._user.addresses: # to avoid mutating the self._user.addresses iterator, create a separate list of addresses addresses_for_deletion.append(address) for address in addresses_for_deletion: user_manager.delete_address(address) user_manager.delete_user(self._user) no_content(response) ** 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/1419519 Title: REST API delete user function does not delete every 2nd linked address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1419519/+subscriptions

2 4

[Bug 1418280] [NEW] "Address already exists" when creating a new user, but user is created anyway
by Andrew Stuart April 28, 2015

April 28, 2015

Public bug reported: When creating a new user via the REST API, if the email address exists, it reports "Address already exists", but it creates the user anyway. After a bit of deep cave diving into the code I suspect it’s this in model/usermanager.py This function appears to create a user before it checks to see if the address exists, with the result that multiple users are created when the address already exists. @implementer(IUserManager) class UserManager: """See `IUserManager`.""" def create_user(self, email=None, display_name=None): """See `IUserManager`.""" user = User(display_name, Preferences()) if email: address = self.create_address(email, display_name) user.link(address) return user this seems to fix the problem - but please don’t trust my solution - needs verification. @implementer(IUserManager) class UserManager: """See `IUserManager`.""" def create_user(self, email=None, display_name=None): """See `IUserManager`.""" if email: address = self.create_address(email, display_name) user = User(display_name, Preferences()) if email: user.link(address) return user ** 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/1418280 Title: "Address already exists" when creating a new user, but user is created anyway To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1418280/+subscriptions

2 4

[Bug 1418276] [NEW] Deleting a user via the REST API does not delete their user preferences
by Andrew Stuart April 28, 2015

April 28, 2015

Public bug reported: The on_delete function in rest/users.py appears to not delete user preferences when the user is deleted resulting in an accumulation of orphaned preferences data. def on_delete(self, request, response): """Delete the named user, all her memberships, and addresses.""" if self._user is None: not_found(response) return for member in self._user.memberships.members: member.unsubscribe() user_manager = getUtility(IUserManager) for address in self._user.addresses: user_manager.delete_address(address) user_manager.delete_user(self._user) no_content(response) ** 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/1418276 Title: Deleting a user via the REST API does not delete their user preferences To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1418276/+subscriptions

5 9

[Bug 1411435] [NEW] installing: TypeError: Can't convert 'NoneType' object to str implicitly
by Sumana Harihareswara April 28, 2015

April 28, 2015

Public bug reported: I am on a stock Ubuntu 14.04 machine (a Digital Ocean virtual server). When I run "mailman start" I get this traceback: $ mailman start Starting Mailman's master runner Traceback (most recent call last): File "/usr/local/bin/mailman", line 9, in <module> load_entry_point('mailman==3.0.0b6', 'console_scripts', 'mailman')() File "/usr/local/lib/python3.4/dist-packages/mailman-3.0.0b6-py3.4.egg/mailman/bin/mailman.py", line 100, in main args.func(args) File "/usr/local/lib/python3.4/dist-packages/mailman-3.0.0b6-py3.4.egg/mailman/commands/cli_control.py", line 138, in process os.execl(*execl_args) File "/usr/lib/python3.4/os.py", line 489, in execl execv(file, args) TypeError: Can't convert 'NoneType' object to str implicitly For reference, my .bash_history (removing the bits where I, e.g., used aptitude to check that I wanted python3-setuptools, and annotating where I got errors): sudo apt-get update sudo apt-get install bzr python-setuptools python-dev build-essential postfix mkdir repos cd repos/ bzr branch lp:mailman bzr branch lp:mailman.client bzr branch lp:postorius bzr branch lp:~mailman-coders/postorius/postorius_standalone cd mailman python setup.py install # got error - it wants Python 3 python3 setup.py install # got ImportError: No module named 'setuptools' sudo apt-get install python3-setuptools sudo python3 setup.py install sudo mailman start (And if I made an error in installing here, please let me know and I'll fix the docs.) ** 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/1411435 Title: installing: TypeError: Can't convert 'NoneType' object to str implicitly To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1411435/+subscriptions

2 3

[Bug 1166911] [NEW] domain option for `bin/mailman lists` doesn't work as expected
by Manish Gill April 28, 2015

April 28, 2015

Public bug reported: (mailman)➜ mailman bin/mailman lists --domain example.cc 4 matching mailing lists found: Test1(a)mail.localhost mytest(a)example.cc test2(a)mail.localhost test3(a)mail.localhost For the above output, only mytest(a)example.cc should've been the output. ** Affects: mailman Importance: Undecided Status: New ** Tags: command-line-scripts easy mailman3 ** Branch linked: lp:~mgill25/mailman/mailman -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1166911 Title: domain option for `bin/mailman lists` doesn't work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1166911/+subscriptions

3 4

[Bug 1021364] [NEW] Catch httplib2 error if REST API is not available
by Florian Fuchs April 28, 2015

April 28, 2015

Public bug reported: httplib2 (used in mailman.client) throws "[Errno 111] Connection refused" if the core api isn't available. This should be turned into a nice error page with a meaningful description (possibly depending on the visiting user's role - details for admins and a more vague error msg for everyone else). ** Affects: mailman.client Importance: Undecided Status: New ** Affects: postorius Importance: Medium Status: Confirmed ** Tags: api ** Description changed: - httplib2 throws "[Errno 111] Connection refused" if the core api isn't - available. + httplib2 (used in mailman.client) throws "[Errno 111] Connection + refused" if the core api isn't available. This should be turned into a nice error page with a meaningful description (possibly depending on the visiting user's role - details for admins and a more vague error msg for everyone else). ** Also affects: mailman.client Importance: Undecided Status: New ** Changed in: postorius Milestone: None => 1.0.0a2 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions

2 6

[Bug 987100] [NEW] enable archival
by Jeff Breidenbach April 28, 2015

April 28, 2015

Public bug reported: Expose mailmans archival booleans as a tristate, either none/private/public or none/local/cloud. ** Affects: postorius Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/987100 Title: enable archival To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/987100/+subscriptions

3 4

[Bug 1004048] [NEW] Able to create superuser with same email as existing BrowserID account
by Jeff Marshall April 28, 2015

April 28, 2015

Public bug reported: I initially connected to Postorius using BrowserID. I then created a superuser from the command line (in dev_setup -> python manage.py createsuperuser). It correctly prevented me from using the existing username, but I was able to use the same email address as my BrowserID account. The superuser account was created and I could log into Postorius successfully. When I then logged back out and logged in via BrowserID I received this error: AuthException at /complete/browserid/ Not unique email address. Request Method: POST Request URL: http://xxxxxxxxxxxxxxxxxx/complete/browserid/ Django Version: 1.3.1 Exception Type: AuthException Exception Value: Not unique email address. Exception Location: /usr/local/lib/python2.7/dist-packages/django_social_auth-0.6.9-py2.7.egg/social_auth/backends/pipeline/associate.py in associate_by_email, line 22 ** Affects: postorius Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004048 Title: Able to create superuser with same email as existing BrowserID account To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004048/+subscriptions

2 1

[Merge] lp:~raj-abhilash1/mailman/docs into lp:mailman
by Abhilash Raj April 18, 2015

April 18, 2015

Abhilash Raj has proposed merging lp:~raj-abhilash1/mailman/docs into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~raj-abhilash1/mailman/docs/+merge/248059 Alembic uses the datatype from mailman.database.types for migrations, which is not desired as they require the field in database to be different( int for Enum() and depending on dailect different for UUID()) -- Your team Mailman Coders is requested to review the proposed merge of lp:~raj-abhilash1/mailman/docs into lp:mailman.

2 1

[Bug 1006356] [NEW] message acceptance settings for list ignored
by Robert Niederreiter April 15, 2015

April 15, 2015

Public bug reported: when setting "hold for moderator" in "Message Acceptance" settings of a list (both cases list member and non list member) the mails get anyway delivered directly without any investigation. ** Affects: postorius Importance: Undecided Status: New ** Tags: list settings -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1006356 Title: message acceptance settings for list ignored To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1006356/+subscriptions

6 5

[Bug 975668] [NEW] mailman.client conflicts with mailman installation
by Richard Wackerbarth March 24, 2015

March 24, 2015

Public bug reported: If mailman.client is loaded as a separate module (as instructed), then mailman cannot exist in the same environment because there are two "mailman" modules to search. I found this when I tried to generate sphinx documentation for mailman after I had installed protorious. To reproduce: mkvirtualenv BUG bzr branch lp:mailman.client cd mailman.client/ python setup.py develop easy_install sphinx cd .. bzr branch lp:mailman cd mailman python bootstrap.py bin/buildout python setup.py build_sphinx Results in: Running Sphinx v1.1.3 Traceback (most recent call last): File "setup.py", line 112, in <module> 'zope.testing<4', File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py", line 152, in setup dist.run_commands() File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/lib/python2.7/site-packages/Sphinx-1.1.3-py2.7.egg/sphinx/setup_command.py", line 140, in run freshenv=self.fresh_env) File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/lib/python2.7/site-packages/Sphinx-1.1.3-py2.7.egg/sphinx/application.py", line 102, in __init__ confoverrides or {}, self.tags) File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/lib/python2.7/site-packages/Sphinx-1.1.3-py2.7.egg/sphinx/config.py", line 216, in __init__ exec code in config File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/mailman/conf.py", line 54, in <module> from mailman.version import VERSION ImportError: No module named version ** 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/975668 Title: mailman.client conflicts with mailman installation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975668/+subscriptions

3 7

[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

[Merge] lp:~abompard/mailman/fix-import-from-mm2 into lp:mailman
by Aurélien Bompard March 16, 2015

March 16, 2015

Aurélien Bompard has proposed merging lp:~abompard/mailman/fix-import-from-mm2 into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~abompard/mailman/fix-import-from-mm2/+merge/250… This branch contains a few fixes for the import-from-mailman2 codepath. -- Your team Mailman Coders is requested to review the proposed merge of lp:~abompard/mailman/fix-import-from-mm2 into lp:mailman.

1 1

[Bug 967951] [NEW] The LMTP runner should reject messages with duplicate Message-IDs
by Barry Warsaw March 6, 2015

March 6, 2015

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

6 8

[Merge] lp:~mgill25/mailman/mailman into lp:mailman
by Manish Gill March 6, 2015

March 6, 2015

Manish Gill has proposed merging lp:~mgill25/mailman/mailman into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #1166911 in GNU Mailman: "domain option for `bin/mailman lists` doesn't work as expected" https://bugs.launchpad.net/mailman/+bug/1166911 For more details, see: https://code.launchpad.net/~mgill25/mailman/mailman/+merge/157920 Fix for #1166911 -- https://code.launchpad.net/~mgill25/mailman/mailman/+merge/157920 Your team Mailman Coders is requested to review the proposed merge of lp:~mgill25/mailman/mailman into lp:mailman.

2 1

[Merge] lp:~raj-abhilash1/mailman/docs-fix into lp:mailman
by Abhilash Raj March 3, 2015

March 3, 2015

Abhilash Raj has proposed merging lp:~raj-abhilash1/mailman/docs-fix into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~raj-abhilash1/mailman/docs-fix/+merge/250092 no need for sudo in virtualenv -- Your team Mailman Coders is requested to review the proposed merge of lp:~raj-abhilash1/mailman/docs-fix into lp:mailman.

2 1

[Bug 1423323] [NEW] Revised Interlingua (ia) translation for Mailman 2.1.19
by Martijn Dekker Feb. 28, 2015

Feb. 28, 2015

Public bug reported: I will am attaching the translation (messages/templates) tarball here, as per the instructions on the wiki. ** Affects: mailman Importance: Undecided Status: New ** Attachment added: "Revised Interlingua (ia) translation for Mailman 2.1.19" https://bugs.launchpad.net/bugs/1423323/+attachment/4322108/+files/mailman-… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1423323 Title: Revised Interlingua (ia) translation for Mailman 2.1.19 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1423323/+subscriptions

3 8

[Bug 1424472] [NEW] pipermail HTML language attribute
by Nemo_bis Feb. 22, 2015

Feb. 22, 2015

Public bug reported: Enhancement request: it would be nice if the HTML archives produced by pipermail had a language attribute, based on the list's default language. For instance <html lang="it"> etc. This would probably make non-English list archives easier to find in search engines. ** Affects: mailman Importance: Undecided Status: New ** Tags: feature i18n indexing language pipermail -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1424472 Title: pipermail HTML language attribute To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1424472/+subscriptions

1 0

[Bug 558249] Re: Host based language selection
by Nemo_bis Feb. 22, 2015

Feb. 22, 2015

** Summary changed: - Host based langage selection + Host based language selection -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558249 Title: Host based language selection To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558249/+subscriptions

1 0

[Merge] lp:~fumiyas/mailman/2.1-ja-messages into lp:mailman/2.1
by SATOH Fumiyasu Feb. 18, 2015

Feb. 18, 2015

SATOH Fumiyasu has proposed merging lp:~fumiyas/mailman/2.1-ja-messages into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~fumiyas/mailman/2.1-ja-messages/+merge/250103 This is a merge request of updateing Japanese translation for Mailman 2.1.19. -- Your team Mailman Coders is requested to review the proposed merge of lp:~fumiyas/mailman/2.1-ja-messages into lp:mailman/2.1.

1 1

[Bug 1287604] [NEW] Enhancement: Sanity Check Subscribers MX Record
by John Howe Feb. 16, 2015

Feb. 16, 2015

Public bug reported: Attempted to path mailman 2.1.17 with a simple MX record check on web- based subscribers. Running Debian 7.4 python 2.7.3-4+deb7u1 python-dns 2.3.6-1+deb7u1 Python-dns installed to /usr/lib/python2.7/dist-packages/DNS Attempted patches follow dragon@quantum:/usr/local/mailman/Mailman/Cgi $ diff subscribe.py subscribe.py.dns 212a213,221 > except Errors.MMBadEmailHostNotFoundError: > results = _("""\ > The email address you supplied is not valid. Host not found.""") > except Errors.MMBadEmailMXRecordNotFoundError: > results = _("""\ > The email address you supplied does not have a MX record.""") > except Errors.MMBadEmailUnknownDNSError: > results = _("""\ > The email address you supplied had some unknown DNS error.""") dragon@quantum:/usr/local/mailman/Mailman $ diff Utils.py Utils.py.dns 40a41 > import DNS 237a239,247 > # MX Record sanity checks > try: > mx_host - DNS.mxlookup(domain_parts) > if len(mx_host) < 1: > raise Errors.MMBadEmailMXRecordNotFoundError, s > except DNS.Base.ServerError: > raise Errors.MMBadEmailHostNotFoundError, s > except: > raise Errors.MMBadEmailUnknownDNSError, s dragon@quantum:/usr/local/mailman/Mailman $ diff Errors.py Errors.py.dns 98a99,110 > class MMBadEmailHostNotFoundError(EmailAddressError): > """Email address domain name does not resolve to a known host.""" > pass > > class MMBadEmailMXRecordNotFoundError(EmailAddressError): > """Email address domain name does not have a MX record.""" > pass > > class MMBadEmailUnknownDNSError(EmailAddressError): > """Email address domain name had unknown DNS error.""" > pass > When running said patches, mailman complained with: admin(13907): [----- Mailman Version: 2.1.17 -----] admin(13907): [----- Traceback ------] admin(13907): Traceback (most recent call last): admin(13907): File "/usr/local/mailman-2.1.17/scripts/driver", line 102, in run_main admin(13907): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(13907): File "/usr/local/mailman-2.1.17/Mailman/Cgi/confirm.py", line 27, in <module> admin(13907): from Mailman import MailList admin(13907): File "/usr/local/mailman-2.1.17/Mailman/MailList.py", line 45, in <module> admin(13907): from Mailman import Utils admin(13907): File "/usr/local/mailman-2.1.17/Mailman/Utils.py", line 41, in <module> admin(13907): import DNS admin(13907): ImportError: No module named DNS admin(13907): [----- Python Information -----] admin(13907): sys.version = 2.7.3 (default, Jan 2 2013, 13:56:14) [GCC 4.7.2] admin(13907): sys.executable = /usr/bin/python admin(13907): sys.prefix = /usr admin(13907): sys.exec_prefix = /usr admin(13907): sys.path = ['/usr/local/mailman-2.1.17/pythonlib', '/usr/local/mailman-2.1.17', '/usr/local/mailman-2.1.17/scripts', '/usr/local/mailman-2.1.17', '/usr/lib/python2.7/', '/usr/lib/python2.7/plat-linux2', '/usr/lib/python2.7/lib-tk', '/usr/lib/python2.7/lib-old', '/usr/lib/python2.7/lib-dynload', '/usr/lib/python2.7/site-packages'] admin(13907): sys.platform = linux2 AFAICS, it seems like Utils.py isn't locating the system wide python-dns library. How do I modify the sys.path to include python-dns under /usr/lib/python2.7/dist-packages? Thanks ** 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/1287604 Title: Enhancement: Sanity Check Subscribers MX Record To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1287604/+subscriptions

2 5

[Merge] lp:~abompard/postorius/include-sdist into lp:postorius
by Aurélien Bompard Feb. 13, 2015

Feb. 13, 2015

Aurélien Bompard has proposed merging lp:~abompard/postorius/include-sdist into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~abompard/postorius/include-sdist/+merge/249486 Easyfix: some additions in MANIFEST.in to include missing files and directories. -- Your team Mailman Coders is requested to review the proposed merge of lp:~abompard/postorius/include-sdist into lp:postorius.

3 2

[Branch ~mailman-coders/mailman.client/trunk] Rev 62: Added missing MANIFEST.in items (Given by Aurélien Bompard).
by noreply＠launchpad.net Feb. 13, 2015

Feb. 13, 2015

Merge authors: Aurélien Bompard (abompard) Related merge proposals: https://code.launchpad.net/~abompard/mailman.client/missing-manifest-includ… proposed by: Aurélien Bompard (abompard) review: Approve - Florian Fuchs (flo-fuchs) ------------------------------------------------------------ revno: 62 [merge] committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Fri 2015-02-13 17:42:23 +0100 message: Added missing MANIFEST.in items (Given by Aurélien Bompard). modified: MANIFEST.in -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Merge] lp:~abompard/mailman.client/missing-manifest-includes into lp:mailman.client
by Aurélien Bompard Feb. 13, 2015

Feb. 13, 2015

Aurélien Bompard has proposed merging lp:~abompard/mailman.client/missing-manifest-includes into lp:mailman.client. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~abompard/mailman.client/missing-manifest-includ… This is a trivial fix: the unittest.cfg and tox.ini files were not included in the sdist tarball, making it impossible to run the unit tests from there. -- Your team Mailman Coders is requested to review the proposed merge of lp:~abompard/mailman.client/missing-manifest-includes into lp:mailman.client.

3 2

[Branch ~mailman-coders/mailman.client/trunk] Rev 61: Documentation: Added a note about using the correct port in testing and production. (Given by Abh...
by noreply＠launchpad.net Feb. 13, 2015

Feb. 13, 2015

Merge authors: Abhilash Raj (raj-abhilash1) Related merge proposals: https://code.launchpad.net/~raj-abhilash1/mailman.client/docs/+merge/249674 proposed by: Abhilash Raj (raj-abhilash1) ------------------------------------------------------------ revno: 61 [merge] committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Fri 2015-02-13 17:35:18 +0100 message: Documentation: Added a note about using the correct port in testing and production. (Given by Abhilash Raj) modified: src/mailmanclient/docs/using.rst -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Merge] lp:~raj-abhilash1/mailman.client/docs into lp:mailman.client
by Abhilash Raj Feb. 13, 2015

Feb. 13, 2015

Abhilash Raj has proposed merging lp:~raj-abhilash1/mailman.client/docs into lp:mailman.client. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~raj-abhilash1/mailman.client/docs/+merge/249674 Add a note about the port 9001 used in docs. -- Your team Mailman Coders is requested to review the proposed merge of lp:~raj-abhilash1/mailman.client/docs into lp:mailman.client.

2 1

[Merge] lp:~abompard/mailman/mailman-no-version-hardcoding into lp:mailman
by Aurélien Bompard Feb. 12, 2015

Feb. 12, 2015

Aurélien Bompard has proposed merging lp:~abompard/mailman/mailman-no-version-hardcoding into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~abompard/mailman/mailman-no-version-hardcoding/… This is a trivial fix: the python version is hardcoded in a doctest. -- Your team Mailman Coders is requested to review the proposed merge of lp:~abompard/mailman/mailman-no-version-hardcoding into lp:mailman.

2 1

[Merge] lp:~abompard/mailman/mailman-templates-utf8 into lp:mailman
by Aurélien Bompard Feb. 11, 2015

Feb. 11, 2015

Aurélien Bompard has proposed merging lp:~abompard/mailman/mailman-templates-utf8 into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~abompard/mailman/mailman-templates-utf8/+merge/… As discussed on the mailing-list in October, the templates should be encoded in UTF-8. (https://mail.python.org/pipermail/mailman-developers/2013-October/023347.ht…) However, the current code does not specify this and relies on locale.getpreferredencoding() returning UTF-8 to read the templates. You can verify this by running the test suite with LANG=C. This branch forces the templates encoding to UTF-8 on read(). -- Your team Mailman Coders is requested to review the proposed merge of lp:~abompard/mailman/mailman-templates-utf8 into lp:mailman.

1 0

[Merge] lp:~sumanah/postorius/copyright-year into lp:postorius
by Sumana Harihareswara Feb. 11, 2015

Feb. 11, 2015

Sumana Harihareswara has proposed merging lp:~sumanah/postorius/copyright-year into lp:postorius. Requested reviews: Florian Fuchs (flo-fuchs) For more details, see: https://code.launchpad.net/~sumanah/postorius/copyright-year/+merge/247377 Update copyright year on source code files to 2015. -- Your team Mailman Coders is subscribed to branch lp:postorius.

2 1

[Bug 266223] Re: Bug with non-ascii characters during subscribe
by Mark Sapiro Feb. 10, 2015

Feb. 10, 2015

*** This bug is a duplicate of bug 1047100 *** https://bugs.launchpad.net/bugs/1047100 ** This bug has been marked a duplicate of bug 1047100 The logger can throw UnicodeEncodeError if the log message is unicode -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266223 Title: Bug with non-ascii characters during subscribe To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266223/+subscriptions

1 0

[Merge] lp:~flo-fuchs/postorius/testing into lp:postorius
by Florian Fuchs Feb. 10, 2015

Feb. 10, 2015

Florian Fuchs has proposed merging lp:~flo-fuchs/postorius/testing into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #1414352 in Postorius: "Improve code coverage by adding tests" https://bugs.launchpad.net/postorius/+bug/1414352 For more details, see: https://code.launchpad.net/~flo-fuchs/postorius/testing/+merge/249215 This branch reworks certain parts of Postorius internal tests: - vcrpy has been added to test those parts of Postorius that rely on a realistic HTTP response from Mailman's administrative API. - A tox config to test different Python and Django versions (currently py27 and Django 1.5 - 1.7) - The package contains a Django settings file for test purposes only, so it can be tested independently from the postorius_standalone branch. - Better developer documentation re how to write new tests. -- The attached diff has been truncated due to its size. Your team Mailman Coders is requested to review the proposed merge of lp:~flo-fuchs/postorius/testing into lp:postorius.

2 1

[Bug 317453] Re: Atom or RSS feeds of Mailing lists
by Hong Xu Feb. 9, 2015

Feb. 9, 2015

I think an additional better feature about this is to add a feed for each thread, thus everyone can just follow a specific thread by subscribing the rss feed. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/317453 Title: Atom or RSS feeds of Mailing lists To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/317453/+subscriptions

1 0

[Bug 1419132] [NEW] An Organization: header is not removed from posts to anonymous lists.
by Mark Sapiro Feb. 7, 2015

Feb. 7, 2015

Public bug reported: Anonymous lists should always remove any Organization: header. Also, there was a bug in the fix for https://bugs.launchpad.net/mailman/+bug/1246039 in that some headers in ANONYMOUS_LIST_KEEP_HEADERS weren't kept if the regexp included the trailing ':'. This is fixed here too. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Committed ** Description changed: Anonymous lists should always remove any Organization: header. Also, there was a bug in the fix for https://bugs.launchpad.net/mailman/+bug/1246039 in that some headers in ANONYMOUS_LIST_KEEP_HEADERS weren't kept if the regexp included the - trailing ':'. This is fixed heare too. + trailing ':'. This is fixed 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/1419132 Title: An Organization: header is not removed from posts to anonymous lists. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1419132/+subscriptions

2 3

[Bug 1418735] [NEW] iso-8859-2 is inappropraite for Romanian - should be utf-8
by Mark Sapiro Feb. 7, 2015

Feb. 7, 2015

Public bug reported: Mailman's use of iso-8859-2 encoding for Romanian is inappropriate. According to wikipedia, <http://en.wikipedia.org/wiki/ISO/IEC_8859-2>, iso8859-2 "can also be used for Romanian, but it is unsuitable for that language, because of lack of letters s and t with commas below, containing s and t with cedillas instead." Mailman's encoding should be changed to utf-8. ** 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/1418735 Title: iso-8859-2 is inappropraite for Romanian - should be utf-8 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1418735/+subscriptions

3 10

[Bug 1418448] [NEW] Change encoding of Russian messages to UTF-8 by default
by Danil Smirnov Feb. 7, 2015

Feb. 7, 2015

Public bug reported: Koi8-r Russian encoding which is used nowadays by Mailman needs to be changed to Unicode. In spite of Koi8-r is most respectful Russian encoding which was in fact standard in ancient times, now it is used on less than 0.1% of sites (http://w3techs.com/technologies/overview/character_encoding/all). Otherwise, UTF-8 become common encoding for every new website/application. Practically, we need to switch to UTF for letting users of Mailman work convenient with bin/scripts in console, which now also Unicode-encoded in most cases. Also most of modern text editors support Unicode by default and may not support other encodings which make editing of template files less convenient and even tricky for some cases. It is not so important for web-interface if we use Russian with English only, as usual. But if we need to put text in several languages on customized pages, we couldn't do this with Koi-8r encoding. ** Affects: mailman Importance: Undecided Status: New ** Tags: i18n -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1418448 Title: Change encoding of Russian messages to UTF-8 by default To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1418448/+subscriptions

3 3

[Bug 1415406] [NEW] Message excerpt corruption on admindb Web UI
by Yasuhito FUTATSUKI＠POEM Feb. 7, 2015

Feb. 7, 2015

Public bug reported: Some messages held on admindb cannot display correctly becase of partial Unicode conversion error or incomplete multi-byte character on mm_cfg.ADMINDB_PAGE_TEXT_LIMIT boundary. Message character corruption has been occured in conditions below. (1) Message charset/encoding is charset/encoding of multi-byte charaters. (2) Message charset/encoding differs from web display charset/encoding. (3) Message contains character that cannot convert to Unicode by using Python codec. or (3') Message body size exceeds mm_cfg.ADMINDB_PAGE_TEXT_LIMIT in bytes after decoding mime and cut down along multi-byte charater's byte sequence. Under these conditions, Unicode error occur in converting message charset/encoding and message has remained not to convert charset/encoding. A patch attached below solves (3) by using decode/encode with 'replace' error handling scheme, and (3') by rounding on character boundary not to exceeds the limit in bytes after character/encoding converted. Note: Even If Message charset/encoding is same as web display charset/encoding, condition (3') may produce invalid html, but patch below don't fix it. ** Affects: mailman Importance: Undecided Status: New ** Attachment added: "patch-admindb-py.txt" https://bugs.launchpad.net/bugs/1415406/+attachment/4307114/+files/patch-ad… -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1415406 Title: Message excerpt corruption on admindb Web UI To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1415406/+subscriptions

2 8

[Bug 1419051] [NEW] Cannot operate on individual messages in moderation queue
by Ralf Jung Feb. 6, 2015

Feb. 6, 2015

Public bug reported: I have two messages from the same sender in the moderation queue, that I want to operate on individually - but the web interface does not let me do that. Steps to reproduce: Send two messages to a list that are both too large. Then open the moderation queue admin website. Actual behavior: I can discard/accept/reject both messages, or none. Expected behavior: I'd like to accept one message (e.g. because the image has been scaled down significantly, but is still a few bytes over our limit) *without* accepting the other. ** 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/1419051 Title: Cannot operate on individual messages in moderation queue To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1419051/+subscriptions

2 1

[Merge] lp:~raj-abhilash1/postorius/bug_1004049 into lp:postorius
by Abhilash Raj Feb. 6, 2015

Feb. 6, 2015

Abhilash Raj has proposed merging lp:~raj-abhilash1/postorius/bug_1004049 into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~raj-abhilash1/postorius/bug_1004049/+merge/2469… Fixes #1004049 -- Your team Mailman Coders is requested to review the proposed merge of lp:~raj-abhilash1/postorius/bug_1004049 into lp:postorius.

3 2

[Merge] lp:~godricglow/postorius/bug_1308219 into lp:postorius
by Pranjal Yadav Feb. 6, 2015

Feb. 6, 2015

Pranjal Yadav has proposed merging lp:~godricglow/postorius/bug_1308219 into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~godricglow/postorius/bug_1308219/+merge/247386 Fixed the bug 1308219 and merged with trunk -- Your team Mailman Coders is requested to review the proposed merge of lp:~godricglow/postorius/bug_1308219 into lp:postorius.

2 1

[Merge] lp:~godricglow/postorius/bug_fix into lp:postorius
by Pranjal Yadav Feb. 6, 2015

Feb. 6, 2015

Pranjal Yadav has proposed merging lp:~godricglow/postorius/bug_fix into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~godricglow/postorius/bug_fix/+merge/247351 Added the previous revisions from main branch and resolved the rendering issue on login page caused by missplaced new line character -- Your team Mailman Coders is requested to review the proposed merge of lp:~godricglow/postorius/bug_fix into lp:postorius.

2 1

[Merge] lp:~godricglow/postorius/bug_login_render_fix into lp:postorius
by Pranjal Yadav Feb. 6, 2015

Feb. 6, 2015

Pranjal Yadav has proposed merging lp:~godricglow/postorius/bug_login_render_fix into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~godricglow/postorius/bug_login_render_fix/+merg… Fixed a rendering bug on login page, corrected missplaced new line character -- Your team Mailman Coders is requested to review the proposed merge of lp:~godricglow/postorius/bug_login_render_fix into lp:postorius.

3 2

[Merge] lp:~godricglow/postorius/bug_1308219_fix into lp:postorius
by Pranjal Yadav Feb. 6, 2015

Feb. 6, 2015

Pranjal Yadav has proposed merging lp:~godricglow/postorius/bug_1308219_fix into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~godricglow/postorius/bug_1308219_fix/+merge/248… Fixed 1308219 by avoiding else loop back and a default new.form() for both moderator and owner after submit click. -- Your team Mailman Coders is requested to review the proposed merge of lp:~godricglow/postorius/bug_1308219_fix into lp:postorius.

3 2