From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Reading gmail
Date: Mon, 14 May 2012 20:51:41 -0700 [thread overview]
Message-ID: <CAL4LZyg1e-kE1+skSpo==ce6qUS3ysq8KUhe56cLyL+4YO7hMA@mail.gmail.com> (raw)
In-Reply-To: <e317a788351d67799c33275b85b56d65@sp.inri.net>
On Mon, May 14, 2012 at 8:08 PM, <sl@9front.org> wrote:
>> Is there any way to read gmail from plan9? Over SSL imap
>> maybe? I searched for imapfs but came up with nothing.
>
> Mount your gmail account via IMAP:
>
> upas/fs -f /imaps/imap.gmail.com/username@gmail.com
>
> The first time you try this, upas/fs will complain:
>
> upas/fs: opening /imaps/imap.gmail.com/username@gmail.com: imap.gmail.com/imaps:server certificate HASH not recognized
>
> Add the provided certificate to /sys/lib/tls/mail, like so:
>
> x509 sha1=HASH
>
> Run the upas/fs line again, and this time gmail via IMAP will
> be mounted in /mail/fs, accessible to the standard mail tools.
>
> -sl
>
If you have a large number of messages, Erik's "nupas" is useful; IIRC
it will cache messages locally so you don't have to download a ton of
headers each time you start upas.
However I've found that with both old upas and nupas, there are some
messages that make them choke. Sadly I can't remember what triggered
it.
john
next prev parent reply other threads:[~2012-05-15 3:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 2:51 Burton Samograd
2012-05-15 3:08 ` sl
2012-05-15 3:51 ` John Floren [this message]
2012-05-15 3:57 ` Matthew Veety
2012-05-15 8:43 ` erik quanstrom
2012-05-20 3:30 ` Matthew Veety
2012-05-20 12:45 ` erik quanstrom
2012-05-20 12:47 ` Matthew Veety
2012-05-20 13:02 ` erik quanstrom
2012-05-20 13:15 ` Kurt H Maier
2012-05-20 13:15 ` Bruce Ellis
2012-05-15 15:56 ` Anthony Sorace
2012-05-15 16:04 ` sl
2012-05-19 17:37 ` Akshat Kumar
2012-05-19 20:31 ` Charles Forsyth
2012-05-19 20:42 ` Anthony Sorace
2012-05-19 20:54 ` Steve Simon
2012-05-19 21:06 ` Charles Forsyth
2012-05-19 22:33 ` Kurt H Maier
2012-05-19 23:11 ` Nemo
2012-05-20 20:50 ` Ethan Grammatikidis
[not found] ` <CABwSpPCb0DrkDocY4Qg=8814HB1Ws=uF=jnGbcDy4j-1U7Y7Ag@mail.gmail.c>
2012-05-19 21:39 ` erik quanstrom
2012-05-15 4:08 ` 9 9
2012-05-15 5:37 ` 9 9
2012-05-15 6:41 ` Federico Benavento
2012-05-15 6:46 ` 9 9
2012-05-15 7:01 ` John Floren
2012-05-15 13:50 ` 9
2012-05-15 6:41 ` 9 9
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='CAL4LZyg1e-kE1+skSpo==ce6qUS3ysq8KUhe56cLyL+4YO7hMA@mail.gmail.com' \
--to=john@jfloren.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).