From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] P9P gmail
Date: Thu, 11 Jun 2009 19:55:44 -0400 [thread overview]
Message-ID: <299c13be4f86597ccd5d7752dd2c959f@quanstro.net> (raw)
In-Reply-To: <3aaafc130906111514l1991f1bfp6c56c14d073877f6@mail.gmail.com>
On Thu Jun 11 18:39:02 EDT 2009, jrm8005@gmail.com wrote:
> That doesn't help. Ridiculously complex or not, I have a mutt that can
> talk to gmail via smtp. I've tried following the basic guide on the
> wiki for getting smtp to work, but it is plan9-specific and not very
> instructive.
i ported all of upas to p9p at one point. unfortunately the quality
of the port is not very good and the code is very old and mouldy.
/n/sources/contrib/quanstro/p9p/upas.tbz
a quick scan of the code says that for a p9p solution, you'll need
to get marshal working. then you'll have to decide if you want to
port send and smtp or fight^w work with the local mailer.
- erik
prev parent reply other threads:[~2009-06-11 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 22:15 J.R. Mauro
2009-06-11 5:42 ` Ethan Grammatikidis
2009-06-11 22:14 ` J.R. Mauro
2009-06-11 23:55 ` erik quanstrom [this message]
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=299c13be4f86597ccd5d7752dd2c959f@quanstro.net \
--to=quanstro@quanstro.net \
--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).