From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_BLOCKED, SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from mail.toke.dk (mail.toke.dk [45.145.95.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id AEB8D1F4B4 for ; Sun, 3 Jan 2021 23:23:05 +0000 (UTC) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1609715872; bh=GIzOjjLMph/8I1cQ9yXJ0cKGusjGud7hmjEked5iS+U=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=B96Gt8myL0CbU+Qd2GbtfHQNgkLCwKHEtknF4bW+aC9HHIozZJ0lRIUB3ccGCmSWF 4CFOLK34XhlDwq6W6md8r2qFTnF08qFKK+DTJ5dWfOvUgwFmSdRmDFK0h0v9RNKRi1 xsXov47io4L55H0teuk+7EgPtfig7HwEuyfPd1a7upg4wDN9jAtqi39WIVF6KAEQwC kN/N2npeUbYfJuA9eoLemdJzR8Tz6xLzuTqeE82DLa7XklsCFUWbd9pkr3P4AJEpQ9 xbzt5CkgJ0ZQWmsIalAkVD0/MGLEFGwYlI0z04z+sAbrVFDipNzBG0yo2mP2qQcZk7 xikGZ7KKiVTcw== To: Eric Wong Cc: meta@public-inbox.org Subject: Re: Mailman 3 archiver for public-inbox In-Reply-To: <20210103212130.GA16765@dcvr> References: <8735zip2d1.fsf@toke.dk> <20210103212130.GA16765@dcvr> Date: Mon, 04 Jan 2021 00:17:52 +0100 X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87ble5obj3.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Eric Wong writes: > Toke H=C3=B8iland-J=C3=B8rgensen wrote: >> Hi >>=20 >> I created an archiver for mailman3 that will use public-inbox as the >> archiving backend (using public-inbox-mda). It's somewhat rudimentary, > > Cool. How's performance? I've been thinking of some better > importers(*) for batch work and -mda has always been horribly > slow for me (which is why -watch exists). I... am not sure, really... I'm using it for fairly low-traffic lists and the server I run it on is in a cupboard. Doesn't appear that public-inbox is any kind of bottleneck in that setup, messages show up in the archive pretty instantly as far as I can tell. >> but works well enough for my use case. Figured I'd post it here in case >> anyone else is interested: >>=20 >> https://github.com/tohojo/mailman-public-inbox >>=20 >> Comments and pull requests welcome, of course! > > Btw, feel free to use meta@public-inbox.org for folks that don't > accept Terms-of-Service, solve CAPTCHAs, or use proprietary services. If you're referring to Github here, the code is also available on Pypi: https://pypi.org/project/mailman-public-inbox/ - and I'm happy to take patches by email if someone does want to hack on it :) -Toke