Mailman 3 September 2011 - Mailman-coders

[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 808821] [NEW] Probe messages should not sent Precedence header
by Barry Warsaw 06 Apr '12

06 Apr '12

Public bug reported: Probe messages (sent after an address has been disabled due to bounces) should not set Precedence. This is because they actually are not bulk or list traffic. It's possible that where list traffic might be bouncing, a non-Precedence containing probe message could have a better chance of getting through. One thing to think about though is vacation programs, which (if well-behaved) will not respond to Precedence messages. Thus, if a person's address were bouncing, and they had a vacation program on, these would respond to probe messages. This might be significant if we were to score probe bounces higher (i.e. as signs to permanently disable or delete the address). ** 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/808821 Title: Probe messages should not sent Precedence header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/808821/+subscriptions

2 4

[Bug 860159] [NEW] Mailman 3.0 support for Postgres
by Stephen A. Goss 06 Apr '12

06 Apr '12

Public bug reported: Currently, the MM3 source is SQLite specific, but only in the schema and database creation code, otherwise, it uses Storm which (mostly) supports Postgres. ** 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/860159 Title: Mailman 3.0 support for Postgres To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/860159/+subscriptions

5 14

[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 862675] [NEW] Changes to a list (subscribe, unsubscribe, etc.) can be lost.
by Mark Sapiro 01 Nov '11

01 Nov '11

Public bug reported: Under certain circumstances such as when bin/add_members is run multiple times in a script, VirginRunner in the process of sending notifications can fail to detect that the list object was updated by another process and can save the list object without having first loaded the latest version, thus losing changes. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) 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/862675 Title: Changes to a list (subscribe, unsubscribe, etc.) can be lost. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/862675/+subscriptions

1 2

[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 831660] [NEW] IDomain.email_host should be renamed to IDomain.mail_host
by Barry Warsaw 25 Sep '11

25 Sep '11

Public bug reported: This would be for consistency with IMailingList.mail_host ** Affects: mailman Importance: Low Assignee: Barry Warsaw (barry) 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/831660 Title: IDomain.email_host should be renamed to IDomain.mail_host To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/831660/+subscriptions

1 2

[Bug 833208] [NEW] test_accepted_message_gets_posted failing on Centos 6 / Python 2.6
by Stephen A. Goss 25 Sep '11

25 Sep '11

Public bug reported: This test seems to still be failing on Centos 6 / Python 2.6.5 for other reasons: Failure in test test_accepted_message_gets_posted (mailman.app.tests.test_moderation.TestModeration) Traceback (most recent call last): File "/usr/lib64/python2.6/unittest.py", line 279, in run testMethod() File "/home/sgoss/mailman_clone/src/mailman/app/tests/test_moderation.py", line 107, in test_accepted_message_gets_posted """) File "/usr/lib64/python2.6/unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: 'From: anne(a)example.com\nTo: test(a)example.com\nMessage-ID: <alpha>\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' != u'From: anne(a)example.com\nTo: test(a)example.com\nMessage-ID: <alpha>\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' ** 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/833208 Title: test_accepted_message_gets_posted failing on Centos 6 / Python 2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/833208/+subscriptions

2 3

[Bug 820660] [NEW] Attempting to DELETE a user through REST API returns '405 Method Not Allowed'
by Stephen A. Goss 25 Sep '11

25 Sep '11

Public bug reported: src/mailman/rest/docs/users.txt clearly states "The REST API can be used to add and remove users, add and remove user addresses, and change their preferred address, password, or name." When I send a DELETE request to either /3.0/users/1 or /3.0/users/foo(a)example.org, I get a '405 Method Not Allowed' response. $ curl -u restadmin:restpass -I http://localhost:8001/3.0/users/bar@foo.com HTTP/1.0 200 OK Date: Wed, 03 Aug 2011 22:36:37 GMT Server: WSGIServer/0.1 Python/2.6.5 content-length: 311 $ curl -X DELETE -u restadmin:restpass -I http://localhost:8001/3.0/users/bar@foo.com HTTP/1.0 405 Method Not Allowed Date: Wed, 03 Aug 2011 22:34:16 GMT Server: WSGIServer/0.1 Python/2.6.5 Content-Type: text/plain Allow: HEAD, GET Content-Length: 22 ** 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/820660 Title: Attempting to DELETE a user through REST API returns '405 Method Not Allowed' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/820660/+subscriptions

2 4