From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.1 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no
	autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id BBABC1F852;
	Wed, 21 Dec 2022 19:54:21 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org;
	s=selector1; t=1671652461;
	bh=SGSC21/0RX9b904F9sBLpK3lxvPvdPSvEc1yoMJZPeE=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=0npSzOiNKQkZy5UyXHbkQ4Gpg7tFx1XQLX/eM/UqxGUHpg/UsPOPL0O7o2amKK4r3
	 URL+8mrrHCkjoZ1GAvAzKSzA+796OnePCMcACsWjh/jZpQKPQvmXRk/hTF3FAnzi4t
	 KQFXG6lVTWZ2SmiwPJ+nvtWL2YfZ/UUZ9tvJ0oX4=
Date: Wed, 21 Dec 2022 19:54:21 +0000
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?
Message-ID: <20221221195421.GB5179@dcvr>
References: <87r0wsli5d.fsf@the-brannons.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <87r0wsli5d.fsf@the-brannons.com>
List-Id: <meta.public-inbox.org>

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.