From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: Recent nnir update broke search on office365
Date: Tue, 3 Feb 2015 11:49:00 +0000 [thread overview]
Message-ID: <87k2zzdxlf.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <871tma9mmj.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Sun, 1 Feb 2015 14:22:44 +0800")
On Sunday, 1 Feb 2015 at 14:22, Eric Abrahamsen wrote:
> david.goldberg6@verizon.net (Dave Goldberg) writes:
>
>> All searches come up empty since this commit (per git-bisect)
This happens to me as well in latest gnus (as of yesterday, that
is). I've backed up to a version that works for now.
[...]
> 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:
To give you a data point, I have followed your instructions for the IMAP
server I use which is outlook.office365.com (Microsoft :(). The only
charset that works is US-ASCII. This is rather annoying, to say the
least.
My default-process-coding-system is utf-8-unix.
HTH,
eric
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 24.4.1 + Ma Gnus v0.12 + evil-git-bdeb602
: BBDB version 3.1.2 (2014-04-27 15:05:20 -0500)
next prev parent reply other threads:[~2015-02-03 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 16:53 Dave Goldberg
2015-02-01 1:40 ` Eric Abrahamsen
2015-02-01 6:22 ` Eric Abrahamsen
2015-02-03 11:49 ` Eric S Fraga [this message]
2015-02-03 13:01 ` Eric Abrahamsen
2015-02-03 15:57 ` e.fraga
2015-02-03 23:21 ` Dave Goldberg
2015-02-04 3:02 ` Eric Abrahamsen
2015-02-04 10:30 ` Eric S Fraga
2015-02-04 0:15 ` Katsumi Yamaoka
2015-02-04 3:30 ` Eric Abrahamsen
2015-02-04 18:28 ` Andreas Schwab
2015-02-05 1:03 ` Eric Abrahamsen
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=87k2zzdxlf.fsf@pinto.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).