From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cgf.cx (external.cgf.cx [107.170.62.102]) by sourceware.org (Postfix) with ESMTP id 88377385DC02 for ; Fri, 3 Apr 2020 20:52:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 88377385DC02 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx 5DAFD407DF X-Spam-Level: X-Spam-CGF-Status: No, score=-6.7 required=5.0 tests=ALL_TRUSTED,BAYES_00, TXREP autolearn=ham autolearn_force=no version=3.4.4 spammy=Messages, H*r:unknown, turned, ready Received: by cgf.cx (sSMTP sendmail emulation); Fri, 03 Apr 2020 16:52:54 -0400 Date: Fri, 3 Apr 2020 16:52:54 -0400 From: Christopher Faylor To: Overseers mailing list Subject: Re: mailman customization not quite right yet Message-ID: <20200403205254.GA12086@cgf.cx> Mail-Followup-To: Overseers mailing list References: <3f4869fd-d852-a8a6-117f-e767a417ff95@codesourcery.com> <8d833f8d-243f-e8b8-69ed-124ef33b7746@codesourcery.com> <20200309102520.GQ2156@tucnak> <69bd8396-1e11-6b87-18f2-658fd171ebc2@suse.cz> <2b833ee3-ffdf-c002-a476-458465f0c6bd@suse.cz> <20200403155420.GI323051@elastic.org> <57e8655b-f4f0-ebcc-8991-0f1f336296c3@suse.cz> <20200403163057.GA1922@cgf.cx> <20200403164245.GB2154@cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200403164245.GB2154@cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Status: No, score=-1276.3 required=5.0 tests=BAYES_00, FORGED_SPF_HELO, GIT_PATCH_0, GIT_PATCH_1, GIT_PATCH_2, GIT_PATCH_3, JMQ_SPF_NEUTRAL, KAM_DMARC_NONE, KAM_DMARC_STATUS, KHOP_HELO_FCRDNS, SPF_HELO_PASS, SPF_NEUTRAL, TXREP, USER_IN_WHITELIST autolearn=ham autolearn_force=no version=3.4.2 X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2020 20:52:57 -0000 On Fri, Apr 03, 2020 at 12:42:45PM -0400, Christopher Faylor wrote: >I'll generate this rpm + patches along with instructions on how to do it >in the future. I tried testing the, I think, least intrusive part of this patch set: diff --git a/templates/en/archidxentry.html b/templates/en/archidxentry.html index f9bb57a..365e836 100644 --- a/templates/en/archidxentry.html +++ b/templates/en/archidxentry.html @@ -1,3 +1,5 @@ +%(datestr)s +
  • %(subject)s   %(author)s It didn't work right after regenerating the test-list archive. It resulted in a web page that looked like (cut from the web page): 2020 Archives by date Messages sorted by: [ thread ] [ subject ] [ author ] More info on this list... Starting: Sun Feb 9 02:40:00 GMT 2020 Ending: Fri Apr 3 17:28:10 GMT 2020 Messages: 37 >>>> %(datestr)s <<<< Test Christopher Faylor via test-list %(datestr)s Inspect headers Christopher Faylor %(datestr)s i.e., the %{datestr}s is being treated literally. I don't think that the template change relies on the rest of the patch so this isn't doing what we'd think. I do have an rpm built with these changes but it obviously isn't quite ready for prime time. I have been experimenting with adding an extra "recent" entry in the mailing list that looks more like ezmlm. You can see it here: https://sourceware.org/pipermail/test-list/2020/recent.html When turned on, it adds a "[ recent ]" link to appropriate pages. Clicking on mailto's on the summary page open your mailer with the mailing list in the To:, the original sender in the Cc: (since I now understand that this is really important), and appropriate In-Reply-To's to maintain threading. I accomplish this by running a perl script whenever mailman has finished with a "post" operation. The script iterates over the html message files to produce an ezmlm-like archive. This isn't perfect yet but I thought I'd offer it as a possible alternative to patching mailman. cgf