Re: gcc-mark-as-read sometimes broken on Exchange

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

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

> 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.

If you could look in the *nnimap ...* buffer just after the APPEND, that
might give us a clue to what the IMAP server is really complaining
about.  My guess is that there's some sort of encoding problem or a
problem with the length of the message or something.  Which might
explain why it's working sometimes, but not other times -- perhaps if
there are some non-ASCII characters in the message, APPEND fails, but
otherwise it works?

That just a guess, though.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen