Mailman 3 September 2010 - Mailman-coders

[Bug 552917] [NEW] Subscribing an already subscribed member via REST should 409
by Barry Warsaw 21 Sep '10

21 Sep '10

Public bug reported: 409 Conflict is probably a better HTTP response code for the REST API when trying to subscribe an already subscribed member. Add some content body to explain the situation. ** Affects: mailman Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailman/3.0 Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed ** Tags: mailman3 ** Changed in: mailman Milestone: None => 3.0.0a6 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Status: New => Confirmed ** Tags added: mailman3 ** Also affects: mailman/3.0 Importance: Undecided Assignee: Barry Warsaw (barry) Status: Confirmed -- Subscribing an already subscribed member via REST should 409 https://bugs.launchpad.net/bugs/552917 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 4

[Bug 601899] [NEW] Delete list function in rest-server
by Anna 21 Sep '10

21 Sep '10

Public bug reported: A function to delete a list is needed in the rest-server (which I believe is necessary to be able to implement it in the rest-client). ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- Delete list function in rest-server https://bugs.launchpad.net/bugs/601899 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 5

[Bug 593029] [NEW] Mailman package in pypi won't install
by FreqMod 21 Sep '10

21 Sep '10

Public bug reported: Mailman in pypi depends on munepy, but munepy has been renamed to flufl.enum. Therefore no munepy-package exists in pypi, and the mailman installation fails because of the dependency. ** Affects: mailman Importance: Undecided Status: New -- Mailman package in pypi won't install https://bugs.launchpad.net/bugs/593029 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 2

[Bug 490114] Re: Mailman should be compliant with the Filesystem Hierarchy Standard
by Barry Warsaw 21 Sep '10

21 Sep '10

** Changed in: mailman/3.0 Status: Fix Committed => Fix Released -- Mailman should be compliant with the Filesystem Hierarchy Standard https://bugs.launchpad.net/bugs/490114 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 600962] [NEW] Rest getter and setter functions needed in MM3
by Anna 21 Sep '10

21 Sep '10

Public bug reported: Below I'll list some functions we need implemented in the rest server to be able to implement them in the rest-client and use them for the UI. I don't think any of these are implemented yet but we'll need them. * A "getter" and a "setter" function for the user settings, i.e. a function returning the values the user had set for a particular mailing list and a function setting the new values the user has changed on the settings page for a mailing list. * A "getter" and a "setter" function for the admin settings for each list. Since there are many settings possible for each list, we may want to divide these into groups and create a getter and setter for each group, but I'm not sure about this. Maybe it's possible to make something generic just changing the values the user has changed making the grouping unnecessary, I really don't know. I just brought it up for consideration. I'll leave the functions necessary for the archives so far but likely we'll later need functions returning old emails grouped according to threads, dates etc. like old Mailman has. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest-api -- Rest getter and setter functions needed in MM3 https://bugs.launchpad.net/bugs/600962 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 5

[Bug 585512] [NEW] Set up virtualenv (and ditch buildout?)
by Barry Warsaw 20 Sep '10

20 Sep '10

Public bug reported: Mailman 3 development needs more isolation from system Python. Two recent reports are semi-related: * On Ubuntu systems that have been upgraded from Karmic to Lucid, there is a bug in python-setuptools that causes buildout to fail with cryptic error messages. See bug 576434 and bug 585188 for related failures (though not in Mailman). * Strange import conflicts with system installed Mailman that are hard to debug. This is related to mailman.testing.i18n giving TypeErrors on incorrect number of arguments when initializing flufl.i18n. I think the fix is to make sure the build works with virtualenv. Then we have to decide whether it's still worth keeping the buildout infrastructure for testing purposes. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Affects: mailman/3.0 Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 ** Also affects: mailman/3.0 Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed -- Set up virtualenv (and ditch buildout?) https://bugs.launchpad.net/bugs/585512 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 582525] [NEW] Add sieve rules to route messages properly to IMAP server
by Barry Warsaw 20 Sep '10

20 Sep '10

Public bug reported: When a message from Mailman gets routed to an IMAP server (e.g. for archiving or administration), we need a sieve rule to do proper routing. E.g. for dovecot. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Add sieve rules to route messages properly to IMAP server https://bugs.launchpad.net/bugs/582525 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 582524] [NEW] Use IMAP CREATE to add folders to IMAP archiver on list creation
by Barry Warsaw 20 Sep '10

20 Sep '10

Public bug reported: For every mailing list we expose to IMAP, we'll want to create a few folders. Hook in the IMAP folder creation to the list creation hooks. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0a6 -- Use IMAP CREATE to add folders to IMAP archiver on list creation https://bugs.launchpad.net/bugs/582524 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 582522] [NEW] Implement archive delivery via LMTP
by Barry Warsaw 20 Sep '10

20 Sep '10

Public bug reported: Dovecot beta supports delivery via LMTP. Mailman 3 should implement a generic archive delivery implementation that delivers via LMTP. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Milestone: None => 3.0.0a6 ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Importance: Undecided => High -- Implement archive delivery via LMTP https://bugs.launchpad.net/bugs/582522 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 543627] [NEW] mailman command does not initialize directory structure on first run
by Patrick Ben Koetter 20 Sep '10

20 Sep '10

Public bug reported: Contrary to "src/mailman/docs/START.txt" which says Run the ``bin/mailman info`` command to see which configuration file Mailman will use, and where it will put its database file. The first time you run this, Mailman will also create any necessary run-time directories and log files. neither the mailman command alone nor running it with option "info" creates the initial directory structure. If you go with the default settings in mailman.cfg you probably won't notice because you are within the correct directory structure. But if you set "var_dir: /opt/mailman" in e.g. /etc/mailman.cfg things break. I believe fixing this would also fix ticket #543620. ** Affects: mailman Importance: Undecided Status: New -- mailman command does not initialize directory structure on first run https://bugs.launchpad.net/bugs/543627 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 2