From hostingnuggets at gmail.com Fri Aug 1 15:19:01 2014 From: hostingnuggets at gmail.com (John Naggets) Date: Fri, 01 Aug 2014 13:19:01 -0000 Subject: [Bug 1351312] [NEW] Message acceptance options not working References: <20140801131901.23605.9540.malonedeb@wampee.canonical.com> Message-ID: <20140801131901.23605.9540.malonedeb@wampee.canonical.com> Public bug reported: I am testing the two following list config parameters: default_nonmember_action default_member_action and actually the following options do not work: Reject (with notification) and Discard (no notification) It looks like currently only the hold for moderator and accept options are working. Is it possible that these two are not ready yet in the beta4 version of mailman? Furthermore the approval mail to the moderator contains in its body as reason XXX: Reason: XXX I guess this also needs adapting. ** Affects: mailman Importance: Undecided Status: New ** Tags: mailman3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1351312 Title: Message acceptance options not working To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1351312/+subscriptions From mark at msapiro.net Fri Aug 8 21:26:14 2014 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 08 Aug 2014 19:26:14 -0000 Subject: [Bug 1350280] Re: Bug in Mailman version 2.1.18-1 References: <20140730105130.5017.91378.malonedeb@gac.canonical.com> Message-ID: <20140808192614.23603.68863.malone@wampee.canonical.com> It appears that the file /usr/local/cpanel/3rdparty/mailman/lists//requests.pck is corrupt. You can see what's in it with /usr/local/cpanel/3rdparty/mailman/bin/dumpdb. If you just remove the requests.pck file, I think that will solve the problem, but first use dumpdb to see if there are any real requests. ** Changed in: mailman Status: New => Incomplete ** 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/1350280 Title: Bug in Mailman version 2.1.18-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1350280/+subscriptions From 1263247 at bugs.launchpad.net Sat Aug 9 03:34:17 2014 From: 1263247 at bugs.launchpad.net (Barry Warsaw) Date: Sat, 09 Aug 2014 01:34:17 -0000 Subject: [Bug 1263247] Re: Bounce warnings from kundenserver.de are not recognized References: <20131220230719.6767.81908.malonedeb@gac.canonical.com> Message-ID: <20140809013419.17882.34270.launchpad@soybean.canonical.com> ** Changed in: flufl.bounce Milestone: None => 2.3 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1263247 Title: Bounce warnings from kundenserver.de are not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/1263247/+subscriptions From barry at canonical.com Fri Aug 15 02:08:25 2014 From: barry at canonical.com (Barry Warsaw) Date: Fri, 15 Aug 2014 00:08:25 -0000 Subject: [Merge] lp:~barry/mailman/falcon into lp:mailman Message-ID: <20140815000824.27633.40160.launchpad@ackee.canonical.com> Barry Warsaw has proposed merging lp:~barry/mailman/falcon into lp:mailman. Requested reviews: Mailman Coders (mailman-coders) For more details, see: https://code.launchpad.net/~barry/mailman/falcon/+merge/230913 Port from restish to falcon for the REST API framework. This currently depends on an unmerged falcon pull request: https://github.com/racker/falcon/pull/307 -- https://code.launchpad.net/~barry/mailman/falcon/+merge/230913 Your team Mailman Coders is requested to review the proposed merge of lp:~barry/mailman/falcon into lp:mailman. -------------- next part -------------- A non-text attachment was scrubbed... Name: review-diff.txt Type: text/x-diff Size: 106878 bytes Desc: not available URL: From 1263247 at bugs.launchpad.net Mon Aug 18 16:59:05 2014 From: 1263247 at bugs.launchpad.net (Barry Warsaw) Date: Mon, 18 Aug 2014 14:59:05 -0000 Subject: [Bug 1263247] Re: Bounce warnings from kundenserver.de are not recognized References: <20131220230719.6767.81908.malonedeb@gac.canonical.com> Message-ID: <20140818145906.4835.84982.launchpad@gac.canonical.com> ** Changed in: flufl.bounce 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/1263247 Title: Bounce warnings from kundenserver.de are not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/flufl.bounce/+bug/1263247/+subscriptions From 266873 at bugs.launchpad.net Wed Aug 20 05:13:50 2014 From: 266873 at bugs.launchpad.net (mc0e) Date: Wed, 20 Aug 2014 03:13:50 -0000 Subject: [Bug 266873] Re: Patch to help report spam in moderator queue References: <20080905194314.1806.82556.launchpad@forster.canonical.com> Message-ID: <20140820031350.12623.83421.malone@wampee.canonical.com> I think something like this would be a very useful feature, but it would be better to have an action which identifies emails as spam, and passes them to a configured handler on the server. Besides reporting to spamcop et. al., it'd be useful to be able to use the moderator actions to train a local bayesian filter. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266873 Title: Patch to help report spam in moderator queue To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266873/+subscriptions From 1360616 at bugs.launchpad.net Sat Aug 23 16:43:01 2014 From: 1360616 at bugs.launchpad.net (Thomas Klausner) Date: Sat, 23 Aug 2014 14:43:01 -0000 Subject: [Bug 1360616] [NEW] mailman: case-sensitivity issue in tarball for 2.18.1-1 References: <20140823144301.13360.92997.malonedeb@wampee.canonical.com> Message-ID: <20140823144301.13360.92997.malonedeb@wampee.canonical.com> Public bug reported: The tarball contains readme.sr, but the installation scripts check for the existence of README.sr. This test works on case-insensitive file systems but not on case-sensitive ones. Please rename it to README.sr so the behaviour is the same across file systems. ** 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/1360616 Title: mailman: case-sensitivity issue in tarball for 2.18.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1360616/+subscriptions From ij at perlpimp.net Sat Aug 30 00:09:57 2014 From: ij at perlpimp.net (Ian Johannesen) Date: Fri, 29 Aug 2014 22:09:57 -0000 Subject: [Bug 1363278] [NEW] REMOVE_DKIM_HEADERS value 2 not reacted to References: <20140829220957.29423.4344.malonedeb@gac.canonical.com> Message-ID: <20140829220957.29423.4344.malonedeb@gac.canonical.com> Public bug reported: When using the value 2 for REMOVE_DKIM_HEADERS in mm_cfg - it does not respond to it at all. After doing through the code, I've noticed that quite simply someone forgot to add this to the code itself. I've attached a patch for this, as I needed to remove ALL DKIM headers for all my lists. ** Affects: mailman Importance: Undecided Status: New ** Patch added: "mailman-2.1.18-1.allowdkimalwaysremove.patch" https://bugs.launchpad.net/bugs/1363278/+attachment/4190499/+files/mailman-2.1.18-1.allowdkimalwaysremove.patch -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1363278 Title: REMOVE_DKIM_HEADERS value 2 not reacted to To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1363278/+subscriptions