Mailman 3 June 2011 - Mailman-coders

[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 788309] [NEW] Site configuration customization unnecessarily stored in tree
by Richard Wackerbarth 06 Apr '12

06 Apr '12

Public bug reported: The i18n templates for site customization are specified to be in <template_dir>/site/ etc., a part of the tree, rather than being placed in <var_dir> (outside the tree) Solution, move them to <var_dir>/templates/site/ ** 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/788309 Title: Site configuration customization unnecessarily stored in tree

2 5

[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 778688] [NEW] Invalid entry in owner roster causes infinite loop
by Richard Wackerbarth 03 Apr '12

03 Apr '12

Public bug reported: If there is an error in the owners roster, a message sent to that roster bounces to the same list generating another (longer) bounce message which also bounces to the same roster, ad nausium. ** 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/778688 Title: Invalid entry in owner roster causes infinite loop

2 1

[Bug 790994] [NEW] GPL License
by Richard Wackerbarth 25 Sep '11

25 Sep '11

Public bug reported: The gnu-COPYING-GPL file in "trunk" is GPL2. Although I would prefer that all of mailman be under no more-restrictive license, there are references to GPL v3. Therefore, should that not be the license distributed with the source code> ** 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/790994 Title: GPL License

2 3

[Bug 778687] [NEW] Invalid roster upon initial list creation
by Richard Wackerbarth 25 Sep '11

25 Sep '11

Public bug reported: GNU Mailman 3.0.0a7+ (Where's My Thing?) -- bzr=7005 When executing bin/mailman create -domain=True example(a)throwaway.domain, the example-owner get populated with an entry INSERT INTO "address" VALUES(1,'main=true','main=True','',NULL,'2005-08-01 07:49:23',1,2); The roster should be empty. ** 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/778687 Title: Invalid roster upon initial list creation

2 4

[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 799612] [NEW] Expose REST API call to look up member/user id given an email address
by Florian Fuchs 25 Sep '11

25 Sep '11

Public bug reported: In order to find out the internal member ID of an email address one currently has to iterate over the whole member roster. While this works fine it's certainly not the most efficient way to retrieve the ID. It would be great to have a REST-exposed mechanism to look up a member (or user) ID directly. ** 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/799612 Title: Expose REST API call to look up member/user id given an email address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/799612/+subscriptions

2 5

[Bug 787599] [NEW] host_name ancient name for mail_host
by benste 25 Sep '11

25 Sep '11

Public bug reported: please update the settings and core to support "mail_host" instead of "host_name" which is confusing in comparision to "web_host" The same thing needs to be done in the REST Api to support this change ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailmanweb Importance: Medium Status: Confirmed ** Also affects: mailmanweb Importance: Undecided Status: New ** Changed in: mailman Status: New => Opinion ** Changed in: mailmanweb Status: New => Opinion -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/787599 Title: host_name ancient name for mail_host

2 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

Mailman-coders June 2011