Mailman 3 December 2011 - Mailman-coders

[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 872391] [NEW] KeyError: u'outgoing' in runner
by Stephen A. Goss 06 Apr '12

06 Apr '12

Public bug reported: Found this in my mailman.log. It may have happened around the time I was attempting to send a message through a mailing list and the SMTP receiver (fakemail.py in this case) died, so there were some failures to deliver. Oct 07 16:14:47 2011 (12057) Uncaught runner exception: u'outgoing' Oct 07 16:14:47 2011 (12057) Traceback (most recent call last): File "/home/phoenix/mailman_clone/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/phoenix/mailman_clone/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/phoenix/mailman_clone/src/mailman/runners/retry.py", line 40, in _dispose config.switchboards['outgoing'].enqueue(msg, msgdata) KeyError: u'outgoing' ** 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/872391 Title: KeyError: u'outgoing' in runner To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/872391/+subscriptions

2 6

[Bug 867459] [NEW] REST API: Implement a simple way to check user credentials
by Florian Fuchs 06 Apr '12

06 Apr '12

Public bug reported: Currently there is no way to check a user's credentials via the REST API. While there were discussions on implementing a middleware "hook" to implement complex authentication logic, there should also be a simple way to check if a given combination of a user's credentials (user name and password) matches the one stored in mailman's internal db. A good way to do this (as discussed on IRC a while ago) could be to implement a SQL stored procedure-like behavior in the REST API. Meaning: A client sends a uname/pwd-combination to a specific URL resource and receives a plain True or False (1 or 0?) if the combination matches. This way, no password string is sent out via the API. Things to discuss or consider: 1.) How is the password stored in MMs internal db? (plaintext or hashed? if hashed, which algorithm is used?) 2.) (How) should the pwd be encrypted when sent to the API (depends on 1.)? 3.) Should this API resource be limited to requests from localhost and/or via SSL? ** 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/867459 Title: REST API: Implement a simple way to check user credentials To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/867459/+subscriptions

2 5

[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