9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mail client; general question web vs command
Date: Fri,  9 Sep 2011 21:48:35 +0200	[thread overview]
Message-ID: <CAOEdRO3f7oLw5UmoNu3L4q88PE-be6UEAWEAGLFJ6o2MPjhLxg@mail.gmail.com> (raw)
In-Reply-To: <9182f5f061e27da9ee652cf9ccc11c82@hamnavoe.com>

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



  reply	other threads:[~2011-09-09 19:48 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-31 20:00 Rudolf Sykora
2011-07-31 20:14 ` Jacob Todd
2011-08-02  4:36   ` Akshat Kumar
2011-08-04 15:49   ` Mathieu Lonjaret
2011-08-06 14:16     ` Rudolf Sykora
2011-08-11 10:42       ` Rudolf Sykora
2011-08-11 10:54         ` Mathieu Lonjaret
2011-08-11 10:55           ` Mathieu Lonjaret
2011-08-13 18:38           ` Rudolf Sykora
2011-08-13 23:26             ` Fazlul Shahriar
2011-08-14 14:50               ` Rudolf Sykora
2011-08-13 23:40             ` Mathieu Lonjaret
2011-08-27 17:59           ` Rudolf Sykora
2011-08-11 12:20         ` Fazlul Shahriar
2011-08-11 16:34           ` John Floren
2011-08-11 17:55             ` David du Colombier
2011-08-28 14:09               ` Rudolf Sykora
     [not found]               ` <CAOEdRO1k0X8tU+QMazETGs2rT4NmMazWPJSDN_79Wd=TbcrHzA@mail.gmail.c>
2011-08-28 15:15                 ` erik quanstrom
2011-08-28 18:22                   ` Rudolf Sykora
2011-08-31 14:22                     ` Richard Miller
2011-09-09 19:48                       ` Rudolf Sykora [this message]
2011-09-14 12:39                         ` Richard Miller
2011-09-19 13:06                           ` Rudolf Sykora
2011-09-20  7:47                             ` David du Colombier
2011-09-21 15:46                               ` Rudolf Sykora
2011-11-16 19:12                                 ` David du Colombier
     [not found]                       ` <CAOEdRO3f7oLw5UmoNu3L4q88PE-be6UEAWEAGLFJ6o2MPjhLxg@mail.gmail.c>
2011-09-10 11:29                         ` erik quanstrom
2011-08-27 17:51     ` Rudolf Sykora
2011-07-31 21:17 ` dexen deVries
2011-08-01  4:22   ` hiro
2011-08-01 11:18 ` Ethan Grammatikidis
2011-08-02 20:32 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-08-02 13:07 erik quanstrom
2011-08-02 13:42 ` Russ Cox
2011-08-02 15:02   ` Charles Forsyth
2011-08-02 19:20     ` David Leimbach
2011-08-03 22:18   ` Akshat Kumar

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=CAOEdRO3f7oLw5UmoNu3L4q88PE-be6UEAWEAGLFJ6o2MPjhLxg@mail.gmail.com \
    --to=rudolf.sykora@gmail.com \
    --cc=9fans@9fans.net \
    /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).