From follybeachris at hotmail.com Fri May 2 22:43:26 2014 From: follybeachris at hotmail.com (Chris Cargile) Date: Fri, 02 May 2014 20:43:26 -0000 Subject: [Bug 265848] Re: Tiny mistake on the remove a list webpage References: <20080905192628.27052.84289.launchpad@forster.canonical.com> Message-ID: <20140502204327.18888.50053.launchpad@chaenomeles.canonical.com> ** Branch linked: lp:~follybeachris/mailman/mailman2-stable-265848 -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/265848 Title: Tiny mistake on the remove a list webpage To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265848/+subscriptions From 265848 at bugs.launchpad.net Sat May 3 06:55:52 2014 From: 265848 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Sat, 03 May 2014 04:55:52 -0000 Subject: [Bug 265848] Re: Tiny mistake on the remove a list webpage References: <20080905192628.27052.84289.launchpad@forster.canonical.com> Message-ID: <20140503045555.29325.29887.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/265848 Title: Tiny mistake on the remove a list webpage To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265848/+subscriptions From mark at msapiro.net Sat May 3 06:56:35 2014 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 03 May 2014 04:56:35 -0000 Subject: [Bug 265848] Re: Tiny mistake on the remove a list webpage References: <20080905192628.27052.84289.launchpad@forster.canonical.com> Message-ID: <20140503045636.31275.45211.launchpad@soybean.canonical.com> ** Changed in: mailman Status: New => Fix Committed ** Changed in: mailman Milestone: 2.1-stable => 2.1.18 ** 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/265848 Title: Tiny mistake on the remove a list webpage To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265848/+subscriptions From mark at msapiro.net Sat May 3 20:13:11 2014 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 03 May 2014 18:13:11 -0000 Subject: [Bug 1313146] Re: Precedence header differs between moderation and list emails References: <20140426171242.18470.38786.malonedeb@chaenomeles.canonical.com> Message-ID: <20140503181313.27069.73108.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/1313146 Title: Precedence header differs between moderation and list emails To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1313146/+subscriptions From mark at msapiro.net Sat May 3 20:12:50 2014 From: mark at msapiro.net (Mark Sapiro) Date: Sat, 03 May 2014 18:12:50 -0000 Subject: [Bug 265848] Re: Tiny mistake on the remove a list webpage References: <20080905192628.27052.84289.launchpad@forster.canonical.com> Message-ID: <20140503181252.24565.91311.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/265848 Title: Tiny mistake on the remove a list webpage To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/265848/+subscriptions From mark at msapiro.net Mon May 5 02:58:25 2014 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 05 May 2014 00:58:25 -0000 Subject: [Bug 1315970] [NEW] The DMARC Munge From action inconsistently removes the original Sender: header. References: <20140505005825.18692.99726.malonedeb@chaenomeles.canonical.com> Message-ID: <20140505005825.18692.99726.malonedeb@chaenomeles.canonical.com> Public bug reported: If from_is_list is Munge From, the original Sender: header is removed from the message, but it is not removed for a dmarc_moderation_action of Munge From. In most cases, it doesn't matter because SMTPDirect replaces it with the bounces address anyway, but if include_sender_header is false, any existing Sender: is left in the message. There is no reason to remove it as it doesn't affect DMARC decisions which are based solely on From: ** 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/1315970 Title: The DMARC Munge From action inconsistently removes the original Sender: header. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1315970/+subscriptions From 1315970 at bugs.launchpad.net Mon May 5 04:49:50 2014 From: 1315970 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Mon, 05 May 2014 02:49:50 -0000 Subject: [Bug 1315970] Re: The DMARC Munge From action inconsistently removes the original Sender: header. References: <20140505005825.18692.99726.malonedeb@chaenomeles.canonical.com> Message-ID: <20140505024955.16613.89178.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/1315970 Title: The DMARC Munge From action inconsistently removes the original Sender: header. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1315970/+subscriptions From mark at msapiro.net Mon May 5 04:50:09 2014 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 05 May 2014 02:50:09 -0000 Subject: [Bug 1315970] Re: The DMARC Munge From action inconsistently removes the original Sender: header. References: <20140505005825.18692.99726.malonedeb@chaenomeles.canonical.com> Message-ID: <20140505025012.23529.76059.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/1315970 Title: The DMARC Munge From action inconsistently removes the original Sender: header. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1315970/+subscriptions From 266836 at bugs.launchpad.net Mon May 5 12:58:21 2014 From: 266836 at bugs.launchpad.net (Jasper) Date: Mon, 05 May 2014 10:58:21 -0000 Subject: [Bug 266836] Re: support openid / yadis References: <20080905194301.1806.97508.launchpad@forster.canonical.com> Message-ID: <20140505105821.24565.98204.malone@wampee.canonical.com> The yadis.org domain has expired and been taken over by a squatter. This might be a better choice for OpenID: https://github.com/jezdez/django-openid-auth But it looks like maintenance has drifted and we'd need to work out which github fork is the most up-to-date. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/266836 Title: support openid / yadis To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/266836/+subscriptions From tim.marx at xrammit.de Mon May 5 22:22:57 2014 From: tim.marx at xrammit.de (Tim Marx) Date: Mon, 05 May 2014 22:22:57 +0200 Subject: [Mailman-Developers] [Bug 1130957] Re: Unicode errors in mailman3 In-Reply-To: <20140430175340.277d4238@anarchist.wooz.org> References: <20130220231858.9018.27307.malonedeb@gac.canonical.com> <20140430213828.4471.26296.malone@soybean.canonical.com> <20140430175340.277d4238@anarchist.wooz.org> Message-ID: <5367F321.7030702@xrammit.de> Am 30.04.2014 23:53, schrieb Barry Warsaw: > On Apr 30, 2014, at 09:38 PM, Tim Marx wrote: > >> I'm using mailman 3.0.0b4 (with mailman-bundler) and ran into the same >> problem as described above. Luckily I found this bug report and could manage >> to fix it with the patches above. >> >> May I ask anybody (with more bazar-knowledge than me) to merge this two >> patches into the mailman 3 branch? Thank you! > I think we just need some test cases. Tim, can you provide any details on how > you it the bug? I had exactly the same stacktraces and error messages as Aur?lien described in his bug report. They appeared after I had sent mails from list-member email adresses to my mailing list server. I have used 'normal' email addresses without any special characters. I'm sorry if I could not really help you with this! > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers at python.org > https://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/tim%40xrammit.de > > Security Policy: http://wiki.list.org/x/QIA9 > From mark at msapiro.net Tue May 6 18:25:02 2014 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 06 May 2014 16:25:02 -0000 Subject: [Bug 1316682] [NEW] The DMARC Wrap Message action is incompatible with some older Python email libraries. References: <20140506162502.23765.81621.malonedeb@wampee.canonical.com> Message-ID: <20140506162502.23765.81621.malonedeb@wampee.canonical.com> Public bug reported: There is a bug in Python's email package (See ) which is fixed in recent versions, but which causes Mailman's OutgoingRunner process to throw a "TypeError: Expected list, got " exception on outgoing messages wrapped by the DMARC Wrap Message action. This bug does not exist in Python 2.6.5 and later. It does exist in all Python 2.5.x and earlier. It is not known to me in which Python 2.6.x (x <= 5) it was fixed. It will cause any outgoing individual messages to which the DMARC Wrap Message action was applied to be shunted and not delivered. ** Affects: mailman Importance: Critical 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/1316682 Title: The DMARC Wrap Message action is incompatible with some older Python email libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1316682/+subscriptions From 1316682 at bugs.launchpad.net Tue May 6 18:42:04 2014 From: 1316682 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Tue, 06 May 2014 16:42:04 -0000 Subject: [Bug 1316682] Re: The DMARC Wrap Message action is incompatible with some older Python email libraries. References: <20140506162502.23765.81621.malonedeb@wampee.canonical.com> Message-ID: <20140506164207.29547.21330.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/1316682 Title: The DMARC Wrap Message action is incompatible with some older Python email libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1316682/+subscriptions From mark at msapiro.net Tue May 6 19:25:16 2014 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 06 May 2014 17:25:16 -0000 Subject: [Bug 1316682] Re: The DMARC Wrap Message action is incompatible with some older Python email libraries. References: <20140506162502.23765.81621.malonedeb@wampee.canonical.com> Message-ID: <20140506172518.21727.90568.launchpad@chaenomeles.canonical.com> ** 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/1316682 Title: The DMARC Wrap Message action is incompatible with some older Python email libraries. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1316682/+subscriptions From mark at msapiro.net Tue May 6 19:26:31 2014 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 06 May 2014 17:26:31 -0000 Subject: [Bug 1315970] Re: The DMARC Munge From action inconsistently removes the original Sender: header. References: <20140505005825.18692.99726.malonedeb@chaenomeles.canonical.com> Message-ID: <20140506172633.22448.58100.launchpad@soybean.canonical.com> ** Changed in: mailman Status: Fix Committed => Fix Released ** Changed in: mailman Milestone: 2.1.19 => 2.1.18-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/1315970 Title: The DMARC Munge From action inconsistently removes the original Sender: header. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1315970/+subscriptions From kaie at kuix.de Wed May 7 21:03:54 2014 From: kaie at kuix.de (Kai Engert) Date: Wed, 07 May 2014 19:03:54 -0000 Subject: [Bug 1317239] [NEW] branch 2.1-pgp-smime: exception, undefined sigfilename References: <20140507190354.20430.64257.malonedeb@gac.canonical.com> Message-ID: <20140507190354.20430.64257.malonedeb@gac.canonical.com> Public bug reported: This bug report is specific to branch https://code.launchpad.net/~joostvb/mailman/2.1-pgp-smime When receiving certain messages, python throws this exception: Uncaught runner exception: local variable 'sigfilename' referenced before assignment Traceback (most recent call last): File "/usr/local/mmcrypto/Mailman/Queue/Runner.py", line 119, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mmcrypto/Mailman/Queue/Runner.py", line 190, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mmcrypto/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mmcrypto/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mmcrypto/Mailman/Handlers/Moderate.py", line 318, in process key_ids.extend(gh.verifyMessage(payload, signature)) File "/usr/local/mmcrypto/Mailman/GPGUtils.py", line 374, in verifyMessage if sigfilename: UnboundLocalError: local variable 'sigfilename' referenced before assignment I'll propose a patch to avoid the exception. ** Affects: mailman Importance: Undecided Status: New ** Attachment added: "ensure sigfilename is defined" https://bugs.launchpad.net/bugs/1317239/+attachment/4107527/+files/gpg-smime-sigfilename.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/1317239 Title: branch 2.1-pgp-smime: exception, undefined sigfilename To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1317239/+subscriptions From kaie at kuix.de Thu May 8 00:42:43 2014 From: kaie at kuix.de (Kai Engert) Date: Wed, 07 May 2014 22:42:43 -0000 Subject: [Bug 1317239] Re: branch 2.1-pgp-smime: exception, undefined sigfilename References: <20140507190354.20430.64257.malonedeb@gac.canonical.com> Message-ID: <20140507224243.20923.25623.malone@gac.canonical.com> ** Patch removed: "ensure sigfilename is defined" https://bugs.launchpad.net/mailman/+bug/1317239/+attachment/4107527/+files/gpg-smime-sigfilename.patch ** Patch added: "ensure sigfilename is defined v2" https://bugs.launchpad.net/mailman/+bug/1317239/+attachment/4107620/+files/gpg-smime-sigfilename.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/1317239 Title: branch 2.1-pgp-smime: exception, undefined sigfilename To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1317239/+subscriptions From mark at msapiro.net Fri May 9 21:13:12 2014 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 09 May 2014 19:13:12 -0000 Subject: [Bug 1318025] [NEW] The DMARC mitigatation actions do not include a Reply-To: header in rare cases. References: <20140509191312.20684.26625.malonedeb@gac.canonical.com> Message-ID: <20140509191312.20684.26625.malonedeb@gac.canonical.com> Public bug reported: If the incoming message contains no From: header or it's From: header can't be parsed into a display name and email address, the DMARC mitigation actions that try to put the From: address in Reply-To: fail to do so. In these cases and also in the non-compliant case where there are multiple From: addresses, just take the sender address from Mailman's get_sender() message method and use that in liu of the From address. ** 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/1318025 Title: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1318025/+subscriptions From mark at msapiro.net Fri May 9 21:22:14 2014 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 09 May 2014 19:22:14 -0000 Subject: [Bug 1318025] Re: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. References: <20140509191312.20684.26625.malonedeb@gac.canonical.com> Message-ID: <20140509192214.21821.69387.launchpad@chaenomeles.canonical.com> ** Description changed: If the incoming message contains no From: header or it's From: header can't be parsed into a display name and email address, the DMARC mitigation actions that try to put the From: address in Reply-To: fail to do so. In these cases and also in the non-compliant case where there are multiple From: addresses, just take the sender address from Mailman's - get_sender() message method and use that in liu of the From address. + get_sender() message method and use that in lieu of the From address. -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1318025 Title: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1318025/+subscriptions From 1318025 at bugs.launchpad.net Fri May 9 21:22:48 2014 From: 1318025 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 09 May 2014 19:22:48 -0000 Subject: [Bug 1318025] Re: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. References: <20140509191312.20684.26625.malonedeb@gac.canonical.com> Message-ID: <20140509192250.10223.82328.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/1318025 Title: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1318025/+subscriptions From mark at msapiro.net Fri May 9 21:22:59 2014 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 09 May 2014 19:22:59 -0000 Subject: [Bug 1318025] Re: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. References: <20140509191312.20684.26625.malonedeb@gac.canonical.com> Message-ID: <20140509192300.20616.68833.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/1318025 Title: The DMARC mitigatation actions do not include a Reply-To: header in rare cases. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1318025/+subscriptions From dave.launchpad at nathanson.org Sun May 11 06:49:49 2014 From: dave.launchpad at nathanson.org (Dave Nathanson) Date: Sun, 11 May 2014 04:49:49 -0000 Subject: [Bug 1318283] [NEW] From Munge - Adjustment Options References: <20140511044949.22007.35342.malonedeb@soybean.canonical.com> Message-ID: <20140511044949.22007.35342.malonedeb@soybean.canonical.com> Public bug reported: FEATURE REQUEST: A setting to configure the new "From" line. Instead of FROM: Author_Name via ListName I want to request that MailMan let the list admin config the text after the author's name in the FROM line. I would use this setting to say: FROM: Author_Name via Club Name * substituted test string "Club Name" for "List Name" * substituted explicit reply_to_address instead of list address. More details: My email lists are served from a sub-domain that I don't use for anything except lists. lists.example.com That is a given, not my option. I have things figured out as well as can be for my situation. The settings we are going to use are: reply_goes_to_list = Explicit address reply_to_address = everybody at example.com (as opposed to everybody at lists.example.com ) from_is_list = Mung From first_strip_reply_to = Yes The only difference is from_is_list = Mung From. The other settings are the same as before DEMARC. Differences before & After DEMARC BEFORE: FROM: Author_Name TO: ListName REPLY-TO: ListName We liked it like that. Everything was fine. AFTER DEMARC, using the best settings for us that we can (Mailman 2.1.17) : FROM: Author_Name via ListName TO: ListName REPLY-TO: ListName This is *pretty good* except that * I don't like the "via list name" in the from header, even though I understand that is the new reality. * I don't like the lack of an author email address. I also tried: first_strip_reply_to = No But that means a normal reply will go to both the list & the author. So the author will get 2 copies, and I don't feel that is desirable, even though it seems to be the only way to include the author's email address. FEATURE REQUEST: A setting to control the new "From" line. Instead of FROM: Author_Name via ListName I want to request that it offer the option to let the list admin config what goes there after the author's name. I would use this setting to say: FROM: Author_Name via Club Name substituted "Club Name" for "List Name", and used explicit reply_to_address instead of list address. Thanks, Dave Nathanson Mac Medix ** Affects: mailman Importance: Undecided Status: New ** Tags: munge -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1318283 Title: From Munge - Adjustment Options To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1318283/+subscriptions From question249403 at answers.launchpad.net Wed May 28 10:21:54 2014 From: question249403 at answers.launchpad.net (Adam) Date: Wed, 28 May 2014 08:21:54 -0000 Subject: [Question #249403]: Mailman Archive does NOT work Message-ID: <20140528082154.26875.55609.launchpad@loganberry.canonical.com> Question #249403 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/249403 Summary changed to: Mailman Archive does NOT work -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu. From question249403 at answers.launchpad.net Wed May 28 10:21:51 2014 From: question249403 at answers.launchpad.net (Adam) Date: Wed, 28 May 2014 08:21:51 -0000 Subject: [Question #249403]: Archive does NOT work Message-ID: <20140528082151.26875.31233.launchpad@loganberry.canonical.com> New question #249403 on mailman in Ubuntu: https://answers.launchpad.net/ubuntu/+source/mailman/+question/249403 Numerous messages have been posted to my mailing list in the past few weeks, and I've configured it to archive messages. Below are my configurations in the Archive Option. Archive messages? - Yes Is archive file source for public or private archival? - public How often should a new archive volume be started? - Monthly But none has been archived so far, whenever I go to List Archives, it displays the following message: No messages have been posted to this list yet, so the archives are currently empty. You can get more information about this list. FYI: I do see the Administrative requests however. Thanks in advance! -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu. From question249403 at answers.launchpad.net Wed May 28 11:07:30 2014 From: question249403 at answers.launchpad.net (=?utf-8?q?Thomas_Kr=C3=BCger?=) Date: Wed, 28 May 2014 09:07:30 -0000 Subject: [Question #249403]: Mailman Archive does NOT work Message-ID: <20140528090730.18036.34153.launchpad@loganberry.canonical.com> Question #249403 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/249403 Status: Open => Answered Thomas Kr?ger proposed the following answer: Mailman is rather sensible to permission problems. Make sure it has the proper rights to write to the archive folder and all the files inside. Also check for "IOError" in the logs. -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu. From question249403 at answers.launchpad.net Wed May 28 16:26:20 2014 From: question249403 at answers.launchpad.net (Mark Sapiro) Date: Wed, 28 May 2014 14:26:20 -0000 Subject: [Question #249403]: Mailman Archive does NOT work References: <20140528090606.10096.50580.lpquestions@gac.canonical.com> Message-ID: <20140528142620.3045.95018.launchpad@loganberry.canonical.com> Question #249403 on mailman in Ubuntu changed: https://answers.launchpad.net/ubuntu/+source/mailman/+question/249403 Mark Sapiro proposed the following answer: Yes, check Mailman's error log, and run Mailman's bin/check_perms. Also, the actual archive is always in Mailman's archives/private/LISTNAME/ directory and archives/public/LISTNAME should be a symlink to archives/private/LISTNAME/. if archives/public/LISTNAME is an actual directory with and index.html file and possibly others, it can cause this. If you go to the archive via a URL like http://example.com/mailman/private/LISTNAME, and log in and see the archived messages, this is the problem. If this is the issue, you can fix it by removing the archives/public/LISTNAME directory and letting Mailman recreate the symlink. If you don't have access to do that, you could try switching the archive to private and then back to public which may or may not help. If not, you'll have to work with the server admins. -- You received this question notification because you are a member of Mailman Coders, which is an answer contact for mailman in Ubuntu. From mark at msapiro.net Thu May 29 15:37:23 2014 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 29 May 2014 13:37:23 -0000 Subject: [Bug 1324541] [NEW] If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. References: <20140529133723.16293.64139.malonedeb@chaenomeles.canonical.com> Message-ID: <20140529133723.16293.64139.malonedeb@chaenomeles.canonical.com> Public bug reported: dmarc_moderation_action other than accept relies on DNS lookups via the dnspython package to check DMARC policy of the From: domain, but if the package is not available, the check silently returns no DMARC policy. It should at least log the fact that the package isn't there. ** Affects: mailman Importance: High Assignee: Mark Sapiro (msapiro) Status: In Progress -- You received this bug notification because you are a member of Mailman Coders, which is subscribed to GNU Mailman. https://bugs.launchpad.net/bugs/1324541 Title: If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1324541/+subscriptions From 1324541 at bugs.launchpad.net Thu May 29 16:16:04 2014 From: 1324541 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Thu, 29 May 2014 14:16:04 -0000 Subject: [Bug 1324541] Re: If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. References: <20140529133723.16293.64139.malonedeb@chaenomeles.canonical.com> Message-ID: <20140529141606.8172.17090.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/1324541 Title: If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1324541/+subscriptions From mark at msapiro.net Thu May 29 16:38:05 2014 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 29 May 2014 14:38:05 -0000 Subject: [Bug 1324541] Re: If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. References: <20140529133723.16293.64139.malonedeb@chaenomeles.canonical.com> Message-ID: <20140529143805.563.4417.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/1324541 Title: If the dnspython package is not available and dmarc_moderation_action is not accept, nothing is logged. To manage notifications about this bug go to: https://bugs.launchpad.net/mailman/+bug/1324541/+subscriptions