Mailman 3 March 2012 - Mailman-coders

[Bug 518517] [NEW] Add the equivalent of postconf(1)
by Barry Warsaw April 22, 2014

April 22, 2014

Public bug reported: Postfix has a very handy command called postconf(1) which lets you dump all or one Postfix configuration variable. It would be very handy for Mailman 3 to have something similar. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Also affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged -- Add the equivalent of postconf(1) https://bugs.launchpad.net/bugs/518517 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

5 19

[Bug 869342] [NEW] bootstrap.py fails if buildout already installed in Python environment
by Stephen A. Goss April 15, 2014

April 15, 2014

Public bug reported: If zc.buildout is already installed (say it was pip installed) in Python environment, the bootstrap.py script fails without reasonable explanation: $ python bootstrap.py Traceback (most recent call last): File "bootstrap.py", line 255, in <module> import zc.buildout.buildout ImportError: No module named zc.buildout.buildout This is confusing because you can see that zc.buildout.buildout is available. $ python Python 2.6.5 (r265:79063, Jun 25 2011, 08:36:25) [GCC 4.4.4 20100726 (Red Hat 4.4.4-13)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import zc.buildout.buildout >>> It turns out that if zc.buildout is already available, bootstrap.py does not need to be run, but that is less than obvious to someone who is not intimately familiar with buildout. ** 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/869342 Title: bootstrap.py fails if buildout already installed in Python environment To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869342/+subscriptions

2 2

[Bug 821438] [NEW] REST and Client are missing membership_settings options
by benste March 15, 2014

March 15, 2014

Public bug reported: Using the Python bindings the following things are available at the moment: self_link: u'http://localhost:8001/3.0/members/2' role: u'member' user: u'http://localhost:8001/3.0/users/2' address': u'katie(a)example.com' fqdn_listname': u'testtwo(a)mail.example.com' For better user management the following options should be seen as wishlist: acknowledge_posts hide_address receive_list_copy receive_own_postings delivery_mode delivery_status in addition i requested _User.get_lists which is in https://bugs.launchpad.net/mailmanwebgsoc2011/+bug/821069 + what about users password ? users e-mails ... ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman.client Importance: Undecided Status: Confirmed ** Affects: mailmanwebgsoc2011 Importance: Wishlist Status: Triaged ** Tags: mailman3 ** Changed in: mailman.client Status: New => Confirmed ** Also affects: mailmanwebgsoc2011 Importance: Undecided Status: New ** Also affects: mailman Importance: Undecided Status: New ** Tags added: mailman3 ** Changed in: mailmanwebgsoc2011 Status: New => Triaged ** Changed in: mailmanwebgsoc2011 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/821438 Title: REST and Client are missing membership_settings options To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/821438/+subscriptions

3 6

[Bug 802971] [NEW] Mailman Client doesn't _DOMAIN doesn't offer a list of lists
by benste March 15, 2014

March 15, 2014

Public bug reported: I'd suggest adding a functionalty which would need a domain as param, and return a list of mailing lists associated with this domain. This could be used to display a choice of all available domains on this web_host and allow simple deletition of all mailinglists on this domains in case a domain will ever be deleted. ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman.client Importance: Undecided Status: New ** Affects: mailmanwebgsoc2011 Importance: Wishlist Assignee: benste (benste) Status: Triaged ** Tags: mailman3 ** Also affects: mailman.client Importance: Undecided Status: New ** Also affects: mailman Importance: Undecided Status: New ** 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/802971 Title: Mailman Client doesn't _DOMAIN doesn't offer a list of lists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions

5 9

[Bug 674352] [NEW] List Moderator Login should check for username
by arky March 12, 2014

March 12, 2014

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

3 3

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

Aug. 5, 2013

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

4 7

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

June 20, 2013

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

4 13

[Bug 886296] [NEW] Improve DSN handling for google 'inactive' accounts
by Kevin Fenzi May 30, 2013

May 30, 2013

Public bug reported: The DSN bouncer handler can't seem to parse out when a bounce is generated due to an inactive google account. See attached bounce file for example. ** 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/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/886296/+subscriptions

3 8

[Bug 949924] [NEW] UnicodeDecodeError when delivering message
by Antti Kaihola Sept. 8, 2012

Sept. 8, 2012

Public bug reported: I did a fresh install of Mailman 3.0.0a8 on a Debian Squeeze box, created a list, subscribed a few people and sent a message to the list. The message didn't come through, and var/logs/mailman.log has: Mar 08 13:21:08 2012 (23645) Uncaught runner exception: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) Traceback (most recent call last): File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/mailman/lib/python2.6/site-packages/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/mailman/lib/python2.6/site-packages/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) SHUNTING: 1331212867.805197+9daec32c73ac20978b856348ada1a60fd97a364c The message did contain an u'\xe4' in both the subject and the body. I sent the message using Thunderbird 10.0.2 on Linux Mint 12. ** 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/949924 Title: UnicodeDecodeError when delivering message To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/949924/+subscriptions

5 11

[Bug 967238] [NEW] Expose IMailingList.archive and .archive_private in the REST API
by Barry Warsaw Sept. 8, 2012

Sept. 8, 2012

Public bug reported: Exposing read and write of these attributes would allow Postorius to provide the list owners with some control over archiving for individual lists. This would work as a patch to src/mailman/rest/configuration.py and should be pretty easy to add. ** Affects: mailman Importance: Medium 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/967238 Title: Expose IMailingList.archive and .archive_private in the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967238/+subscriptions

2 6