From: Russ Cox <russcox@gmail.com>
To: David Leimbach <leimy2k@gmail.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] gmail's new POP features + upas/fs
Date: Mon, 22 Nov 2004 15:25:11 -0500 [thread overview]
Message-ID: <ee9e417a04112212254ec74c79@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60411221137352dce88@mail.gmail.com>
> According to this it's POP3 with ssl:
> http://gmail.google.com/support/bin/answer.py?answer=13287
>
> is that done with /pop/? I'm confused.
Actually it wasn't done at all. But now it can
be done with /pops/. The difference between
/pops/ and /poptls/ is that /pops/ means dial
port 995 and start SSL/TLS immediately, while
/poptls/ means dial port 110 as usual and
then issue a STLS command during handshaking
to start SSL/TLS. Why have one way to do it
when you could have two?
I just wrote the code and pushed it to sources --
pull to get a new source and binary.
I can now get at (the oldest 300 messages of) my
gmail with upas/fs -f/pops/pop.gmail.com/russcox.
Russ
next prev parent reply other threads:[~2004-11-22 20:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 6:07 David Leimbach
2004-11-22 13:05 ` Russ Cox
2004-11-22 19:37 ` David Leimbach
2004-11-22 20:25 ` Russ Cox [this message]
[not found] ` <b5a997b232d9134198a35ef32e607841@plan9.ucalgary.ca>
2004-11-22 21:01 ` Russ Cox
2004-11-22 21:03 ` David Leimbach
2004-11-23 1:24 ` David Leimbach
2004-11-23 1:36 ` andrey mirtchovski
2004-11-23 2:05 ` David Leimbach
2004-11-23 2:51 ` andrey mirtchovski
2004-11-23 3:06 ` David Leimbach
2004-11-23 3:08 ` David Leimbach
2004-11-23 3:10 ` David Leimbach
2004-11-23 2:46 ` Russ Cox
2004-11-23 3:14 andrey mirtchovski
2004-11-23 3:19 ` Russ Cox
2004-11-23 3:33 ` andrey mirtchovski
2004-11-23 21:34 ` Richard Miller
2004-11-23 21:45 ` andrey mirtchovski
2004-11-23 21:54 ` Christopher Nielsen
2004-11-23 22:13 ` andrey mirtchovski
2004-11-24 2:21 ` Russ Cox
2004-11-24 2:45 ` boyd, rounin
2004-11-24 3:46 ` boyd, rounin
2004-11-23 3:23 ` David Leimbach
2004-11-24 10:10 Richard Miller
2004-11-24 13:44 ` Russ Cox
2004-11-24 14:01 ` Richard Miller
2004-11-24 16:24 ` David Leimbach
2004-11-24 16:57 ` Steve Simon
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=ee9e417a04112212254ec74c79@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=leimy2k@gmail.com \
/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).