From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: gcc-mark-as-read sometimes broken on Exchange
Date: Thu, 16 Dec 2010 17:35:29 +0100 [thread overview]
Message-ID: <m3d3p17k1a.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <84zksdbmmw.fsf@davestoy.home>
david.goldberg6@verizon.net (Dave Goldberg) writes:
> 1252 OK [READ-ONLY] EXAMINE completed.
> * 401 FETCH (FLAGS (%Seen) UID 210486)
>
> [...]
>
> * 442 FETCH (FLAGS () UID 210577)
>
> [...]
>
> 1253 OK FETCH completed.
> * BYE Connection is closed. 13
> *** Fatal error: A TLS packet with unexpected length was received.
> *** Server has terminated the connection abnormally.
>
> 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?
> 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.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-16 16:35 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 [this message]
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=m3d3p17k1a.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).