From: Augusto Stoffel <arstoffel@gmail.com>
To: meta@public-inbox.org
Subject: Bug in FETCH request?
Date: Wed, 23 Oct 2024 09:12:50 +0200 [thread overview]
Message-ID: <87jzdzguml.fsf@gmail.com> (raw)
Hi,
The following request querying the latest message id fails on
public-inbox.org
curl 'imaps://:@public-inbox.org/inbox.comp.mail.public-inbox.meta.0'\
-X 'FETCH * (UID)'
It works on other IMAP servers and AFAICT is allowed by the protocol
spec.
This on the other hand works, but you need to choose a high enough
number...
curl 'imaps://:@public-inbox.org/inbox.comp.mail.public-inbox.meta.0'\
-X 'FETCH 999999:* (UID)'
next reply other threads:[~2024-10-23 7:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 7:12 Augusto Stoffel [this message]
2024-10-23 9:30 ` [PATCH] imap: allow bare `*' in range Eric Wong
2024-10-29 6:53 ` Augusto Stoffel
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=87jzdzguml.fsf@gmail.com \
--to=arstoffel@gmail.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).