From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: SMTP: SSL and auth, not STARTTLS
Date: 01 Mar 2006 09:51:02 -0800 [thread overview]
Message-ID: <86lkvukq9l.fsf@blue.stonehenge.com> (raw)
I have an SMTP server that wants me to connect to port 465 with SSL and auth,
but not with STARTTLS, or something sane like POP-before-SMTP.
I can connect to the server with "openssl s_client -connect
foo.example.com:465" just fine. How do I get that into smtpmail's settings so
that it uses that for the connection on which to auth and then send?
Pardon me if this is a FAQ... I probably didn't search hard enough.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
*** Free account sponsored by SecureIX.com ***
*** Encrypt your Internet usage with a free VPN account from http://www.SecureIX.com ***
reply other threads:[~2006-03-01 17:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=86lkvukq9l.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.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 NNTP newsgroup(s).