user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Mailman 3 archiver for public-inbox
Date: Mon, 04 Jan 2021 00:17:52 +0100	[thread overview]
Message-ID: <87ble5obj3.fsf@toke.dk> (raw)
In-Reply-To: <20210103212130.GA16765@dcvr>

Eric Wong <e@80x24.org> writes:

> Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> Hi
>> 
>> 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:
>> 
>> https://github.com/tohojo/mailman-public-inbox
>> 
>> 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

      reply	other threads:[~2021-01-03 23:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03 13:38 Mailman 3 archiver for public-inbox Toke Høiland-Jørgensen
2021-01-03 21:21 ` Eric Wong
2021-01-03 23:17   ` Toke Høiland-Jørgensen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ble5obj3.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).