From: Mateusz Loskot <mateusz@loskot.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Mirroring mailing lists directly
Date: Sat, 23 Feb 2019 22:19:43 +0100 [thread overview]
Message-ID: <CABUeae_eu-aGaUUJqDSqcNtGSs-BKJtRfETq1Oyq36VrnJp+jw@mail.gmail.com> (raw)
In-Reply-To: <20190223031048.GA7084@dcvr>
On Sat, 23 Feb 2019 at 04:10, Eric Wong <e@80x24.org> wrote:
> Mateusz Loskot <mateusz@loskot.net> wrote:
> >
> > I'm trying to figure out how to "mirror existing mailing lists" [1]
> > in practice. I've got Debian 9 with all dependencies installed.
> > [...]
> > 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.
This is helpful. I will try offlineimap.
> If you run your own MTA
No, I'd prefer to avoid own MTA.
> > 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?
The example is clear and I think it should be enough for me.
All the details you gave about configs will be useful, I'm sure.
It's just that I'm not there yet. I'm still missing some
aspects of the bigger picture of mirroring a mailing list.
I've realised, I'm missing an outline of the overall procedure:
0. Install public-inbox and its dependencies
1. Find mailing list to mirror e.g. public@list.org
2. Get a new e-mail address e.g. mirror@user.org
3. Subscribe to list@host.org with mirror@user.org
4. Set up (to run manually or daemon) offlineimap to
sync from mirror@user.org to local Maildir
5. Set up public-inbox-watch
6. Set up public-inbox-httpd to publish via HTTP
7. Set up public-inbox-index to enable search
8. Set up git daemon to allow `git clone` access to mirrored archives.
Is this plan correct, complete or am I missing anything?
Do I need to bother with public-inbox-watch's bidirectional sync?
> 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
The docs of the public-inbox toolset are clear and they seem complete.
As explained above, I am missing a basic "where do I start" to
create mirror, especially for someone who is not a sysadmin,
like myself :)
Once I get to the 4. and later points of the plan above,
I will get back to your other suggestions on the implementation
details.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
next prev parent reply other threads:[~2019-02-23 21:20 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
2019-02-23 21:19 ` Mateusz Loskot [this message]
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=CABUeae_eu-aGaUUJqDSqcNtGSs-BKJtRfETq1Oyq36VrnJp+jw@mail.gmail.com \
--to=mateusz@loskot.net \
--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.
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).