From: David Edmondson <dme@dme.org>
To: ding@gnus.org
Subject: gnus-search & imap: always "CHARSET UTF-8" when literal+ is supported
Date: Thu, 21 Oct 2021 20:11:32 +0100 [thread overview]
Message-ID: <cun5ytqxkez.fsf@dme.org> (raw)
Using current emacs git head, talking to outlook.office365.com over
IMAP.
Attempts to use gnus-search always fail with the server reporting:
(("NO" ("BADCHARSET" "(US-ASCII)") "The" "specified" "charset" "is" "not" "supported."))
Looking at gnus-search.el, `gnus-search-imap-search-command' always
sends CHARSET UTF-8 if the server supports literal+ (which this one
does). Sending US-ASCII (or no charset at all) causes the server to
return the required results in simple test cases.
Is there a way to determine whether a server supports UTF-8 in searches,
and adjust the command sent accordingly? If not, could the use of UTF-8
be controlled with (yet another!) variable?
Thanks.
dme.
--
We're deep in discussion, the party's on mute.
reply other threads:[~2021-10-22 23:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cun5ytqxkez.fsf@dme.org \
--to=dme@dme.org \
--cc=ding@gnus.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 NNTP newsgroup(s).