Mailman 3 November 2011 - Mailman-coders

[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

[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

[Bug 880613] [NEW] PostgreSQL constraints disabled
by Barry Warsaw Nov. 29, 2014

Nov. 29, 2014

Public bug reported: In src/mailman/database/sql/postgres.sql, several foreign key constraints have been commented out because otherwise the test suite, or other aspects do not work. This is probably because there are cases where Mailman violates these constraints, but SQLite3 (the default database) does not care. All disabled constraints are marked with XXX in the above file. Really, these should be fixed. ** Affects: mailman Importance: Medium 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/880613 Title: PostgreSQL constraints disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/880613/+subscriptions

1 2

[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