Re: Recent nnir update broke search on office365

[Eric Abrahamsen <eric@ericabrahamsen.net>]

david.goldberg6@verizon.net (Dave Goldberg) writes:

> All searches come up empty since this commit (per git-bisect)
>
> 046825b09ff6e23ec7dfacd451d10985615b9793 is the first bad commit
> commit 046825b09ff6e23ec7dfacd451d10985615b9793
> Author: Eric Abrahamsen <eric@ericabrahamsen.net>
> Date:   Tue Jan 27 16:35:25 2015 +1100
>
>     * nnir.el (nnir-run-imap): Enable non-ASCII IMAP searches.
>
> :040000 040000 5131b4d4212b134d58fdaec4481a41239a69926c
> e22212e758aa6a15e13c23ec8fb00f65bcf3a741 M lisp
>
> I should have thought to check my other server (cyrus) - I can do so
> when I get back to work next week. I'm happy to help troubleshoot but
> need guidance on what to look for.

The main problem here is that we're feeding a CHARSET argument to the
imap SEARCH command, but I really had no idea how to determine the
appropriate charset. Right now it's done using a value derived from the
`default-process-coding-system', which is bad because:

1. That variable doesn't exist in xemacs
2. It's probably just the wrong thing to do.

I guess what would be most helpful is if you could tell me your value
for default-process-coding-system, and then do a telnet session with
your exchange server. I'm not sure about exchange but, assuming you're
connecting with ssl, here's what I do with gmail:

openssl s_client -crlf -connect imap.gmail.com:993

Once you're in:

. login email@address.com password
. select INBOX ; or whatever mailbox

(if hitting return doesn't seem to produce a response, try leaving out
the -crlf argument to openssl).

Then you should be able to search with:

. search charset UTF-8 subject "search string"

What I'd like to know is how the different charset arguments affect the
result. Find a string you know is in one of the headers, and try to
search with a few different charsets:

UTF-8
WINDOWS-1252
US-ASCII
ISO-8859-1
whatever you've got in 'default-process-coding-system'

And just see what comes up.

It might also be nice to see the CAPABILITY line that the server gives
you after you connect.

Sorry to give you all this homework! Until someone more knowledgeable
steps up, we're stuck with me muddling through :)

Eric