From: Manos Pitsidianakis <manos@pitsidianak.is>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] imap: use spec compliant continuation request
Date: Tue, 25 Jun 2024 21:40:19 +0300 [thread overview]
Message-ID: <fng6h.6mcfasdnlqei@pitsidianak.is> (raw)
In-Reply-To: <20240625175248.M565435@dcvr>
On Tue, 25 Jun 2024 20:52, Eric Wong <e@80x24.org> wrote:
>Manos Pitsidianakis <manos@pitsidianak.is> wrote:
>> cmd_authenticate() replies to AUTHENTICATE commands with "+" CRLF but
>> the imap4rev1 RFC [^0] defines the following ABNF syntax for a continuation
>> request:
>>
>> continue-req = "+" SP (resp-text / base64) CRLF
>>
>> A space (SP) is required before CRLF.
>
>Thanks for the fix. Pushed as 7bdfb48c3f2c1084f2a7112e039bc0ca0d42c1c1
>Curious, did you notice this in another IMAP client or something else?
>Either way, great to see IMAP getting more attention :>
Noticed this in my own backend imap client library I use for my terminal
e-mail client meli. <https://git.meli-email.org/meli/meli/>
I'm working on higher-level patch-flow mailing list integrations [after
years of working on the basics of a mail client first :-)] and plan on
using public-inbox like servers for fetching arbitrary messages from
lists.
Cheers!
next prev parent reply other threads:[~2024-06-25 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 12:26 [PATCH] imap: use spec compliant continuation request Manos Pitsidianakis
2024-06-25 17:52 ` Eric Wong
2024-06-25 18:40 ` Manos Pitsidianakis [this message]
2024-06-26 3:32 ` Undelivered replies [was: [PATCH] imap: use spec compliant continuation request] 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=fng6h.6mcfasdnlqei@pitsidianak.is \
--to=manos@pitsidianak.is \
--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).