Re: [9fans] mail client; general question web vs command

[Rudolf Sykora <rudolf.sykora@gmail.com>]

Hello,

On 28 August 2011 17:15, erik quanstrom <quanstro@quanstro.net> wrote:
>> now when I try (74.125.39.108 should be smtp.gmail.com):
>> cat q | upas/smtp -a -d -h a.com 74.125.39.108 rudolf.sykora@gmail.com
>> rsykora@cern.ch
>
> i'm confused.  are you using plan 9 or p9p?

p9p now

> i would think that a.com is wrong. you need to use your real domain.

you may well be right. I have no idea what/why I should write there. I
am using a notebook that is used regularly at diferent places and the
only thing I now want is to pass my e-mail to gmail via smtp (where I
have an account) so that it then can be sent further. Thus I'd expect
that all I need is i) the mail itself with the info to whom it should
be sent, and ii) login/password for the gmail account. I don't see any
reason for any other domain name... I just wrote that a.com there so
that there is something (so, simply, understand that I do not
understand...).

> also i think you want the real target system, not an ip address.
> mx lookup for google isn't broken for me.
>
>        ; fn mxquery {x=`{ndb/dnsquery google.com mx | sort +1n | sed 1q}; echo $x(4)>[1=2]; ndb/dnsquery $x(4)}
>        ; mxquery google.com >[2=]
>        aspmx.l.google.com ip   74.125.47.27

well, is there any difference if I use smtp.gmail.com or the
corresponding ip? (for the former to work I need, I have a feeling,
add sth somewhere [ndb?], so the ip was easier for the experiment).

> on plan 9, upas typically uses /mail/lib/remotemail to send
> to remote systems.  my remotemail looks like
>
>        #!/bin/rc
>        sender = $1; addr = $2; * = $*(3-)
>        fd=`{/bin/upas/aliasmail -f $sender}
>        switch($fd){
>        case *.*
>                ;
>        case *
>                fd=quanstro.net
>        }
>        exec /bin/upas/smtp -h $fd $addr $sender $*
>

on p9p a similar thing is also in remotemail...

> this is invoked by qmail/kickqueue which are tickled
> by sending mail and/or a cron job.
>
>        ; cat /cron/upas/cron
>        # kick mail retries (replace ladd with your system)
>        0,10,20,30,40,50 * * * *        ladd            /bin/upas/runq -a /mail/queue /mail/lib/remotemail
>
>        # clean up after grey list
>        47 4 * * *      ladd    rm -rf /mail/grey/tmp/*/*
>
> ymmv, and there may be nupasisms in here.
>
> - erik

Ok. But putting aside the way how different programs are invoked,
finally there is always that line with
/bin/upas/smtp -h $fd $addr $sender $*
that actually sends the mail (which it reads from stdin). This line of
yours has to have -a added since gmail needs authentication (so
finally a key in factotum). So before engaging the rewrite,
remotemail, vf, qer, runq, ... (?) programs, I would like to be able
to send an email using just this and be sure it works...

Thanks
Ruda