Mailman 3 August 2011 - Mailman-coders

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

26 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

[Bug 832404] [NEW] Test failing: test_accepted_message_gets_posted
by Stephen A. Goss 26 Sep '11

26 Sep '11

Public bug reported: This test seems to be failing on both Ubuntu 11.04 with Python 2.7.1 and Centos 6 with Python 2.6.5: Failure in test test_accepted_message_gets_posted (mailman.app.tests.test_moderation.TestModeration) Traceback (most recent call last): File "/usr/lib/python2.7/unittest/case.py", line 321, in run testMethod() File "/home/sgoss/launchpad/mailman/src/mailman/app/tests/test_moderation.py", line 99, in test_accepted_message_gets_posted """) File "/usr/lib/python2.7/unittest/case.py", line 503, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python2.7/unittest/case.py", line 496, in _baseAssertEqual raise self.failureException(msg) AssertionError: 'From: anne(a)example.com\nTo: test(a)example.com\nMessage-ID: <alpha>\nX-Mailman-Approved-At: Mon, 01 Aug 2005 07:49:23 -0700\nSubject: [Test] hold me\nX-BeenThere: test(a)example.com\nPrecedence: list\nList-Id: <test.example.com>\nX-Message-ID-Hash: XZ3DGG4V37BZTTLXNUX4NABB4DNQHTCP\nList-Post: <mailto:test@example.com>\nList-Subscribe: <http://lists.example.com/listinfo/test@example.com>,\n <mailto:test-join@example.com>\nArchived-At: http://lists.example.com/archives/XZ3DGG4V37BZTTLXNUX4NABB4DNQHTCP\nList-Un…: <http://lists.example.com/listinfo/test@example.com>,\n <mailto:test-leave@example.com>\nList-Archive: <http://lists.example.com/archives/test@example.com>\nList-Help: <mailto:test-request@example.com?subject=help>\nX-MailFrom: test-bounces(a)example.com\nX-RcptTo: bart(a)example.com\n\n' != u'From: anne(a)example.com\nTo: test(a)example.com\nMessage-ID: <alpha>\nX-Mailman-Approved-At: Mon, 01 Aug 2005 07:49:23 -0400\nSubject: [Test] hold me\nX-BeenThere: test(a)example.com\nPrecedence: list\nList-Id: <test.example.com>\nX-Message-ID-Hash: XZ3DGG4V37BZTTLXNUX4NABB4DNQHTCP\nList-Post: <mailto:test@example.com>\nList-Subscribe: <http://lists.example.com/listinfo/test@example.com>,\n\t<mailto:test-join@example.com>\nArchived-At: http://lists.example.com/archives/XZ3DGG4V37BZTTLXNUX4NABB4DNQHTCP\nList-Un…: <http://lists.example.com/listinfo/test@example.com>,\n\t<mailto:test-leave@example.com>\nList-Archive: <http://lists.example.com/archives/test@example.com>\nList-Help: <mailto:test-request@example.com?subject=help>\nX-MailFrom: test-bounces(a)example.com\nX-RcptTo: bart(a)example.com\n\n' ** 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/832404 Title: Test failing: test_accepted_message_gets_posted To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/832404/+subscriptions

2 3

[Bug 827697] [NEW] Moderating a message with Action.accept does not cause held message to be sent or even removed from pending.
by Stephen A. Goss 26 Sep '11

26 Sep '11

Public bug reported: I'm building a REST API for moderation. Calling moderator.handle_message with Action.discard and Action.reject seem to do the right thing, but calling it with Action.accept doesn't seem to. Instead the held message stays in the pending queue and nothing is delivered to the list. I thought it was related to this: https://bugs.launchpad.net/mailman/+bug/827547 But I get the same result whether or not that error message appears in the logs. ** 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/827697 Title: Moderating a message with Action.accept does not cause held message to be sent or even removed from pending. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/827697/+subscriptions

2 8

[Merge] lp:~postfuturist/mailman/rest-api-delivery_mode into lp:mailman
by Stephen A. Goss 02 Sep '11

02 Sep '11

Stephen A. Goss has proposed merging lp:~postfuturist/mailman/rest-api-delivery_mode into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #833132 in GNU Mailman: "Unable to query or change member delivery_mode through REST API." https://bugs.launchpad.net/mailman/+bug/833132 Bug #833376 in GNU Mailman: "Attempting to PATCH an invalid attribute on a member object in REST API results in 500, instead of 400." https://bugs.launchpad.net/mailman/+bug/833376 For more details, see: https://code.launchpad.net/~postfuturist/mailman/rest-api-delivery_mode/+me… Currently, in the REST API for members/subscriptions you can create a subscription with a specific delivery_mode (regular or various digest modes). However, you can't get this information back from the REST API or change it. This branch addresses these shortcomings by adding delivery_mode to the information returned by the API when GETing member info, it also allows you to PATCH the delivery_mode of a member. It handles edge/error cases, like patching nonexistent members, patching invalid parameters, etc. All cases are tested (I think). This resolves 833132 and 833376. -- https://code.launchpad.net/~postfuturist/mailman/rest-api-delivery_mode/+me… Your team Mailman Coders is requested to review the proposed merge of lp:~postfuturist/mailman/rest-api-delivery_mode into lp:mailman.

3 3

[Merge] lp:~postfuturist/mailman/rest-api-mods_owners into lp:mailman
by Stephen A. Goss 26 Aug '11

26 Aug '11

Stephen A. Goss has proposed merging lp:~postfuturist/mailman/rest-api-mods_owners into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #834130 in GNU Mailman: "eUnable to create list moderators or ownrs with REST API." https://bugs.launchpad.net/mailman/+bug/834130 For more details, see: https://code.launchpad.net/~postfuturist/mailman/rest-api-mods_owners/+merg… Added ability to add moderators and owners through existing REST API endpoints. Tests were updated as well. -- https://code.launchpad.net/~postfuturist/mailman/rest-api-mods_owners/+merg… Your team Mailman Coders is requested to review the proposed merge of lp:~postfuturist/mailman/rest-api-mods_owners into lp:mailman.

1 1

Re: [Question #168834]: missing pending requests in mailman administrative database
by Mark Sapiro 23 Aug '11

23 Aug '11

Question #168834 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/168834 Status: Open => Answered Mark Sapiro proposed the following answer: See the FAQ at <http://wiki.list.org/x/EoCE>. -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0

[Question #168834]: missing pending requests in mailman administrative database
by kisakye moses 22 Aug '11

22 Aug '11

New question #168834 on mailman in Ubuntu: https://answers.launchpad.net/ubuntu/+source/mailman/+question/168834 The administrator/moderator of the list gets a message saying that there is a post pending approval. However, when he logs in and clicks "Tend to pending moderator requests" there is nothing there. Basically we keep getting "pending" notices but the queue is empty. It had been working and no settings were changed. When a message is sent to a mailing list there are no pending requests but if sent to a list and some members of the list have the moderation bit set as off they receive the message . How can i solve this? thanx in advance -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu.

1 0

[Bug 266317] Re: attachments archived even when archiving disabled
by Mark Sapiro 11 Aug '11

11 Aug '11

> is it safe to remove these attachments directories? Or will all the attachment files just come back? Assuming the list doesn't archive (archive = No), the only things stored in the attachments directory are attachments scrubbed from the 'plain' format digest. You can remove the attachments directory and its contents, and those specific files won't come back, but as long as your list is digestable, attachments from subsequent digests will continue to be stored. You might think creating a attachments directory as a symlink to /dev/null would work, but it won't because Mailman tries to create and access subdirectories under attachments. Probably the best you can do is create a cron job to 'rm -rf archives/private/listname/attachments' or maybe 'find archives/private/listname/attachments -maxdepth 1 -mtime +2 -exec rm -f \{\} \;'. The 'find' example should just remove those subdirectories older than 2 days (-mtime +2). -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266317 Title: attachments archived even when archiving disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266317/+subscriptions

1 0

[Bug 266317] Re: attachments archived even when archiving disabled
by Denis Roy 10 Aug '11

10 Aug '11

I've been struggling with this for years. If there is no fix in sight, is it safe to remove these attachments directories? Or will all the attachment files just come back? Looking for a workaround here... -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266317 Title: attachments archived even when archiving disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266317/+subscriptions

1 0

[Bug 822358] [NEW] zip or bzip2 should be compression choices as well as gzip
by Tom Browder 09 Aug '11

09 Aug '11

Public bug reported: Currently gzip is the only compression choice. Novice Windows users usually have a zip utility available but may not be able to easily install another utility like 7-Zip that can handle gzip. Also, bzip2 (or other compression utility) may be a better compression choice than gzip for very active mailing lists ** Affects: mailman Importance: Undecided Status: New ** Tags: administration archive setup -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/822358 Title: zip or bzip2 should be compression choices as well as gzip To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/822358/+subscriptions

2 2