Mailman-coders April 2014

mailman-coders@python.org

51 participants
169 discussions

[Bug 1285496] [NEW] A test in src/mailman/model/docs/registration.rst fails if Python default encoding is UTF-8
by Mark Sapiro 23 May '15

23 May '15

Public bug reported: The Invalid email addresses section in the doctests in src/mailman/model/docs/registration.rst attempts to register various invalid email addresses and checks that they are rejected. In particular, the test >>> registrar.register(mlist, '\xa0(a)example.com') Traceback (most recent call last): ... InvalidEmailAddressError: \xa0(a)example.com will fail if python's sys.getdefaultencoding() returns 'UTF-8' because the invalid address is reported with the UTF-8 encoding of nonbreaking space rather than \xa0. ** 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/1285496 Title: A test in src/mailman/model/docs/registration.rst fails if Python default encoding is UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1285496/+subscriptions

2 1

[Bug 1252575] [NEW] The Mail<->News gateway doesn't honor moderation or *_these_nonmembers for messages gated from usnet.
by Mark Sapiro 23 May '15

23 May '15

Public bug reported: Messages gated to a list from usenet bypass all the checks in Moderate.py. It is appropriate to bypass generic_nonmember_action because many usenet posts will be from nonmembers of the list, but if the sender is a moderated member or a nonmember matching one of the *_these_nonmembers filters, those things should be honored. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1252575 Title: The Mail<->News gateway doesn't honor moderation or *_these_nonmembers for messages gated from usnet. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1252575/+subscriptions

4 5

[Bug 1197473] [NEW] moderating usenet->mailman posts
by Karl Berry 23 May '15

23 May '15

Public bug reported: In http://www.mail-archive.com/mailman-users%40python.org/msg62889.html, I explained the (very strong) desirability of having posts made from Usenet to Mailman be subject to normal moderation rules instead of automatically and unconditionally approved. (In short, to not let Usenet spam through to the mailing lists without any checking.) In his reply, http://www.mail-archive.com/mailman- users%40python.org/msg62890.html, Mark gave a simple one-line change (that is working fine so far as we can tell). When I asked, Mark told me that the change couldn't be made for mailman 2.1, since it would need to be a user option and thus have i18n impact, so suggested that I post it here, tagged mailman3, which I hope I've done here. Happy hacking, Karl ** 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/1197473 Title: moderating usenet->mailman posts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1197473/+subscriptions

3 2

[Bug 1190582] [NEW] Add some common filters to REST API resources that expose collections
by Florian Fuchs 23 May '15

23 May '15

Public bug reported: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test(a)example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there are x unadvertised lists in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 rest ** Description changed: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test(a)example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there are x unadvertised list in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept - a number of common filter params which are used for the WHERE clause of + a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both ** Description changed: When Postorius GETs a collection of lists from the REST API, it will in most situations only use a subset (the ones that are set to "advertise in list index"). This is a minor issue as long as the request isn't paginated, but can lead to incorrect item counts when it is. Example: GET /lists/test(a)example.com?page=1&count=10 will return all lists within the range [:10] from the database. If there - are x unadvertised list in the result, the page will only show 10 - x + are x unadvertised lists in the result, the page will only show 10 - x results. I guess the most common way to solve this is for the REST API to accept a number of common filter params which are used in the WHERE clause of the database query. In this case: GET /lists/test(a)example.com?page=1&count=10&advertised=(0|1|2) 0 - only non-advertised 1 - only advertised 2 - both -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1190582 Title: Add some common filters to REST API resources that expose collections To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1190582/+subscriptions

2 1

[Bug 1170726] [NEW] The LMTP server needs to check acceptable aliases
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: The LMTP server currently does a sanity check on the To field of the incoming message, to ensure that it is addressed to a valid mailing list. This check ignores acceptable aliases, but it should honor them. ** 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/1170726 Title: The LMTP server needs to check acceptable aliases To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1170726/+subscriptions

4 3

[Bug 1170388] [NEW] the tomoderators argument to "send" is ignored
by Stephen A. Goss 23 May '15

23 May '15

Public bug reported: searching all the code (mailman-3.0.0b3) (with ack) for "tomoderators" returns this: $ ack -ai tomoderators src/mailman/bin/checkdbs.py 202: msg.send(mlist, **{'tomoderators': True}) src/mailman/chains/hold.py 241: nmsg.send(mlist, **dict(tomoderators=True)) src/mailman/app/moderator.py 228: msg.send(mlist, tomoderators=True) 299: msg.send(mlist, tomoderators=True) I can't see where this option is actually used. In practice, the moderation notification sent from hold.py in line 241 just goes to everyone in the mailing list, not the moderators. ** 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/1170388 Title: the tomoderators argument to "send" is ignored To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1170388/+subscriptions

2 3

[Bug 1104505] [NEW] Web posting interface
by Kẏra 23 May '15

23 May '15

Public bug reported: There should be an interface for posting to a list from the Web UI ** Affects: mailman Importance: Undecided Status: New ** Tags: wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1104505 Title: Web posting interface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1104505/+subscriptions

4 5

[Bug 1104484] [NEW] Link to post in email footer
by Kẏra 23 May '15

23 May '15

Public bug reported: With the new web UI, there should be a feature to have message footers include a link to the message in the web UI ** Affects: mailman Importance: Undecided Status: New ** Tags: wishlist -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1104484 Title: Link to post in email footer To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1104484/+subscriptions

4 4

[Bug 1096812] [NEW] Threading issues in mailman 3.0.0b2
by David Bell 23 May '15

23 May '15

Public bug reported: I am seeing concurrency issues when using mailman 3 in a threaded application server. Reading the Storm documentation it states that "Store objects are not threadsafe. [...] Therefore, the best policy is usually to create a Store object for each thread which needs one" (https://storm.canonical.com/Manual#Working_with_multiple_threads) In mailman/database/base.py:141 I see a Store being created and cached. As recommended in the storm docs, Stores should not be cached. ** 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/1096812 Title: Threading issues in mailman 3.0.0b2 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1096812/+subscriptions

3 2

[Bug 1096066] [NEW] mailman raises exception if passed message not contains text/plain message part
by Robert Niederreiter 23 May '15

23 May '15

Public bug reported: If message sent to mailman not contains a text/plain message part (i.e. only text/html), an error is raised and the message gets swallowed. I fixed this this way in my setup: === modified file 'src/mailman/rules/approved.py' --- src/mailman/rules/approved.py 2012-07-02 20:08:58 +0000 +++ src/mailman/rules/approved.py 2013-01-04 13:31:09 +0000 @@ -73,6 +73,8 @@ stripped = False for part in typed_subpart_iterator(msg, 'text', 'plain'): break + if not part: + return False payload = part.get_payload(decode=True) if payload is not None: charset = part.get_content_charset('us-ascii') regards, 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/1096066 Title: mailman raises exception if passed message not contains text/plain message part To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1096066/+subscriptions

3 2

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders April 2014