From: Eric Abrahamsen <firstname.lastname@example.org>
Subject: Help testing Exchange IMAP server search?
Date: Fri, 06 May 2022 10:32:51 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
Hey can someone(s) with an IMAP account on a Microsoft Exchange server,
who is running Emacs from master, help me test search capability?
I just pushed a change to gnus-search that will help improve search
handling for Exchange servers, but there's more work to do.
In a nutshell: Exchange advertises the LITERAL+ capability. But it only
accepts searches using the US-ASCII charset. Right now, if the code sees
a non-ascii search string, and the server has LITERAL+, it will encode
the string using the literal+ format and send CHARSET UTF-8, which
results in an error from Exchange.
The other option is to ignore Exchange's LITERAL+ capability, and put
double quotes around the non-ascii string. I don't know if that will
work or not, that's what I need help testing.
I'm hoping someone will:
1. Pull and build today's Emacs code.
2. Search an ascii-only string like "FROM eric" (it doesn't matter if
you use the parsed queries or not) and verify it works.
3. Search a non-ascii string like "FROM Jérôme" (something that *should*
return results!) and tell me what happens.
4. Eval the method definition below, and repeat both of the above tests.
Thanks in advance!
(cl-defmethod gnus-search-imap-handle-string ((engine gnus-search-imap)
(if (string-match-p "[^[:ascii:]]" str)
(if (string-prefix-p "\"" str)
(format "\"%s\"" str))
next reply other threads:[~2022-05-06 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 17:32 Eric Abrahamsen [this message]
2022-06-03 11:53 ` Alberto Luaces
2022-06-03 15:58 ` Eric Abrahamsen
2022-06-03 17:26 ` Andreas Schwab
2022-06-06 14:46 ` Alberto Luaces
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).