From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ssmtp
Date: Mon, 4 Jun 2007 13:28:20 +0100 [thread overview]
Message-ID: <34987142b0e800b6f5a53bf3268dd1c2@quintile.net> (raw)
In-Reply-To: <1180822392.121730.286790@m36g2000hse.googlegroups.com>
> Is there any easy way to configure upas/smtp to use port 465 (ssmtp)
> for authenticated smtp ?
If you just refer to your smtp realy as net!smtp.your-relay.dom!ssmtp then it will use
port 456 - grep for 456 in /lib/ndb/common to see where this magic comes from.
There is only support for a limited subset of auth methods, plain and login I believe
but this should be enough - they are insecure on a clear link but over TLS its fine.
you will need to save the tls thumbprint for your relay, the first time you use it
this will be logged in /sys/log/smtp.fail (I think, one of the email related log
files anyway), and you can then cut and paste this into /sys/lib/tls/smtp, eg:
x509 sha1=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
-Steve
prev parent reply other threads:[~2007-06-04 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 9:09 onyx.peridot
2007-06-04 12:28 ` Steve Simon [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=34987142b0e800b6f5a53bf3268dd1c2@quintile.net \
--to=steve@quintile.net \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).