From: Gaute B Strokkenes <gs234@cam.ac.uk>
Subject: Re: nnimap versus tls
Date: Sat, 05 Jul 2003 09:44:48 +0100 [thread overview]
Message-ID: <87k7axwef3.fsf@cam.ac.uk> (raw)
In-Reply-To: <84of0ab15z.fsf@lucy.is.informatik.uni-duisburg.de>
On 4 jul 2003, kai.grossjohann@gmx.net wrote:
> Gaute B Strokkenes <gs234@cam.ac.uk> writes:
>
>> --8<-- Debugger entered--Lisp error: (error "Selecting deleted
>> buffer") imap-arrival-filter(#<process imap<1>> "* BYE
>> kern.srcf.societies.cam.ac.uk IMAP4rev1 server terminating
>> connection^M\n6 OK LOGOUT completed^M\n*** Received corrupted
>> data(-9) - server has terminated the connection abnormally\n")
>> delete-process(#<process imap<2>>)
>
> It seems that Gnus isn't expecting the server to close the
> connection, err, unexpectedly.
>
> Or am I misinterpreting this?
I wouldn't know.
This is a cut-and-past of the relevant portions of *imap-log*. I
haven't changed anything, other than to replace my password with
something else.
Connecting to '131.111.179.82:993'...
Resolving 'imap.srcf.ucam.org'...
- Certificate type: X.509
- Certificate info:
# Certificate is valid since: Wed Aug 14 14:17:00 BST 2002
# Certificate expires: Thu Aug 14 14:17:00 BST 2003
# Certificate fingerprint: 0e 51 8a 6b c3 e0 c3 bf d1 54 1e 1b af ab ac cf
# Certificate serial number: 00
# Certificate version: #3
# Certificate public key algorithm: RSA
# Modulus: 1024 bits
# CN=imap.srcf.ucam.org,E=sysadmins@srcf.ucam.org,OU=Student-Run Computing Facility,O=University of Cambridge,L=Cambridge,ST=Cambridgeshire,C=UK
# Certificate Issuer's info:
# CN=imap.srcf.ucam.org,E=sysadmins@srcf.ucam.org,OU=Student-Run Computing Facility,O=University of Cambridge,L=Cambridge,ST=Cambridgeshire,C=UK
- Peer's certificate is NOT trusted
- Version: TLS 1.0
- Key Exchange: RSA
- Cipher: ARCFOUR 128
- MAC: SHA
- Compression: NULL
- Handshake was completed
- Simple Client Mode:
* OK [CAPABILITY IMAP4REV1 X-NETSCAPE LOGIN-REFERRALS STARTTLS AUTH=LOGIN] localhost IMAP4rev1 2001.315 at Sat, 5 Jul 2003 09:22:10 +0100 (BST)
1 CAPABILITY
* CAPABILITY IMAP4REV1 X-NETSCAPE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND LOGIN-REFERRALS STARTTLS AUTH=LOGIN
1 OK CAPABILITY completed
2 LOGIN "gs234" "I'm not telling you..."
2 OK [CAPABILITY IMAP4REV1 X-NETSCAPE NAMESPACE MAILBOX-REFERRALS SCAN SORT THREAD=REFERENCES THREAD=ORDEREDSUBJECT MULTIAPPEND] User gs234 authenticated
3 SELECT "INBOX"
* 3 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1056494962] UID validity status
* OK [UIDNEXT 43763] Predicted next UID
* FLAGS (\Answered \Flagged \Deleted \Draft \Seen)
* OK [PERMANENTFLAGS (\* \Answered \Flagged \Deleted \Draft \Seen)] Permanent flags
3 OK [READ-WRITE] SELECT completed
4 UID SEARCH UNSEEN UNDELETED
* SEARCH
4 OK UID SEARCH completed
5 CLOSE
5 OK CLOSE completed
6 LOGOUT
And this is what I get by setting debug-on-error to t:
Debugger entered--Lisp error: (error "Selecting deleted buffer")
imap-arrival-filter(#<process imap<1>> "* BYE kern.srcf.societies.cam.ac.uk IMAP4rev1 server terminating connection\r\n6 OK LOGOUT completed\r\n*** Received corrupted data(-9) - server has terminated the connection abnormally\n")
By comparision, this is what I get in *imap-log* on one of those
occasions when the error does not occur:
[snip]
5 OK UID FETCH completed
6 UID STORE 43765 +FLAGS (\Deleted)
* 4 FETCH (FLAGS (\Recent \Deleted) UID 43765)
6 OK UID STORE completed
7 CLOSE
7 OK CLOSE completed
8 LOGOUT
* BYE kern.srcf.societies.cam.ac.uk IMAP4rev1 server terminating connection
8 OK LOGOUT completed
*** Received corrupted data(-9) - server has terminated the connection abnormally
Note the similarities here. It seems that the "*** Received corrupted
data"... etc. is just gnutls complaining about the other end hanging
up--but that is what it is supposed to do, given that we've gone
through the normal IMAP logout sequence.
So, the problem is that imap-arrival-filter and "Selecting deleted
buffer", whatever that means. I do not at all know how this stuff
works, but I see that imap-arrival-filter does a
(with-current-buffer (process-buffer proc)
...
So it seems that the process buffer dies unexpectedly. But my elisp
skills are insufficiently 1337 to handle this.
--
Big Gaute http://www.srcf.ucam.org/~gs234/
I want EARS! I want two ROUND BLACK EARS to make me feel warm 'n secure!!
next prev parent reply other threads:[~2003-07-05 8:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 13:32 Gaute B Strokkenes
2003-07-02 23:46 ` Gaute B Strokkenes
2003-07-04 18:24 ` Kai Großjohann
2003-07-05 8:44 ` Gaute B Strokkenes [this message]
2003-07-05 12:53 ` Kai Großjohann
2003-07-06 12:56 ` Gaute B Strokkenes
2003-07-06 15:54 ` Kai Großjohann
2003-07-06 21:53 ` Gaute B Strokkenes
2003-07-07 6:08 ` Kai Großjohann
2003-07-07 7:26 ` Gaute B Strokkenes
2003-07-07 9:46 ` Gaute B Strokkenes
2003-07-07 15:35 ` Kai Großjohann
2003-07-08 22:20 ` Gaute B Strokkenes
2003-07-09 19:46 ` Kai Großjohann
2003-07-10 0:03 ` Gaute B Strokkenes
2003-07-09 19:52 ` Kai Großjohann
2003-07-10 1:25 ` Gaute B Strokkenes
2003-07-10 7:24 ` Kai Großjohann
2003-07-10 10:32 ` Gaute B Strokkenes
2003-07-10 7:49 ` Simon Josefsson
2003-07-10 11:42 ` Gaute B Strokkenes
2003-07-10 12:13 ` Simon Josefsson
2003-07-10 13:16 ` Matthias Andree
2003-07-07 15:38 ` Kai Großjohann
2003-07-07 19:37 ` Gaute B Strokkenes
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=87k7axwef3.fsf@cam.ac.uk \
--to=gs234@cam.ac.uk \
/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).