Mailman 3 December 2012 - Mailman-coders

[Bug 881312] [NEW] Properly decode payload
by Vincent Fretin 23 May '15

23 May '15

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 23 May '15

23 May '15

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 1004044] [NEW] BrowserID system does not keep me logged in
by Jeff Marshall 28 Apr '15

28 Apr '15

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 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