Mailman 3 May 2012 - Mailman-coders

[Bug 886296] [NEW] Improve DSN handling for google 'inactive' accounts
by Kevin Fenzi 30 May '13

30 May '13

Public bug reported: The DSN bouncer handler can't seem to parse out when a bounce is generated due to an inactive google account. See attached bounce file for example. ** 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/886296 Title: Improve DSN handling for google 'inactive' accounts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/886296/+subscriptions

3 8

[Bug 982551] [NEW] ./mailman.cfg only used partially
by Bernhard Schmidt 31 Dec '12

31 Dec '12

Public bug reported: GNU Mailman 3.0.0b1+ (current bzr head). http://packages.python.org/mailman/src/mailman/docs/START.html#running- mailman-3 talks about ./mailman.cfg being used as configuration (among others). This seems to be only partially true. I put this mailman.cfg into /usr/local/mailman --- [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:mailman@xxx/mailman [shell] use_ipython: yes [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mailout.xxx lmtp_port: 8024 smtp_host: mailout.xxx smtp_port: 25 [runner.nntp] start: no --- and started bin/mailman start. The PostgreSQL database was initialized, bin/mailman status showed the correct configuration location. I could create lists and they were added in the SQL database. It would use ipython as shell. But it would still try to send mail through localhost, and it would still start the nntp runner. And LMTP would reject mails to the existing lists with "mailbox unavailable". So it seems the configuration was only used by the main process, but not by the runners. Moving the configuration to a non-relative location fixed 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/982551 Title: ./mailman.cfg only used partially To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/982551/+subscriptions

2 7

[Bug 975692] [NEW] Allow style assignments when creating a list through REST
by Barry Warsaw 31 Dec '12

31 Dec '12

Public bug reported: You should be able to query the available list styles through the REST API, and choose an available style when creating the mailing list through REST. ** Affects: mailman Importance: Low Status: Confirmed ** Tags: api easy mailman3 ** Tags removed: rest ** Tags added: api -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/975692 Title: Allow style assignments when creating a list through REST To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975692/+subscriptions

1 4

[Bug 971013] [NEW] Database schema migrations needed
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: The following database schema migrations are required. This is a release blocker for 3.0 final. Add more to this bug as you find them. * Change news_prefix_subject_too -> nntp_prefix_subject_too * Remove nntp_host from table mailing list ** Affects: mailman Importance: Critical 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/971013 Title: Database schema migrations needed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions

2 13

[Bug 949924] [NEW] UnicodeDecodeError when delivering message
by Antti Kaihola 08 Sep '12

08 Sep '12

Public bug reported: I did a fresh install of Mailman 3.0.0a8 on a Debian Squeeze box, created a list, subscribed a few people and sent a message to the list. The message didn't come through, and var/logs/mailman.log has: Mar 08 13:21:08 2012 (23645) Uncaught runner exception: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) Traceback (most recent call last): File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/mailman/lib/python2.6/site-packages/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/mailman/lib/python2.6/site-packages/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) SHUNTING: 1331212867.805197+9daec32c73ac20978b856348ada1a60fd97a364c The message did contain an u'\xe4' in both the subject and the body. I sent the message using Thunderbird 10.0.2 on Linux Mint 12. ** 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/949924 Title: UnicodeDecodeError when delivering message To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/949924/+subscriptions

5 11

[Bug 967238] [NEW] Expose IMailingList.archive and .archive_private in the REST API
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: Exposing read and write of these attributes would allow Postorius to provide the list owners with some control over archiving for individual lists. This would work as a patch to src/mailman/rest/configuration.py and should be pretty easy to add. ** Affects: mailman Importance: Medium Status: Triaged ** Tags: easy 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/967238 Title: Expose IMailingList.archive and .archive_private in the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967238/+subscriptions

2 6

[Bug 975696] [NEW] Eradicate generic_nonmember_action
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: This attribute should be removed, it's no longer used. The tricky part is that it must be removed from the IMailingList interface, the model, lots of places in the code, and a schema migration is needed too. ** Affects: mailman Importance: High 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/975696 Title: Eradicate generic_nonmember_action To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975696/+subscriptions

1 3

[Bug 975698] [NEW] On email validation confirmation, trigger an event
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: Trigger a zope.event when an email address has been confirmed (validated). This could be used to inform Postorius about the event. ** Affects: mailman Importance: High Status: Confirmed ** Tags: easy 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/975698 Title: On email validation confirmation, trigger an event To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975698/+subscriptions

1 2

[Bug 975700] [NEW] On password change, trigger an event
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: When a user changes her password (e.g. via the email API), a zope.event should be triggered. This could be used to inform Postorius of the event. ** Affects: mailman Importance: High Status: Confirmed ** Tags: easy 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/975700 Title: On password change, trigger an event To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975700/+subscriptions

1 2

[Bug 987563] [NEW] List-Post should be NO when posting is not allowed
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: >From RFC 2369: 3.4. List-Post The List-Post field describes the method for posting to the list. This is typically the address of the list, but MAY be a moderator, or potentially some other form of submission. For the special case of a list that does not allow posting (e.g., an announcements list), the List-Post field may contain the special value "NO". Mailman currently prevents adding the List-Post header for announce-only lists. Instead it should include it with the value of NO. ** Affects: mailman Importance: High Status: Confirmed ** Tags: easy 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/987563 Title: List-Post should be NO when posting is not allowed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987563/+subscriptions

1 2

Mailman-coders May 2012