9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] gmail 0: messages
Date: Wed,  7 Dec 2005 13:56:10 -0500	[thread overview]
Message-ID: <ee9e417a0512071056p3746db9dr2fe94d2de5a5990b@mail.gmail.com> (raw)
In-Reply-To: <20051207102914.247b74ab.countryjoe@myrealbox.com>

> I'm out of option for now as how to get my gmail emails on my plan9 box.

Gmail pop is not compatible with Plan 9.  Gmail
assumes that clients are running in what is
usually called "move messages off the server"
mode, and so once the client has downloaded a
message, gmail doesn't show the message to the
client again.  This confuses upas/fs, which
expects to see the same set of messages the next
time it connects, assuming that if a message is
gone, it has been deleted.

In Gmail's defense, they're using pop3 in a
context it wasn't designed for, namely having
thousands or more messages to show the user.
Rather than respond to the "list messages" command
with thousands of lines, they show 100, and once
those 100 have been downloaded, they show the next
100.  It works for clients that use pop3 as a
download protocol, but not for clients that want
to leave the messages on the server.

Upas/fs isn't the only pop3 client that gmail
confuses.  My roommate's cell phone exhibits
exactly the same problem: it downloads enough to
show the message list, and then when you open a
message, it tries to redownload the message, but
the message is gone.  So you can see the message
but not open it.

You could run a separate pop3 fetch program and
then deliver the mail to a local Plan 9 mail box.
See /n/sources/contrib/rsc/cmd/pop3get.c.

You cannot use gmail's pop server directly.

Russ


  reply	other threads:[~2005-12-07 18:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 17:29 Philippe from Myrealbox
2005-12-07 18:56 ` Russ Cox [this message]
2005-12-07 20:47   ` Russ Cox
2005-12-08  1:17   ` Adrian Tritschler
2005-12-08  1:28     ` Russ Cox
2005-12-08  3:00       ` Adrian Tritschler
2005-12-08  3:59         ` Rob Pike
2005-12-08  7:36         ` geoff
2005-12-08  1:30     ` Uriel
2005-12-08  2:27       ` Adrian Tritschler
2005-12-08  2:35         ` John Floren
2005-12-09 16:13           ` David Leimbach
2005-12-09 22:56             ` Paweł Lasek

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=ee9e417a0512071056p3746db9dr2fe94d2de5a5990b@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    /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).