From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <9182f5f061e27da9ee652cf9ccc11c82@hamnavoe.com>
References: <CAOEdRO2za1VcgEbR=WfQErybDZpkADBd3rhz7-NB3DQ-EvpyKw@mail.gmail.com>
	<9182f5f061e27da9ee652cf9ccc11c82@hamnavoe.com>
Date: Fri,  9 Sep 2011 21:48:35 +0200
Message-ID: <CAOEdRO3f7oLw5UmoNu3L4q88PE-be6UEAWEAGLFJ6o2MPjhLxg@mail.gmail.com>
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [9fans] mail client; general question web vs command
Topicbox-Message-UUID: 1ca6bde0-ead7-11e9-9d60-3106f5b1d025

Hello,

On 31 August 2011 16:22, Richard Miller <9fans@hamnavoe.com> wrote:
> 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

I tried to follow this recipe, however, not fully succeeded...
1) I ran 'hg pull' and 'hg update' in my $PLAN9 directory.
2) My computer has a name 'bluestar' (output of 'hostname').
3) I created the testing message 'mesg'.
4) I added the key to factotum by running:
factotum -g 'proto=pass role=client server=bluestar service=smtp
user=rudolf.sykora@gmail.com !password?'
and I entered my gmail password when promted.
5) I issued:
sudo /usr/sbin/stunnel3 -c -d 12345 -r smtp.gmail.com:465
6) then issued:
$PLAN9/bin/upas/smtp -ai 'tcp!bluestar!12345' rudolf.sykora@gmail.com
rudolf.sykora@cern.ch <msg
and got this:
smtp: bad network /net/tcp!bluestar!12345 (tcp!bluestar!12345)
so I tried
$PLAN9/bin/upas/smtp -ai 'tcp!128.141.146.215!12345'
rudolf.sykora@gmail.com rudolf.sykora@cern.ch <msg
where 128.141.146.215 is my current ip address. (What and where should
I add so that the name bluestar would be resolved? I obtain the ip
using dhcp, thus it can vary from boot to boot, together with the
domain...) The result is:

Fri Sep  9 21:34:17 CES 2011 connect to tcp!128.141.146.215!12345:
250-mx.google.com at your service, [128.141.146.215]
250-SIZE 35882577
250-8BITMIME
250-AUTH LOGIN PLAIN XOAUTH
250 ENHANCEDSTATUSCODES

but it does not seem like any email has been sent anywhere...

Btw. I don't quite understand what '9fans@hamnavoe.com' really stands
for. Plan9 man page says it should perhaps be a sender, but then, I
want to send as if from my gmail account; and more, even from gmail
web I can send under different names, but these are not arbitrary, but
must have been varified in advance. So should there stand any of these
addresses I can use when sending from the web interface?

Thanks for help!

Ruda