Mailman 3 August 2012 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net 19 Aug '22

19 Aug '22

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[Bug 965532] [NEW] Need a script to upgrade from MM2 to MM3
by Barry Warsaw 13 Dec '21

13 Dec '21

Public bug reported: We need a script, documentation, or other procedure to help people migrate from Mailman 2 to Mailman 3. ** 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/965532 Title: Need a script to upgrade from MM2 to MM3 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/965532/+subscriptions

8 21

[Bug 544477] [NEW] setting localhost in postfix_lmtp breaks delivery
by Patrick Ben Koetter 26 Sep '20

26 Sep '20

Public bug reported: Setting localhost in postfix_lmtp works against Postfix defaults and breaks delivery. Reason: The Postfix lmtp client only uses dns queries by default to search for hostnames. If the DNS server does not provide an answer for "localhost" delivery from the lmtp client to mailman fails. Solution: Provide "127.0.0.1" instead of "localhost". This does not require DNS and is even faster because it saves DNS lookups. Example: hey2(a)mailman.state-of-mind.de lmtp:[localhost.localdomain]:8024 ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- setting localhost in postfix_lmtp breaks delivery https://bugs.launchpad.net/bugs/544477 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 7

[Bug 883193] [NEW] Remove the X- prefix from some headers
by Barry Warsaw 14 Jan '19

14 Jan '19

Public bug reported: MM3 still uses a lot of X- headers, but some of the X- prefixes can be removed. In general, we can just claim the Mailman- prefix for Mailman specific headers. Candidates include: Mailman-Rule-Hits Mailman-Rule-Misses Mailman-Version Mailman-Approved-At Mailman-LMTP-MailFrom (i.e. X-MailFrom) Mailman-Copy (or remove this header) Mailman-Content-Filter (from X-Content-Filtered-By) Also, fix the outdated comments about add-dup-header in avoid_duplicates.py and verp.py. Probably also get rid of X-List-Administrivia (and possibly reduced_list_headers). These seem unnecessary now. ** 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/883193 Title: Remove the X- prefix from some headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/883193/+subscriptions

3 6

[Bug 701558] [NEW] Content filtering leaves a single sub-part in a multipart message.
by Mark Sapiro 09 Jun '17

09 Jun '17

Public bug reported: If the original message is multipart but not multipart/alternative and content filtering removes all but one part, the message is left as a multipart message with only the one sub-part instead of being recast as just the sub-part. This can cause msg_header and/or msg_footer to be added as separate parts to a text/plain message instead of being added to the text/plain body part. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Triaged ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Milestone: None => 2.1.15 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) ** Description changed: - If the original message in multipart but not multipart/alternative and + If the original message is multipart but not multipart/alternative and content filtering removes all but one part, the message is left as a multipart message with only the one sub-part instead of being recast as just the sub-part. This can cause msg_header and/or msg_footer to be added as separate - parts to a text/plain message instead if being added to the text/plain + parts to a text/plain message instead of being added to the text/plain body part. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/701558 Title: Content filtering leaves a single sub-part in a multipart message.

3 7

[Bug 576675] [NEW] Content filtering fails to collapse alternatives.
by Mark Sapiro 09 Jun '17

09 Jun '17

Public bug reported: Collapsing multipart/alternative parts to just the first alternative only works if the message itself is multipart/alternative, or the multipart/alternative part is at the first sub-level. For example, given this structure: multipart/mixed | multipart/related | | multipart/alternative | | | text/plain | | | text/html | | image/jpeg | application/msword The multipart/alternative part will not be collapsed. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => In Progress ** Changed in: mailman Milestone: None => 2.1.14 ** Changed in: mailman Assignee: (unassigned) => Mark Sapiro (msapiro) -- Content filtering fails to collapse alternatives. https://bugs.launchpad.net/bugs/576675 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 7

[Bug 978351] [NEW] Content Filtering *_filename_extension matches are case sensitive.
by Mark Sapiro 09 Jun '17

09 Jun '17

Public bug reported: If the case of the filename extension in the message doesn't agree with that in *_filename_extension, they won't match. Matching should be case insensitive. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Affects: mailman/2.1 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Released ** Affects: mailman/3.0 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Tags: mailman3 ** Also affects: mailman/3.0 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: Fix Released ** Also affects: mailman/2.1 Importance: Undecided Status: New ** Changed in: mailman/3.0 Status: Fix Released => In Progress ** Changed in: mailman/3.0 Milestone: mailman-2.1 => 3.0.0b2 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/978351 Title: Content Filtering *_filename_extension matches are case sensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/978351/+subscriptions

3 5

[Bug 757062] [NEW] Content filtering can remove the headers from a message/rfc822 part.
by Mark Sapiro 09 Jun '17

09 Jun '17

Public bug reported: If Content filtering accepts both message/rfc822 and multipart/alternative MIME parts, and a message/rfc822 part contains a message whose content type is multipart/alternative and collapse_alternatives is Yes, the headers of the message in the message/rfc822 part will be lost. ** Affects: mailman Importance: Low Assignee: Mark Sapiro (msapiro) Status: In Progress ** 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/757062 Title: Content filtering can remove the headers from a message/rfc822 part.

3 12

[Bug 775294] [NEW] Set lifetime for input forms
by Tokio Kikuchi 05 Sep '16

05 Sep '16

*** This bug is a security vulnerability *** Private security bug reported: We may have to set lifetime for input forms because of recent activities on cross-site request forgery (CSRF). The form lifetime is successfully deployed in frameworks like web.py or plone etc. Proposed branch lp:~tkikuchi/mailman/form-lifetime implement lifetime in admin, admindb, options and edithtml interfaces. Other forms like create and rmlist have confirmation by password thus are safe regarding CSRF. The form generation time is set by a hidden parameter whose value is calculated following the mailman cookie algorithm. The default lifetime is set 1 hour in Default.py thus configurable by a site administrator. If a password is set in request, authorization cookie is discarded so the password authentication is forced. Wget tricks to manage list in FAQ can be used as they are now. ** Affects: mailman Importance: Undecided Status: New ** Branch linked: lp:~tkikuchi/mailman/form-lifetime -- You received this bug notification because you are a member of Mailman Coders, which is a direct subscriber. https://bugs.launchpad.net/bugs/775294 Title: Set lifetime for input forms

2 5

[Bug 889829] [NEW] setup takes zope interface 3.5.1, but needs 3.8.0
by Harry Enke 31 Jul '15

31 Jul '15

Public bug reported: separate installation of zope interface 3.8.0 fixes the issue, afterwards mailman 3.0.0.8a OS: Scientific Linux 6.1, Python 2.6.6 ** 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/889829 Title: setup takes zope interface 3.5.1, but needs 3.8.0 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889829/+subscriptions

3 7

[Bug 1036207] [NEW] mailman.client hangs accessing moderation queue
by Stephen Turnbull 08 Jun '15

08 Jun '15

Public bug reported: Here's what I did as recorded in Terminal.app: steve@turnbull:~/src/Mailman3/mailman.client$ python Python 2.7.3rc2 (default, Apr 22 2012, 22:30:17) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import os >>> import time >>> import subprocess >>> from mailman.client import Client >>> c = Client('http://localhost:8001/3.0', 'restadmin', 'restpass') >>> dump(c.system) Traceback (most recent call last): File "<stdin>", line 1, in <module> NameError: name 'dump' is not defined >>> c.lists [<List "mm3-test(a)turnbull.sk.tsukuba.ac.jp">] >>> c.domains [<Domain "turnbull.sk.tsukuba.ac.jp">] >>> print c.domains[0].url_host turnbull.sk.tsukuba.ac.jp >>> print c.domains[0].mail_host turnbull.sk.tsukuba.ac.jp >>> l = c.lists[0] >>> l.fqdn_listname u'mm3-test(a)turnbull.sk.tsukuba.ac.jp' >>> c.get_list('mm3-test(a)turnbull.sk.tsukuba.ac.jp') <List "mm3-test(a)turnbull.sk.tsukuba.ac.jp"> >>> c.get_list(u'mm3-test(a)turnbull.sk.tsukuba.ac.jp') <List "mm3-test(a)turnbull.sk.tsukuba.ac.jp"> >>> c.members [<Member "turnbull(a)sk.tsukuba.ac.jp" on "mm3-test(a)turnbull.sk.tsukuba.ac.jp">] >>> print c.members[0].self_link http://localhost:8001/3.0/members/230487102891977069915270988864921324936 >>> print c.members[0].link Traceback (most recent call last): File "<stdin>", line 1, in <module> AttributeError: '_Member' object has no attribute 'link' >>> print c.users[0] <User "None" (323817100493882819169277267745120573853)> >>> print c.users [<User "None" (323817100493882819169277267745120573853)>] >>> print c.users[0].addresses <mailman.client._client._Addresses object at 0x7f6b849c7a10> >>> print c.users[0].addresses[0] Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: '_Addresses' object does not support indexing >>> for a in print c.users[0].addresses: File "<stdin>", line 1 for a in print c.users[0].addresses: ^ SyntaxError: invalid syntax >>> for a in c.users[0].addresses: ... print a ... turnbull(a)sk.tsukuba.ac.jp >>> for a in sorted(l.settings): ... print a + ': ' + string(l.settings[a]) ... Traceback (most recent call last): File "<stdin>", line 2, in <module> NameError: name 'string' is not defined >>> for a in sorted(l.settings): ... print a + ': ' + str(l.settings[a]) ... acceptable_aliases: [] admin_immed_notify: True admin_notify_mchanges: False administrivia: True advertised: True allow_list_posts: True anonymous_list: False autorespond_owner: none autorespond_postings: none autorespond_requests: none autoresponse_grace_period: 90d autoresponse_owner_text: autoresponse_postings_text: autoresponse_request_text: bounces_address: mm3-test-bounces(a)turnbull.sk.tsukuba.ac.jp collapse_alternatives: True convert_html_to_plaintext: False created_at: 2012-08-09T03:16:21.186456 default_member_action: defer default_nonmember_action: hold description: digest_last_sent_at: None digest_size_threshold: 30.0 display_name: Mm3-test filter_content: False fqdn_listname: mm3-test(a)turnbull.sk.tsukuba.ac.jp generic_nonmember_action: 1 http_etag: "b8b4e1df6bc8d8ee33f363927022d0bcc86569bb" include_rfc2369_headers: True join_address: mm3-test-join(a)turnbull.sk.tsukuba.ac.jp last_post_at: None leave_address: mm3-test-leave(a)turnbull.sk.tsukuba.ac.jp list_name: mm3-test mail_host: turnbull.sk.tsukuba.ac.jp next_digest_number: 1 no_reply_address: noreply(a)turnbull.sk.tsukuba.ac.jp owner_address: mm3-test-owner(a)turnbull.sk.tsukuba.ac.jp post_id: 1 posting_address: mm3-test(a)turnbull.sk.tsukuba.ac.jp posting_pipeline: default-posting-pipeline reply_goes_to_list: no_munging request_address: mm3-test-request(a)turnbull.sk.tsukuba.ac.jp scheme: http send_welcome_message: True volume: 1 web_host: turnbull.sk.tsukuba.ac.jp welcome_message_uri: mailman:///welcome.txt >>> dir() ['Client', '__builtins__', '__doc__', '__name__', '__package__', 'a', 'c', 'l', 'os', 'subprocess', 'time'] >>> dir(Client) ['__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__hash__', '__init__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'create_domain', 'delete_domain', 'delete_list', 'domains', 'get_domain', 'get_list', 'get_user', 'lists', 'members', 'preferences', 'system', 'users'] >>> dir(Client.system) ['__class__', '__delattr__', '__delete__', '__doc__', '__format__', '__get__', '__getattribute__', '__hash__', '__init__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__set__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', 'deleter', 'fdel', 'fget', 'fset', 'getter', 'setter'] >>> dir(l) ['__class__', '__delattr__', '__dict__', '__doc__', '__format__', '__getattribute__', '__hash__', '__init__', '__module__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', '_connection', '_get_info', '_info', '_url', 'accept_message', 'defer_message', 'delete', 'discard_message', 'display_name', 'fqdn_listname', 'get_member', 'held', 'list_name', 'mail_host', 'members', 'moderate_message', 'reject_message', 'settings', 'subscribe', 'unsubscribe'] >>> l._connection.__doc__ u'A connection to the REST client.' >>> l.held.__doc__ ^CTraceback (most recent call last): File "<stdin>", line 1, in <module> File "mailman/client/_client.py", line 350, in held 'lists/{0}/held'.format(self.fqdn_listname), None, 'GET') File "mailman/client/_client.py", line 114, in call response, content = Http().request(url, method, data, headers) File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1543, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1293, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/lib/python2.7/dist-packages/httplib2/__init__.py", line 1263, in _conn_request response = conn.getresponse() File "/usr/lib/python2.7/httplib.py", line 1030, in getresponse response.begin() File "/usr/lib/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib/python2.7/httplib.py", line 365, in _read_status line = self.fp.readline() File "/usr/lib/python2.7/socket.py", line 430, in readline data = recv(1) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/email/message.py", l\ ine 226, in _enqueue virginq.enqueue(self, **str_keywords) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/switchboard.py"\ , line 123, in enqueue msgsave = cPickle.dumps(_msg, protocol) After the above I tried a couple of things, like printing l.held (with no further attribute). These also hung for a few seconds and I interrupted with ^C. Eventually it failed with an error about not being connected to Mailman. I thought Mailman had crashed, but when I tried shutting down Mailman using bin/mailman, it seemed to shut down normally. ** 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/1036207 Title: mailman.client hangs accessing moderation queue To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1036207/+subscriptions

3 4

[Bug 1006345] [NEW] Anonymous subscription via confirmation email
by Robert Niederreiter 08 Jun '15

08 Jun '15

Public bug reported: Currently it is not possible to subscribe as anonymous user. ** Affects: postorius Importance: Undecided Status: New ** Tags: anonymous confirmation subscription ui -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1006345 Title: Anonymous subscription via confirmation email To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1006345/+subscriptions

7 16

[Bug 1023681] [NEW] bin/mailman -C config start does not work with a relativ config path
by AlexanderS 23 May '15

23 May '15

Public bug reported: During testing I encountered, that bin/mailman is not working correctly if you supply a relative path as -C argument. For the main process the path is converted into a absolute path during startup but the bin/master process is getting the relative filename but maybe a different working directory. The attached patch fixes that behavior by supplying the generated absolute pathname to the new process. ** 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/1023681 Title: bin/mailman -C config start does not work with a relativ config path To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1023681/+subscriptions

4 4

[Bug 998949] [NEW] Admin notice of held subscription is not fully in list's preferred language.
by Mark Sapiro 23 May '15

23 May '15

Public bug reported: When admin_immed_notify is Yes and subscribe_policy is approve, the Subject: of the notice to the admin is in the user's preferred language rather than the list's preferred language and it may not be properly RFC 2047 encoded. ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman/2.1 Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress ** Affects: mailman/3.0 Importance: Undecided Status: New ** Tags: mailman3 ** Also affects: mailman/2.1 Importance: Undecided Status: New ** Also affects: mailman/3.0 Importance: Undecided Status: New ** Tags added: mailman3 ** Changed in: mailman/2.1 Importance: Undecided => Medium ** Changed in: mailman/2.1 Status: New => In Progress ** Changed in: mailman/2.1 Milestone: None => 2.1.15 ** Changed in: mailman/2.1 Assignee: (unassigned) => Mark Sapiro (msapiro) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/998949 Title: Admin notice of held subscription is not fully in list's preferred language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/998949/+subscriptions

3 4

[Bug 987031] [NEW] archival hashes can be shortened
by Jeff Breidenbach 23 May '15

23 May '15

Public bug reported: The draft for archival hashes for mailman specifies 32 character, base 32 encoding. We can get away with 13 characters which expects the first collision at around 50 billion messages. The the wikipedia charts in their "birthday attack" article. It's not like an occasional collision is a big deal and this is not a security issue. ** 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/987031 Title: archival hashes can be shortened To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987031/+subscriptions

2 1

[Bug 856004] [NEW] "OperationalError: database is locked" encountered under very light load while using REST API
by Stephen A. Goss 23 May '15

23 May '15

Public bug reported: I've seen this error twice while running integration tests (of our own application) that access Mailman 3 using the API. The load on Mailman is very light, as all requests made to the API are serial, never in parallel. Of course the various processing queues in MM3 are separate processes and could be doing work concurrently. The platform is Centos 6. Traceback (most recent call last): File "/usr/lib64/python2.6/wsgiref/handlers.py", line 93, in run self.result = application(self.environ, self.start_response) File "/home/sgoss/mailman_clone/src/mailman/rest/wsgiapp.py", line 63, in __call__ config.db.commit() File "/home/sgoss/mailman_clone/src/mailman/database/stock.py", line 70, in commit self.store.commit() File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/store.py", line 122, in commit self._connection.commit() File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 126, in commit self.raw_execute("COMMIT", _end=True) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/databases/sqlite.py", line 154, in raw_execute return Connection.raw_execute(self, statement, params) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/database.py", line 321, in raw_execute self._check_disconnect(raw_cursor.execute, *args) File "/home/sgoss/phoenix-deploy/lib/python2.6/site-packages/storm-0.18-py2.6-linux-x86_64.egg/storm/database.py", line 366, in _check_disconnect return function(*args, **kwargs) OperationalError: database is locked The backend here is SQLite, which falls over very quickly under concurrent load. If the goal here is to create a stable mailing list server, maybe SQLite is a poor default. ** 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/856004 Title: "OperationalError: database is locked" encountered under very light load while using REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/856004/+subscriptions

3 8

[Bug 827547] [NEW] KeyError in "virgin" runner.
by Stephen A. Goss 23 May '15

23 May '15

Public bug reported: Not sure what caused this error that showed up in mailman.log: Aug 16 10:54:50 2011 (31400) Uncaught runner exception: u'foo.example.com' Aug 16 10:54:50 2011 (31400) Traceback (most recent call last): File "/home/sgoss/mailman_clone/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/runners/virgin.py", line 37, in _dispose process(mlist, msg, msgdata, 'virgin') File "/home/sgoss/mailman_clone/src/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/pipeline/cook_headers.py", line 360, in process process(mlist, msg, msgdata) File "/home/sgoss/mailman_clone/src/mailman/pipeline/cook_headers.py", line 202, in process listinfo = mlist.script_url('listinfo') File "/home/sgoss/mailman_clone/src/mailman/model/mailinglist.py", line 243, in script_url return urljoin(self.domain.base_url, target + '/' + self.fqdn_listname) File "/home/sgoss/mailman_clone/src/mailman/model/mailinglist.py", line 227, in domain return getUtility(IDomainManager)[self.mail_host] File "/home/sgoss/mailman_clone/src/mailman/model/domain.py", line 142, in __getitem__ raise KeyError(email_host) KeyError: u'foo.example.com' ** 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/827547 Title: KeyError in "virgin" runner. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/827547/+subscriptions

3 8

[Bug 956384] [NEW] Continuous integration and real-world testing
by Andrea Crotti 23 May '15

23 May '15

Public bug reported: This is not a real bug, I would just like to start a discussion about what can be done to set up a continuos integration system. Is there any Jenkins server which can be used? Another thing which I was thinking is if we have some real tests on real systems with various MTA such as Postfix/Exim. I haven't tried it yet but it seems that http://vagrantup.com/ and puppet could really be very nice tools for the job. And we could then 1. fire up a VM 2. install the different MTAs 3. create some complicated mailing lists and check that everything works correctly Other ideas? ** 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/956384 Title: Continuous integration and real-world testing To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/956384/+subscriptions

3 4

[Bug 1035061] [NEW] setup.py build_sphinx is broken
by Stephen Turnbull 23 May '15

23 May '15

Public bug reported: Like this: steve@turnbull:~/src/Mailman3/mailman-trunk$ python setup.py build_sphinx usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'build_sphinx' For more information (version, configuration, and build log), see Bug #1035057. ** 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/1035061 Title: setup.py build_sphinx is broken To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035061/+subscriptions

4 4

[Bug 1035021] [NEW] Referring people to launchpad for lazr.config docs is rude
by Stephen Turnbull 23 May '15

23 May '15

Public bug reported: I suggest snarfing their docs, and rewriting them from a user's point of view. Feel free to assign it to me. :-) ** 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/1035021 Title: Referring people to launchpad for lazr.config docs is rude To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035021/+subscriptions

3 3

[Bug 1004056] [NEW] ability to add administrator via command line
by Jeff Marshall 23 May '15

23 May '15

Public bug reported: How do I add another person as an administrator to either a single >list or to my full mailman installation? I don't see this in either >Postorius or the command line tools. It would be useful to have a command line interface for adding extra administrators to a mailing list. It could either be added: 1) to the existing 'members' subcommand as an additional option on the --add command (like --admin --add blah(a)blah.com) 2) to the existing 'members' subcommand as a separate post-add step (step 1: --add blah(a)blah.com step 2: --admin blah(a)blah.com to add admin rights to that existing subscriber) 3) a new subcommand #2 seems like a reasonable approach. #1 is limited because you could only give admin rights when first adding a user. ** 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/1004056 Title: ability to add administrator via command line To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1004056/+subscriptions

3 2

[Bug 975708] [NEW] Switch to the `requests` package
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: The `requests` package <http://pypi.python.org/pypi/requests/0.11.1> was all the rage at Pycon 2012. Seems like it could replace the use of several similar packages like httplib2, urllib2, etc. For future investigation. ** Affects: mailman Importance: Low 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/975708 Title: Switch to the `requests` package To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975708/+subscriptions

2 1

[Bug 975707] [NEW] Investigate something like ZeroMQ
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: At Pycon, we talked about the need for the core to potentially push data to Postorius, HyperKitty, and other components. It makes much more sense for the core to be capable of publishing events and data to a messaging system like ZeroMQ, which those other components could subscribe to. This is a placeholder for future investigation. ** Affects: mailman Importance: Low 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/975707 Title: Investigate something like ZeroMQ To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975707/+subscriptions

2 1

[Bug 975705] [NEW] Rip out or redesign the topic system
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: At Pycon, it was observed that the topic system as it exists in mm2.1 isn't really all that useful. Terri had some thoughts about that in regards to work that Systers did. This is mostly a placeholder for future ideas and to get it out of my TODO list. :) ** Affects: mailman Importance: Low 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/975705 Title: Rip out or redesign the topic system To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975705/+subscriptions

4 4

[Bug 975703] [NEW] -d should (maybe) be the default for `bin/mailman create`
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: `bin/mailman create` has a -d option which says to create the domain of the new mailing list's posting address if it doesn't already exist. At Pycon it was observed that it was kind of silly to always have to specify -d and that maybe it should be the default. The reason I didn't do that was because of typos, which would be a bit of work to undo. Maybe once we have list renaming exposed, this would be useful. But I'm still not sure. ** Affects: mailman Importance: Low Status: Triaged ** 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/975703 Title: -d should (maybe) be the default for `bin/mailman create` To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975703/+subscriptions

2 1

[Bug 975702] [NEW] Implement a pipeline in other runners
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: Stephen observed that it might be useful to implement a pipeline of handlers (even chain processing?) for other runners such as archive, bounce, and command. This is probably not something for 3.0 final, thus I'm marking it triaged,low. But it's an interesting idea and may lead to other useful refactoring. ** Affects: mailman Importance: Low 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/975702 Title: Implement a pipeline in other runners To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975702/+subscriptions

3 2

[Bug 973790] [NEW] 'approved' rule should not modify the message
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: In Mailman 3, technically rules should not have side effects. The 'approved' rule breaks this because it removes the Approved header (and other supported headers) from the message. There should instead be a handler that does the header cleaning, and the rule should not do this. >From an implementation standpoint, the same code can be used in both the handler and in the rule. You can use a slightly different API wrapper and use a flag to indicate whether the header should be removed or not. OTOH, some clever refactoring might make better sense. ** 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/973790 Title: 'approved' rule should not modify the message To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/973790/+subscriptions

3 3

[Bug 967954] [NEW] IMessageStore should be exposed as a top level REST resource
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: At the simplest, it should support GET on a Message-ID or X-Message-ID- Hash value and return the bytes of the stored message, or 404. ** 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/967954 Title: IMessageStore should be exposed as a top level REST resource To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967954/+subscriptions

2 3

[Bug 953531] [NEW] Add graphs of the overall architecture
by Andrea Crotti 23 May '15

23 May '15

Public bug reported: Adding to the documentation some graphs in graphviz format. ** 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/953531 Title: Add graphs of the overall architecture To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/953531/+subscriptions

4 5

[Bug 937154] [NEW] bin/disabled.py is nonfunctional
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: The bin/disabled.py script needs tests, documentation, and fixing in Mailman 2. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: Confirmed ** Tags: mailman3 ** Changed in: mailman Status: New => Confirmed ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Milestone: None => 3.0.0b1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/937154 Title: bin/disabled.py is nonfunctional To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/937154/+subscriptions

4 8

[Bug 889635] [NEW] Per-list configurable message headers for digests
by Joseph Fall 23 May '15

23 May '15

Public bug reported: Digest messages are sent out with a partial set of headers for each message. The list of headers kept for each plain-text digested message is configured by the setting: PLAIN_DIGEST_KEEP_HEADERS = [ 'Message', 'Date', 'From', 'Subject', 'To', 'Cc', 'Message-ID', 'Keywords', 'Content-Type', ] My users are very perplexed and frustrated by the e-mail headers included in the digest - in particular, the Message-ID and Content-Type are meaningless, and the To header is repetitive. All this "noise" clutters up the content and makes the digest harder to read. Given that this is a plain-text digest, with the headers listed in the message body, I don't really see an RFC issue here? Yet they can only be configured using a list-wide override in mm_cfg.py I would be willing to work on this to allow a list admin to override the plain digest headers using the web interface, but want to hear from the development team if this is a patch they would be willing to consider before I invest the time. thanks. ** 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/889635 Title: Per-list configurable message headers for digests To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/889635/+subscriptions

4 7

[Bug 885715] [NEW] Mailman should add a Received header
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: When the LMTP runner or any other injection vector receives a message, it should add a Received header to indicate the time at which Mailman got the message. Use case: there is a spam filter between the incoming MTA and Mailman, and the message sits in the spam filter for a while before its administrator accepts the message. ** 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/885715 Title: Mailman should add a Received header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/885715/+subscriptions

2 3

[Bug 869347] [NEW] bin/test script fails unless zope.testrunner is pip installed
by Stephen A. Goss 23 May '15

23 May '15

Public bug reported: I am running Mailman 3 in a virtualenv with most of its package dependencies installed through pip. In this particular configuration, if I run `buildout`, the test script that is created cannot seem to load zope.testrunner properly: $ bin/test -vv Traceback (most recent call last): File "bin/test", line 35, in <module> import zope.testrunner ImportError: No module named testrunner The workaround is to remove the eggs folder, pip install zope.testrunner, and then re-run buildout. ** 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/869347 Title: bin/test script fails unless zope.testrunner is pip installed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869347/+subscriptions

3 3

[Bug 837700] [NEW] Issues with users subscribed via their preferred address
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: You can subscribe an address to a mailing list, and you can subscribe a user to a mailing list, if the user has a preferred address. There are two problems with this. * You can actually end up getting doubly subscribed (i.e. same address with the same role). Normally, the subscription mechanism prevents you from subscribing the same address with the same role more than once, or the same user with the same role more than once. However, if you subscribe once by the address, and once by the user whose preferred address is that same address, the double subscription occurs. * The Member repr() doesn't distinguish between a member that's subscribed via explicit address, and one that's subscribed via preferred address. This means that the above will appear as a double address subscription, when it's really not. Are these substantial problems that need to be fixed? Almost certainly the second one does, but I haven't come up with an elegant repr() for the case of a user subscribed with their preferred address. ** Affects: mailman Importance: Low 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/837700 Title: Issues with users subscribed via their preferred address To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/837700/+subscriptions

2 2

[Bug 793669] [NEW] feature request. change the 'list my other subscriptions' to also report if the other subscriptions are enabled or disabled
by Laura Creighton 23 May '15

23 May '15

Public bug reported: I have a large number of subscriptions to mailing lists on python.org. Delivery is disabled on most of them. This is exactly how I want it -- I don't want to keep up with the day to day matters of the list, but I do want to be able to re-anable delivery and discuss things there should the need arise without having to create a new account. However, when I go on vacation, what I want to do is also disable a few high volume lists that I normally want to read every day. Thus what I would really like to see is which lists are currently enabled, so I can decide which one(s) if any I want to disable for the vacation. I don't want to disable the low-volume ones. Given that I am going to have to re-enable the lists I want to read when I get back one by one, I want the number of lists that get temporarily disabled to be as small as possible. And I want to be able to email me the short list of what they were so I can remember which ones to turn on again. Interestingly, the text of the message indicates a usability misunderstanding, and a grammatical error. The text reads: You can view a list of all the other mailing lists at python.org for which you are a member. Use this if you want to make the same membership option changes to this other subscriptions. It should be 'these other subscriptions'. And the people who want to make the same membership option changes to all the lists they are subscribed to on a site are precisely the users who don't need the feature. They can blindly go off and change things globally. If the number of lists they are subscribed to on that site is 1 -- i.e. they do not have any other subscriptions -- then saying to do things globally will do no harm. The reason you might want to look is to check because you might _not_ want to do things globally. And once you are dealing with that case, things you do not want to do globally, then of course you want to see the current settings that you have. But for my use case, all I care about is changing delivery status. All the other options I either never change, or want to change globally. I suspect that most people use mailing lists in this way, where the only thing they need to worry about is changes due to vacation, but I haven't conducted any polls to test this theory. This request sent to the tracker because the automated mail I recevied when some moderator refused to accept my mail to mailman-dev with this feature request, with the message 'why don't you just disable delivery globally and then reset them globally when you return' said that this was the place for feature requests and not the mailing list. Hope this request is clearer and explains why globally disabling is not what I want to do. Thank you ** 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/793669 Title: feature request. change the 'list my other subscriptions' to also report if the other subscriptions are enabled or disabled

4 9

[Bug 707295] [NEW] Membership Management Better Search Function
by arky 23 May '15

23 May '15

Public bug reported: In Mailman Membership Management, I would like to option to filter search results by status viz (hide,nomail [reason], ack, not metoo, nodupes, digest, plain) ** 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/707295 Title: Membership Management Better Search Function

4 3

[Bug 514625] [NEW] Mailman 3 member functions should "guess" address membership
by Stephen Turnbull 23 May '15

23 May '15

Public bug reported: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.domain.tld" is subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." ** Affects: mailman Importance: Undecided Status: New ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and - address>. [ ] Add <unknown> address as an alias for <member>." + address>. [ ] Add <unknown address> as an alias for <member>." ** Description changed: Feature request Mailman 3 should try to fuzzily match unknown author addresses against - the member database. For example, if "turnbull(a)sk.tsukuba.ac.jp" is - subscribed, then "turnbull(a)shako.sk.tsukuba.ac.jp" probably is the same + the member database. For example, if "turnbull(a)sk.domain.tld" is + subscribed, then "turnbull(a)shako.sk.domain.tld" probably is the same person. This could probably be efficiently implemented by storing domains in bigendian order, and testing for prefixes. Bonus points for matching on full name. For example, for me personally firstname(a)xemacs.org and lastname(a)xemacs.org both resolve to me, which could not be reasonably associated by algorithm, but I always use the same full name, which would be strong indication that it's me. Possibly matching on mailbox would also be useful, but only as an optimization to be confirmed by one of the other two (or maybe if the match is unique?) Note that for the first example, the second "turnbull@shako" variant is today used only by spammers; I haven't sent a message with that "From" since 1995, and I doubt it's been used as "Sender" more than a very small handful of times since 2000. For this reason, the feature should *never* be automated. Instead, it should be part of the moderation interface. If a match is detected, then an option should appear saying something like "This address appears to be an alias for <member name and address>. [ ] Add <unknown address> as an alias for <member>." -- Mailman 3 member functions should "guess" address membership https://bugs.launchpad.net/bugs/514625 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 5

[Bug 881320] [NEW] Mailman 3 translations
by Vincent Fretin 23 May '15

23 May '15

Public bug reported: In mailman 3.0.0a8, the locales directory contains actually mailman 2 translations. The unsubscribe mail is not translated into French because the msgids are different between mailman2 and mailman3. Do you have a script to generate a pot file and sync the po files? I had to generate myself the French mo file from the po. It's maybe a good idea to include mo files in the sdist, or generate mo files at mailman startup. ** 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/881320 Title: Mailman 3 translations To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/881320/+subscriptions

4 5

[Bug 1042828] [NEW] UI web URLs should be per-mailinglist
by Richard Wackerbarth 23 May '15

23 May '15

Public bug reported: The web URL needs to be attached to the individual mailing lists and not to the email domain. However, for ease of configuration, and following DRY principals, default values should be derived from the list hierarchy. As an example use case, consider: The mail server is run by an umbrella organization. Each of the groups under the umbrella has its own website. Some of those might be co-hosted from the same server, but others could be elsewhere. Each group wants it to appear as if they are "stand alone", providing UI access to the mailing list functions from their individual websites rather than from that of the umbrella organization. ** 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/1042828 Title: UI web URLs should be per-mailinglist To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1042828/+subscriptions

3 5

[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

[Bug 1004049] [NEW] Held messages show display message body
by Jeff Marshall 28 Apr '15

28 Apr '15

Public bug reported: The Held Messages page on Postorius only shows the subject line of the messages. It seems like the body of the message will also be important for reviewing the held message. According to Barry the body of the message, as a text blob, should be accessible via the REST API: http://packages.python.org/mailman/src/mailman/rest/docs/moderation.html ** 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/1004049 Title: Held messages show display message body To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004049/+subscriptions

5 8

[Bug 1004051] [NEW] Accepting Held messages results in stack trace
by Jeff Marshall 28 Apr '15

28 Apr '15

Public bug reported: I get an error dump whenever I accept a held message on Postorius. The message does get accepted and sends ok. But this error dump is displayed each time: Exception Type: AttributeError Exception Value: 'module' object has no attribute 'successful' Exception Location: /home/marshman/mailman/postorius/src/postorius/views.py in accept_held_message, line 405 ** 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/1004051 Title: Accepting Held messages results in stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004051/+subscriptions

2 5

[Bug 1025709] [NEW] When logging in through BrowserID or django.contrib.auth: Create new MM user if none exists
by Florian Fuchs 28 Apr '15

28 Apr '15

Public bug reported: Currently user data held by Postorius is not neccessarily connected to Mailman. Once logged in, it should be checked if the user already exists in MM and a new user should be added to via the API if necessary. ** Affects: postorius Importance: Undecided Status: New ** Description changed: Currently user data held by Postorius is not neccessarily connected to - Mailman. Once logged in, it should be checked if the user exists in MM - and add a new user if necessary. + Mailman. Once logged in, it should be checked if the user already exists + in MM and a new user should be added to via the API if necessary. -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1025709 Title: When logging in through BrowserID or django.contrib.auth: Create new MM user if none exists To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1025709/+subscriptions

1 1

[Bug 1027496] [NEW] Check code against pep8 conventions
by Florian Fuchs 28 Apr '15

28 Apr '15

Public bug reported: It's a dirty job, but someone's gotta do it. ** Affects: postorius Importance: Undecided Status: In Progress ** Changed in: postorius Status: New => In Progress ** Changed in: postorius Milestone: None => 1.0.0a2 ** Branch linked: lp:~flo-fuchs/postorius/pep8 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1027496 Title: Check code against pep8 conventions To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1027496/+subscriptions

1 2

[Bug 1021364] [NEW] Catch httplib2 error if REST API is not available
by Florian Fuchs 28 Apr '15

28 Apr '15

Public bug reported: httplib2 (used in mailman.client) throws "[Errno 111] Connection refused" if the core api isn't available. This should be turned into a nice error page with a meaningful description (possibly depending on the visiting user's role - details for admins and a more vague error msg for everyone else). ** Affects: mailman.client Importance: Undecided Status: New ** Affects: postorius Importance: Medium Status: Confirmed ** Tags: api ** Description changed: - httplib2 throws "[Errno 111] Connection refused" if the core api isn't - available. + httplib2 (used in mailman.client) throws "[Errno 111] Connection + refused" if the core api isn't available. This should be turned into a nice error page with a meaningful description (possibly depending on the visiting user's role - details for admins and a more vague error msg for everyone else). ** Also affects: mailman.client Importance: Undecided Status: New ** Changed in: postorius Milestone: None => 1.0.0a2 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1021364 Title: Catch httplib2 error if REST API is not available To manage notifications about this bug go to: https://bugs.launchpad.net/mailman.client/+bug/1021364/+subscriptions

2 6

[Bug 987100] [NEW] enable archival
by Jeff Breidenbach 28 Apr '15

28 Apr '15

Public bug reported: Expose mailmans archival booleans as a tristate, either none/private/public or none/local/cloud. ** Affects: postorius Importance: Undecided Status: New ** Tags: mailman3 ** Tags added: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/987100 Title: enable archival To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/987100/+subscriptions

3 4

[Bug 1004048] [NEW] Able to create superuser with same email as existing BrowserID account
by Jeff Marshall 28 Apr '15

28 Apr '15

Public bug reported: I initially connected to Postorius using BrowserID. I then created a superuser from the command line (in dev_setup -> python manage.py createsuperuser). It correctly prevented me from using the existing username, but I was able to use the same email address as my BrowserID account. The superuser account was created and I could log into Postorius successfully. When I then logged back out and logged in via BrowserID I received this error: AuthException at /complete/browserid/ Not unique email address. Request Method: POST Request URL: http://xxxxxxxxxxxxxxxxxx/complete/browserid/ Django Version: 1.3.1 Exception Type: AuthException Exception Value: Not unique email address. Exception Location: /usr/local/lib/python2.7/dist-packages/django_social_auth-0.6.9-py2.7.egg/social_auth/backends/pipeline/associate.py in associate_by_email, line 22 ** 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/1004048 Title: Able to create superuser with same email as existing BrowserID account To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1004048/+subscriptions

2 1

[Bug 1006356] [NEW] message acceptance settings for list ignored
by Robert Niederreiter 15 Apr '15

15 Apr '15

Public bug reported: when setting "hold for moderator" in "Message Acceptance" settings of a list (both cases list member and non list member) the mails get anyway delivered directly without any investigation. ** Affects: postorius Importance: Undecided Status: New ** Tags: list settings -- You received this bug notification because you are a member of Mailman Coders, which is the registrant for Postorius. https://bugs.launchpad.net/bugs/1006356 Title: message acceptance settings for list ignored To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1006356/+subscriptions

6 5

[Bug 975668] [NEW] mailman.client conflicts with mailman installation
by Richard Wackerbarth 24 Mar '15

24 Mar '15

Public bug reported: If mailman.client is loaded as a separate module (as instructed), then mailman cannot exist in the same environment because there are two "mailman" modules to search. I found this when I tried to generate sphinx documentation for mailman after I had installed protorious. To reproduce: mkvirtualenv BUG bzr branch lp:mailman.client cd mailman.client/ python setup.py develop easy_install sphinx cd .. bzr branch lp:mailman cd mailman python bootstrap.py bin/buildout python setup.py build_sphinx Results in: Running Sphinx v1.1.3 Traceback (most recent call last): File "setup.py", line 112, in <module> 'zope.testing<4', File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/core.py", line 152, in setup dist.run_commands() File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 953, in run_commands self.run_command(cmd) File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/distutils/dist.py", line 972, in run_command cmd_obj.run() File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/lib/python2.7/site-packages/Sphinx-1.1.3-py2.7.egg/sphinx/setup_command.py", line 140, in run freshenv=self.fresh_env) File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/lib/python2.7/site-packages/Sphinx-1.1.3-py2.7.egg/sphinx/application.py", line 102, in __init__ confoverrides or {}, self.tags) File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/lib/python2.7/site-packages/Sphinx-1.1.3-py2.7.egg/sphinx/config.py", line 216, in __init__ exec code in config File "/Volumes/UserSpace/rkw/.virtualenvs/BUG/mailman/conf.py", line 54, in <module> from mailman.version import VERSION ImportError: No module named version ** 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/975668 Title: mailman.client conflicts with mailman installation To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975668/+subscriptions

3 7

[Bug 543618] [NEW] test breaks if existing mailman.cfg is found
by Patrick Ben Koetter 24 Mar '15

24 Mar '15

Public bug reported: The test program reports an error if it detects an existing mailman.cfg: Failure in test test_current_working_directory (mailman.tests.test_configfile.TestConfigFileSearch) Traceback (most recent call last): File "/usr/lib/python2.6/unittest.py", line 279, in run testMethod() File "/root/mailman/src/mailman/tests/test_configfile.py", line 107, in test_current_working_directory self.assertEqual(found, config_file) File "/usr/lib/python2.6/unittest.py", line 350, in failUnlessEqual (msg or '%r != %r' % (first, second)) AssertionError: '/etc/mailman.cfg' != u'/tmp/tmpVfAIyB/home/alex/mailman/hacking/mailman.cfg' I believe it should not do this. It should either silently ignore the difference or use the test mailman.cfg or ... but not break. ** Affects: mailman Importance: Undecided Status: New ** Tags: 3.0 mailman -- test breaks if existing mailman.cfg is found https://bugs.launchpad.net/bugs/543618 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

4 6

[Bug 967951] [NEW] The LMTP runner should reject messages with duplicate Message-IDs
by Barry Warsaw 06 Mar '15

06 Mar '15

Public bug reported: Subject says it all. Mailman 3 requires unique Message-IDs for posts. ** Affects: mailman Importance: Undecided Status: New ** 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/967951 Title: The LMTP runner should reject messages with duplicate Message-IDs To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967951/+subscriptions

6 8

[Bug 880613] [NEW] PostgreSQL constraints disabled
by Barry Warsaw 29 Nov '14

29 Nov '14

Public bug reported: In src/mailman/database/sql/postgres.sql, several foreign key constraints have been commented out because otherwise the test suite, or other aspects do not work. This is probably because there are cases where Mailman violates these constraints, but SQLite3 (the default database) does not care. All disabled constraints are marked with XXX in the above file. Really, these should be fixed. ** 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/880613 Title: PostgreSQL constraints disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/880613/+subscriptions

1 2

[Bug 518517] [NEW] Add the equivalent of postconf(1)
by Barry Warsaw 22 Apr '14

22 Apr '14

Public bug reported: Postfix has a very handy command called postconf(1) which lets you dump all or one Postfix configuration variable. It would be very handy for Mailman 3 to have something similar. ** Affects: mailman Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged ** Also affects: mailman/3.0 Importance: Medium Assignee: Barry Warsaw (barry) Status: Triaged -- Add the equivalent of postconf(1) https://bugs.launchpad.net/bugs/518517 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

5 19

[Bug 869342] [NEW] bootstrap.py fails if buildout already installed in Python environment
by Stephen A. Goss 15 Apr '14

15 Apr '14

Public bug reported: If zc.buildout is already installed (say it was pip installed) in Python environment, the bootstrap.py script fails without reasonable explanation: $ python bootstrap.py Traceback (most recent call last): File "bootstrap.py", line 255, in <module> import zc.buildout.buildout ImportError: No module named zc.buildout.buildout This is confusing because you can see that zc.buildout.buildout is available. $ python Python 2.6.5 (r265:79063, Jun 25 2011, 08:36:25) [GCC 4.4.4 20100726 (Red Hat 4.4.4-13)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import zc.buildout.buildout >>> It turns out that if zc.buildout is already available, bootstrap.py does not need to be run, but that is less than obvious to someone who is not intimately familiar with buildout. ** 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/869342 Title: bootstrap.py fails if buildout already installed in Python environment To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/869342/+subscriptions

2 2

[Bug 821438] [NEW] REST and Client are missing membership_settings options
by benste 15 Mar '14

15 Mar '14

Public bug reported: Using the Python bindings the following things are available at the moment: self_link: u'http://localhost:8001/3.0/members/2' role: u'member' user: u'http://localhost:8001/3.0/users/2' address': u'katie(a)example.com' fqdn_listname': u'testtwo(a)mail.example.com' For better user management the following options should be seen as wishlist: acknowledge_posts hide_address receive_list_copy receive_own_postings delivery_mode delivery_status in addition i requested _User.get_lists which is in https://bugs.launchpad.net/mailmanwebgsoc2011/+bug/821069 + what about users password ? users e-mails ... ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman.client Importance: Undecided Status: Confirmed ** Affects: mailmanwebgsoc2011 Importance: Wishlist Status: Triaged ** Tags: mailman3 ** Changed in: mailman.client Status: New => Confirmed ** Also affects: mailmanwebgsoc2011 Importance: Undecided Status: New ** Also affects: mailman Importance: Undecided Status: New ** Tags added: mailman3 ** Changed in: mailmanwebgsoc2011 Status: New => Triaged ** Changed in: mailmanwebgsoc2011 Importance: Undecided => 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/821438 Title: REST and Client are missing membership_settings options To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/821438/+subscriptions

3 6

[Bug 802971] [NEW] Mailman Client doesn't _DOMAIN doesn't offer a list of lists
by benste 15 Mar '14

15 Mar '14

Public bug reported: I'd suggest adding a functionalty which would need a domain as param, and return a list of mailing lists associated with this domain. This could be used to display a choice of all available domains on this web_host and allow simple deletition of all mailinglists on this domains in case a domain will ever be deleted. ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman.client Importance: Undecided Status: New ** Affects: mailmanwebgsoc2011 Importance: Wishlist Assignee: benste (benste) Status: Triaged ** Tags: mailman3 ** Also affects: mailman.client Importance: Undecided Status: New ** Also affects: mailman Importance: Undecided Status: New ** 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/802971 Title: Mailman Client doesn't _DOMAIN doesn't offer a list of lists To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/802971/+subscriptions

5 9

[Bug 674352] [NEW] List Moderator Login should check for username
by arky 12 Mar '14

12 Mar '14

Public bug reported: List Moderator logins currently prompt for list moderator password only. It would be good idea if prompt for username/password login as well. Mailman: 2.1.9 ** Affects: mailman Importance: Undecided Status: New -- List Moderator Login should check for username https://bugs.launchpad.net/bugs/674352 You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman.

3 3

[Bug 1031953] [NEW] failed to access my mailing lists and the message " Bug in Mailman version 2.1.14-1
by Henry Chitsenga 10 Aug '13

10 Aug '13

*** This bug is a security vulnerability *** Private security bug reported: I have been failling to log into my mailman administration interface and this ,essage has been appearing "Bug in Mailman version 2.1.14-1 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. " There are a lot of emails that need to released but I can do that. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1031953 Title: failed to access my mailing lists and the message " Bug in Mailman version 2.1.14-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1031953/+subscriptions

5 8

[Bug 725498] [NEW] expose message-id to templates
by Thijs Kinkhorst 05 Aug '13

05 Aug '13

Public bug reported: As reported by Adrian von Bidder to Debian: Please consider this trivial patch, which exposees message-ids to the templates used for the email archive. See it in action on lists.debian.ch. (I don't think my modification to the templates should be in, but having te message-id exposed would mean I won't have to remember to patch mailman on every update...) (AFAICT mailman adds a Message-Id when an incoming email doesn't have one, so this should never be a problem.) ** Affects: mailman Importance: Undecided Status: New ** Affects: mailman (Debian) Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/725498 Title: expose message-id to templates

4 7

[Bug 1032378] [NEW] The Mass Remove function in the web UI requires that send_unsub_notifications_to_list_owner and send_unsub_ack_to_this_batch be set.
by Mark Sapiro 14 Jul '13

14 Jul '13

Public bug reported: This is not a problem for the actual web admin interface, as send_unsub_notifications_to_list_owner and send_unsub_ack_to_this_batch are in the form and the CGI will always be able to access them in the CGI data, but if a user creates a URL with query fragments to try to do the unsubscribe via wget in a script, these two items must be included. They should just assume their defaults from list settings. ** Affects: mailman Importance: Low 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/1032378 Title: The Mass Remove function in the web UI requires that send_unsub_notifications_to_list_owner and send_unsub_ack_to_this_batch be set. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1032378/+subscriptions

1 2

[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 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/1043258 into lp:postorius
by Richard Wackerbarth 17 Sep '12

17 Sep '12

Richard Wackerbarth has proposed merging lp:~wacky/postorius/1043258 into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~wacky/postorius/1043258/+merge/121840 Patches to remove the MAILMAN_THEME cruft Themes can be implemented by providing alternate templates and static files in an app that overrides the default versions, but utilizes the same namespace. Rather than using a MAILMAN_THEME in the settings file, the entry is in the form of an additional entry in INSTALLED_APPS -- The attached diff has been truncated due to its size. https://code.launchpad.net/~wacky/postorius/1043258/+merge/121840 Your team Mailman Coders is requested to review the proposed merge of lp:~wacky/postorius/1043258 into lp:postorius.

3 2

[Bug 971013] [NEW] Database schema migrations needed
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: The following database schema migrations are required. This is a release blocker for 3.0 final. Add more to this bug as you find them. * Change news_prefix_subject_too -> nntp_prefix_subject_too * Remove nntp_host from table mailing list ** Affects: mailman Importance: Critical 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/971013 Title: Database schema migrations needed To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/971013/+subscriptions

2 13

[Bug 949924] [NEW] UnicodeDecodeError when delivering message
by Antti Kaihola 08 Sep '12

08 Sep '12

Public bug reported: I did a fresh install of Mailman 3.0.0a8 on a Debian Squeeze box, created a list, subscribed a few people and sent a message to the list. The message didn't come through, and var/logs/mailman.log has: Mar 08 13:21:08 2012 (23645) Uncaught runner exception: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) Traceback (most recent call last): File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/lib/python2.6/site-packages/mailman/runners/incoming.py", line 64, in _dispose process(mlist, msg, msgdata, mlist.start_chain) File "/home/mailman/lib/python2.6/site-packages/mailman/core/chains.py", line 68, in process if link.rule.check(mlist, msg, msgdata): File "/home/mailman/lib/python2.6/site-packages/mailman/rules/approved.py", line 81, in check if ':' in line: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 20: ordinal not in range(128) Mar 08 13:21:08 2012 (23645) SHUNTING: 1331212867.805197+9daec32c73ac20978b856348ada1a60fd97a364c The message did contain an u'\xe4' in both the subject and the body. I sent the message using Thunderbird 10.0.2 on Linux Mint 12. ** 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/949924 Title: UnicodeDecodeError when delivering message To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/949924/+subscriptions

5 11

[Bug 967238] [NEW] Expose IMailingList.archive and .archive_private in the REST API
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: Exposing read and write of these attributes would allow Postorius to provide the list owners with some control over archiving for individual lists. This would work as a patch to src/mailman/rest/configuration.py and should be pretty easy to add. ** Affects: mailman Importance: Medium Status: Triaged ** 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/967238 Title: Expose IMailingList.archive and .archive_private in the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/967238/+subscriptions

2 6

[Bug 975696] [NEW] Eradicate generic_nonmember_action
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: This attribute should be removed, it's no longer used. The tricky part is that it must be removed from the IMailingList interface, the model, lots of places in the code, and a schema migration is needed too. ** 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/975696 Title: Eradicate generic_nonmember_action To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975696/+subscriptions

1 3

[Bug 975698] [NEW] On email validation confirmation, trigger an event
by Barry Warsaw 08 Sep '12

08 Sep '12

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

1 2

[Bug 975700] [NEW] On password change, trigger an event
by Barry Warsaw 08 Sep '12

08 Sep '12

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

1 2

[Bug 987563] [NEW] List-Post should be NO when posting is not allowed
by Barry Warsaw 08 Sep '12

08 Sep '12

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

1 2

[Bug 1015757] [NEW] Migrate from flufl.password to passlib
by Barry Warsaw 08 Sep '12

08 Sep '12

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

1 2

[Bug 1024509] [NEW] Link between members and mailing lists should use List-ID
by Barry Warsaw 08 Sep '12

08 Sep '12

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

3 6

[Bug 1031391] [NEW] remove msgdata['received_time'] in mailman.app.moderator before calling IListRequests.hold_request
by Robert Niederreiter 08 Sep '12

08 Sep '12

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

4 9

[Bug 1031393] [NEW] wrong attribute name according to mailman.interfaces.mailinglist.IMailingList
by Robert Niederreiter 08 Sep '12

08 Sep '12

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

2 6

[Bug 1035028] [NEW] bin/mailman info -v could be improved
by Stephen Turnbull 08 Sep '12

08 Sep '12

Public bug reported: 1. bin/mailman info -v should tell about whether devmode is on. 2. there ought to be a bin/mailman info -v -v which lists *all* configurable options, their values, and their defaults if different from configured values. ("defaults" includes everything in hardwired fallbacks as well as in .cfgs distributed with mailman). 3. for bonus points, do something sane with all the suites of options under bin/mailman info -v -v. ** 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/1035028 Title: bin/mailman info -v could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035028/+subscriptions

2 3

[Bug 1039129] [NEW] archive_policy should be exposed via REST interface
by AlexanderS 08 Sep '12

08 Sep '12

Public bug reported: Currently the new property archive_policy is not available via the REST API. ** Affects: mailman Importance: Undecided Status: New ** Tags: api 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/1039129 Title: archive_policy should be exposed via REST interface To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1039129/+subscriptions

2 4

[Bug 953497] [NEW] Unused variable in loop
by Andrea Crotti 08 Sep '12

08 Sep '12

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

2 5

[Bug 963612] [NEW] ArchiveRunner has Pipermail artifacts
by Barry Warsaw 08 Sep '12

08 Sep '12

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

1 2

[Bug 967409] [NEW] NewsRunner needs to be ported to Mailman 3
by Barry Warsaw 08 Sep '12

08 Sep '12

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

1 3

[Bug 887610] [NEW] RFC 1153 digests should not work around VM bug
by Barry Warsaw 08 Sep '12

08 Sep '12

Public bug reported: In RFC1153Digester.finish(), we have this comment: # This is not strictly conformant RFC 1153. The trailer is only # supposed to contain two lines, i.e. the "End of ... Digest" line # and the row of asterisks. If this screws up MUAs, the solution # is to add the footer as the last message in the RFC 1153 digest. # I just hate the way that VM does that and I think it's confusing # to users, so don't do it unless there's a clamor. It is bogus that Mailman works around VM this way, so the code should be fixed to fully conform to RFC 1153. While this bug report is specifically targeted to Mailman 3, it also affects MM2.1, but I'll let Mark decide the priority of that bugtask. ** Affects: mailman Importance: Medium 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/887610 Title: RFC 1153 digests should not work around VM bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/887610/+subscriptions

3 8

[Bug 1004000] [NEW] Version conflict of zone.interface on installation of Mailman 3.0b1
by Nicole Rauch 06 Sep '12

06 Sep '12

Public bug reported: I've downloaded Mailman 3.0.0b1 on a Mac with OS X 10.7.3 and Python 2.7.1. When executing the installation commands, I got the following error message: cardhu:mailman-3.0.0b1 rauch$ python bootstrap.py cardhu:mailman-3.0.0b1 rauch$ bin/buildout Develop: '/Users/rauch/Applications/mailman-3.0.0b1/.' warning: no files found matching '*.rc' warning: no files found matching '*' under directory '.buildout' warning: no files found matching '*' under directory 'contrib' warning: no previously-included files matching '*.egg-info' found anywhere in distribution no previously-included directories found matching 'src/attic' no previously-included directories found matching 'src/web' no previously-included directories found matching 'parts' Updating interpreter. While: Updating interpreter. Error: There is a version conflict. We already have: zope.interface 3.5.1 but zope.component 3.12.1 requires 'zope.interface>=3.8.0'. ** 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/1004000 Title: Version conflict of zone.interface on installation of Mailman 3.0b1 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1004000/+subscriptions

2 4

[Bug 987020] [NEW] remove mail-archive.dev from configs
by Jeff Breidenbach 05 Sep '12

05 Sep '12

Public bug reported: The URL mail-archive.dev is in the mailman code. Time to use the real thing. ** 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/987020 Title: remove mail-archive.dev from configs To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/987020/+subscriptions

2 1

[Bug 899344] [NEW] Ability to set nomail on initial subscription
by Josh Triplett 04 Sep '12

04 Sep '12

Public bug reported: I frequently find myself subscribing to a list for the sole purpose of ensuring I can post to that list, since it only allows posting from members. I often read those (high-volume) lists via the archives only, as well as threads that CC me. Thus, I want to set the nomail flag. Often I end up doing so for multiple subscriptions to the same list with a few different email addresses. Currently, the process for doing that looks something like this: Type in my name and email address, hit subscribe, wait for confirmation mail, confirm subscription, wait for subscription confirmation mail, go back to web form, copy/paste password, log in, check nomail, delete the handful of unwanted emails that arrived in the meantime. Repeat for every list I want to subscribe to, and every email address I want to post from. I'd like to have a way to set the "nomail" flag right from the subscription form. That would simplify the process significantly; I'd still have to confirm the subscription, but I wouldn't need to bother logging in and setting the flag, and I wouldn't receive unwanted emails from high-volume lists. ** 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/899344 Title: Ability to set nomail on initial subscription To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/899344/+subscriptions

2 2

[Bug 736849] [NEW] Sender header change to improve Outlook
by Joseph Brennan 31 Aug '12

31 Aug '12

Public bug reported: FAQ 2.3 describes problems with Outlook's ugly display of Sender "on behalf of" From, giving the example as "From listname- bounces(a)mailman.server.com On behalf of fred(a)poster.domain.com". But Outlook prefers to show the real name and hide the Internet address, when a real name is present. Most commonly the From would be "From: Fred Example <fred(a)poster.domain.com>" and as a result Outlook would display "From listname-bounces(a)mailman.server.com On behalf of Fred Example". If Mailman wrote the Sender header with a real name Outlook would show the name there too. For example, if the list name (local part) were inserted, thus "Sender: listname <listname-bounces(a)mailman.server.com>", then Outlook would display "From listname on behalf of Fred Example" which is much better in appearance and still complies with using a Sender header. RFC 2822 allows Sender to contain a real name. sender = "Sender:" mailbox CRLF mailbox = name-addr / addr-spec name-addr = [display-name] angle-addr ** 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/736849 Title: Sender header change to improve Outlook

3 7

[Bug 1041591] [NEW] Add Persian language.
by Yousha Aleayoub 25 Aug '12

25 Aug '12

Public bug reported: Its possible to add Persian language to Mailman? Thanks. ** Affects: mailman Importance: Undecided Status: New ** Tags: language persian -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1041591 Title: Add Persian language. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1041591/+subscriptions

2 2

[Bug 1039175] [NEW] use new archive_policy property everywhere
by AlexanderS 20 Aug '12

20 Aug '12

Public bug reported: At some points the old properties MailingList.archive and MailingList.archive_private are used. This patch use the new archive_policy. ** 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/1039175 Title: use new archive_policy property everywhere To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1039175/+subscriptions

2 2

[Bug 984765] [NEW] MM3: Expected unicode, found <type 'datetime.datetime'>:
by Bernhard Schmidt 19 Aug '12

19 Aug '12

Public bug reported: Mailman 3.0.0b1+ (hg checkout of two days ago) throws the following error in the log Apr 18 12:53:57 2012 (23857) Uncaught runner exception: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 4, 18, 10, 53, 56, 403336) Apr 18 12:53:58 2012 (23857) Traceback (most recent call last): File "/usr/local/mailman/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/local/mailman/src/mailman/core/runner.py", line 220, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/src/mailman/runners/incoming.py", line 67, in _dispose process(mlist, msg, msgdata, start_chain) File "/usr/local/mailman/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/usr/local/mailman/src/mailman/chains/hold.py", line 146, in _process request_id = hold_message(mlist, msg, msgdata, None) File "/usr/local/mailman/src/mailman/app/moderator.py", line 105, in hold_message RequestType.held_message, message_id, msgdata) File "/usr/local/mailman/src/mailman/model/requests.py", line 87, in hold_request token = getUtility(IPendings).add(pendable, timedelta(days=5000)) File "/usr/local/mailman/src/mailman/model/pending.py", line 130, in add keyval = PendedKeyValue(key=key, value=value) File "/usr/local/mailman/src/mailman/model/pending.py", line 54, in __init__ self.value = value File "/usr/lib/python2.7/dist-packages/storm/properties.py", line 67, in __set__ obj_info.variables[column].set(value) File "/usr/lib/python2.7/dist-packages/storm/variables.py", line 396, in parse_set % (type(value), value)) TypeError: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 4, 18, 10, 53, 56, 403336) Apr 18 12:53:58 2012 (23857) SHUNTING: 1334746438.043432+d81b75cc8924fd572477ebc0358bde18bf755fd9 ** 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/984765 Title: MM3: Expected unicode, found <type 'datetime.datetime'>: To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/984765/+subscriptions

2 2

[Bug 1035023] [NEW] bin/mailman info shouldn't create anything
by Stephen Turnbull 18 Aug '12

18 Aug '12

Public bug reported: One good reason for doing "bin/mailman info" is to check what mailman is going to put where before it does it. Oops, it just did. :-( ** 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/1035023 Title: bin/mailman info shouldn't create anything To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035023/+subscriptions

2 2

[Bug 1035057] [NEW] Unicode error prevents delivery of post
by Stephen Turnbull 18 Aug '12

18 Aug '12

Public bug reported: So here's the build. ######################## Mailman3 build log ######################## # N.B. "Mailman3" is a new, active python 2.7 virtualenv. # God, do I hate bzr for not being git. steve@turnbull:~/src/Mailman3/mailman-trunk$ bzr revno 7157 steve@turnbull:~/src/Mailman3/mailman-trunk$ bzr log -r 7157 ------------------------------------------------------------ revno: 7157 [merge] committer: Barry Warsaw <barry(a)list.org> branch nick: 3.0 timestamp: Thu 2012-07-26 00:22:19 -0400 message: * The policy for archiving has now been collapsed into a single enum, called ArchivePolicy. This describes the three states of never archive, archive privately, and archive_publicly. (LP: #967238) Database -------- * Schema migrations (LP: #971013) - include_list_post_header -> allow_list_posts - news_prefix_subject_too -> nntp_prefix_subject_too - news_moderation -> newsgroup_moderation - archive and archive_private have been collapsed into archive_policy. - nntp_host has been removed. * The PostgreSQL port of the schema accidentally added a moderation_callback column to the mailinglist table. Since this is unused in Mailman, it was simply commented out of the base schema for PostgreSQL. ------------------------------------------------------------ steve@turnbull:~/src/Mailman3/mailman-trunk$ python Python 2.7.3rc2 (default, Apr 22 2012, 22:30:17) [GCC 4.6.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> steve@turnbull:~/src/Mailman3/mailman-trunk$ python bootstrap.py Downloading http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11-py2.7.egg Creating directory '/home/steve/src/Mailman3/mailman-trunk/bin'. Creating directory '/home/steve/src/Mailman3/mailman-trunk/parts'. Creating directory '/home/steve/src/Mailman3/mailman-trunk/eggs'. Creating directory '/home/steve/src/Mailman3/mailman-trunk/develop-eggs'. Getting distribution for 'setuptools'. Got setuptools 0.6c12dev-r88846. Generated script '/home/steve/src/Mailman3/mailman-trunk/bin/buildout'. steve@turnbull:~/src/Mailman3/mailman-trunk$ bin/buildout Develop: '/home/steve/src/Mailman3/mailman-trunk/.' Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.8.tar.gz Extracting in /tmp/tmpOzSp2M Now working in /tmp/tmpOzSp2M/distribute-0.6.8 Building a Distribute egg in /home/steve/src/Mailman3/mailman-trunk /home/steve/src/Mailman3/mailman-trunk/distribute-0.6.8-py2.7.egg warning: no files found matching '*.rc' warning: no files found matching '*' under directory '.buildout' warning: no files found matching '*' under directory 'contrib' warning: no previously-included files matching '*.egg-info' found anywhere in distribution no previously-included directories found matching 'src/attic' no previously-included directories found matching 'src/web' no previously-included directories found matching 'parts' Getting distribution for 'z3c.recipe.scripts'. Got z3c.recipe.scripts 1.0.1. Getting distribution for 'zc.recipe.egg>=1.3.0'. Got zc.recipe.egg 1.3.2. Getting distribution for 'z3c.recipe.tag'. Got z3c.recipe.tag 0.4.1. Getting distribution for 'zc.recipe.testrunner'. zip_safe flag not set; analyzing archive contents... Got zc.recipe.testrunner 1.4.0. Getting distribution for 'zope.testrunner'. package init file 'src/zope/testrunner/testrunner-ex/__init__.py' not found (or not a regular file) Creating missing __init__.py for zope.testrunner.testrunner-ex Got zope.testrunner 4.0.4. Getting distribution for 'zope.interface'. Got zope.interface 4.0.1. Getting distribution for 'zope.exceptions'. Got zope.exceptions 4.0.0.1. Installing interpreter. Getting distribution for 'zope.testing<4'. warning: no files found matching '*.test' under directory 'src' warning: no files found matching 'sampletests' under directory 'src' Got zope.testing 3.10.3. Getting distribution for 'zope.event'. Got zope.event 4.0.0. Getting distribution for 'zope.configuration'. Got zope.configuration 4.0.0. Getting distribution for 'zope.component'. Got zope.component 4.0.0. Getting distribution for 'storm'. Got storm 0.19. Getting distribution for 'restish'. Got restish 0.12.1. Getting distribution for 'passlib'. warning: no files found matching 'passlib/*.cfg' no previously-included directories found matching '*.komodoproject' Got passlib 1.6.1. Getting distribution for 'mock'. warning: no files found matching '*.png' under directory 'docs' warning: no files found matching '*.css' under directory 'docs' warning: no files found matching '*.html' under directory 'docs' warning: no files found matching '*.js' under directory 'docs' zip_safe flag not set; analyzing archive contents... Got mock 1.0b1. Getting distribution for 'lazr.smtptest'. Got lazr.smtptest 1.3. Getting distribution for 'lazr.config'. Got lazr.config 1.1.3. Getting distribution for 'flufl.lock'. Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.10.tar.gz Extracting in /tmp/easy_install-_r_jTR/flufl.lock-2.2.1/temp/tmpUjGygF Now working in /tmp/easy_install-_r_jTR/flufl.lock-2.2.1/temp/tmpUjGygF/distribute-0.6.10 Building a Distribute egg in /tmp/easy_install-_r_jTR/flufl.lock-2.2.1 /tmp/easy_install-_r_jTR/flufl.lock-2.2.1/distribute-0.6.10-py2.7.egg zip_safe flag not set; analyzing archive contents... flufl.__init__: module references __path__ Got flufl.lock 2.2.1. Getting distribution for 'flufl.i18n'. Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.10.tar.gz Extracting in /tmp/easy_install-HqJWPx/flufl.i18n-1.1.1/temp/tmp33Zt_H Now working in /tmp/easy_install-HqJWPx/flufl.i18n-1.1.1/temp/tmp33Zt_H/distribute-0.6.10 Building a Distribute egg in /tmp/easy_install-HqJWPx/flufl.i18n-1.1.1 /tmp/easy_install-HqJWPx/flufl.i18n-1.1.1/distribute-0.6.10-py2.7.egg Got flufl.i18n 1.1.1. Getting distribution for 'flufl.enum'. Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.19.tar.gz Extracting in /tmp/easy_install-10gV93/flufl.enum-3.3.2/temp/tmpz01MIV Now working in /tmp/easy_install-10gV93/flufl.enum-3.3.2/temp/tmpz01MIV/distribute-0.6.19 Building a Distribute egg in /tmp/easy_install-10gV93/flufl.enum-3.3.2 /tmp/easy_install-10gV93/flufl.enum-3.3.2/distribute-0.6.19-py2.7.egg zip_safe flag not set; analyzing archive contents... flufl.__init__: module references __path__ Got flufl.enum 3.3.2. Getting distribution for 'flufl.bounce'. Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.14.tar.gz Extracting in /tmp/easy_install-g21I2F/flufl.bounce-2.1.1/temp/tmpyEYnaw Now working in /tmp/easy_install-g21I2F/flufl.bounce-2.1.1/temp/tmpyEYnaw/distribute-0.6.14 Building a Distribute egg in /tmp/easy_install-g21I2F/flufl.bounce-2.1.1 /tmp/easy_install-g21I2F/flufl.bounce-2.1.1/distribute-0.6.14-py2.7.egg warning: no previously-included files found matching '*.egg' no previously-included directories found matching 'build' zip_safe flag not set; analyzing archive contents... flufl.__init__: module references __path__ Got flufl.bounce 2.1.1. Getting distribution for 'argparse'. warning: no previously-included files matching '*.pyc' found anywhere in distribution warning: no previously-included files matching '*.pyo' found anywhere in distribution warning: no previously-included files matching '*.orig' found anywhere in distribution warning: no previously-included files matching '*.rej' found anywhere in distribution no previously-included directories found matching 'doc/_build' no previously-included directories found matching 'env24' no previously-included directories found matching 'env25' no previously-included directories found matching 'env26' no previously-included directories found matching 'env27' zip_safe flag not set; analyzing archive contents... Got argparse 1.2.1. Getting distribution for 'zope.schema'. warning: no files found matching '*.txt' under directory 'src/zope/schema' warning: no previously-included files matching '*.pyc' found anywhere in distribution Got zope.schema 4.2.0. Getting distribution for 'zope.i18nmessageid'. Got zope.i18nmessageid 4.0.0. Getting distribution for 'WebOb'. no previously-included directories found matching '*.pyc' no previously-included directories found matching '*.pyo' Got WebOb 1.2.1. Getting distribution for 'mimeparse>=0.1.3'. Got mimeparse 0.1.3. Getting distribution for 'lazr.delegates'. Got lazr.delegates 1.2.0. Generated script '/home/steve/src/Mailman3/mailman-trunk/bin/runner'. Generated script '/home/steve/src/Mailman3/mailman-trunk/bin/master'. Generated script '/home/steve/src/Mailman3/mailman-trunk/bin/mailman'. Generated script '/home/steve/src/Mailman3/mailman-trunk/bin/onebounce'. Generated interpreter '/home/steve/src/Mailman3/mailman-trunk/bin/py'. Installing tags. Generated script '/home/steve/src/Mailman3/mailman-trunk/bin/tags'. Installing test. Generated script '/home/steve/src/Mailman3/mailman-trunk/bin/test'. steve@turnbull:~/src/Mailman3/mailman-trunk$ bin/test -vv Running tests at level 1 Running mailman.testing.layers.ConfigLayer tests: Set up mailman.testing.layers.MockAndMonkeyLayer in 0.000 seconds. Set up mailman.testing.layers.ConfigLayer Traceback (most recent call last): File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 380, in run_layer setup_layer(options, layer, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 672, in setup_layer layer.setUp() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/testing/layers.py", line 130, in setUp initialize.initialize_2(testing=True) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/initialize.py", line 153, in initialize_2 config.db = getUtility(IDatabaseFactory, utility_name).create() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/database/factory.py", line 80, in create database.initialize() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/database/base.py", line 68, in initialize self._create(debug) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/database/base.py", line 141, in _create store = Store(database, GenerationalCache()) File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/store.py", line 73, in __init__ self._connection = database.connect(self._event) File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/database.py", line 410, in connect return self.connection_factory(self, event) File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/database.py", line 185, in __init__ self._raw_connection = self._database.raw_connect() File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/databases/postgres.py", line 329, in raw_connect raw_connection = psycopg2.connect(self._dsn) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) OperationalError: FATAL: password authentication failed for user "barry" FATAL: password authentication failed for user "barry" Running mailman.testing.layers.LMTPLayer tests: Set up mailman.testing.layers.ConfigLayer Traceback (most recent call last): File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 380, in run_layer setup_layer(options, layer, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 667, in setup_layer setup_layer(options, base, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 672, in setup_layer layer.setUp() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/testing/layers.py", line 103, in setUp initialize.initialize_1(INHIBIT_CONFIG_FILE) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/initialize.py", line 125, in initialize_1 mailman.config.config.load(config_path) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/config/config.py", line 101, in load self._post_process() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/config/config.py", line 120, in _post_process notify(ConfigurationUpdatedEvent(self)) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.event-4.0.0-py2.7.egg/zope/event/__init__.py", line 31, in notify subscriber(event) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/switchboard.py", line 268, in handle_ConfigurationUpdatedEvent 'Duplicate runner name: {0}'.format(name)) AssertionError: Duplicate runner name: in Running mailman.testing.layers.SMTPLayer tests: Set up mailman.testing.layers.ConfigLayer Traceback (most recent call last): File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 380, in run_layer setup_layer(options, layer, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 667, in setup_layer setup_layer(options, base, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 672, in setup_layer layer.setUp() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/testing/layers.py", line 103, in setUp initialize.initialize_1(INHIBIT_CONFIG_FILE) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/initialize.py", line 125, in initialize_1 mailman.config.config.load(config_path) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/config/config.py", line 101, in load self._post_process() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/config/config.py", line 120, in _post_process notify(ConfigurationUpdatedEvent(self)) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.event-4.0.0-py2.7.egg/zope/event/__init__.py", line 31, in notify subscriber(event) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/switchboard.py", line 268, in handle_ConfigurationUpdatedEvent 'Duplicate runner name: {0}'.format(name)) AssertionError: Duplicate runner name: in Running mailman.testing.layers.RESTLayer tests: Set up mailman.testing.layers.ConfigLayer Traceback (most recent call last): File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 380, in run_layer setup_layer(options, layer, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 667, in setup_layer setup_layer(options, base, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 667, in setup_layer setup_layer(options, base, setup_layers) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.testrunner-4.0.4-py2.7.egg/zope/testrunner/runner.py", line 672, in setup_layer layer.setUp() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/testing/layers.py", line 103, in setUp initialize.initialize_1(INHIBIT_CONFIG_FILE) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/initialize.py", line 125, in initialize_1 mailman.config.config.load(config_path) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/config/config.py", line 101, in load self._post_process() File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/config/config.py", line 120, in _post_process notify(ConfigurationUpdatedEvent(self)) File "/home/steve/src/Mailman3/mailman-trunk/eggs/zope.event-4.0.0-py2.7.egg/zope/event/__init__.py", line 31, in notify subscriber(event) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/switchboard.py", line 268, in handle_ConfigurationUpdatedEvent 'Duplicate runner name: {0}'.format(name)) AssertionError: Duplicate runner name: in Running zope.testrunner.layer.UnitTests tests: Tear down mailman.testing.layers.MockAndMonkeyLayer in 0.000 seconds. Set up zope.testrunner.layer.UnitTests in 0.000 seconds. Running: test_acquire_lock_1 (mailman.bin.tests.test_master.TestMasterLock) test_master_state (mailman.bin.tests.test_master.TestMasterLock) test_current_working_directory (mailman.tests.test_configfile.TestConfigFileSearch) test_baseline (mailman.tests.test_configfile.TestConfigFileSearchWithChroot) test_environment_variable (mailman.tests.test_configfile.TestConfigFileSearchWithChroot) test_environment_variable_to_missing_path (mailman.tests.test_configfile.TestConfigFileSearchWithChroot) test_etc_file (mailman.tests.test_configfile.TestConfigFileSearchWithChroot) test_home_dot_file (mailman.tests.test_configfile.TestConfigFileSearchWithChroot) test_sibling_directory (mailman.tests.test_configfile.TestConfigFileSearchWithChroot) test_adding_the_message_hash (mailman.utilities.tests.test_email.TestEmail) test_angle_brackets_dont_contribute_to_hash (mailman.utilities.tests.test_email.TestEmail) test_hash_header_left_alone_if_no_message_id (mailman.utilities.tests.test_email.TestEmail) test_mismatched_angle_brackets_do_contribute_to_hash (mailman.utilities.tests.test_email.TestEmail) test_no_at_split (mailman.utilities.tests.test_email.TestEmail) test_normal_split (mailman.utilities.tests.test_email.TestEmail) test_remove_hash_headers_first (mailman.utilities.tests.test_email.TestEmail) test_dont_honor_ws (mailman.utilities.tests.test_wrap.TestWrap) test_honor_ws (mailman.utilities.tests.test_wrap.TestWrap) test_indentation_boundary (mailman.utilities.tests.test_wrap.TestWrap) test_simple_wrap (mailman.utilities.tests.test_wrap.TestWrap) test_two_paragraphs (mailman.utilities.tests.test_wrap.TestWrap) Ran 21 tests with 0 failures and 0 errors in 0.020 seconds. Tearing down left over layers: Tear down zope.testrunner.layer.UnitTests in 0.000 seconds. Tests with errors: Layer: mailman.testing.layers.ConfigLayer Layer: mailman.testing.layers.LMTPLayer Layer: mailman.testing.layers.SMTPLayer Layer: mailman.testing.layers.RESTLayer Total: 21 tests, 0 failures, 4 errors in 0.464 seconds. steve@turnbull:~/src/Mailman3/mailman-trunk$ python setup.py build_sphinx usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'build_sphinx' steve@turnbull:~/src/Mailman3/mailman-trunk$ grep -r build_sphinx . ./eggs/passlib-1.6.1-py2.7.egg/passlib/_setup/docdist.py: self.run_command("build_sphinx") ./eggs/passlib-1.6.1-py2.7.egg/passlib/_setup/docdist.py: cmd = self.get_finalized_command("build_sphinx") Binary file ./eggs/passlib-1.6.1-py2.7.egg/passlib/_setup/docdist.pyo matches Binary file ./eggs/passlib-1.6.1-py2.7.egg/passlib/_setup/docdist.pyc matches ./src/mailman/docs/START.rst: % python setup.py build_sphinx ./src/mailman/__init__.py:if 'build_sphinx' not in sys.argv: Binary file ./src/mailman/__init__.pyc matches steve@turnbull:~/src/Mailman3/mailman-trunk$ mkdir instance; cd instance steve@turnbull:~/src/Mailman3/mailman-trunk$ xemacs mailman.cfg steve@turnbull:~/src/Mailman3/mailman-trunk/instance$ ../bin/mailman start Starting Mailman's master runner steve@turnbull:~/src/Mailman3/mailman-trunk/instance$ ../bin/mailman create -d -o turnbull(a)sk.tsukuba.ac.jp mm3-test(a)turnbull.sk.tsukuba.ac.jp Created mailing list: mm3-test(a)turnbull.sk.tsukuba.ac.jp steve@turnbull:~/src/Mailman3/mailman-trunk/instance$ ../bin/mailman info -vGNU Mailman 3.0.0b1+ (Freeze) Python 2.7.3rc2 (default, Apr 22 2012, 22:30:17) [GCC 4.6.3] config file: /home/steve/src/Mailman3/mailman-trunk/instance/mailman.cfg db url: sqlite:////home/steve/src/Mailman3/mailman-trunk/instance/var/data/mailman.db REST root url: http://localhost:8001/3.0/ REST credentials: restadmin:restpass File system paths: ARCHIVE_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/archives BIN_DIR = /home/steve/src/Mailman3/mailman-trunk/bin DATA_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/data ETC_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/etc EXT_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/ext LIST_DATA_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/lists LOCK_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/locks LOCK_FILE = /home/steve/src/Mailman3/mailman-trunk/instance/var/locks/master.lck LOG_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/logs MESSAGES_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/messages PID_FILE = /home/steve/src/Mailman3/mailman-trunk/instance/var/master.pid QUEUE_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/queue TEMPLATE_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var/templates VAR_DIR = /home/steve/src/Mailman3/mailman-trunk/instance/var ######################## instance/var/logs/mailman.log ######################## Aug 08 23:56:45 2012 (16782) command failure: /usr/sbin/postmap /home/steve/src/Mailman3/mailman-trunk/instance/var/data/postfix_lmtp, 127, Key has expired Aug 09 12:15:33 2012 (7571) DigestRunner runner started. Aug 09 12:15:33 2012 (7570) IncomingRunner runner started. Aug 09 12:15:33 2012 (7579) LMTPRunner runner started. Aug 09 12:15:33 2012 (7574) OutgoingRunner runner started. Aug 09 12:15:33 2012 (7575) VirginRunner runner started. Aug 09 12:15:33 2012 (7580) CommandRunner runner started. Aug 09 12:15:33 2012 (7576) RetryRunner runner started. Aug 09 12:15:33 2012 (7581) NNTPRunner runner started. Aug 09 12:15:34 2012 (7577) RESTRunner runner started. Aug 09 12:15:34 2012 (7577) Starting REST server Aug 09 12:15:34 2012 (7573) ArchiveRunner runner started. Aug 09 12:15:34 2012 (7572) PipelineRunner runner started. Aug 09 12:15:35 2012 (7578) BounceRunner runner started. Aug 09 13:39:41 2012 (7570) Uncaught runner exception: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 8, 9, 4, 39, 41, 475922) Aug 09 13:39:41 2012 (7570) Traceback (most recent call last): File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/runner.py", line 221, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/runners/incoming.py", line 67, in _dispose process(mlist, msg, msgdata, start_chain) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/chains/hold.py", line 142, in _process request_id = hold_message(mlist, msg, msgdata, None) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/app/moderator.py", line 105, in hold_message RequestType.held_message, message_id, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/database/transaction.py", line 78, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/model/requests.py", line 91, in hold_request token = getUtility(IPendings).add(pendable, timedelta(days=5000)) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/database/transaction.py", line 78, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/model/pending.py", line 131, in add keyval = PendedKeyValue(key=key, value=value) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/model/pending.py", line 54, in __init__ self.value = value File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/properties.py", line 67, in __set__ obj_info.variables[column].set(value) File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/variables.py", line 396, in parse_set % (type(value), value)) TypeError: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 8, 9, 4, 39, 41, 475922) Aug 09 13:39:41 2012 (7570) SHUNTING: 1344487181.861564+93e44eec2008ac77dfaf0df4676c6b5ef2b68de8 Aug 09 13:42:09 2012 (7570) Uncaught runner exception: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 8, 9, 4, 42, 8, 769294) Aug 09 13:42:09 2012 (7570) Traceback (most recent call last): File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/runner.py", line 138, in _one_iteration self._process_one_file(msg, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/runner.py", line 221, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/runners/incoming.py", line 67, in _dispose process(mlist, msg, msgdata, start_chain) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/core/chains.py", line 90, in process link.function(mlist, msg, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/chains/hold.py", line 142, in _process request_id = hold_message(mlist, msg, msgdata, None) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/app/moderator.py", line 105, in hold_message RequestType.held_message, message_id, msgdata) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/database/transaction.py", line 78, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/model/requests.py", line 91, in hold_request token = getUtility(IPendings).add(pendable, timedelta(days=5000)) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/database/transaction.py", line 78, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/model/pending.py", line 131, in add keyval = PendedKeyValue(key=key, value=value) File "/home/steve/src/Mailman3/mailman-trunk/src/mailman/model/pending.py", line 54, in __init__ self.value = value File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/properties.py", line 67, in __set__ obj_info.variables[column].set(value) File "/home/steve/src/Mailman3/mailman-trunk/eggs/storm-0.19-py2.7-linux-x86_64.egg/storm/variables.py", line 396, in parse_set % (type(value), value)) TypeError: Expected unicode, found <type 'datetime.datetime'>: datetime.datetime(2012, 8, 9, 4, 42, 8, 769294) Aug 09 13:42:09 2012 (7570) SHUNTING: 1344487329.078011+1a488523540df1b454f0797dcae59dfd3dac27b9 ######################## instance/mailman.cfg ######################## # Copyright (C) 2012 by the Free Software Foundation, Inc. # # This file was contributed to GNU Mailman as an example # # This is an example local configuration file for an Exim installation. [mailman] layout: dev [devmode] enabled: yes recipient: me(a)example.edu [language.en] charset: utf-8 [mta] # The class defining the interface to the incoming mail transport agent. incoming: mailman.mta.exim.LMTP # The callable implementing delivery to the outgoing mail transport agent. # This must accept three arguments, the mailing list, the message, and the # message metadata dictionary. outgoing: mailman.mta.deliver.deliver # The runners are defined in the master "mailman.cfg". # The style is defined in the master "mailman.cfg". ######################## src/mailman/src/mta/exim.py ######################## # N.B. All of the methods of class LMTP can probably be replaced with # trivial methods that just "pass". However I haven't tested that # yet, so I include the exim.py that was actually used when I created # my test list "mm3-test(a)turnbull.sk.tsukuba.ac.jp". # Copyright (C) 2001-2012 by the Free Software Foundation, Inc. # # This file is part of GNU Mailman. # # GNU Mailman is free software: you can redistribute it and/or modify it under # the terms of the GNU General Public License as published by the Free # Software Foundation, either version 3 of the License, or (at your option) # any later version. # # GNU Mailman is distributed in the hope that it will be useful, but WITHOUT # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for # more details. # # You should have received a copy of the GNU General Public License along with # GNU Mailman. If not, see <http://www.gnu.org/licenses/>. """Creation/deletion hooks for the Exim MTA. This file has been used with and lightly tested on a Debian system with the exim4-4.80-4 package. #### Move this to user-accessible documentation: Exim doesn't use an alias file. Instead, the address is filtered by the Exim router and passed to a transport. Both the relevant router and the transport are named 'mailman3'. The transport is just an smtp driver with lmtp protocol. The router needs to accept any name, and parse out the list name from the administrative aliases. In order to check whether string is actually a list name, we have Exim check for the directory $var_dir/lists with the same name as the list's posting address. AFAICS, creating lists is a no-op here. I use main/15_local_mailman_macros, router/444_local_mailman3, and transport/54_local_mailman3 on a Debian system. """ from __future__ import absolute_import, print_function, unicode_literals __metaclass__ = type __all__ = [ 'LMTP', ] # #### Most of these imports can go away, I suppose import os import logging from flufl.lock import Lock from operator import attrgetter from zope.component import getUtility from zope.interface import implementer from mailman.config import config from mailman.interfaces.listmanager import IListManager from mailman.interfaces.mta import ( IMailTransportAgentAliases, IMailTransportAgentLifecycle) from mailman.utilities.datetime import now # #### We don't need this AFAICS. # log = logging.getLogger('mailman.error') # #### This can be removed, but that is untested. def _receipt(mlist): return os.path.join(config.VAR_DIR, 'receipts', mlist.list_name) @implementer(IMailTransportAgentLifecycle) class LMTP: """Connect Mailman to Exim via LMTP.""" # #### This probably can be replaced with "def create(s, m): pass", # but that is untested. def create(self, mlist): """See `IMailTransportAgentLifecycle`. Exim detects lists in its router. We provide a dummy entry in the file system in the 'receipts' directory for Exim's check.""" # Acquire a lock file to prevent other processes from racing us here. lock_file = os.path.join(config.LOCK_DIR, 'mta') with Lock(lock_file): os.makedirs(_receipt(mlist)) # #### This probably can be replaced with "def delete(s, m): pass", # but that is untested. def delete(self, mlist): """See `IMailTransportAgentLifecycle`. Removes mlist's receipt.""" # Acquire a lock file to prevent other processes from racing us here. lock_file = os.path.join(config.LOCK_DIR, 'mta') with Lock(lock_file): os.rmdir(_receipt(mlist)) def regenerate(self, output=None): """See `IMailTransportAgentLifecycle`. This routine does nothing. """ pass ######################## Exim macros for Mailman3 ######################## domainlist mm_domains=turnbull.sk.tsukuba.ac.jp MM3_LMTP_PORT=8024 MM3_HOME=/home/steve/src/Mailman3/mailman-trunk/instance # #### Next two unused? MM3_UID=list MM3_GID=list # The path of the Mailman mail wrapper script MM3_WRAP=MM3_HOME/bin/mailman # The path of the list receipt (only used as a required file when # verifying list addresses) MM3_LISTCHK=MM3_HOME/var/lists/${local_part}@${domain} ######################## Exim router for Mailman3 ######################## # Routers are the only configuration that is order dependent. In my # Debian configuration, the following routers precede Mailman3: # # 00_exim4-config_header # 100_exim4-config_domain_literal # 150_exim4-config_hubbed_hosts # 200_exim4-config_primary # 300_exim4-config_real_local # 400_exim4-config_system_aliases # 430_ack_class_mail # a local hack # 440_class_mail # a local hack (cont.) # # It should be reasonably clear what these do but I'll provide details # on request. mailman3_router: driver = accept domains = +mm_domains require_files = MM3_LISTCHK local_part_suffix_optional local_part_suffix = -admin : \ -bounces : -bounces+* : \ -confirm : -confirm+* : \ -join : -leave : \ -owner : -request : \ -subscribe : -unsubscribe transport = mailman3_transport ######################## Exim transport for Mailman3 ######################## mailman3_transport: driver = smtp protocol = lmtp allow_localhost hosts = localhost port = MM3_LMTP_PORT ** 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/1035057 Title: Unicode error prevents delivery of post To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035057/+subscriptions

2 5

[Bug 418457] Re: buildout fails: can't install Jinja2
by Stephen Turnbull 16 Aug '12

16 Aug '12

** 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/418457 Title: buildout fails: can't install Jinja2 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/418457/+subscriptions

1 0

[Bug 265843] Re: sync_members bugs (possible fixes included)
by Barry Warsaw 02 Aug '12

02 Aug '12

** Changed in: mailman Assignee: Bernard Keimel (sladev5976) => (unassigned) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265843 Title: sync_members bugs (possible fixes included) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265843/+subscriptions

1 0

[Bug 265179] Re: Security hole: passwords mailed in clear
by Barry Warsaw 02 Aug '12

02 Aug '12

** Changed in: mailman Status: Fix Released => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265179 Title: Security hole: passwords mailed in clear To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265179/+subscriptions

1 0

[Bug 265179] Re: Security hole: passwords mailed in clear
by Bernard Keimel 01 Aug '12

01 Aug '12

** Changed in: mailman Status: Invalid => Confirmed ** Changed in: mailman Status: Confirmed => 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/265179 Title: Security hole: passwords mailed in clear To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265179/+subscriptions

1 0

[Bug 265843] Re: sync_members bugs (possible fixes included)
by Bernard Keimel 01 Aug '12

01 Aug '12

** Changed in: mailman Assignee: (unassigned) => Bernard Keimel (sladev5976) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265843 Title: sync_members bugs (possible fixes included) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265843/+subscriptions

1 0

[Bug 265179] Re: Security hole: passwords mailed in clear
by W. Prins 01 Aug '12

01 Aug '12

Ran into this today, believe it or not, on the Python mailing list. I'm surprised that bad security is justified by referring to bad policy documentation... as if the fact that a bad idea written as policy on a subscription page makes it suddenly a good idea or beyond criticism. IMHO Users should not be told to "follow instructions" to compensate for lax handling of password data, no matter how trivial it may seem. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265179 Title: Security hole: passwords mailed in clear To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265179/+subscriptions

2 1