Mailman 3 December 2012 - Mailman-coders

[Bug 1065447] [NEW] Feature request: REST api to verify password
by Dieter Maurer 31 Dec '12

31 Dec '12

Public bug reported: "mailman" manages users with their individual passwords. It is supposed to be controlled via a REST api which uses a global (user independent) authentication. Obviously, an arbitrary user should not be allowed to change preferences (and other settings) for a different user. This implies that a REST client has to check user access rights and (especially) verify the user's identity. The typical way for user identity verification would be to check that the user knows the password registered with this user in "mailman". However, the REST api lacks a corresponding operation. The REST api should probably be extended by a "verify_password" user subresource. To avoid passwords being logged by typical webserver logging, the password to be verified should probably be submitted via "POST" (not transmitted as part of the "URL"). If the project does not want to go this route (password verification via a REST operation), then it must document how a client can verify a given cleartext password against the encrypted password information available as user attribute. ** 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/1065447 Title: Feature request: REST api to verify password To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1065447/+subscriptions

3 5

[Bug 1062893] Re: No ability to add prefix on subject line
by Barry Warsaw 31 Dec '12

31 Dec '12

** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions

1 0

[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

[Bug 1062963] Re: Admin notification not received
by Barry Warsaw 23 Dec '12

23 Dec '12

OP: Can you provide more information? What changes do you expect to get notified on? Do you have a way to reproduce the problem? There are two attributes which control admin notifications. admin_immed_notify controls whether the admin is notified when a subscription (or unsubscription) request is held for moderator approval. admin_notify_mchanges controls whether the administrator gets a notification when a user is subscribed to the mailing list. ** Changed in: mailman Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1062963 Title: Admin notification not received To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062963/+subscriptions

1 0

[Bug 1092973] [NEW] implement flame-retardant option
by Carnë Draug 21 Dec '12

21 Dec '12

Public bug reported: This is more of a feature request than a bug. I have added it to my todo list but it's been there long enough to know that I probably will never get around to do it. I'm posting it here as an idea in case anyone also finds it good and wishes to pick it up. I had read about the idea the first time on this post (http://www.shirky.com/writings/group_user.html) which does mention mailman. It's a bit long post but near the end, on the "Novel Operations on Social Facts" section proposes some ideas for mailing lists. There's other worthy ideas there but the one I was planning to implement was the flame retardant in which basically if a user has been too active, its e-mails would be sent with a delay. I think that's pretty neat. Recently the mailing list where I am now is facing such problems. This could be set to the whole mailing list or as an alternative to place an user under moderation (for those that are actual helpful members of the mailing list but have a tendency to get too much involved in flame wars). ** 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/1092973 Title: implement flame-retardant option To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1092973/+subscriptions

1 0

[Bug 1062893] Re: No ability to add prefix on subject line
by Barry Warsaw 17 Dec '12

17 Dec '12

** Branch linked: lp:~terriko/mailman/subject_prefix ** Changed in: mailman Assignee: (unassigned) => Terri (terriko) ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 3.0.0b3 ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1062893 Title: No ability to add prefix on subject line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062893/+subscriptions

1 0