Mailman 3 February 2013 - Mailman-coders

[Bug 1004049] [NEW] Held messages show display message body
by Jeff Marshall 28 Apr '15

28 Apr '15

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 28 Apr '15

28 Apr '15

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 28 Apr '15

28 Apr '15

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 28 Apr '15

28 Apr '15

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 1021364] [NEW] Catch httplib2 error if REST API is not available
by Florian Fuchs 28 Apr '15

28 Apr '15

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 28 Apr '15

28 Apr '15

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 28 Apr '15

28 Apr '15

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

[Bug 1006356] [NEW] message acceptance settings for list ignored
by Robert Niederreiter 15 Apr '15

15 Apr '15

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 24 Mar '15

24 Mar '15

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 24 Mar '15

24 Mar '15

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