From 1660989 at bugs.launchpad.net Wed Feb 1 08:51:49 2017 From: 1660989 at bugs.launchpad.net (Leonard) Date: Wed, 01 Feb 2017 13:51:49 -0000 Subject: [Bug 1660989] [NEW] impossible to end completely account of mailman Message-ID: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Public bug reported: Hi, I removed everything at my provider about mailinglists etc. I still receive monthly this announcement: ----------------- This is a reminder, sent out once a month, about your dosh.nl mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request at dosh.nl) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner at dosh.nl. Thanks! Passwords for lpvr55 at gmail.com: List Password // URL ---- -------- nieuwsbrief-sr at dosh.nl vuwauxif http://lists.dosh.nl/mailman/options/nieuwsbrief-sr/lpvr55%40gmail.com _____________________________ But http://lists.dosh.nl/mailman/ doesn't exists anymore for a long time. Please help me to stop the mailinglist completely. Thanks! bye, Leonard van Rhijn (e-mail: doshweb at dosh.nl or lpvr55 at gmail.com) Rotterdam ** 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/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From mark at msapiro.net Wed Feb 1 12:11:01 2017 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 01 Feb 2017 17:11:01 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170201171101.12114.4754.malone@soybean.canonical.com> The notices are coming from a server that used to host the lists.dosh.nl domain and from which the list was never removed. See https://wiki.list.org/x/8683538 ** Changed in: mailman Status: New => Invalid -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From 1660989 at bugs.launchpad.net Thu Feb 2 03:24:19 2017 From: 1660989 at bugs.launchpad.net (Leonard) Date: Thu, 02 Feb 2017 08:24:19 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170202082419.11526.6060.malone@soybean.canonical.com> Thanks, but I don't understand at all what to do. I'll donate $ 20,- if you completely help me out with this. Thanks, bye, Leonard -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From mark at msapiro.net Thu Feb 2 10:48:44 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 02 Feb 2017 15:48:44 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170202154844.1103.66393.malone@wampee.canonical.com> We would be happy to accept your donation at https://my.fsf.org/civicrm/contribute/transact?reset=1&id=22 but our support is not contingent upon that. As far as what to do, if you read the article at https://wiki.list.org/x/8683538 and still don't know, I'll try to explain. The messages are coming from the server that used to host the lists.dosh.nl domain at some time in the past. In order to find that server, if you can't remember where it was, examine the full headers or full raw message of the daily notice you receive. The earliest Received: headers (furthest from the top) will contain the IP address of the server which contains the Mailman installation that is sending the notice. Using tools like 'host' and 'whois' you should be able to find who operates the server. That is who you need to contact to remove the list. If you can't figure it out, post the full headers here, and I'll try to help. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From 1660989 at bugs.launchpad.net Thu Feb 2 11:31:13 2017 From: 1660989 at bugs.launchpad.net (Leonard) Date: Thu, 02 Feb 2017 16:31:13 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170202163113.9284.62917.malone@gac.canonical.com> Please try to help me, thanks As I never like free software, I always like to pay. Only the the sun rises for free, and lunches are never free (anyway in Holland, ha, ha) --------------------------------------------------------------- Thank you for supporting GNU Mailman! Please print this receipt for your records. =========================================================== Contribution Information =========================================================== Amount: $ 25.00 -------------------------------------------------------------- Underneath the heading of the mail: Delivered-To: lpvr55 at gmail.com Received: by 10.194.65.70 with SMTP id v6csp2162954wjs; Tue, 31 Jan 2017 20:00:32 -0800 (PST) X-Received: by 10.99.104.198 with SMTP id d189mr1012735pgc.55.1485921632434; Tue, 31 Jan 2017 20:00:32 -0800 (PST) Return-Path: Received: from nov-007-i455.relay.mailchannels.net (nov-007-i455.relay.mailchannels.net. [46.232.183.9]) by mx.google.com with ESMTPS id u21si13159235pgi.398.2017.01.31.20.00.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2017 20:00:32 -0800 (PST) Received-SPF: neutral (google.com: 46.232.183.9 is neither permitted nor denied by best guess record for domain of mailman-bounces at ns1.pleskserver3.nl) client-ip=46.232.183.9; Authentication-Results: mx.google.com; spf=neutral (google.com: 46.232.183.9 is neither permitted nor denied by best guess record for domain of mailman-bounces at ns1.pleskserver3.nl) smtp.mailfrom=mailman-bounces at ns1.pleskserver3.nl X-Sender-Id: internetserviceeurope|env-sender|mailman-bounces at ns1.pleskserver3.nl Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 1AD3A1427C2 for ; Wed, 1 Feb 2017 04:00:13 +0000 (UTC) Received: from ns1.pleskserver3.nl (unknown [100.96.17.213]) by relay.mailchannels.net (Postfix) with ESMTPA id 1F0C61429D3 for ; Wed, 1 Feb 2017 04:00:11 +0000 (UTC) X-Sender-Id: internetserviceeurope|env-sender|mailman-bounces at ns1.pleskserver3.nl Received: from ns1.pleskserver3.nl ([TEMPUNAVAIL]. [172.20.56.146]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.7.14); Wed, 01 Feb 2017 04:00:12 +0000 X-MC-Relay: Junk X-MailChannels-SenderId: internetserviceeurope|env-sender|mailman-bounces at ns1.pleskserver3.nl X-MailChannels-Auth-Id: InternetServiceEurope X-MC-Loop-Signature: 1485921612543:1815160819 X-MC-Ingress-Time: 1485921612543 Received: from ns1.pleskserver3.nl (localhost [IPv6:::1]) by ns1.pleskserver3.nl (Postfix) with ESMTP id 350222E0085 for ; Wed, 1 Feb 2017 05:00:05 +0100 (CET) Received-SPF: pass (ns1.pleskserver3.nl: localhost is always allowed.) client-ip=::1; envelope-from=mailman-bounces at ns1.pleskserver3.nl; helo=ns1.pleskserver3.nl; MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: dosh.nl mailing list memberships reminder From: mailman-owner at dosh.nl To: lpvr55 at gmail.com X-No-Archive: yes Message-ID: Date: Wed, 01 Feb 2017 05:00:01 +0100 Precedence: bulk X-BeenThere: mailman at ns1.pleskserver3.nl X-Mailman-Version: 2.1.12 List-Id: X-List-Administrivia: yes Sender: mailman-bounces at ns1.pleskserver3.nl Errors-To: mailman-bounces at ns1.pleskserver3.nl This is a reminder, sent out once a month, about your dosh.nl mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request at dosh.nl) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner at dosh.nl. Thanks! Passwords for lpvr55 at gmail.com: List Password // URL ---- -------- nieuwsbrief-sr at dosh.nl vuwauxif http://lists.dosh.nl/mailman/options/nieuwsbrief-sr/lpvr55%40gmail.com -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From mark at msapiro.net Thu Feb 2 12:49:00 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 02 Feb 2017 17:49:00 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170202174900.12050.5166.malone@soybean.canonical.com> The list in question is at http://ns1.pleskserver3.nl/mailman/listinfo /nieuwsbrief-sr The admin interface for that list is at http://ns1.pleskserver3.nl/mailman/admin/nieuwsbrief-sr and the admindb interface is at http://ns1.pleskserver3.nl/mailman/admindb/nieuwsbrief- sr >From the information in your reminder, I was able to go to http://ns1.pleskserver3.nl/mailman/options/nieuwsbrief- sr/lpvr55%40gmail.com, log in and unsubscribe you. If you know the admin password for the list you can log in at http://ns1.pleskserver3.nl/mailman/admin/nieuwsbrief-sr and there may be a "Delete this mailing list (requires confirmation)" link at the upper right depending on the server configuration. If you don't know the password or if the link is not there, you will have to contact pleskserver.nl to remove the list. This may not be easy as it is not clear from https://who.is/whois/pleskserver.nl who this is, but it may be http://dutchwebhosting.nl/ -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From 1660989 at bugs.launchpad.net Thu Feb 2 14:39:46 2017 From: 1660989 at bugs.launchpad.net (Leonard) Date: Thu, 02 Feb 2017 19:39:46 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170202193946.1178.73381.malone@wampee.canonical.com> Hi Mark, I just contacted my provider (Dutch Webhosting). There was indeed an issue about an upgrade to a new nameserver while mailman was left behind on the old one. Anyway it was something I couldn't solve myself as they told me(I don't understand much about this kind of things). They removed all now, and it should be solved by now. Anyway, many many thanks for your very kind help! (helpdesks are sometimes hard to reach) Do you close this ticket, or do I have to do that? bye, Leonard -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From mark at msapiro.net Thu Feb 2 15:07:42 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 02 Feb 2017 20:07:42 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170202200742.11526.44028.malone@soybean.canonical.com> It's effectively closed. I'm glad you got it resolved. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From 1660989 at bugs.launchpad.net Thu Feb 2 15:58:22 2017 From: 1660989 at bugs.launchpad.net (Leonard) Date: Thu, 02 Feb 2017 20:58:22 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> <20170202200742.11526.44028.malone@soybean.canonical.com> Message-ID: <000e01d27d97$171bd780$45538680$@dosh.nl> not without your kind help! and ok, a donation may perhaps not be for extra help or whatsoever, still I liked to do so as Mailman can't live for free. L. webmeester www.dosh.nl -----Oorspronkelijk bericht----- Van: bounces at canonical.com [mailto:bounces at canonical.com] Namens Mark Sapiro Verzonden: donderdag 2 februari 2017 21:08 Aan: doshweb at dosh.nl Onderwerp: [Bug 1660989] Re: impossible to end completely account of mailman It's effectively closed. I'm glad you got it resolved. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman Status in GNU Mailman: Invalid Bug description: Hi, I removed everything at my provider about mailinglists etc. I still receive monthly this announcement: ----------------- This is a reminder, sent out once a month, about your dosh.nl mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request at dosh.nl) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner at dosh.nl. Thanks! Passwords for lpvr55 at gmail.com: List Password // URL ---- -------- nieuwsbrief-sr at dosh.nl vuwauxif http://lists.dosh.nl/mailman/options/nieuwsbrief-sr/lpvr55%40gmail.com _____________________________ But http://lists.dosh.nl/mailman/ doesn't exists anymore for a long time. Please help me to stop the mailinglist completely. Thanks! bye, Leonard van Rhijn (e-mail: doshweb at dosh.nl or lpvr55 at gmail.com) Rotterdam To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From mark at msapiro.net Thu Feb 2 16:12:20 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 02 Feb 2017 21:12:20 -0000 Subject: [Bug 1660989] Re: impossible to end completely account of mailman References: <20170201135149.16745.34469.malonedeb@chaenomeles.canonical.com> Message-ID: <20170202211221.11421.28386.malone@soybean.canonical.com> We try to help as we can, and we do appreciate your donation. Thank you. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1660989 Title: impossible to end completely account of mailman To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1660989/+subscriptions From mark at msapiro.net Sat Feb 4 01:07:25 2017 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 04 Feb 2017 06:07:25 -0000 Subject: [Bug 1661810] [NEW] Certain Malformed list names throw TypeError: in roster CGI Message-ID: <20170204060726.14491.70065.malonedeb@soybean.canonical.com> Public bug reported: We've seen attacks visiting URLs such as . The list name after unescaping is python-dev%22%2dswffelqj%2d%22 which websafes to the same thing. Ultimately, this calls error_page(_('No such list %(safelistname)s')) which in turn calls error_page_doc(doc, errmsg) with the translated error message. The problem is error_page_doc is defined as def error_page_doc(doc, errmsg, *args): even though it is never called with any additional args. It then tries to interpolate the (empty) args into the errmsg string which in this case contains a '%' an results in TypeError: not enough arguments for format string The solution, since error_page_doc is never called with extra arguments is to just drop the *args and the attempted interpolation. ** 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/1661810 Title: Certain Malformed list names throw TypeError: in roster CGI To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1661810/+subscriptions From 1661810 at bugs.launchpad.net Sat Feb 4 01:21:25 2017 From: 1661810 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sat, 04 Feb 2017 06:21:25 -0000 Subject: [Bug 1661810] Re: Certain Malformed list names throw TypeError: in roster CGI References: <20170204060726.14491.70065.malonedeb@soybean.canonical.com> Message-ID: <20170204062126.719.15474.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1661810 Title: Certain Malformed list names throw TypeError: in roster CGI To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1661810/+subscriptions From mark at msapiro.net Tue Feb 14 16:44:56 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 14 Feb 2017 21:44:56 -0000 Subject: [Bug 1664729] [NEW] Processing a probe bounce from a deleted member throws NotAMemberError Message-ID: <20170214214456.29967.71622.malonedeb@gac.canonical.com> Public bug reported: In processing a probe bounce, BounceRunner attempts to get the bounce_info for the user. The situation where the probe is delayed and the bounce_info is gone was covered in https://bugs.launchpad.net/mailman/+bug/1482940 but if the user has been removed, getBounceInfo throws NotAMemberError which should be caught and handled appropriately. ** 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/1664729 Title: Processing a probe bounce from a deleted member throws NotAMemberError To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1664729/+subscriptions From 1664729 at bugs.launchpad.net Tue Feb 14 22:17:46 2017 From: 1664729 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 15 Feb 2017 03:17:46 -0000 Subject: [Bug 1664729] Re: Processing a probe bounce from a deleted member throws NotAMemberError References: <20170214214456.29967.71622.malonedeb@gac.canonical.com> Message-ID: <20170215031747.21582.42539.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1664729 Title: Processing a probe bounce from a deleted member throws NotAMemberError To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1664729/+subscriptions From 1666390 at bugs.launchpad.net Mon Feb 20 23:57:11 2017 From: 1666390 at bugs.launchpad.net (Jeremy) Date: Tue, 21 Feb 2017 04:57:11 -0000 Subject: [Bug 1666390] [NEW] SpamAssassin documentation missing step from patch file Message-ID: <20170221045711.4184.78557.malonedeb@chaenomeles.canonical.com> Public bug reported: This page gives a few methods for using SpamAssassin with mailman: https://wiki.list.org/DOC/4.23%20How%20do%20I%20use%20SpamAssassin%20with%20Mailman%3F The second methods links to a set of instructions (http://www.jamesh.id.au/articles/mailman-spamassassin/) and then gives some additional steps to take. There are two different patch files given that you need apply to SpamAssassin.py to integrate SpamAssassin with mailman, depending on what version. The second one (just after "And beginning with Mailman 2.1.21, the following patch is required instead of the above.") isn't complete, there is an old import that needs to be deleted that isn't mentioned. Specifically, line 31, `from Mailman.Handlers.Moderate import matches_p` needs to be deleted. I just went through the instructions and it took a bit of debugging to find where the error logs were, and what the problem was. ** Affects: mailman Importance: Undecided Status: New ** Tags: documentation -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1666390 Title: SpamAssassin documentation missing step from patch file To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1666390/+subscriptions From mark at msapiro.net Tue Feb 21 00:26:24 2017 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 21 Feb 2017 05:26:24 -0000 Subject: [Bug 1666390] Re: SpamAssassin documentation missing step from patch file References: <20170221045711.4184.78557.malonedeb@chaenomeles.canonical.com> Message-ID: <20170221052624.4336.25983.malone@chaenomeles.canonical.com> Thanks for the report. I updated the wiki. ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Released ** Changed in: mailman 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/1666390 Title: SpamAssassin documentation missing step from patch file To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1666390/+subscriptions From mark at msapiro.net Thu Feb 23 00:46:24 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 23 Feb 2017 05:46:24 -0000 Subject: [Bug 1667215] [NEW] Uncaught TypeError in subscribe CGI with multiple digest flags in post/query data Message-ID: <20170223054624.4063.63833.malonedeb@chaenomeles.canonical.com> Public bug reported: If a malicious user, bot or whatever POSTs or GETs with query data to the subscribe CGI and the data contains multiple 'digest=' fragments, the resultant digest data seen by the subscribe CGI is a list rather than a string. The CGI calls int() on this which throws TypeError. The int() call is already in a try: that catches ValueError. It needs to catch TypeError too. ** 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/1667215 Title: Uncaught TypeError in subscribe CGI with multiple digest flags in post/query data To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1667215/+subscriptions From 1667215 at bugs.launchpad.net Thu Feb 23 01:06:27 2017 From: 1667215 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 23 Feb 2017 06:06:27 -0000 Subject: [Bug 1667215] Re: Uncaught TypeError in subscribe CGI with multiple digest flags in post/query data References: <20170223054624.4063.63833.malonedeb@chaenomeles.canonical.com> Message-ID: <20170223060629.2891.89892.launchpad@ackee.canonical.com> ** Branch linked: lp:mailman/2.1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1667215 Title: Uncaught TypeError in subscribe CGI with multiple digest flags in post/query data To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1667215/+subscriptions From mark at msapiro.net Thu Feb 23 01:09:49 2017 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 23 Feb 2017 06:09:49 -0000 Subject: [Bug 1667215] Re: Uncaught TypeError in subscribe CGI with multiple digest flags in post/query data References: <20170223054624.4063.63833.malonedeb@chaenomeles.canonical.com> Message-ID: <20170223060950.4063.84497.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1667215 Title: Uncaught TypeError in subscribe CGI with multiple digest flags in post/query data To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1667215/+subscriptions