From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: gcc-mark-as-read sometimes broken on Exchange
Date: Wed, 08 Dec 2010 14:50:53 -0500 [thread overview]
Message-ID: <84bp4w82n6.fsf@davestoy.home> (raw)
In-Reply-To: <84fwu98c8p.fsf@davestoy.home> (Dave Goldberg's message of "Tue, 07 Dec 2010 17:11:18 -0500")
> It appears to be some sort of race condition. If I step through
> nnimap-find-article-by-message-id I succeed all the time. If I get
> impatient and press 'c' to continue through the function without
> stopping then some percentage of the time (I didn't really keep track)
> the function returns nil.
Maybe it's not quite that bad. I just noticed the following in my message log after a failure:
Result: (("BAD" "Command" "received" "in" "Invalid" "state."))
This at this spot in nnimap-find-article-by-message-id:
(when (and result
(car (setq result (nnimap-parse-response))))
So perhaps something is going wrong with the connection to the Exchange server after the successful APPEND? How would I check for that? The *nnimap ...* buffer seems to get erased before the attempt at the search.
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next prev parent reply other threads:[~2010-12-08 19:50 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 [this message]
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
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=84bp4w82n6.fsf@davestoy.home \
--to=david.goldberg6@verizon.net \
--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).