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

[david.goldberg6@verizon.net (Dave Goldberg)]

>> And then I get the
>> 
>> 1364 BAD Command received in Invalid state.
>> 
>> in the subsequent *nnimap ...* buffer.

> Hm.  Is that the first response in the new *nnimap ...* buffer?

Well, it's the only one in there at the time I look.  I am not stepping manually (I assume) through every function involved so there may be something beforehand followed by an erase-buffer.

>> What's not clear to me is whether that TLS error message is generated
>> by gnutls-cli or the server.

> I think it's from gnutls-cli -- I think it just says that when the peer
> closes the connection.

Which wouldn't surprise me.  I've always had issues with TLS and the Exchange server.  Prior to the rewrite of nnimap this typically resulted in the server being in a weird state and I wrote some hooks to detect it and go through a deny/close/open process.  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.

-- 
Dave Goldberg
david.goldberg6@verizon.net