9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] using smtp port 587
Date: Fri, 29 May 2015 08:25:35 +0100	[thread overview]
Message-ID: <2b487c7961be5ff2ffb1c0c0165e4b97@quintile.net> (raw)
In-Reply-To: <b0db33b46d796548bd869b9dcdbe6525@hera.eonet.ne.jp>

I would modify /lib/mail/remotemail adding a line somthing like this:

	echo  /bin/upas/smtp -d -h $fd $addr $sender $* > /mail/tmp/smtp.cli
	exec /bin/upas/smtp -d -h $fd $addr $sender $* >[2] /mail/tmp/smtp.err

The important fact is that /mail/tmp exists in smtp(1)'s namespace.

This way you can see exactly what is happening.

There are two ways to implement tls on for smtp. Either a fully encrypted session,
which plan9 does not support, or switching from a non-encrypted to an encrypted session
if both ends agree (which plan9 does support). This is the HELO -v- EHLO greetingthe latter switches to TLS.

you may need to ensure your plan9 supports tls1.2 if your smtp relays needs it,
9front has the fixes necessary.

The labs distribution has the lines to confirm the TLS thumbprint of the relay
commented out - it causes many problems in environments where the relay was 
implemenetd by several different servers. This may or may not be the case for your
distro. the wiki has details of how to get and save the thumbprint.


authentication of smtp is another issue, LOGIN and BASIC are very similar and quite
insecure without TLS. NEGOIATE is a special microsoft protocol and is not supported,
this leaves MD5 digest and machap which are chalange response and fairly secure.

smtp tries to use tls but can be forced to talk insecurely by command line options.

hope this helps,

-Steve


  reply	other threads:[~2016-12-01 20:28 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-01  4:41 kokamoto
2016-12-01  4:51 ` [9front] " Stanley Lieber
2016-12-01  5:10   ` kokamoto
2016-12-01  5:22     ` Stanley Lieber
2016-12-01  7:59       ` kokamoto
2016-12-01  8:01         ` kokamoto
2015-05-29  7:25           ` Steve Simon [this message]
2016-12-01 20:35             ` Stanley Lieber
2016-12-01 20:48               ` Steve Simon
2016-12-02  1:58                 ` kokamoto
2016-12-08  7:10                   ` kokamoto
2016-12-09  1:42                     ` kokamoto
2016-12-09 12:11                       ` cinap_lenrek
2016-12-11  3:56                         ` kokamoto
2016-12-11 15:02                           ` Steve Simon
2016-12-12  1:33                             ` kokamoto
2016-12-17  6:18                               ` kokamoto
2016-12-17  6:23                                 ` kokamoto
2016-12-17  9:19                                   ` Steve Simon
2016-12-17 11:46                                     ` kokamoto

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=2b487c7961be5ff2ffb1c0c0165e4b97@quintile.net \
    --to=steve@quintile.net \
    --cc=9front@9front.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).