Mailman 3 April 2011 - Mailman-coders

[Bug 714424] [NEW] Held message user notification should be from -owner, not -bounces
by Mark Sapiro 19 May '12

19 May '12

Public bug reported: If respond_to_post_requests is Yes the notice to the poster of a held post is From: the listname-bounces address. It should be from the listname-owner address. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/714424 Title: Held message user notification should be from -owner, not -bounces

1 1

[Bug 600780] [NEW] Login function needed in rest-client
by Anna 06 Apr '12

06 Apr '12

Public bug reported: For a good, working Mailman 3.0 UI we have to handle the passwords for each user (needed when they subscribe/unsubscribe/want to access their settings page but also for the admins and listowners). Hence, we need to implement the possibility to check for passwords in the rest-client (I believe these are saved in the user table in the core DB) and/or a login function. We should probably use https for the psw authentication. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- Login function needed in rest-client https://bugs.launchpad.net/bugs/600780 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 4

[Bug 685261] [NEW] emailed command in subject header is ignored
by Mark Sapiro 06 Apr '12

06 Apr '12

Public bug reported: For example, a held message notification to the list owner/moderator contains an attached message/rfc822 part with subject "confirm <token>" and this message can be replied to with or without an "Approved: <password>" header/first body line to accept or discard the held message. The code allows for an MUA possibly inserting 'Re:' or some l10n equivalent in the subject making it "Re: confirm <token>", but if the l10n equivalent contains a non-ascii character, the entire command is ignored and the message continues to be held. ** 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/685261 Title: emailed command in subject header is ignored

2 6

[Bug 770328] [NEW] REST qrunner sometimes does not exit after tests exception
by Barry Warsaw 25 Sep '11

25 Sep '11

Public bug reported: When the test suite gets an exception in the REST qrunner, it sometimes prevents the qrunner from exiting. The symptom of this is that the next time you try to run the test suite, you'll get an Address In Use error early on. This is because the test suite will try to start a new REST qrunner, which wants to bind to port 9001, but that's already in use by the "zombie" qrunner. The workaround is fairly simple. Just kill -HUP the zombie from the shell. Once it exits, the port gets freed up and the test suite will work again. ** 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/770328 Title: REST qrunner sometimes does not exit after tests exception

1 4

[Bug 772135] [NEW] The bounce qrunner needs to be enabled
by Barry Warsaw 25 Sep '11

25 Sep '11

Public bug reported: The Mailman 3 bounce qrunner isn't really enabled. It needs to be hooked up to scan_message() and tested. ** 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/772135 Title: The bounce qrunner needs to be enabled

1 2

[Merge] lp:~flo-fuchs/mailman.client/settings into lp:mailman.client
by Florian Fuchs 20 Jun '11

20 Jun '11

Florian Fuchs has proposed merging lp:~flo-fuchs/mailman.client/settings into lp:mailman.client. Requested reviews: Barry Warsaw (barry) For more details, see: https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088 Hi, I have added methods to delete mailing lists as well as a _Settings class to read and write list settings. Please feel free to make any changes you want (...and, of course, tell me if you feel this should be done completely differently... ;-) Cheers Florian -- https://code.launchpad.net/~flo-fuchs/mailman.client/settings/+merge/56088 Your team Mailman Coders is subscribed to branch lp:mailman.client.

3 7

[Bug 667252] [NEW] Mailman 3 Branch, install fails with --prefix specified
by Simon Fraser 13 Jun '11

13 Jun '11

Public bug reported: When trying to install mailman outside the Python tree, I get the following error: (I've replaced my home directory with $HOME in the below text) $ whoami srf $ /software/bin/python-2.6.3 setup.py install --prefix=~srf/mailman-install running install Checking .pth file support in /$HOME/mailman-install/lib/python2.6/site-packages/ error: can't create or remove files in install directory The following error occurred while trying to add or remove files in the installation directory: [Errno 2] No such file or directory: '/$HOME/mailman- install/lib/python2.6/site-packages/test-easy-install-20075.pth' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /$HOME/mailman-install/lib/python2.6/site-packages/ This directory does not currently exist. Please create it and try again, or choose a different installation directory (using the -d or --install-dir option). ** Affects: mailman Importance: Undecided Status: New -- Mailman 3 Branch, install fails with --prefix specified https://bugs.launchpad.net/bugs/667252 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 5

[Bug 756943] [NEW] 13 revisions removed from the branch
by Barry Warsaw 29 Apr '11

29 Apr '11

Public bug reported: I did a trunk merge of lp:mailman into a local 3.0 branch that had some weird resolution issues. The email notification said "13 revisions were removed from the branch" and the test suite broke. I reverted the revision and attach the diff for future resolution. ** 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/756943 Title: 13 revisions removed from the branch

1 4

[Bug 710182] [NEW] REST API: Subribing to more then one list raises AssertionError / returns HTTP 500
by Florian Fuchs 29 Apr '11

29 Apr '11

Public bug reported: Subscribing to more than one mailing list with the same email address via the REST API raises an AssertionError in app/membership.py and and subsequently returns a 500 HTTP status code. System Info: Ubuntu 10.10 Python 2.6.6 Mailman 3.0.0a7 (Rev. 6976) I added a patch file containing a test for multiple list subscriptions and a possible fix. Cheers Florian ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/710182 Title: REST API: Subribing to more then one list raises AssertionError / returns HTTP 500

2 4

[Bug 667472] [NEW] Support Python 2.7
by Barry Warsaw 29 Apr '11

29 Apr '11

Public bug reported: Mailman 3 should support either Python 2.6 or Python 2.7. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Fix Committed ** Tags: mailman3 ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a7 ** Tags added: mailman3 ** Changed in: mailman Status: In Progress => Fix Committed -- Support Python 2.7 https://bugs.launchpad.net/bugs/667472 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 2