Mailman 3 August 2010 - Mailman-coders

[Bug 552917] [NEW] Subscribing an already subscribed member via REST should 409
by Barry Warsaw Sept. 21, 2010

Sept. 21, 2010

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 Sept. 21, 2010

Sept. 21, 2010

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 Sept. 21, 2010

Sept. 21, 2010

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 600962] [NEW] Rest getter and setter functions needed in MM3
by Anna Sept. 21, 2010

Sept. 21, 2010

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 Sept. 20, 2010

Sept. 20, 2010

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 543627] [NEW] mailman command does not initialize directory structure on first run
by Patrick Ben Koetter Sept. 20, 2010

Sept. 20, 2010

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

[Bug 627264] [NEW] list moderation fails with two moderators
by Frank Nemec Aug. 31, 2010

Aug. 31, 2010

Public bug reported: I have a discussion list (weekly(a)lists.valleychurch.org) with two moderators. If someone submits a post requiring moderation, nothing happens. There is no notification to either moderator or to the poster. Nothing appears in pending moderator requests. ** Affects: mailman Importance: Undecided Status: New -- list moderation fails with two moderators https://bugs.launchpad.net/bugs/627264 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 266018] Re: Impossible to recover lost admin-list passwords
by rcmichelle Aug. 25, 2010

Aug. 25, 2010

you can try to google Password Genius -- Impossible to recover lost admin-list passwords https://bugs.launchpad.net/bugs/266018 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0

[Bug 620539] [NEW] From_ lines within the message body can confuse the archiver
by Axel Thimm Aug. 19, 2010

Aug. 19, 2010

Public bug reported: This is on mailman 2.1.12 as shipped by Fedora 12. The following From line in a message body caused the mail to have been properly distributed, but was split in two in the archiving part: === Quote start I think this would be a fairly common set up? Indeed I have three machines that are setup this way (1 has 2 fans, the other 2 have 3 fans) >From what I can see, pwmconfig does this: pwm1_enable=0 pwm2_enable=0 === Quote end I'm not sure whether the From line was actually escaped or not when mailman was processing it, as the copy I received went through exim /dovecot-lda, and I think at least exim does fix unescaped From lines. The mail above was split into the following in the mbox archives (http://lists.lm-sensors.org/pipermail/lm-sensors/2010-August.txt.gz): === Quote start I think this would be a fairly common set up? Indeed I have three machines that are setup this way (1 board has 2 fans, the other 2 have 3 fans each) >From bogus(a)does.not.exist.com Thu Aug 12 18:07:19 2010 From: bogus(a)does.not.exist.com () Date: Thu, 12 Aug 2010 16:07:19 -0000 Subject: No subject Message-ID: <mailman.0.1281931669.3888.lm-sensors(a)lm-sensors.org> pwm1_enable=3D0 pwm2_enable=3D0 === Quote end The html archives are truncated in a similar fashion. I don't have the original mail, but I suspect that it was missing Lines /Content-Length headers and therefore the possibly unescaped From line was bogus. Still, if mailman was smart enough to ship the mail as a whole it should be properly filing it into the archives as well. Also, why is there an mbox splitting during archiving in the first place? Thanks! ** Affects: mailman Importance: Undecided Status: New -- From_ lines within the message body can confuse the archiver https://bugs.launchpad.net/bugs/620539 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

2 1

[Bug 266588] Re: Add SpamAssassin filter to mail pipeline
by Mark Sapiro Aug. 18, 2010

Aug. 18, 2010

Regarding comment #24: Have you defined SPAMASSASSIN_MEMBER_BONUS in Defaults.py and/or mm_cfg.py? Did you define it as a string rather than as a float? i.e. something like SPAMASSASSIN_MEMBER_BONUS = '5' as opposed to SPAMASSASSIN_MEMBER_BONUS = 5.0 if MEMBER_BONUS actually has a string value, simply changing score -= MEMBER_BONUS into score -= (MEMBER_BONUS) won't help. Did you mean score -= float(MEMBER_BONUS)? -- Add SpamAssassin filter to mail pipeline https://bugs.launchpad.net/bugs/266588 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

1 0