Mailman 3 September 2012 - Mailman-coders

[Bug 693134] [NEW] Uncaught bounce from Dovecot when Quota Exceeded
by JorSol 20 Jun '13

20 Jun '13

Public bug reported: I have a Debian 5 (Lenny) server with Postfix - Dovecot and Mailman 2.1.11 and 1700+ users. The problem is when Dovecot returns the bounce message about "Quota exceeded", Mailman don't recognize the format: Your message to <user(a)domain.com> was automatically rejected: Quota exceeded It's suposed that Mailman recognize this type of message using the VERP feature, I have "recipient_delimiter = +" in Postfix but Mailman don't detect message coming from Dovecot. /var/log/mailman/bounce: Dec 21 10:58:08 2010 (3214) listnews: bounce message w/no discernable addresses: <dovecot-1292944464-47721-0@mail> Dec 21 10:58:08 2010 (3214) noticias: forwarding unrecognized, message-id: <dovecot-1292944464-47721-0@mail> ** Affects: mailman Importance: Undecided Status: New ** Tags: dovecot mailman postfix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/693134 Title: Uncaught bounce from Dovecot when Quota Exceeded

4 13

[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 1054730] [NEW] Set the verified_on flag for IAddress through the REST API
by Barry Warsaw 31 Dec '12

31 Dec '12

Public bug reported: IAddress.verified_on is how the core knows whether the registered address has been verified or not. Because Postorius supports registration via BrowserID, and by definition a BrowserID email address must be verified, we want to allow Postorius to set the verified_on field via the REST API. This probably won't be a direct value setting. Instead, I think you want to POST true or false to .../addresses/foo(a)example.com/verified and that will set IAddresses.verified_on to now() or to None. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: New ** Tags: mailman3 rest -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1054730 Title: Set the verified_on flag for IAddress through the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1054730/+subscriptions

1 3

[Bug 1047286] [NEW] Notifications for core events
by George Chatzisofroniou 31 Dec '12

31 Dec '12

Public bug reported: It would be great if core could provide notifications for more events to support plugins or any new internal functionality like: - New subscription - New thread started Those two notifications seems to be essential for the MM3-Metrics module (https://launchpad.net/mm3-metrics) in order to provide a nice overview of the system activity. Also, the notification that the core currently provides is that of a new posting. If this notification carried more information like the number of recipients or the message size we could provide additional interesting metrics via the MM3-Metrics module. ** Affects: mailman Importance: Undecided Status: New ** Tags: events metrics modules notifications plugins -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1047286 Title: Notifications for core events To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1047286/+subscriptions

2 4

[Bug 1035033] [NEW] bin/mailman --help could be improved
by Stephen Turnbull 31 Dec '12

31 Dec '12

Public bug reported: What the "reopen" command does is not at all clear. (Is it like "reload" in an init script, rereading config files? If so, maybe "reload" would be a better name.) Presumably the "restart" command stops *and* starts the runners. You can assign this to me (it would be appreciated if you'd tell me what reopen does, although I guess I could read the 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/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions

2 4

[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

[Merge] lp:~wacky/postorius/django_1_5 into lp:postorius
by Richard Wackerbarth 20 Oct '12

20 Oct '12

Richard Wackerbarth has proposed merging lp:~wacky/postorius/django_1_5 into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~wacky/postorius/django_1_5/+merge/127060 Django 1.5 will require that URL names be quoted These changes conform to the revised form and continue to support django 1.4 by loading the "future" version of the url tag. -- https://code.launchpad.net/~wacky/postorius/django_1_5/+merge/127060 Your team Mailman Coders is requested to review the proposed merge of lp:~wacky/postorius/django_1_5 into lp:postorius.

3 2

[Branch ~mailman-coders/mailman.client/trunk] Rev 36: * changed package name to mailmanclient to avoid import collisions
by noreply＠launchpad.net 26 Sep '12

26 Sep '12

------------------------------------------------------------ revno: 36 committer: Florian Fuchs <flo.fuchs(a)gmail.com> branch nick: mailman.client timestamp: Wed 2012-09-26 23:06:31 +0200 message: * changed package name to mailmanclient to avoid import collisions renamed: mailman/ => src/ mailman/client/ => src/mailmanclient/ modified: setup.py src/mailmanclient/__init__.py src/mailmanclient/_client.py src/mailmanclient/docs/using.txt src/mailmanclient/tests/test_docs.py -- lp:mailman.client https://code.launchpad.net/~mailman-coders/mailman.client/trunk Your team Mailman Coders is subscribed to branch lp:mailman.client. To unsubscribe from this branch go to https://code.launchpad.net/~mailman-coders/mailman.client/trunk/+edit-subsc…

1 0

[Bug 1056222] [NEW] Can't post to mail list or enter Admin interface
by Tammy Collins 25 Sep '12

25 Sep '12

Public bug reported: Mail that I sent to the list below has not posted, and I receive the error message shown below when trying to log in to the administrative interface of the following list: niehs-fellowslist(a)list.niehs.nih.gov "Bug in Mailman version 2.1.9 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs." ** 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/1056222 Title: Can't post to mail list or enter Admin interface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1056222/+subscriptions

2 1