Mailman-coders July 2012

mailman-coders@python.org

25 participants
99 discussions

[Bug 975698] [NEW] On email validation confirmation, trigger an event

by Barry Warsaw

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

8 years, 7 months

[Bug 975700] [NEW] On password change, trigger an event

by Barry Warsaw

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

8 years, 7 months

[Bug 987563] [NEW] List-Post should be NO when posting is not allowed

by Barry Warsaw

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

8 years, 7 months

[Bug 1015757] [NEW] Migrate from flufl.password to passlib

by Barry Warsaw

Public bug reported: http://packages.python.org/passlib/index.html This is a much better password hashing library than flufl.password, so let's switch to it. ** Affects: mailman Importance: Undecided Assignee: Barry Warsaw (barry) 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/1015757 Title: Migrate from flufl.password to passlib To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1015757/+subscriptions

8 years, 7 months

[Bug 1024509] [NEW] Link between members and mailing lists should use List-ID

by Barry Warsaw

Public bug reported: The link between users and the mailing lists they are subscribed to is kept in the IMember implementation (and the member table). To allow for separation of database, these are not foreign keys, but instead string references using the fqdn_listname. However, mailing lists can be renamed, so using the fqdn_listname is wrong. List-ID is a much more stable identifier, so that should be used instead. ** 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/1024509 Title: Link between members and mailing lists should use List-ID To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1024509/+subscriptions

8 years, 7 months

[Bug 1031391] [NEW] remove msgdata['received_time'] in mailman.app.moderator before calling IListRequests.hold_request

by Robert Niederreiter

Public bug reported: msgdata['received_time'] in mailman.app.moderator.hold_message contains datetime.datetime object when being called. this causes hold_request to fail -> it expects only strings as additional data. so either remove received_time like so: http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7159 before calling hold_request, convert received_time to string before calling hold_request, or improve mailman.model.request.ListRequests.hold_request as already commented in source code (maybe to also accept datetime instances?) cheers, robert ** Affects: mailman Importance: Undecided Status: New ** Description changed: msgdata['received_time'] in mailman.app.moderator.hold_message contains datetime.datetime object when being called. this causes hold_request to fail -> it expects only strings as additional data. so either remove received_time like so: http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7159 before calling hold_request, convert received_time to string before calling hold_request, or improve mailman.model.request.ListRequests.hold_request as already - commented in source code + commented in source code (maybe to also accept datetime instances?) cheers, robert -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1031391 Title: remove msgdata['received_time'] in mailman.app.moderator before calling IListRequests.hold_request To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1031391/+subscriptions

8 years, 7 months

[Bug 1031393] [NEW] wrong attribute name according to mailman.interfaces.mailinglist.IMailingList

by Robert Niederreiter

Public bug reported: as pointed out here... http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7160 http://bazaar.launchpad.net/~rnix/mailman/anon-subscribe/revision/7161 ...it seems that mlist.archive is no longer or is declared in the interface the wrong way cheers robert ** 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/1031393 Title: wrong attribute name according to mailman.interfaces.mailinglist.IMailingList To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1031393/+subscriptions

8 years, 7 months

[Bug 953497] [NEW] Unused variable in loop

by Andrea Crotti

Public bug reported: in mailman/src/mailman/config/config.py the property header_matches for match in matches: yield (matches.header, matches.pattern, matches.chain) has a probable typo in the loop, and the variablel looping over is not used. ** 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/953497 Title: Unused variable in loop To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/953497/+subscriptions

8 years, 7 months

[Bug 963612] [NEW] ArchiveRunner has Pipermail artifacts

by Barry Warsaw

Public bug reported: When the original message has a Date header, ArchiveRunner._dispose() will check to see if the date should be trusted or clobbered. This code still references the out of date [archiver.pipermail]clobber_date_policy value. The config var needs to be moved or renamed and the functionality re-implemented (and tested!). For now, I'm going to disable this bit of code but it should be re-addressed for beta2. ** Affects: mailman Importance: Medium 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/963612 Title: ArchiveRunner has Pipermail artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/963612/+subscriptions

8 years, 7 months

[Bug 967409] [NEW] NewsRunner needs to be ported to Mailman 3

by Barry Warsaw

Public bug reported: In src/mailman/runners/news.py, prepare_message() is ported to mm3 and tested, however ArchiveRunner is not. We also need some unittests, and this probably means that we'll pull in mock as a test dependency. It beats requiring a real NNTP server. ** Affects: mailman Importance: Undecided Status: Triaged ** 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/967409 Title: NewsRunner needs to be ported to Mailman 3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967409/+subscriptions

8 years, 7 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders July 2012