From: bxf4@u.washington.edu
Subject: tls question
Date: Fri, 05 Aug 2005 16:25:18 -0700 [thread overview]
Message-ID: <m2y87g6k69.fsf@d-128-95-226-37.dhcp4.washington.edu> (raw)
Hello,
After many days of trying, I have authenticated smtp working with my
ISP's smtp servers, gnus, and smtpmail by using TLS via starttls.el.
My question is how can I tell if TLS is actually working? My computer
issues the STARTTLS command, but I don't see any of the handshake,
etc. information that the starttls.el file shows. Here's the relevant
part of my .emacs:
(setq starttls-gnutls-program "/usr/local/bin/gnutls-cli"
starttls-program nil
starttls-use-gnutls t
;; doesn't seem to help here, maybe need to somehow route output to another buffer?
;; starttls-extra-arguments '("--debug" "1")
smtpmail-starttls-credentials
'(("smtp.isp.com" 587 nil nil)))
As you can see, I tried to add the debug argument, but the smtp trace
did not look any different. Please also note the final two nil
arguments to smtpmail-starttls-credentials. I've seen this one the
web, but I don't understand how TLS will work with the key and
certificate. Is that part of the problem?
Part of the trace follows. Thank you for any input you may have.
220 smtp.isp.com ESMTP Sendmail 8.13.4+UW05.04/8.13.4+UW05.07; Fri, 5 Aug 2005 14:23:34 -0700
Process SMTP killed
EHLO dhcp.isp.com
250-smtp.isp.com Hello dhcp.isp.com [IP deleted], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-EXPN
250-VERB
250-8BITMIME
250-SIZE 60000000
250-AUTH GSSAPI
250-STARTTLS
250-DELIVERBY
250 HELP
STARTTLS
220 2.0.0 Ready to start TLS
EHLO dhcp.isp.com
250-smtp.isp.com Hello dhcp.isp.com [IP deleted], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
[...]
050 >>> EHLO smtp.isp.com
050 250-mxout.isp.com Hello smtp.isp.com [IP deleted], pleased to meet you
050 250-ENHANCEDSTATUSCODES
050 250-PIPELINING
050 250-EXPN
050 250-VERB
050 250-8BITMIME
050 250-SIZE 60000000
050 250-ETRN
050 250-STARTTLS
050 250-DELIVERBY
050 250 HELP
050 >>> STARTTLS
050 220 2.0.0 Ready to start TLS
050 >>> EHLO smtp.isp.com
[...]
250 2.0.0 j75LNYdv029427 Message accepted for delivery
QUIT
221 2.0.0 smtp.isp.com closing connection
- Peer has closed the GNUTLS connection
next reply other threads:[~2005-08-05 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 23:25 bxf4 [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-05 23:22 tls question bxf4
2005-08-05 23:16 bxf4
2005-08-06 0:24 ` Brian P. Flaherty
[not found] ` <m2slxovutn.fsf-INHAs3gjgrFdBwumxGWZyk8mzxbseA6u8hQs7eYZtGL2fBVCVOL8/A@public.gmane.org>
2005-08-06 18:38 ` Jochen Küpper
[not found] ` <mailman.2785.1123355327.20277.help-gnu-emacs@gnu.org>
2005-08-26 15:29 ` Brian P. Flaherty
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=m2y87g6k69.fsf@d-128-95-226-37.dhcp4.washington.edu \
--to=bxf4@u.washington.edu \
/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).