Mailman 3 February 2012 - Mailman-coders

[Bug 876774] [NEW] AttributeError: 'MailingList' object has no attribute 'bounce_processing'
by Vincent Fretin 06 Apr '12

06 Apr '12

Public bug reported: With mailman 3.0.0a8 Oct 17 12:06:34 2011 (15436) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/bounce.py", line 46, in _dispose if not mlist.bounce_processing: AttributeError: 'MailingList' object has no attribute 'bounce_processing' It seems that bounce_processing is defined in src/mailman/styles/default.py The style are applied at mailing-list creation, but bounce_processing attribute is not persisted, the src/mailman/database/mailman.sql file doesn't define it. ** 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/876774 Title: AttributeError: 'MailingList' object has no attribute 'bounce_processing' To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/876774/+subscriptions

2 3

[Bug 874929] [NEW] Missing aliases in postfix_lmtp file when using more than one mailing-list
by Vincent Fretin 06 Apr '12

06 Apr '12

Public bug reported: With mailman 3.0.0a8. When I create a first mailing-list, I get in var/data/postfix_lmtp cpoi(a)example.com lmtp:[127.0.0.1]:8024 cpoi-bounces(a)example.com lmtp:[127.0.0.1]:8024 cpoi-confirm(a)example.com lmtp:[127.0.0.1]:8024 cpoi-join(a)example.com lmtp:[127.0.0.1]:8024 cpoi-leave(a)example.com lmtp:[127.0.0.1]:8024 cpoi-owner(a)example.com lmtp:[127.0.0.1]:8024 cpoi-request(a)example.com lmtp:[127.0.0.1]:8024 cpoi-subscribe(a)example.com lmtp:[127.0.0.1]:8024 cpoi-unsubscribe(a)example.com lmtp:[127.0.0.1]:8024 Then if I create a second mailing-list, I get: cpoi(a)example.com lmtp:[127.0.0.1]:8024 test(a)example.com lmtp:[127.0.0.1]:8024 test-bounces(a)example.com lmtp:[127.0.0.1]:8024 test-confirm(a)example.com lmtp:[127.0.0.1]:8024 test-join(a)example.com lmtp:[127.0.0.1]:8024 test-leave(a)example.com lmtp:[127.0.0.1]:8024 test-owner(a)example.com lmtp:[127.0.0.1]:8024 test-request(a)example.com lmtp:[127.0.0.1]:8024 test-subscribe(a)example.com lmtp:[127.0.0.1]:8024 test-unsubscribe(a)example.com lmtp:[127.0.0.1]:8024 I lost all aliases of the first mailing-list. I attached a patch for the src/mailman/mta/postfix.py file. ** 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/874929 Title: Missing aliases in postfix_lmtp file when using more than one mailing- list To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/874929/+subscriptions

2 4

[Bug 869317] [NEW] Mailman startup script missing --force option.
by Stephen A. Goss 06 Apr '12

06 Apr '12

Public bug reported: I rebooted the VM that mailman was running on, when I tried to start mailman up after the reboot, i got this output: $ mailman -C /etc/mailman.cfg start usage: mailman [-h] [-v] [-C CONFIG] {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases} ... mailman: error: A previous run of GNU Mailman did not exit cleanly. Try using --force. Running with the --force option didn't work: $ mailman --force -C /etc/mailman.cfg start usage: mailman [-h] [-v] [-C CONFIG] {info,status,help,withlist,start,unshunt,create,stop,remove,lists,reopen,version,import21,inject,members,qfile,restart,aliases} ... mailman: error: unrecognized arguments: --force ** 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/869317 Title: Mailman startup script missing --force option. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869317/+subscriptions

3 7

[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

[Merge] lp:~syst3mw0rm/mailman/bug-890675 into lp:mailman
by Aamir Khan 05 Apr '12

05 Apr '12

Aamir Khan has proposed merging lp:~syst3mw0rm/mailman/bug-890675 into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~syst3mw0rm/mailman/bug-890675/+merge/93669 -- https://code.launchpad.net/~syst3mw0rm/mailman/bug-890675/+merge/93669 Your team Mailman Coders is requested to review the proposed merge of lp:~syst3mw0rm/mailman/bug-890675 into lp:mailman.

3 2

[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 938695] [NEW] [PATCH] No wrap in text emails
by strainu 22 Feb '12

22 Feb '12

Public bug reported: As users of mailman in a corporate environment, we noticed that text or HTML emails sent by Outlook are not wrapped. When they arrive on mailman, the message text is automatically surrounded by <pre></pre>. When someone wants to read the archive, the messages will appear with very long lines, exceeding the width of the screen. As a solution, we added style="white-space:pre-wrap" to the PRE tag. Any alternative solution is acceptable if the use of CSS is not OK. ** 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/938695 Title: [PATCH] No wrap in text emails To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/938695/+subscriptions

2 2