Gnus development mailing list
 help / color / mirror / Atom feed
From: Tibor Simko <tibor.simko@cern.ch>
To: ding@gnus.org
Subject: Re: gcc-mark-as-read sometimes broken on Exchange
Date: Fri, 17 Dec 2010 01:08:17 +0100	[thread overview]
Message-ID: <87y67p6z2m.fsf@pcuds33.cern.ch> (raw)
In-Reply-To: <8462utbaka.fsf@davestoy.home>

On Thu, 16 Dec 2010, Dave Goldberg wrote:
> After the rewrite I no longer have to do that as the new nnimap
> handles that much better.  It's odd that the issue with gcc just
> started showing up recently but given that it's not repeatable perhaps
> I was just getting lucky.

FWIW, I've been having the same experience with Exchange 2010 and Gcc;
it used to work well with Oct-Nov gnus git versions but started to show
issues occasionally in Dec gnus git versions; lately it has become
relatively frequent for me, at least a few times per day.

Exchange IMAP is understandingly not among primary Gnus test platforms.
Thinking also of gnus agent nnimap features that have low TODO priority
such as moving email between folders when unplugged, perhaps it's time
to plug dovecot and offlineimap between gnus and Exchange so as not to
connect to Exchange directly?  This setup could be both (i) more robust
(since people using other MUAs like mutt are using offlineimap for
Exchange too, so any intricacies of Exchange IMAP may be better handled
there); and (ii) more advantageous offline-feature-wise (e.g. the
above-mentioned moving/triage of email between IMAP folders when
unplugged).  Though there were also some issues WRT offlineimap and
marks, for example, so dunno.

Does anyone with `corporate Exchange' have first-class experience with
such a gnus-dovecot-offlineimap-exchange setup for a reasonably long
period of time?  Personally I tested such a setup only briefly, and only
with old nnimap.  (I preferred to keep the gnus agent way of doing
things at the time.)

Best regards
-- 
Tibor Simko




  reply	other threads:[~2010-12-17  0:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-30 19:10 Dave Goldberg
2010-12-01 17:15 ` Lars Magne Ingebrigtsen
2010-12-06 20:53   ` Dave Goldberg
2010-12-06 22:24     ` Lars Magne Ingebrigtsen
2010-12-07 13:32       ` Dave Goldberg
2010-12-07 18:15         ` Dave Goldberg
2010-12-07 18:24           ` Dave Goldberg
2010-12-07 22:11             ` Dave Goldberg
2010-12-08 19:50               ` Dave Goldberg
2010-12-09 22:59                 ` Lars Magne Ingebrigtsen
2010-12-10 16:47                   ` Dave Goldberg
2010-12-16 16:35                     ` Lars Magne Ingebrigtsen
2010-12-16 22:46                       ` Dave Goldberg
2010-12-17  0:08                         ` Tibor Simko [this message]
2010-12-17 16:37                           ` Lars Magne Ingebrigtsen
2010-12-21  0:01                             ` Tibor Simko
2010-12-17 16:35                         ` Lars Magne Ingebrigtsen
2010-12-21  0:12                           ` Tibor Simko
2011-01-02  6:59                             ` Lars Magne Ingebrigtsen

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=87y67p6z2m.fsf@pcuds33.cern.ch \
    --to=tibor.simko@cern.ch \
    --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).