From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Gnus looses IMAP server
Date: Sun, 03 Nov 2013 06:14:44 -0500 [thread overview]
Message-ID: <87mwllu47v.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <87bo2ymcci.fsf@hornet.workgroup>
On Wed, 09 Oct 2013 23:13:49 +0300 Melleus <melleus@openmailbox.org> wrote:
M> Maybe this is a gnustls bug. When trying to reconnect from Servers
M> buffer I got following errors in my Messages buffer:
M> Opening connection to imap.bla.bla via tls...
M> gnutls.c: [0] (Emacs) fatal error: A TLS fatal alert has been received.
M> gnutls.c: [0] (Emacs) Received alert: Bad record MAC
M> Restarting Gnus has no effect, but after restarting Emacs everything
M> gets working againg for some time.
M> When setting imap logging to true I got an empty log.
M> Any suggestions?
Set `gnutls-log-level' and then `M-x report-emacs-bug' if you can. Try
`gnutls-cli' from the command line and see if you get the same error (in
which case it's definitely a GnuTLS issue).
The version and type of the remote server would be helpful, and if it's
publicly accessible it would be even better.
Thanks!
Ted
prev parent reply other threads:[~2013-11-03 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 21:37 Melleus
2013-10-09 20:13 ` Melleus
2013-11-03 11:14 ` Ted Zlatanov [this message]
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=87mwllu47v.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.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).