unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Chris Brannon <chris@the-brannons.com>
Cc: meta@public-inbox.org
Subject: Re: dovecot fronting for public-inbox-imapd + private mail groups?
Date: Wed, 21 Dec 2022 19:54:21 +0000	[thread overview]
Message-ID: <20221221195421.GB5179@dcvr> (raw)
In-Reply-To: <87r0wsli5d.fsf@the-brannons.com>

Chris Brannon <chris@the-brannons.com> wrote:
> Perhaps this is a better question for the dovecot list, but I'll throw
> it out here in case someone else has dealt with this scenario.
> 
> I self-host email, so I'm already running dovecot.  I also want to
> publish some public-inbox archives over IMAP that are available to the
> world, with anonymous access.  I essentially just have one public IPv4
> address, so I'm limited to one public-facing IMAP server.

I'm in the same situation.  My current workaround is to run my
personal IMAP stuff on a different port and keep 993+143 for
public-inbox-imapd.

> What I'd like to do is proxy all access to groups in the inbox.*
> namespace to public-inbox-imapd, and open those up for anonymous access.
> Everything else would remain private, requiring credentials.

I know nginx can support IMAP proxying, but I'm not sure if it
can decide on backend based on usernames or inboxes.  Would
appreciate an example config if you figure it out.

> Can it be done?  Are there better ways to do it?  In an ideal world,
> everyone would be using IPv6 by now and this wouldn't be an issue.

I'm already planning on adding support for HTTP proxying, so
IMAP proxying wouldn't be too big a step.

  reply	other threads:[~2022-12-21 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21 18:35 dovecot fronting for public-inbox-imapd + private mail groups? Chris Brannon
2022-12-21 19:54 ` Eric Wong [this message]
2022-12-21 21:07   ` Chris Brannon
2022-12-22 10:55     ` Chris Brannon
2022-12-22 11:38       ` 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=20221221195421.GB5179@dcvr \
    --to=e@80x24.org \
    --cc=chris@the-brannons.com \
    --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).