Mailman-coders October 2012

mailman-coders@python.org

24 participants
100 discussions

[Bug 987019] [NEW] special case archive@mail-archive.com
by Jeff Breidenbach 23 May '15

23 May '15

Public bug reported: As discussed, confusion can arise between the archiving module for mailman, and the manual mechanism of adding the archiving subscriber. Do something, perhaps involving ban lists, to keep us out of trouble. (I don't really know what is most sensible. I'd always imagined the archiving module would simply be adding the special subscriber address, but that's not the way it turned out.) ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: 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/987019 Title: special case archive(a)mail-archive.com To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987019/+subscriptions

3 2

[Bug 985149] [NEW] Add List-Post value to permalink hash input
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: Currently, we define the X-Message-ID-Hash as the base32 encoding of the sha1 hash of the Message-ID content (sans angle brackets as defined in RFC 5322). The suggestion is made that List-Post value should be added to this hash so as to be able to distinguish cross-posted messages. This should be fine, and pretty easy. My only concern is that the header name is now a misnomer. I wonder, is it worth coming up with a better header? Now's the time to do it since it's likely that there are almost no consumers of this standard. What about `Permalink-Hash` ? ** 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/985149 Title: Add List-Post value to permalink hash input To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/985149/+subscriptions

4 7

[Bug 982555] [NEW] LMTP should reject unknown lists in RCPT-stage
by Bernhard Schmidt 23 May '15

23 May '15

Public bug reported: At the moment the LMTP runner rejects mails to non-existing lists after the DATA stage. # telnet localhost 8024 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.svr02.mucip.net Python LMTP runner 1.0 MAIL FROM: <berni(a)birkenwald.de> 250 Ok RCPT TO: <thislistdoesnotexist(a)birkenwald.de> 250 Ok DATA 354 End data with <CR><LF>.<CR><LF> Message-ID: <bal(a)blubb.de> as . 550 Requested action not taken: mailbox unavailable It should reject invalid addresses in the RCPT TO stage, this way it could easily be used with Postfix' feature "reject_unverified_recipient" to avoid accepting and then bouncing messages. ** 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/982555 Title: LMTP should reject unknown lists in RCPT-stage To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/982555/+subscriptions

4 3

[Bug 975711] [NEW] Store the list style in the mailinglist table
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: It seems useful to record the list style that was used to create the mailing list. Maybe this could be used later to propagate changes in the style to lists that were created with it. The problem is that the style machinery is way to over-engineered. There's actually a priority system for applying a style to a mailing list. This should be simplified anyway, and then we could store the style name in the database. It makes no sense to do this with the complicated scheme currently used. ** 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/975711 Title: Store the list style in the mailinglist table To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975711/+subscriptions

2 1

[Bug 975670] [NEW] Documentation fails to specifying sphinx requirement
by Richard Wackerbarth 23 May '15

23 May '15

Public bug reported: Sphinx is required to build the documentation. However, it is not automatically installed and the installation documentation fails to instruct that it be installed before building the online docs. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: 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/975670 Title: Documentation fails to specifying sphinx requirement To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975670/+subscriptions

5 6

[Bug 965520] [NEW] Improve installation documentation
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: This page: http://packages.python.org/mailman/src/mailman/docs/START.html describes how to install, configure, and start Mailman 3. It's a bit sparse and out-of-date. For example, it doesn't describe all the locations that mailman.cfg is search for. It also doesn't describe installing and running mm3 in a virtualenv. This would make a nice bite-sized bug for someone wanting to contribution to Mailman. ** Affects: mailman Importance: Undecided Status: New ** Tags: documentation easy mailman3 ** Tags removed: bite-size ** Tags added: easy -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/965520 Title: Improve installation documentation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/965520/+subscriptions

6 12

[Bug 881316] [NEW] RuntimeError: maximum recursion depth exceeded while pickling an object
by Vincent Fretin 23 May '15

23 May '15

Public bug reported: With mailman 3.0.0a8. I got the following traceback from a html mail with html signature+image from Outlook, Oct 14 09:21:31 2011 (17579) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/chains/hold.py", line 245, in _process nmsg.send(mlist, **dict(tomoderators=True)) File "/home/zope/mailman/src/mailman/email/message.py", line 198, in send self._enqueue(mlist, **_kws) File "/home/zope/mailman/src/mailman/email/message.py", line 216, in _enqueue virginq.enqueue(self, **str_keywords) File "/home/zope/mailman/src/mailman/core/switchboard.py", line 133, in enqueue msgsave = cPickle.dumps(_msg, protocol) RuntimeError: maximum recursion depth exceeded while pickling an object It's really an obscure issue for me. I resolved it by adding sys.setrecursionlimit(10000) in src/mailman/core/switchboard.py before msgsave = cPickle.dumps(_msg, protocol) line 134 and doing bin/mailman unshunt fixed the issue. By default sys.getrecursionlimit() returns 1000. If you want to have a test email to reproduce, I can ask my customer to send an email to a test mailing-list. ** 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/881316 Title: RuntimeError: maximum recursion depth exceeded while pickling an object To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881316/+subscriptions

4 6

[Bug 881312] [NEW] Properly decode payload
by Vincent Fretin 23 May '15

23 May '15

Public bug reported: With mailman 3.0.0a8 in src/mailman/runners/command.py, there is an issue with body = part.get_payload(decode=True) if you send a mail to test-unsubscribe(a)example.com, with accents in the mail, in the signature for example, you get a body string encoded in iso-8859-1. When you try to concatenate iso-8859-1 string with unicode, this the case when the mail body with "Unprocessed:" and "Ignored:" is generated, you get a UnicodeDecodeError ascii. The code should be modified to correctly decode the mail body like it is done in src/mailman/pipeline/decorate.py mcset = msg.get_content_charset() or 'us-ascii' unicode(msg.get_payload(decode=True), mcset) There are similar issues in src/mailman/rules/administrivia.py with the line: if line == '': where it give you a warning because it compare an iso to an empty unicode. and in src/mailman/rules/approved.py where it simply crashes: Oct 18 17:54:41 2011 (18207) Traceback (most recent call last): File "/home/zope/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/zope/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/zope/mailman/src/mailman/runners/incoming.py", line 65, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/zope/mailman/src/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/zope/mailman/src/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe0 in position 14: invalid continuation byte Currently, mailman is unusable for another language than English, like French. ** 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/881312 Title: Properly decode payload To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881312/+subscriptions

4 6

[Bug 826861] [NEW] doctests failing on Centos 6 due to "unprintable" error objects
by Stephen A. Goss 23 May '15

23 May '15

Public bug reported: On Centos 6 (64 bit), the following tests fail due to what looks like some kind of Python object printing quirk with the version that ships with RHEL 6 and derivatives: src/mailman/model/docs/membership.txt src/mailman/model/docs/users.txt The errors all look like this: File "/home/sgoss/mailman_clone/src/mailman/model/docs/membership.txt", line 296, in membership.txt Failed example: gwen_member.address = new_address Differences (ndiff with -expected +actual): Traceback (most recent call last): - ... - UnverifiedAddressError: gperson(a)example.com + File "/usr/lib64/python2.6/doctest.py", line 1248, in __run + compileflags, 1) in test.globs + File "<doctest membership.txt[68]>", line 1, in <module> + gwen_member.address = new_address + File "/home/sgoss/mailman_clone/src/mailman/model/member.py", line 116, in address + raise UnverifiedAddressError(new_address) + UnverifiedAddressError: <unprintable UnverifiedAddressError object> The system reports Python version 2.6.5. This error does not seem to occur with Python 2.7 on Ubuntu 11.04. One possibility is that for some reason when it comes to printing out those error objects, Python doesn't have a default encoding scheme for representing the embedded unicode strings in that particular context (email address in the above example). ** 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/826861 Title: doctests failing on Centos 6 due to "unprintable" error objects To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/826861/+subscriptions

3 7

[Bug 1004044] [NEW] BrowserID system does not keep me logged in
by Jeff Marshall 28 Apr '15

28 Apr '15

Public bug reported: The BrowserID system on Postorius logs me out all the time, even after just a few page views. I'm constantly having to hit the sign-in button again. If I am trying to perform an administrative function I have to do it very quickly after signing in or else I'm logged out again. There's no error when I get logged out. It simply loses my logged-in state. Creating a superuser account via the command line and logging in that way works flawlessly without any unexpected logouts. The problem is isolated to BrowserID login only. Mac OS X: 10.7.3 Chrome: 19.0.1084.46 (all default settings on the browser) ** Affects: postorius Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1004044 Title: BrowserID system does not keep me logged in To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004044/+subscriptions

2 1

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

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders October 2012