From mark at msapiro.net Tue Feb 2 01:12:50 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 02 Feb 2016 06:12:50 -0000 Subject: [Bug 1539384] Re: Non-blocking DMARC mitigations should also be done for p=none References: <20160129040100.28859.40339.malonedeb@soybean.canonical.com> Message-ID: <20160202061251.12192.84253.malone@chaenomeles.canonical.com> If I understand correctly, what you are saying is that by publishing DMARC p=none you receive reports of Mailman list mail that fails DMARC and some of these reports MIGHT be spurious because if your DMARC policy were quarantine or reject the lists MIGHT apply Mailman's DMARC mitigations. I will consider addressing this, but not in the way you suggest. I will consider adding another list setting dmarc_none_moderation_action - Shall the above dmarc_moderation_action if Munge From or Wrap Message apply to messages From: domains with DMARC p=none as well as p=reject and p=quarantine? with the more detailed help explaining that a Yes setting only makes sense if dmarc_quarantine_moderation_action is also Yes and also explaining that the intend is to suppress the reports to the domain owner of failures that wouldn't be failures if the domain owner's policy were quarantine or reject. I will not do this unconditionally because I believe it should be up to the individual list owner to decide whether she wants Munge From or Wrap Message applied to messages that should be accepted without these transformations. ** Changed in: mailman Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1539384 Title: Non-blocking DMARC mitigations should also be done for p=none To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1539384/+subscriptions From 1539384 at bugs.launchpad.net Tue Feb 2 15:19:31 2016 From: 1539384 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 02 Feb 2016 20:19:31 -0000 Subject: [Bug 1539384] Re: Non-blocking DMARC mitigations should also be done for p=none References: <20160129040100.28859.40339.malonedeb@soybean.canonical.com> Message-ID: <20160202201932.18599.62931.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/1539384 Title: Non-blocking DMARC mitigations should also be done for p=none To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1539384/+subscriptions From mark at msapiro.net Tue Feb 2 15:20:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 02 Feb 2016 20:20:13 -0000 Subject: [Bug 1539384] Re: Non-blocking DMARC mitigations should also be done for p=none References: <20160129040100.28859.40339.malonedeb@soybean.canonical.com> Message-ID: <20160202202014.31310.72248.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Triaged => Fix Committed ** Changed in: mailman Milestone: None => 2.1.21 ** 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/1539384 Title: Non-blocking DMARC mitigations should also be done for p=none To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1539384/+subscriptions From mark at msapiro.net Tue Feb 2 21:25:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:25:13 -0000 Subject: [Bug 1447445] Re: Web subscribe can fail in cases of load balancers or other devices. References: <20150423043932.26920.60572.malonedeb@gac.canonical.com> Message-ID: <20160203022514.25173.22725.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1447445 Title: Web subscribe can fail in cases of load balancers or other devices. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1447445/+subscriptions From mark at msapiro.net Tue Feb 2 21:24:16 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:24:16 -0000 Subject: [Bug 1444673] Re: Anonymous lists can expose the sending domain. References: <20150415195110.29907.24669.malonedeb@gac.canonical.com> Message-ID: <20160203022417.25099.99987.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1444673 Title: Anonymous lists can expose the sending domain. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1444673/+subscriptions From mark at msapiro.net Tue Feb 2 21:23:15 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:23:15 -0000 Subject: [Bug 1442298] Re: Find member does not match name in multibyte characters References: <20150409173114.7787.72106.malonedeb@chaenomeles.canonical.com> Message-ID: <20160203022316.24582.70285.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1442298 Title: Find member does not match name in multibyte characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1442298/+subscriptions From mark at msapiro.net Tue Feb 2 21:28:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:28:40 -0000 Subject: [Bug 1532504] Re: Galician language templates are encoded in the wrong Character set. References: <20160110031138.18565.38579.malonedeb@soybean.canonical.com> Message-ID: <20160203022841.12804.64428.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1532504 Title: Galician language templates are encoded in the wrong Character set. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1532504/+subscriptions From mark at msapiro.net Tue Feb 2 21:28:13 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:28:13 -0000 Subject: [Bug 1525733] Re: Banned subscription log entries should include the source. References: <20151214002456.25935.81258.malonedeb@gac.canonical.com> Message-ID: <20160203022814.12130.87848.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1525733 Title: Banned subscription log entries should include the source. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1525733/+subscriptions From mark at msapiro.net Tue Feb 2 21:27:46 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:27:46 -0000 Subject: [Bug 1519062] Re: Unshunting a shunted message can skip the original shunting handler. References: <20151123185305.18069.19589.malonedeb@soybean.canonical.com> Message-ID: <20160203022747.13039.98793.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1519062 Title: Unshunting a shunted message can skip the original shunting handler. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1519062/+subscriptions From mark at msapiro.net Tue Feb 2 21:27:14 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:27:14 -0000 Subject: [Bug 1518084] Re: documentation: reply-to munging "useful" link now points to a spam domain References: <20151119211334.3736.55800.malonedeb@gac.canonical.com> Message-ID: <20160203022715.31796.97250.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1518084 Title: documentation: reply-to munging "useful" link now points to a spam domain To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1518084/+subscriptions From mark at msapiro.net Tue Feb 2 21:26:48 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:26:48 -0000 Subject: [Bug 1512866] Re: Some news servers reject some posts from the mail<->news gateway References: <20151103202409.21371.50512.malonedeb@soybean.canonical.com> Message-ID: <20160203022649.24313.38814.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1512866 Title: Some news servers reject some posts from the mail<->news gateway To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1512866/+subscriptions From mark at msapiro.net Tue Feb 2 21:26:20 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:26:20 -0000 Subject: [Bug 1482940] Re: A bounced probe can throw AttributeError References: <20150809013629.25012.97996.malonedeb@chaenomeles.canonical.com> Message-ID: <20160203022621.31339.94973.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1482940 Title: A bounced probe can throw AttributeError To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1482940/+subscriptions From mark at msapiro.net Tue Feb 2 21:30:02 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:30:02 -0000 Subject: [Bug 1462755] Re: qrunner crashes on invalid unicode sequence References: <20150607142830.12558.37544.malonedeb@soybean.canonical.com> Message-ID: <20160203023004.24477.5388.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1462755 Title: qrunner crashes on invalid unicode sequence To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1462755/+subscriptions From mark at msapiro.net Tue Feb 2 21:25:53 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:25:53 -0000 Subject: [Bug 1459236] Re: Mailman/Postfix integration doesn't generate virtual maps for all site list domains. References: <20150527132047.2773.60450.malonedeb@wampee.canonical.com> Message-ID: <20160203022554.12923.26833.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1459236 Title: Mailman/Postfix integration doesn't generate virtual maps for all site list domains. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1459236/+subscriptions From mark at msapiro.net Tue Feb 2 21:29:25 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:29:25 -0000 Subject: [Bug 1450826] Re: DMARC entries in the vette log don't include the list name. References: <20150501154155.28678.65492.malonedeb@soybean.canonical.com> Message-ID: <20160203022927.31310.3239.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1450826 Title: DMARC entries in the vette log don't include the list name. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1450826/+subscriptions From mark at msapiro.net Tue Feb 2 21:31:47 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:31:47 -0000 Subject: [Bug 1536816] Re: Mailman can create a non-ascii or improperly RFC 2047encoded From: header. References: <20160121223614.30742.29986.malonedeb@gac.canonical.com> Message-ID: <20160203023148.31377.55627.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1536816 Title: Mailman can create a non-ascii or improperly RFC 2047encoded From: header. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1536816/+subscriptions From mark at msapiro.net Tue Feb 2 21:35:15 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:35:15 -0000 Subject: [Bug 1523273] Re: Posting to the options page for a non-member can throw an uncaught exception References: <20151206192435.15647.99811.malonedeb@chaenomeles.canonical.com> Message-ID: <20160203023516.12763.74800.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1523273 Title: Posting to the options page for a non-member can throw an uncaught exception To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1523273/+subscriptions From mark at msapiro.net Tue Feb 2 21:34:44 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:34:44 -0000 Subject: [Bug 1507241] Re: Bad regexps in *_these_nonmembers, subscribe_auto_approval and ban_list should be logged References: <20151018021144.21127.68846.malonedeb@gac.canonical.com> Message-ID: <20160203023445.12130.48649.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1507241 Title: Bad regexps in *_these_nonmembers, subscribe_auto_approval and ban_list should be logged To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1507241/+subscriptions From mark at msapiro.net Tue Feb 2 21:34:11 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:34:11 -0000 Subject: [Bug 1505878] Re: Mailman can cause extraneous tabs to be displayed in Subject: headers References: <20151014024632.20704.24186.malonedeb@gac.canonical.com> Message-ID: <20160203023412.24313.31928.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1505878 Title: Mailman can cause extraneous tabs to be displayed in Subject: headers To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1505878/+subscriptions From mark at msapiro.net Tue Feb 2 21:33:38 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:33:38 -0000 Subject: [Bug 1503422] Re: Mailman's provided init.d script may not work with systemctl. References: <20151006202515.26614.28165.malonedeb@gac.canonical.com> Message-ID: <20160203023339.25099.30627.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1503422 Title: Mailman's provided init.d script may not work with systemctl. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1503422/+subscriptions From mark at msapiro.net Tue Feb 2 21:32:51 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:32:51 -0000 Subject: [Bug 1496632] Re: visiting the user options page with crafted post data or query fragments can produce "we hit a bug" References: <20150916234244.24517.15762.malonedeb@gac.canonical.com> Message-ID: <20160203023253.14893.42911.launchpad@gac.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1496632 Title: visiting the user options page with crafted post data or query fragments can produce "we hit a bug" To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1496632/+subscriptions From mark at msapiro.net Tue Feb 2 21:32:19 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:32:19 -0000 Subject: [Bug 1496620] Re: Mailman sometimes fails to remove redundant Re: when prefixing subject. References: <20150916230814.24810.98990.malonedeb@gac.canonical.com> Message-ID: <20160203023220.12472.71308.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1496620 Title: Mailman sometimes fails to remove redundant Re: when prefixing subject. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1496620/+subscriptions From mark at msapiro.net Tue Feb 2 21:31:07 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:31:07 -0000 Subject: [Bug 1486263] Re: cron/gate_news doesn't catch EOFError on opening the newsgroup. References: <20150818213856.19045.79167.malonedeb@wampee.canonical.com> Message-ID: <20160203023109.24443.35721.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1486263 Title: cron/gate_news doesn't catch EOFError on opening the newsgroup. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1486263/+subscriptions From mark at msapiro.net Tue Feb 2 21:30:31 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:30:31 -0000 Subject: [Bug 1476298] Re: User-options available for digest despite this option unavailable References: <20150720154742.11174.60883.malonedeb@wampee.canonical.com> Message-ID: <20160203023032.31619.21404.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1476298 Title: User-options available for digest despite this option unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1476298/+subscriptions From mark at msapiro.net Tue Feb 2 21:37:25 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:37:25 -0000 Subject: [Bug 1539384] Re: Non-blocking DMARC mitigations should also be done for p=none References: <20160129040100.28859.40339.malonedeb@soybean.canonical.com> Message-ID: <20160203023726.15629.4074.launchpad@gac.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1539384 Title: Non-blocking DMARC mitigations should also be done for p=none To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1539384/+subscriptions From mark at msapiro.net Tue Feb 2 21:36:58 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:36:58 -0000 Subject: [Bug 1526550] Re: Posts to a list with regular_exclude_lists can be delivered to excluded list members. References: <20151215223037.18834.18561.malonedeb@wampee.canonical.com> Message-ID: <20160203023659.12398.57305.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1526550 Title: Posts to a list with regular_exclude_lists can be delivered to excluded list members. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1526550/+subscriptions From mark at msapiro.net Tue Feb 2 21:36:05 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:36:05 -0000 Subject: [Bug 1525954] Re: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters References: <20151214152550.25123.231.malonedeb@soybean.canonical.com> Message-ID: <20160203023606.31796.49018.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1525954 Title: mailman-2.1.20: option "subject_prefix": prefix trailing blanks are removed when subject lines have non-ASCII characters To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1525954/+subscriptions From mark at msapiro.net Tue Feb 2 21:41:51 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 03 Feb 2016 02:41:51 -0000 Subject: [Bug 1491187] Re: mailmanctl check_privs should check effective uid, not real uid References: <20150902000405.6489.56134.malonedeb@chaenomeles.canonical.com> Message-ID: <20160203024152.24443.29479.launchpad@soybean.canonical.com> ** Changed in: mailman Status: In Progress => Fix Released ** Changed in: mailman Milestone: 2.1.21 => 2.1.21rc1 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1491187 Title: mailmanctl check_privs should check effective uid, not real uid To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1491187/+subscriptions From rajeevs1992 at gmail.com Wed Feb 3 02:43:14 2016 From: rajeevs1992 at gmail.com (Rajeev S) Date: Wed, 03 Feb 2016 07:43:14 -0000 Subject: [Merge] lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client In-Reply-To: <20140926032320.10882.41704.launchpad@ackee.canonical.com> Message-ID: <20160203074313.28864.57489.launchpad@ackee.canonical.com> The proposal to merge lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli/+merge/236052 -- Your team Mailman Coders is requested to review the proposed merge of lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client. From rajeevs1992 at gmail.com Wed Feb 3 02:43:16 2016 From: rajeevs1992 at gmail.com (Rajeev S) Date: Wed, 03 Feb 2016 07:43:16 -0000 Subject: [Merge] lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client In-Reply-To: <20140926032320.10882.41704.launchpad@ackee.canonical.com> Message-ID: <20160203074316.28865.45213.launchpad@ackee.canonical.com> The proposal to merge lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client has been updated. Status: Merged => Needs review For more details, see: https://code.launchpad.net/~rajeevs1992/mailman.client/mailmancli/+merge/236052 -- Your team Mailman Coders is requested to review the proposed merge of lp:~rajeevs1992/mailman.client/mailmancli into lp:mailman.client. From berni at birkenwald.de Fri Feb 5 07:03:36 2016 From: berni at birkenwald.de (Bernhard Schmidt) Date: Fri, 05 Feb 2016 12:03:36 -0000 Subject: [Merge] lp:~berni/mailman/fix-typo into lp:mailman Message-ID: <20160205120334.9770.64362.launchpad@ackee.canonical.com> The proposal to merge lp:~berni/mailman/fix-typo into lp:mailman has been updated. Status: Needs review => Superseded For more details, see: https://code.launchpad.net/~berni/mailman/fix-typo/+merge/285178 -- Your team Mailman Coders is requested to review the proposed merge of lp:~berni/mailman/fix-typo into lp:mailman. From berni at birkenwald.de Fri Feb 5 07:04:30 2016 From: berni at birkenwald.de (Bernhard Schmidt) Date: Fri, 05 Feb 2016 12:04:30 -0000 Subject: [Merge] lp:~berni/mailman/fix-typo into lp:mailman/2.1 Message-ID: <20160205120425.22459.77918.launchpad@ackee.canonical.com> Bernhard Schmidt has proposed merging lp:~berni/mailman/fix-typo into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~berni/mailman/fix-typo/+merge/285179 Fix German spelling for E-Mail -- Your team Mailman Coders is requested to review the proposed merge of lp:~berni/mailman/fix-typo into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 469 bytes Desc: not available URL: From 1517446 at bugs.launchpad.net Sun Feb 7 23:57:11 2016 From: 1517446 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Mon, 08 Feb 2016 04:57:11 -0000 Subject: [Bug 1517446] Re: Please add multipart/signed to DEFAULT_PASS_MIME_TYPES References: <20151118120903.17696.21099.malonedeb@gac.canonical.com> Message-ID: <20160208045713.13188.66920.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/1517446 Title: Please add multipart/signed to DEFAULT_PASS_MIME_TYPES To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1517446/+subscriptions From mark at msapiro.net Sun Feb 7 23:57:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 08 Feb 2016 04:57:40 -0000 Subject: [Bug 1517446] Re: Please add multipart/signed to DEFAULT_PASS_MIME_TYPES References: <20151118120903.17696.21099.malonedeb@gac.canonical.com> Message-ID: <20160208045741.24582.26915.launchpad@soybean.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/1517446 Title: Please add multipart/signed to DEFAULT_PASS_MIME_TYPES To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1517446/+subscriptions From berni at birkenwald.de Tue Feb 9 05:04:26 2016 From: berni at birkenwald.de (Bernhard Schmidt) Date: Tue, 09 Feb 2016 10:04:26 -0000 Subject: [Merge] lp:~berni/mailman/fix-typo2 into lp:mailman/2.1 Message-ID: <20160209100422.12631.22502.launchpad@ackee.canonical.com> Bernhard Schmidt has proposed merging lp:~berni/mailman/fix-typo2 into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~berni/mailman/fix-typo2/+merge/285451 Another update of German translations -- Your team Mailman Coders is requested to review the proposed merge of lp:~berni/mailman/fix-typo2 into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 1604 bytes Desc: not available URL: From berni at birkenwald.de Thu Feb 11 10:52:28 2016 From: berni at birkenwald.de (Bernhard Schmidt) Date: Thu, 11 Feb 2016 15:52:28 -0000 Subject: [Merge] lp:~berni/mailman/fix-typo3 into lp:mailman/2.1 Message-ID: <20160211155224.28292.55327.launchpad@ackee.canonical.com> Bernhard Schmidt has proposed merging lp:~berni/mailman/fix-typo3 into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~berni/mailman/fix-typo3/+merge/285763 Three minor updates on German translation -- Your team Mailman Coders is requested to review the proposed merge of lp:~berni/mailman/fix-typo3 into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 1400 bytes Desc: not available URL: From futatuki at poem.co.jp Fri Feb 12 01:20:41 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Fri, 12 Feb 2016 06:20:41 -0000 Subject: [Merge] lp:~futatuki/mailman/fix-typo-in-nondigest-help into lp:mailman/2.1 Message-ID: <20160212062037.20018.39730.launchpad@ackee.canonical.com> Yasuhito FUTATSUKI at POEM has proposed merging lp:~futatuki/mailman/fix-typo-in-nondigest-help into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~futatuki/mailman/fix-typo-in-nondigest-help/+merge/285829 I think 'regular_exclude_lists' in Mailman/Gui/NonDigest.py is a typo of 'regular_exclude_lists', so I try to make a fix. -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/fix-typo-in-nondigest-help into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 17455 bytes Desc: not available URL: From futatuki at poem.co.jp Fri Feb 12 04:13:22 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Fri, 12 Feb 2016 09:13:22 -0000 Subject: [Merge] lp:~futatuki/mailman/fix-typo-in-nondigest-help into lp:mailman/2.1 In-Reply-To: <20160212062037.20018.39730.launchpad@ackee.canonical.com> Message-ID: <20160212091321.24113.89415.codereview@chaenomeles.canonical.com> Oviously first occurrence of 'regular_exclude_lists' in above description sentence is a typo of 'regular_exlude_lists', auto spell correction system corrected unexpectedly.... -- https://code.launchpad.net/~futatuki/mailman/fix-typo-in-nondigest-help/+merge/285829 Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/fix-typo-in-nondigest-help into lp:mailman/2.1. From 1279980 at bugs.launchpad.net Sun Feb 14 15:22:24 2016 From: 1279980 at bugs.launchpad.net (J-K) Date: Sun, 14 Feb 2016 20:22:24 -0000 Subject: [Bug 1279980] Re: Some forms in list admin interfaces use absolute links in form action References: <20140213211429.1563.11659.malonedeb@gac.canonical.com> Message-ID: <20160214202224.22876.76935.malone@soybean.canonical.com> I have following problem: The list's host_name is example.org but the mailman pages (list-info, admin interface, archive) are located at http://www.example.com/mailman/ , example.com is the provider. The .htaccess for example.org contains: # without www -> with www RewriteCond %{HTTP_HOST} !^www\. RewriteRule ^/(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L] # mailman RewriteRule /mailman/(.*)$ http://www.example.com/mailman/$1 [R=301,NC,L] But still I'm not able to use the forms where the action URLs are absolute! I can't see why it could be problematic to have relative URLs by default. For example: At the moment the members can't access the private archive. This is annoying. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1279980 Title: Some forms in list admin interfaces use absolute links in form action To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1279980/+subscriptions From 1279980 at bugs.launchpad.net Sun Feb 14 16:57:49 2016 From: 1279980 at bugs.launchpad.net (J-K) Date: Sun, 14 Feb 2016 21:57:49 -0000 Subject: [Bug 1279980] Re: Some forms in list admin interfaces use absolute links in form action References: <20140213211429.1563.11659.malonedeb@gac.canonical.com> Message-ID: <20160214215749.676.65249.malone@gac.canonical.com> I just learned that the POST data is lost with a 301 redirect. You can use a 307 redirect but the user will get a warning about the redirection: https://programmers.stackexchange.com/a/99966 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1279980 Title: Some forms in list admin interfaces use absolute links in form action To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1279980/+subscriptions From mark at msapiro.net Sun Feb 14 19:33:31 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 15 Feb 2016 00:33:31 -0000 Subject: [Bug 1279980] Re: Some forms in list admin interfaces use absolute links in form action References: <20140213211429.1563.11659.malonedeb@gac.canonical.com> Message-ID: <20160215003331.24290.32786.malone@chaenomeles.canonical.com> It looks to me like your Mailman is not correctly configured. See the FAQ at . If your configuration is correct, any absolute form action URLs will not need redirection. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1279980 Title: Some forms in list admin interfaces use absolute links in form action To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1279980/+subscriptions From berni at birkenwald.de Mon Feb 15 08:01:33 2016 From: berni at birkenwald.de (Bernhard Schmidt) Date: Mon, 15 Feb 2016 13:01:33 -0000 Subject: [Merge] lp:~berni/mailman/fix-typo3 into lp:mailman/2.1 In-Reply-To: <20160211155224.28292.55327.launchpad@ackee.canonical.com> Message-ID: <20160215130130.9527.825.launchpad@ackee.canonical.com> The proposal to merge lp:~berni/mailman/fix-typo3 into lp:mailman/2.1 has been updated. Status: Needs review => Superseded For more details, see: https://code.launchpad.net/~berni/mailman/fix-typo3/+merge/285763 -- Your team Mailman Coders is requested to review the proposed merge of lp:~berni/mailman/fix-typo3 into lp:mailman/2.1. From berni at birkenwald.de Mon Feb 15 08:08:33 2016 From: berni at birkenwald.de (Bernhard Schmidt) Date: Mon, 15 Feb 2016 13:08:33 -0000 Subject: [Merge] lp:~berni/mailman/fix-typo5 into lp:mailman/2.1 Message-ID: <20160215130830.13710.11767.launchpad@ackee.canonical.com> Bernhard Schmidt has proposed merging lp:~berni/mailman/fix-typo5 into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~berni/mailman/fix-typo5/+merge/286056 Update German translation -- Your team Mailman Coders is requested to review the proposed merge of lp:~berni/mailman/fix-typo5 into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 1402 bytes Desc: not available URL: From mark at msapiro.net Wed Feb 17 13:20:38 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 17 Feb 2016 18:20:38 -0000 Subject: [Bug 1546679] [NEW] User's acknowlege option doesn't work on anonymous lists. Message-ID: <20160217182038.799.199.malonedeb@gac.canonical.com> Public bug reported: We actually save the original sender for Acknowledge.py in the message metadata as it passes through the pipeline, but we don't save it soon enough. ** 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/1546679 Title: User's acknowlege option doesn't work on anonymous lists. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1546679/+subscriptions From 1546679 at bugs.launchpad.net Wed Feb 17 13:43:52 2016 From: 1546679 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Wed, 17 Feb 2016 18:43:52 -0000 Subject: [Bug 1546679] Re: User's acknowlege option doesn't work on anonymous lists. References: <20160217182038.799.199.malonedeb@gac.canonical.com> Message-ID: <20160217184354.17673.38098.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/1546679 Title: User's acknowlege option doesn't work on anonymous lists. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1546679/+subscriptions From mark at msapiro.net Wed Feb 17 13:44:30 2016 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 17 Feb 2016 18:44:30 -0000 Subject: [Bug 1546679] Re: User's acknowlege option doesn't work on anonymous lists. References: <20160217182038.799.199.malonedeb@gac.canonical.com> Message-ID: <20160217184431.391.18809.launchpad@gac.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/1546679 Title: User's acknowlege option doesn't work on anonymous lists. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1546679/+subscriptions From futatuki at poem.co.jp Thu Feb 18 04:53:29 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Thu, 18 Feb 2016 09:53:29 -0000 Subject: [Merge] lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1 Message-ID: <20160218095325.19738.3382.launchpad@ackee.canonical.com> Yasuhito FUTATSUKI at POEM has proposed merging lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~futatuki/mailman/2.1-ja-translation/+merge/286473 This is tentative Japanese translation of messages. As there is no language master for Japanese after Mr. Kikuchi has gone, this translation is not reviewed by anyone yet. Note: mailman-users-jp at python.jp has stopped and moved to Google Groups, https://groups.google.com/forum/#!forum/mailman-users-jp , but I cannot attend it for my personal reason. So I changed E-Mail address of Language-Team: tag in mailman.po, but I don't contact with it. -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 33492 bytes Desc: not available URL: From noreply at launchpad.net Thu Feb 18 23:58:15 2016 From: noreply at launchpad.net (noreply at launchpad.net) Date: Fri, 19 Feb 2016 04:58:15 -0000 Subject: [Merge] lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1 In-Reply-To: <20160218095325.19738.3382.launchpad@ackee.canonical.com> Message-ID: <20160219045813.3194.27029.launchpad@ackee.canonical.com> The proposal to merge lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1 has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~futatuki/mailman/2.1-ja-translation/+merge/286473 -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/2.1-ja-translation into lp:mailman/2.1. From mark at msapiro.net Fri Feb 19 11:02:01 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 19 Feb 2016 16:02:01 -0000 Subject: [Bug 328353] Re: decoding unicode (still) not supported bug References: <20090212023754.4890.76025.malonedeb@potassium.ubuntu.com> Message-ID: <20160219160202.1515.86314.malone@soybean.canonical.com> Changing status back to Fix Released as the underlying issue is fixed in current releases of the Python email package. ** Changed in: mailman Status: In Progress => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/328353 Title: decoding unicode (still) not supported bug To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/328353/+subscriptions From mark at msapiro.net Fri Feb 19 16:00:40 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 19 Feb 2016 21:00:40 -0000 Subject: [Merge] lp:~msapiro/mailman/fix21tags into lp:mailman/2.1 Message-ID: <20160219210038.6665.46261.launchpad@ackee.canonical.com> Mark Sapiro has proposed merging lp:~msapiro/mailman/fix21tags into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~msapiro/mailman/fix21tags/+merge/286713 Try to remove tags introduced by prior merge. -- Your team Mailman Coders is requested to review the proposed merge of lp:~msapiro/mailman/fix21tags into lp:mailman/2.1. From futatuki at poem.co.jp Mon Feb 22 18:01:11 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Mon, 22 Feb 2016 23:01:11 -0000 Subject: [Bug 558167] Re: Use correct char set for command-line scripts References: <20100408090710.1687.25203.launchpad@loganberry.canonical.com> Message-ID: <20160222230111.1734.56181.malone@wampee.canonical.com> This bug still annoys Japanese users using ja_JP.UTF-8 locale on their terminals, using euc-jp as list charset. Fortunately, patch attached to comment #1 has been maintained on rpm sources for fedora/RHEL with additional patches, so I'm try to review them and working on a branch to follow latest 2.1 branch, lp:mailman/2.1-commandline-locale (merged these patches, fix for potfile making, but not tested yet). -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions From futatuki at poem.co.jp Mon Feb 22 18:59:03 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Mon, 22 Feb 2016 23:59:03 -0000 Subject: [Bug 558167] Re: Use correct char set for command-line scripts References: <20100408090710.1687.25203.launchpad@loganberry.canonical.com> Message-ID: <20160222235904.1813.78915.launchpad@soybean.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/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions From rob-launchpad.net at tigertech.com Wed Feb 24 13:06:12 2016 From: rob-launchpad.net at tigertech.com (Robert Mathews) Date: Wed, 24 Feb 2016 18:06:12 -0000 Subject: [Bug 1549420] [NEW] DMARC munging fails on subdomains that use parent domain policy Message-ID: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Public bug reported: An address ending with "@reply.yahoo.com" posted a message to a list that has "dmarc_moderation_action" set to "Munge From". This causes IsDMARCProhibited() in Utils.py to lookup TXT records for "_dmarc.reply.yahoo.com". It finds none, so Mailman does not apply the munging. However, in this situation, DMARC "clients" apparently need to look "up the chain" at "_dmarc.yahoo.com". See RFC 7489 section 4.3 point 7, and section 6.6.3 point 3 ("Organizational Domain"), and here's an example of it in action: https://dmarcian.com/dmarc-inspector/reply.yahoo.com The result of this bug is that mail from a subdomain like "@reply.yahoo.com" does not get munged, but does get rejected downstream by yahoo.com/gmail.com etc. for failing DMARC policy. (I'm using Mailman 2.1.20.) ** Affects: mailman Importance: Undecided Status: New ** Tags: dmarc -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From 1549420 at bugs.launchpad.net Thu Feb 25 02:24:52 2016 From: 1549420 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 25 Feb 2016 07:24:52 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160225072454.12299.94122.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/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From mark at msapiro.net Thu Feb 25 02:32:57 2016 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 25 Feb 2016 07:32:57 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160225073258.1867.68562.malone@chaenomeles.canonical.com> Thank you for your report. The fix I committed is something of a Kludge and will test more domains that just the From: domain and Organizational Domain as determining the Organizational Domain in general is a challenge, but hopefully it will produce the correct result in at least most cases. ** Changed in: mailman Importance: Undecided => High ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.21 ** 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/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From jimpop at gmail.com Thu Feb 25 10:25:42 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Thu, 25 Feb 2016 15:25:42 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160225152542.2258.93340.malone@soybean.canonical.com> The real problem is Yahoo not putting a DMARC record at _dmarc.reply.yahoo.com. 1) It would be ridiculous to implement code, which would need to be updated with every new TLD, to properly determine a parent domain. 2) Checking the parent domain really only applies when the signing is in relaxed mode, certainly not strict.... so that needs to be checked to. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From mark at msapiro.net Thu Feb 25 22:33:15 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Feb 2016 03:33:15 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160226033315.1816.56565.malone@wampee.canonical.com> RFC 7489 is pretty clear. Sec 6.6.2 gives the first 2 steps as: 1. Extract the RFC5322.From domain from the message (as above). 2. Query the DNS for a DMARC policy record. Continue if one is found, or terminate DMARC evaluation otherwise. See Section 6.6.3 for details. and 6.6.3 gives the first 3 steps as: 1. Mail Receivers MUST query the DNS for a DMARC TXT record at the DNS domain matching the one found in the RFC5322.From domain in the message. A possibly empty set of records is returned. 2. Records that do not start with a "v=" tag that identifies the current version of DMARC are discarded. 3. If the set is now empty, the Mail Receiver MUST query the DNS for a DMARC TXT record at the DNS domain matching the Organizational Domain in place of the RFC5322.From domain in the message (if different). This record can contain policy to be asserted for subdomains of the Organizational Domain. A possibly empty set of records is returned. I.e. If the From: domain doesn't have a valid DMARC policy record, you MUST query the Organizational Domain. All of this occurs before any DKIM and SPF checks which are steps 3 and 4 of the sec 6.6.2 procedure. I have refactored the fix to use the data from https://publicsuffix.org/list/public_suffix_list.dat and apply the algorithm described at https://publicsuffix.org/list/ to determine the organizational domain and to query that in cases where the From: domain has no DMARC record and the computed organizational domain is different. The refactored fix will read the data only once after Mailman is (re)started and build a dictionary kept in global memory to use in implementing the algorithm. See http://bazaar.launchpad.net/~mailman- coders/mailman/2.1/revision/1620 for the original fix and http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1621 for the refactoring. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From futatuki at poem.co.jp Fri Feb 26 05:04:29 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Fri, 26 Feb 2016 10:04:29 -0000 Subject: [Merge] lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1 Message-ID: <20160226100426.24897.16482.launchpad@ackee.canonical.com> Yasuhito FUTATSUKI at POEM has proposed merging lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~futatuki/mailman/2.1-commandline-locale/+merge/287282 This is a branch to fix bug #558167 . With this changes, command line utilities show messages as LC_CTYPE and LC_MESSAGES specified, if they have appropriate translation. -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 92255 bytes Desc: not available URL: From futatuki at poem.co.jp Fri Feb 26 04:56:26 2016 From: futatuki at poem.co.jp (Yasuhito FUTATSUKI at POEM) Date: Fri, 26 Feb 2016 09:56:26 -0000 Subject: [Bug 558167] Re: Use correct char set for command-line scripts References: <20100408090710.1687.25203.launchpad@loganberry.canonical.com> Message-ID: <20160226095626.1723.82456.malone@chaenomeles.canonical.com> I have tested for each commands under bin, with -h option on both of ja_JP.UTF-8 and ja_JP.eucJP terminal environment by using LC_CTYPE and LC_MESSAGES environment variables. It works fine. Some commands still outputs untranslated messages, bin/b4b5-archfix and bin/transcheck for example, but It is because those messages are not wrapped in _() or C_(). I'll send merge 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/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions From jimpop at gmail.com Fri Feb 26 10:31:43 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Fri, 26 Feb 2016 15:31:43 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160226153143.2009.90745.malone@gac.canonical.com> Nice stuff Mark. The thing that I don't see is that we must determine the Org policy on how to handle subdomains. If we don't find a policy at _dmarc.reply.yahoo.com, then we still need to parse _dmarc.yahoo.com to see if it can even be applied to a subdomain ("adkim", "aspf", and "sp" ). It's messy stuff. I firmly believe people crafted DMARC for job security. :-) -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From mark at msapiro.net Fri Feb 26 14:54:22 2016 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 26 Feb 2016 19:54:22 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160226195422.1707.28604.malone@gac.canonical.com> I think you are confusing two things: One is what DMARC policy if any to apply to a message and the other is how to determine whether a message passes DMARC. In our case, we want only to determine what if any DMARC policy will be applied, and the RFC says it's the policy of the From: domain if the From: domain has one and if not and the From: domain is a subdomain of an organizational domain, the organizational domain's policy if any applies. A recipient will then look at things like DKIM sigs and SPF and strict vs. relaxed alignment to determine if the message has a valid SPF or DKIM sig alligned with the From: domain, but we already know that we broke the incoming DKIM sig and it won't validate in any case or we wouldn't be applying DMARC mitigations. Thus, we need to know what if any DMARC policy will be applied in order to know whether to apply our mitigations. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From jimpop at gmail.com Fri Feb 26 18:33:25 2016 From: jimpop at gmail.com (Jim Popovitch) Date: Fri, 26 Feb 2016 23:33:25 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160226233325.2126.14656.malone@gac.canonical.com> Let's look at this from a different angle. Say a message arrives (admittedly from a poorly configured setup) as From: bob at vps1234.digitalocean.com do you use the DMARC policy defined at _dmarc.digitalocean.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/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From mark at msapiro.net Fri Feb 26 20:11:52 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 27 Feb 2016 01:11:52 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160227011152.1625.85682.malone@gac.canonical.com> Following RFC7489 sec 6.6.3, we first look up the TXT records at _dmarc.vps1234.digitalocean.com. That returns no record with v= the current DMARC version (actually none at all) so we then query _dmarc.digitalocean.com (the organizational domain in this case) and find a valid v=DMARC1 p=reject record, so if we are Mailman doing this to determine whether or not to apply dmarc_moderation_action, we do apply the action. If Mailman didn't apply dmarc_moderation_action and just processed the post, the ultimate receiver would get to the same point and determine the applicable DMARC policy is reject and then proceed with the DKIM and SPF checks to determine if the message passes DMARC. If we assume that the message didn't go via a list and instead went directly to the ultimate receiver, that receiver would determine the DMARC policy was reject in the same way. Then it would check DKIM and SPF. This is the first point at which adkim or aspf would be checked for strict/relaxed alignment between the From: domain and the DKIM signing or SPF domain. As Mailman we don't care about any of this because we aren't trying to validate DMARC on the incoming message, and we assume that DMARC won't validate against the outgoing message if we don't alter the From: domain because we aren't the From: domain for SPF and we transform the message in ways that break the DKIM sig, so all we want to know is what DMARC policy will be applied by the receiver. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From mark at msapiro.net Sat Feb 27 18:23:11 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 27 Feb 2016 23:23:11 -0000 Subject: [Bug 558167] Re: Use correct char set for command-line scripts References: <20100408090710.1687.25203.launchpad@loganberry.canonical.com> Message-ID: <20160227232312.32746.74584.launchpad@wampee.canonical.com> ** Changed in: mailman Importance: Undecided => Medium ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: None => 2.1.21 ** 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/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions From noreply at launchpad.net Sat Feb 27 18:22:39 2016 From: noreply at launchpad.net (noreply at launchpad.net) Date: Sat, 27 Feb 2016 23:22:39 -0000 Subject: [Merge] lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1 In-Reply-To: <20160226100426.24897.16482.launchpad@ackee.canonical.com> Message-ID: <20160227232237.9874.63582.launchpad@ackee.canonical.com> The proposal to merge lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1 has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~futatuki/mailman/2.1-commandline-locale/+merge/287282 -- Your team Mailman Coders is requested to review the proposed merge of lp:~futatuki/mailman/2.1-commandline-locale into lp:mailman/2.1. From mark at msapiro.net Sun Feb 28 16:12:55 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 28 Feb 2016 21:12:55 -0000 Subject: [Bug 1549420] Re: DMARC munging fails on subdomains that use parent domain policy References: <20160224180612.1853.11642.malonedeb@wampee.canonical.com> Message-ID: <20160228211257.2182.50192.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1549420 Title: DMARC munging fails on subdomains that use parent domain policy To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1549420/+subscriptions From mark at msapiro.net Sun Feb 28 16:13:29 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 28 Feb 2016 21:13:29 -0000 Subject: [Bug 1546679] Re: User's acknowlege option doesn't work on anonymous lists. References: <20160217182038.799.199.malonedeb@gac.canonical.com> Message-ID: <20160228211330.1686.12973.launchpad@chaenomeles.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1546679 Title: User's acknowlege option doesn't work on anonymous lists. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1546679/+subscriptions From mark at msapiro.net Sun Feb 28 16:13:41 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 28 Feb 2016 21:13:41 -0000 Subject: [Bug 1517446] Re: Please add multipart/signed to DEFAULT_PASS_MIME_TYPES References: <20151118120903.17696.21099.malonedeb@gac.canonical.com> Message-ID: <20160228211343.32746.94177.launchpad@wampee.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1517446 Title: Please add multipart/signed to DEFAULT_PASS_MIME_TYPES To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1517446/+subscriptions From mark at msapiro.net Sun Feb 28 16:13:12 2016 From: mark at msapiro.net (Mark Sapiro) Date: Sun, 28 Feb 2016 21:13:12 -0000 Subject: [Bug 558167] Re: Use correct char set for command-line scripts References: <20100408090710.1687.25203.launchpad@loganberry.canonical.com> Message-ID: <20160228211313.2050.58086.launchpad@gac.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/558167 Title: Use correct char set for command-line scripts To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/558167/+subscriptions From mark at msapiro.net Mon Feb 29 00:01:53 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 29 Feb 2016 05:01:53 -0000 Subject: [Bug 1551075] [NEW] Content filtering breaks some PGP Mime signed messages. Message-ID: <20160229050154.1894.56042.malonedeb@wampee.canonical.com> Public bug reported: In some cases it is inevitable that Mailman's content filtering will break a PGP MIME signature. I.e., if content filtering removes signed content, the signature will be broken. For example, assume an original message is multipart/alternative and it is then wrapped in a multipart/signed outer message along with a signature part. If content filtering collapses alternatives, the signature will be broken. Likewise, if the original has an attached image/png part or any MIME type part which content filtering removes, the signature will be broken. These are inevitable results of content filtering, and content filtering should override signature preservation or people could avoid having their content filtered just by signing their posts. There is however a situation that has developed where signature breaking can be avoided. The latest (at the time of writing) versions of enigmail will sign a message in the following way. Assume the original unsigned message is just text/plain. It could be more complex, but the following still holds. The text/plain (or whatever) message is first recast as multipart mixed like: Content-Type: multipart/mixed; boundary="bbbbbb" From: (Original from) To: (Original to) Message-ID: (original message-id) Subject: (original subject) --bbbbbb Content-Type: (original message's content-type) Content-Transfer-Encoding: (original message's content-transfer-encoding) (remainder of original message) --bbbbbb-- Then the signed message is created with structure multipart/signed multipart/mixed text/plain (or whatever the original was) (original message) application/pgp-signature (signature of the multipart/mixed part) The problem is Mailman has logic to detect multipart parts with only one sub-part and collapse them to just the sub-part, so in this case, even though content filtering doesn't remove anything, it still collapses the above to multipart/signed text/plain (or whatever the original was) (original message) application/pgp-signature (signature of the multipart/mixed part) and the signature is no longer valid. This can be fixed by short- circuiting the "collapse multipart parts with only one sub-part" logic when encountering a multipart/signed part and not collapsing anything below it. ** 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/1551075 Title: Content filtering breaks some PGP Mime signed messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1551075/+subscriptions From 1551075 at bugs.launchpad.net Mon Feb 29 01:29:30 2016 From: 1551075 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Mon, 29 Feb 2016 06:29:30 -0000 Subject: [Bug 1551075] Re: Content filtering breaks some PGP Mime signed messages. References: <20160229050154.1894.56042.malonedeb@wampee.canonical.com> Message-ID: <20160229062930.22584.45842.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/1551075 Title: Content filtering breaks some PGP Mime signed messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1551075/+subscriptions From mark at msapiro.net Mon Feb 29 01:36:14 2016 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 29 Feb 2016 06:36:14 -0000 Subject: [Bug 1551075] Re: Content filtering breaks some PGP Mime signed messages. References: <20160229050154.1894.56042.malonedeb@wampee.canonical.com> Message-ID: <20160229063615.2202.46481.launchpad@wampee.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/1551075 Title: Content filtering breaks some PGP Mime signed messages. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1551075/+subscriptions From kmit.medhach at gmail.com Mon Feb 29 23:31:33 2016 From: kmit.medhach at gmail.com (Medha Ch) Date: Tue, 01 Mar 2016 04:31:33 -0000 Subject: [Bug 1450469] Re: install step using buildout fails with os.path.walk error References: <20150430130749.14355.38917.malonedeb@chaenomeles.canonical.com> Message-ID: <20160301043133.1847.60091.malone@gac.canonical.com> I am facing the same issue. How do I solve it? -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman suite bundler. https://bugs.launchpad.net/bugs/1450469 Title: install step using buildout fails with os.path.walk error To manage notifications about this bug go to: https://bugs.launchpad.net/mailman-bundler/+bug/1450469/+subscriptions From mark at msapiro.net Mon Feb 29 23:49:55 2016 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 01 Mar 2016 04:49:55 -0000 Subject: [Bug 1450469] Re: install step using buildout fails with os.path.walk error References: <20150430130749.14355.38917.malonedeb@chaenomeles.canonical.com> Message-ID: <20160301044955.1925.64408.malone@gac.canonical.com> This project has moved to . Please look there for the latest info and file an issue there if necessary. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman suite bundler. https://bugs.launchpad.net/bugs/1450469 Title: install step using buildout fails with os.path.walk error To manage notifications about this bug go to: https://bugs.launchpad.net/mailman-bundler/+bug/1450469/+subscriptions