From: Eric Wong <e@80x24.org>
To: Mateusz Loskot <mateusz@loskot.net>
Cc: meta@public-inbox.org
Subject: Re: Mirroring mailing lists directly
Date: Sat, 23 Feb 2019 03:10:48 +0000 [thread overview]
Message-ID: <20190223031048.GA7084@dcvr> (raw)
In-Reply-To: <CABUeae9aUQhg=sGROB4cBqP1tPmyKTDGwnwecWXGjeSVg48X9Q@mail.gmail.com>
Mateusz Loskot <mateusz@loskot.net> wrote:
> Hi,
>
> I'm trying to figure out how to "mirror existing mailing lists" [1]
> in practice. I've got Debian 9 with all dependencies installed.
> I also did [2]
>
> git clone https://public-inbox.org/ public-inbox
>
> Next, AFAIU, is to set up inbox watcher [3].
>
> However, I'm missing some details of the bigger picture:
> I'm going to host a docker or VM somewhere, and I'd like to set it up
> as a mirror of all new posts.
Fwiw, a chroot also works fine and requires less tools to download
(but less isolation than containers or VMs).
> If I manage to get mbox archives, I may also try to import existing
> archives, but that is for later.
In that case, you might want to try the newish --skip feature
which leaves epoch space when running public-inbox-init:
https://public-inbox.org/meta/20181228101611.16702-1-e@80x24.org/
(no padding for old NNTP article numbers, yet :x)
> How to actually deliver mailing list posts to the public-inbox watch?
-watch currently requires mail to be delivered to a Maildir.
I use offlineimap for that; but mbsync (isync) or other
similar tools should work, too.
If you run your own MTA, using public-inbox-mda is a
possibility, too; but I figure more people have IMAP or Maildir
access than run their own MTAs.
> Could anyone mirroring a list out there share any details on setup of
> the public-inbox mirror host?
Is the example at the top of
https://public-inbox.org/public-inbox-watch.html
not enough?
For the git mailing list, I also have a "filter" attribute
to kill signatures in old mails:
[publicinbox "git"]
address = git@vger.kernel.org
watch = maildir:/home/ew/.maildir/.INBOX.git
watchheader = X-Mailing-List:git@vger.kernel.org
filter = PublicInbox::Filter::Vger
I also use the ListMirror SpamAssassin plugin because I'm
paranoid about mail only hitting the archives, but not going
through vger, first:
https://public-inbox.org/meta/20160624204718.27540-1-e@80x24.org/
One (of many) goals I have for the web interface is to expose
part of the config so it's easier to setup mirrors of existing
list.
But I also don't want to be exposing local pathnames or resource
limiter details (Qspawn stuff) since that can be used to aid
attackers.
Please let us know if there's specific stuff to clarify in docs
or if the getting mail-to-Maildir was the primary thing. I have
a lot on my plate :x
> [1] https://public-inbox.org/public-inbox-overview.html
> [2] https://public-inbox.org/README.html
> [3] https://public-inbox.org/public-inbox-watch.html
next prev parent reply other threads:[~2019-02-23 3:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 0:35 Mirroring mailing lists directly Mateusz Loskot
2019-02-23 3:10 ` Eric Wong [this message]
2019-02-23 21:19 ` Mateusz Loskot
2019-02-23 22:07 ` Eric Wong
2019-02-26 17:54 ` Mateusz Łoskot
2019-02-26 23:19 ` Eric Wong
2019-02-27 0:28 ` Mateusz Łoskot
2019-02-27 0:41 ` Eric Wong
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: https://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=20190223031048.GA7084@dcvr \
--to=e@80x24.org \
--cc=mateusz@loskot.net \
--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.
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).