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: Thu, 22 Dec 2022 11:38:50 +0000	[thread overview]
Message-ID: <20221222113850.M127335@dcvr> (raw)
In-Reply-To: <87y1qzk8r9.fsf@the-brannons.com>

Chris Brannon <chris@the-brannons.com> wrote:
> Well, nginx as a mail proxy looks promising, but it doesn't yet work
> with public-inbox-imapd.  Nginx sends the authentication information as
> synchronizing literals [RFC9051, section 4.3].

Oops, yeah...  public-inbox-imapd doesn't yet support most uses
of synchronizing literals since it's mostly for read-only stuff
which clients will send in a line-oriented way.

> So the login sequence looks similar to this example lifted from RFC9051
> section 7.6:
> 
>      C: A001 LOGIN {11}
>      S: + Ready for additional command text
>      C: FRED FOOBAR {7}
>      S: + Ready for additional command text
>      C: fat man
>      S: A001 OK LOGIN completed
> 
> I could potentially look into working up a patch, though my Perl is
> rusty and more than 15 years out of practice.

I would probably adapt the existing HTTP psgi.input logic for
dealing with them.  But no worries, I should be able to handle
it.  I'd have to support them eventually if I turn lei into a
localhost-only R/W IMAP server.

      reply	other threads:[~2022-12-22 11:38 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
2022-12-21 21:07   ` Chris Brannon
2022-12-22 10:55     ` Chris Brannon
2022-12-22 11:38       ` Eric Wong [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: 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=20221222113850.M127335@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).