From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <83a7be48b17d96a4d3d9207cebcdc618@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gmail's new POP features + upas/fs
From: Richard Miller <9fans@hamnavoe.com>
Date: Wed, 24 Nov 2004 10:10:14 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 0b98a04e-eace-11e9-9e20-41e7f4b1d025

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