9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gmail's new POP features + upas/fs
Date: Wed, 24 Nov 2004 10:10:14 +0000	[thread overview]
Message-ID: <83a7be48b17d96a4d3d9207cebcdc618@hamnavoe.com> (raw)

russcox@gmail.com says:

> Well, yes and no.  It does use the UIDs but also depends
> on ordering.  ...
> 
> I don't think this is Gmail's problem.  If that were happening,
> the messages would just look reordered.

Having tried it myself now, I see what Russ means.  I did find with
demon.co.uk that the server's reordering of messages confused upas/fs
sufficiently that some would seem to disappear.  But gmail's trouble
is more fundamental - after you've fetched the messages once, it
replies +OK 0 0 to subsequent STAT commands.  Because upas/fs
keeps reattaching to the server to refresh its list, it sees an
apparently empty list and therefore deletes its own copy of messages
to keep in sync.

I wonder if this causes trouble with any other pop clients?

I suppose we could add a "gmail compatibility" flag to upas/fs/pop3
to stop it from deleting its copies of messages except by
explicit local request.  This would allow it to be used for
fetching stuff (once) from gmail to be copied to a local mailbox.

-- Richard



             reply	other threads:[~2004-11-24 10:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 10:10 Richard Miller [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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-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
     [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

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=83a7be48b17d96a4d3d9207cebcdc618@hamnavoe.com \
    --to=9fans@hamnavoe.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).