Mailman 3 October 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 14 Dec '21

14 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 27 Sep '20

27 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 15 Jan '19

15 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 10 Jun '17

10 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 10 Jun '17

10 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 10 Jun '17

10 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 10 Jun '17

10 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 01 Aug '15

01 Aug '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 1070064] [NEW] Add a 'policy' command
by Barry Warsaw 23 May '15

23 May '15

Public bug reported: It would be kind of nice for MM3 to implement a 'policy' command. If you issue this email command, you would receive a response containing an admin supplied policy text. This response should adhere to the general grace period timeouts, and the text should be retrieved via the generalized url retrieval and caching machinery. This way, the same policy text could be retrievable via email command or web ui. There should be a way to request policy documents in multiple languages. ** Affects: mailman Importance: Wishlist Status: New ** Tags: mailman3 ** Changed in: mailman 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/1070064 Title: Add a 'policy' command To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1070064/+subscriptions

2 1

[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 29 Apr '15

29 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 29 Apr '15

29 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 29 Apr '15

29 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 29 Apr '15

29 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 29 Apr '15

29 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 25 Mar '15

25 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 1060951] [NEW] Bug getting i18n'ed attachment filenames (RFC2231)
by Aurélien Bompard 31 Dec '14

31 Dec '14

Public bug reported: RFC 2231 allows filenames to have non-ascii characters. The get_filename() method in Python's Message class handles this by calling email.utils.collapse_rfc2231_value() at the end of get_filename. This method returns the filename in Unicode. This fails in Mailman because the mailman.email.message.Message class has a wrapper around get() and __getitem__() to return unicode headers. As a result, the collapse_rfc2231_value() tries to transforms into unicode an already unicode string, and I get the following exception: File "/usr/lib/python2.7/email/utils.py", line 319, in collapse_rfc2231_value return unicode(rawval, charset, errors) TypeError: decoding Unicode is not supported A possible solution to this would be to make Mailman's Message get_filename() method be more than just an exception-catching wrapper, and re-implement the original get_filename() method, inserting a conversion to str before calling collapse_rfc2231_value(). Does this make sense ? Any other idea for a possible solution ? ** 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/1060951 Title: Bug getting i18n'ed attachment filenames (RFC2231) To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1060951/+subscriptions

3 8

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

30 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 23 Apr '14

23 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 1067953] [NEW] Request: Add HTML support for message excerpt preview
by Conrad Yoder 17 Apr '14

17 Apr '14

Public bug reported: Many if not most people currently use HTML-formatted email. When list moderators have to approve email postings on the Administrative Requests page, only a plaintext Message Excerpt is displayed, making informed viewing of a list member's message sometimes next to impossible. Looking through the mailman discussion list archives, I see that this feature was asked for as far back as 2005 - 7 years ago, so this is not a "new" suggestion. This would be an extremely helpful feature to add. If there are security concerns, a toggle or config option could easily be added so HTML viewing is not the default, and/or java/javascript could be disabled in the preview window. Thank you for your consideration here. ** Affects: mailman Importance: Undecided Status: New ** Tags: excerpt html preview request -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1067953 Title: Request: Add HTML support for message excerpt preview To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1067953/+subscriptions

2 1

[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 16 Mar '14

16 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 16 Mar '14

16 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 11 Aug '13

11 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 15 Jul '13

15 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 1068837] [NEW] Automatic rejects of incoming posts are not logged.
by Mark Sapiro 15 Jul '13

15 Jul '13

Public bug reported: When a message is rejected by a pipeline handler raising Errors.RejectMessage, the message is bounced to the sender with an appropriate message, but nothing is logged. This should be logged in the vette log. ** Affects: mailman Importance: Medium Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1068837 Title: Automatic rejects of incoming posts are not logged. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1068837/+subscriptions

2 3

[Bug 1047100] [NEW] The logger can throw UnicodeEncodeError if the log message is unicode
by Mark Sapiro 15 Jul '13

15 Jul '13

Public bug reported: There is code in Mailman's _Syslog.write_ex() method to catch a UnicodeError when writing the log file and quoted-printable encode the log message. This works on messages that contain non-ascii, 8-bit bytes, but if the message is a unicode with non-ascii characters, the attempt to quoted-printable encode it will throw UnicodeEncodeError which is not caught. Fix this by first encoding the unicode message as utf-8 and then quoted- printable encoding that. ** Affects: mailman Importance: High 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/1047100 Title: The logger can throw UnicodeEncodeError if the log message is unicode To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1047100/+subscriptions

1 2

[Bug 1070574] [NEW] add_members needs a 'nomail' option
by Mark Sapiro 15 Jul '13

15 Jul '13

Public bug reported: Some situations make it desirable to add a member to a list with mail delivery disabled. It would be convenient if add_members had an option to do this. ** 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/1070574 Title: add_members needs a 'nomail' option To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1070574/+subscriptions

1 1

[Bug 693134] [NEW] Uncaught bounce from Dovecot when Quota Exceeded
by JorSol 21 Jun '13

21 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

[Merge] lp:~sunu0000/postorius/general_settings into lp:postorius
by Tarashish Mishra 19 Mar '13

19 Mar '13

Tarashish Mishra has proposed merging lp:~sunu0000/postorius/general_settings into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) Related bugs: Bug #1062877 in Postorius: "General Settings" https://bugs.launchpad.net/postorius/+bug/1062877 For more details, see: https://code.launchpad.net/~sunu0000/postorius/general_settings/+merge/1322… Added placeholder text for General Settings -- https://code.launchpad.net/~sunu0000/postorius/general_settings/+merge/1322… Your team Mailman Coders is requested to review the proposed merge of lp:~sunu0000/postorius/general_settings into lp:postorius.

3 3

[Bug 1073506] [NEW] Drop support for Python 2.6
by Barry Warsaw 31 Dec '12

31 Dec '12

Public bug reported: Whenever the dependency stack is ported to Python 3, Mailman 3 will be ported to Python 3. In the meantime, making the code Python 2.7 -3 clean is an intermediate step toward Python 3 support. In order to do this, we really need to drop Python 2.6 support and this will also allow us to improve the test suite, as well as other code improvements. Besides, Python 2.6 is 4 years old and in security-only maintenance mode, while Python 2.7 is stable and still supported for bug fixes. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: In Progress ** Tags: mailman3 ** Changed in: mailman Status: New => Triaged ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Assignee: (unassigned) => Barry Warsaw (barry) ** Changed in: mailman Milestone: None => 3.0.0b3 ** Tags added: mailman3 ** Changed in: mailman Status: Triaged => 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/1073506 Title: Drop support for Python 2.6 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1073506/+subscriptions

1 3

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

31 Dec '12

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

3 5

[Bug 1054730] [NEW] Set the verified_on flag for IAddress through the REST API
by Barry Warsaw 31 Dec '12

31 Dec '12

Public bug reported: IAddress.verified_on is how the core knows whether the registered address has been verified or not. Because Postorius supports registration via BrowserID, and by definition a BrowserID email address must be verified, we want to allow Postorius to set the verified_on field via the REST API. This probably won't be a direct value setting. Instead, I think you want to POST true or false to .../addresses/foo(a)example.com/verified and that will set IAddresses.verified_on to now() or to None. ** Affects: mailman Importance: High Assignee: Barry Warsaw (barry) Status: New ** Tags: mailman3 rest -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1054730 Title: Set the verified_on flag for IAddress through the REST API To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1054730/+subscriptions

1 3

[Bug 1047286] [NEW] Notifications for core events
by George Chatzisofroniou 31 Dec '12

31 Dec '12

Public bug reported: It would be great if core could provide notifications for more events to support plugins or any new internal functionality like: - New subscription - New thread started Those two notifications seems to be essential for the MM3-Metrics module (https://launchpad.net/mm3-metrics) in order to provide a nice overview of the system activity. Also, the notification that the core currently provides is that of a new posting. If this notification carried more information like the number of recipients or the message size we could provide additional interesting metrics via the MM3-Metrics module. ** Affects: mailman Importance: Undecided Status: New ** Tags: events metrics modules notifications plugins -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1047286 Title: Notifications for core events To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1047286/+subscriptions

2 4

[Bug 1035033] [NEW] bin/mailman --help could be improved
by Stephen Turnbull 31 Dec '12

31 Dec '12

Public bug reported: What the "reopen" command does is not at all clear. (Is it like "reload" in an init script, rereading config files? If so, maybe "reload" would be a better name.) Presumably the "restart" command stops *and* starts the runners. You can assign this to me (it would be appreciated if you'd tell me what reopen does, although I guess I could read the code. :-) ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1035033 Title: bin/mailman --help could be improved To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1035033/+subscriptions

2 4

[Bug 982551] [NEW] ./mailman.cfg only used partially
by Bernhard Schmidt 31 Dec '12

31 Dec '12

Public bug reported: GNU Mailman 3.0.0b1+ (current bzr head). http://packages.python.org/mailman/src/mailman/docs/START.html#running- mailman-3 talks about ./mailman.cfg being used as configuration (among others). This seems to be only partially true. I put this mailman.cfg into /usr/local/mailman --- [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:mailman@xxx/mailman [shell] use_ipython: yes [mta] incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mailout.xxx lmtp_port: 8024 smtp_host: mailout.xxx smtp_port: 25 [runner.nntp] start: no --- and started bin/mailman start. The PostgreSQL database was initialized, bin/mailman status showed the correct configuration location. I could create lists and they were added in the SQL database. It would use ipython as shell. But it would still try to send mail through localhost, and it would still start the nntp runner. And LMTP would reject mails to the existing lists with "mailbox unavailable". So it seems the configuration was only used by the main process, but not by the runners. Moving the configuration to a non-relative location fixed it. ** Affects: mailman Importance: Undecided Status: New -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/982551 Title: ./mailman.cfg only used partially To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/982551/+subscriptions

2 7

[Bug 975692] [NEW] Allow style assignments when creating a list through REST
by Barry Warsaw 31 Dec '12

31 Dec '12

Public bug reported: You should be able to query the available list styles through the REST API, and choose an available style when creating the mailing list through REST. ** Affects: mailman Importance: Low Status: Confirmed ** Tags: api easy mailman3 ** Tags removed: rest ** Tags added: api -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/975692 Title: Allow style assignments when creating a list through REST To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/975692/+subscriptions

1 4

[Merge] lp:~sunu0000/postorius/newuser_hint into lp:postorius
by Tarashish Mishra 16 Dec '12

16 Dec '12

Tarashish Mishra has proposed merging lp:~sunu0000/postorius/newuser_hint into lp:postorius. Requested reviews: Terri (terriko) Related bugs: Bug #1062856 in Postorius: "It is not clear how to log in if you do not already have an account." https://bugs.launchpad.net/postorius/+bug/1062856 For more details, see: https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263 Added hint for new users to sign in. -- https://code.launchpad.net/~sunu0000/postorius/newuser_hint/+merge/132263 Your team Mailman Coders is subscribed to branch lp:postorius.

3 2

[Merge] lp:~sophron/postorius/create_users into lp:postorius
by George Chatzisofroniou 26 Oct '12

26 Oct '12

George Chatzisofroniou has proposed merging lp:~sophron/postorius/create_users into lp:postorius. Requested reviews: Florian Fuchs (flo-fuchs) For more details, see: https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567 I worked on this bug: https://bugs.launchpad.net/postorius/+bug/1058445 I added the feature to create a mailman user account, but in order to edit the basic user data via the web interface, some additions to mailman client are required. See, https://bugs.launchpad.net/mailman.client/+bug/1066352 and https://bugs.launchpad.net/mailman.client/+bug/1066343. We also need an icon for the new entry on the menu: https://bugs.launchpad.net/postorius/+bug/1066340 I think it's better to divide the whole 'edit user' feature into smaller ones (delete user, register addresses to a user, basic data edit, etc). -- https://code.launchpad.net/~sophron/postorius/create_users/+merge/129567 Your team Mailman Coders is subscribed to branch lp:postorius.

4 4

[Merge] lp:~wacky/postorius/django_1_5 into lp:postorius
by Richard Wackerbarth 20 Oct '12

20 Oct '12

Richard Wackerbarth has proposed merging lp:~wacky/postorius/django_1_5 into lp:postorius. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~wacky/postorius/django_1_5/+merge/127060 Django 1.5 will require that URL names be quoted These changes conform to the revised form and continue to support django 1.4 by loading the "future" version of the url tag. -- https://code.launchpad.net/~wacky/postorius/django_1_5/+merge/127060 Your team Mailman Coders is requested to review the proposed merge of lp:~wacky/postorius/django_1_5 into lp:postorius.

3 2

[Bug 1068944] [NEW] *Everything* in the moderation interface needs to be batchable
by Stephen Turnbull 20 Oct '12

20 Oct '12

Public bug reported: A user of 2.1.9 reports on Mailman-Users that his server is being hammered by automated subscription requests (including handling the confirmation process). He generously says it's not a big deal except that his list-owners get inundated with subscription requests. The issue is that such requests ** 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/1068944 Title: *Everything* in the moderation interface needs to be batchable To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1068944/+subscriptions

1 1

[Bug 558204] Re: allow specifying another list in accept_these_nonmembers
by Mark Sapiro 20 Oct '12

20 Oct '12

** Changed in: mailman Status: New => Fix Released ** Changed in: mailman Milestone: None => 2.1-stable -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558204 Title: allow specifying another list in accept_these_nonmembers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558204/+subscriptions

1 0

[Bug 266756] Re: add_members command
by Mark Sapiro 20 Oct '12

20 Oct '12

You could make bin/my_add_members containing #!/bin/sh cd /path/to/mailman/bin echo $2 | add_members -r - $1 and then do my_add_members mylist customer(a)address.tld ** Changed in: mailman Status: New => Won't Fix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266756 Title: add_members command To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266756/+subscriptions

1 0

[Bug 266678] Re: Add X-Listmember header
by Mark Sapiro 20 Oct '12

20 Oct '12

Adding such a header requires that a separate message be sent to each user. This is no different from enabling personalization for the list and adding the list member's address in msg_header or msg_footer. If the adding of X-Listmember: were an option, this is essentially no different from the personalize = Yes/No option, and if it were not optional, it would force sending of individual messages on those installations/lists that don't want to. ** Changed in: mailman Status: New => Won't Fix -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266678 Title: Add X-Listmember header To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266678/+subscriptions

1 0

[Bug 1066465] [NEW] Remove e-mail adresses from html attachments
by rm87 19 Oct '12

19 Oct '12

Public bug reported: As some mail clients add previous messages to email as html attachments, an option to remove (or scramble) e-mail adresses from these would be nice. ** 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/1066465 Title: Remove e-mail adresses from html attachments To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1066465/+subscriptions

2 3

[Bug 1062963] Re: Admin notification not received
by Barry Warsaw 14 Oct '12

14 Oct '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/1062963 Title: Admin notification not received To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062963/+subscriptions

1 0

[Bug 1062957] Re: No welcome message
by Terri 13 Oct '12

13 Oct '12

Mostly a note to self: I need to check that this was not a function of the test setup used on gimli. ** Also affects: mailman Importance: Undecided Status: New ** No longer affects: mailman ** Changed in: postorius Status: New => Incomplete -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1062957 Title: No welcome message To manage notifications about this bug go to: https://bugs.launchpad.net/postorius/+bug/1062957/+subscriptions

1 0

[Bug 1062963] Re: Admin notification not received
by Terri 13 Oct '12

13 Oct '12

Need to confirm that the setting is being set correctly in REST, but this may be a Mailman3 bug. ** Also affects: mailman Importance: Undecided Status: New ** Changed in: postorius Status: New => Triaged ** Changed in: postorius Importance: Undecided => High -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1062963 Title: Admin notification not received To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1062963/+subscriptions

1 0

[Bug 418457] Re: buildout fails: can't install Jinja2
by Barry Warsaw 03 Oct '12

03 Oct '12

This is a test; please ignore. -- 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 266821] Re: privacy hole in password reminder
by Mark Sapiro 02 Oct '12

02 Oct '12

*** This bug is a duplicate of bug 265179 *** https://bugs.launchpad.net/bugs/265179 ** This bug has been marked a duplicate of bug 265179 Security hole: passwords mailed in clear -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266821 Title: privacy hole in password reminder To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions

2 2

[Bug 265179] Re: Security hole: passwords mailed in clear
by Mark Sapiro 02 Oct '12

02 Oct '12

Won't fix applies to Mailman 2.1. Mailman 3 does not store clear text passwords. ** Changed in: mailman Status: Invalid => Won't Fix -- 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 266821] Re: privacy hole in password reminder
by trampster 01 Oct '12

01 Oct '12

It is completely unacceptable that such a widely used opensource tool as this has such a major security flaw in it. You should not be able to send me my password in plaintext. Because passwords should be stored using an non reversible salted hash. This is a major PR disaster just waiting to happen. Mainman would become a laughing stock of the software world. How has this gone unfixed for 6 years. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266821 Title: privacy hole in password reminder To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266821/+subscriptions

2 1