From: torys.anderson@gmail.com (Tory S. Anderson)
To: Lars Magne Ingebrigtsen <lmi@gnus.org>
Cc: help-gnu-emacs@gnu.org, Robert Thorpe <rt@robertthorpeconsulting.com>
Subject: Re: Dynamically switching send-mail settings
Date: Mon, 09 Feb 2015 07:18:08 -0500 [thread overview]
Message-ID: <87iofbuvlr.fsf@gmail.com> (raw)
In-Reply-To: <87y4o7znff.fsf@building.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 09 Feb 2015 16:03:32 +1100")
Thanks Lars,
After years of emailing in Gnus I didn't think that was an issue; I guess I thought gnutls was built in to Fedora, or I wouldn't have been working. Anyway, I sudo yum installed it and rebuilt emacs. Now I get a different set of errors:
gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [1] (Emacs) setting the trustfile: /etc/pki/tls/certs/ca-bundle.crt
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
gnutls.c: [audit] Note that the security level of the Diffie-Hellman key exchange has been lowered to 256 bits and this may allow decryption of the session data
gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [11798 times]
gnutls.c: [audit] Received record packet of unknown type 50
gnutls.c: [0] (Emacs) fatal error: An unexpected TLS packet was received.
gnutls.el: (err=[-15] An unexpected TLS packet was received.) boot: (:priority NORMAL :hostname mail.toryanderson2.com :loglevel 1 :min-prime-bits 256 :trustfiles (/etc/pki/tls/certs/ca-bundle.crt) :crlfiles nil :keylist nil :verify-flags nil :verify-error nil :callbacks nil)
gnutls-negotiate: GnuTLS error: #<process smtpmail>, -15
I was happy to see the Diffie-Hellman alert; that's what I get on my working email setup. But what's with the gnutls errors now? Seems like I'm getting closer and closer...
Lars Magne Ingebrigtsen <lmi@gnus.org> writes:
> torys.anderson@gmail.com (Tory S. Anderson) writes:
>
>> In this case it happens even if not a gmail account, and unfortunately
>> a new day didn't fix it. Two questions: First, with this message:
>>
>> Opening TLS connection with `gnutls-cli --insecure -p 587
>> smtp.gmail2.com'...failed
>
> If you get these messages, then that means that your Emacs hasn't been
> built with libgnutls support.
next prev parent reply other threads:[~2015-02-09 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 13:35 > 24.3 can't send mail Tory S. Anderson
2015-02-07 14:29 ` Tory S. Anderson
2015-02-07 14:49 ` Eli Zaretskii
2015-02-07 15:31 ` Tory S. Anderson
2015-02-07 15:37 ` Eli Zaretskii
2015-02-07 16:26 ` Tory S. Anderson
2015-02-07 17:51 ` Sivaram Neelakantan
2015-02-08 3:51 ` Dynamically switching send-mail settings (WAS: > 24.3 can't send mail) Tory S. Anderson
2015-02-08 21:49 ` Robert Thorpe
2015-02-09 2:54 ` Dynamically switching send-mail settings Tory S. Anderson
[not found] ` <mailman.19558.1423450457.1147.help-gnu-emacs@gnu.org>
2015-02-09 5:03 ` Lars Magne Ingebrigtsen
2015-02-09 12:18 ` Tory S. Anderson [this message]
2015-02-18 1:20 ` Lars Ingebrigtsen
2015-02-18 2:10 ` Tory S. Anderson
2015-04-15 16:08 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iofbuvlr.fsf@gmail.com \
--to=torys.anderson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=lmi@gnus.org \
--cc=rt@robertthorpeconsulting.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).