From: Leo <sdl.web@gmail.com>
To: ding@gnus.org
Subject: Re: Fatal error: A TLS packet with unexpected length was received
Date: Sun, 16 Sep 2007 00:33:39 +0100 [thread overview]
Message-ID: <m2ejgz8pws.fsf@cam.ac.uk> (raw)
In-Reply-To: <87y7f7y2sc.fsf@denkblock.local>
On 2007-09-15 23:36 +0100, Elias Oltmanns wrote:
> Leo <sdl.web@gmail.com> wrote:
>> ---- " trace of POP session to pop.gmail.com" ----
> [...]
>> +OK Gpop ready for requests from 131.111.223.122 e10pf2134124qbe
>> *** Fatal error: A TLS packet with unexpected length was received.
>> *** Server has terminated the connection abnormally.
>>
>> Process POP finished
>
> I don't quite see how this could possibly be caused by gnus. Isn't this
> rather a gnutls-cli issue or am I missing something?
>
> Regards,
>
> Elias
It looks like it is caused by gnutls-cli.
However, I explicitly setting tls-program to ("openssl s_client -connect
%h:%p -no_ssl2") but then the following message is displayed in echo
area FOREVER:
Retrieving message 1 of 1 from pop.gmail.com...
I have to type "C-g" to free Emacs from freeze.
--
.: Leo :. [ sdl.web AT gmail.com ] .: [ GPG Key: 9283AA3F ] :.
>>> I use GNU Emacs
>>> http://www.gnu.org/software/emacs/
next prev parent reply other threads:[~2007-09-15 23:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2wt3qbops.fsf@sl392.st-edmunds.cam.ac.uk>
2007-01-19 1:19 ` POP SSL conexion failed Leo
2007-02-01 0:08 ` Leo
2007-03-25 9:31 ` Leo
2007-09-15 21:53 ` Fatal error: A TLS packet with unexpected length was received (was: POP SSL conexion failed) Leo
2007-09-15 22:36 ` Fatal error: A TLS packet with unexpected length was received Elias Oltmanns
2007-09-15 23:33 ` Leo [this message]
2007-09-24 13:41 ` Simon Josefsson
2007-09-24 14:30 ` Leo
2007-09-25 14:41 ` Simon Josefsson
2007-09-18 19:33 ` POP SSL conexion failed Leo
2007-09-18 20:27 ` Leo
2007-10-18 20:58 ` Leo
2007-11-14 20:40 ` Leo
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=m2ejgz8pws.fsf@cam.ac.uk \
--to=sdl.web@gmail.com \
--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).