From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <9182f5f061e27da9ee652cf9ccc11c82@hamnavoe.com>
To: 9fans@9fans.net
From: Richard Miller <9fans@hamnavoe.com>
Date: Wed, 31 Aug 2011 15:22:21 +0100
In-Reply-To: <CAOEdRO2za1VcgEbR=WfQErybDZpkADBd3rhz7-NB3DQ-EvpyKw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] mail client; general question web vs command
Topicbox-Message-UUID: 17913d3a-ead7-11e9-9d60-3106f5b1d025

To use the plan9port version of upas/smtp with authenticated connections,
you need a couple of fixes which I've just submitted. 'hg pull -u' will
get them.

The plan9port upas/smtp also does not support tls, which is required
by gmail. The workaround is to run smtp inside a tls tunnel, as shown
below. Note that you can't use 'localhost' to address the near end
of the tunnel because smtp doesn't like forwarding to 127.0.0.1.

bash-3.1$ hostname
epia
bash-3.1$ cat msg
Subject: test

hello
bash-3.1$ 9p read factotum/ctl
key proto=pass role=client server=epia service=smtp user=example@gmail.com !password?
bash-3.1$ sudo /usr/sbin/stunnel3 -c -d 12345 -r smtp.gmail.com:465
bash-3.1$ $PLAN9/bin/upas/smtp -ai 'tcp!epia!12345' 9fans@hamnavoe.com xxx@example.com <msg
epia Aug 31 15:01:34 9fans@hamnavoe.com sent 127 bytes to xxx@example.com