From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b520fd26307a28aaad4bce960dcff740@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gmail's new POP features + upas/fs
From: Richard Miller <9fans@hamnavoe.com>
Date: Tue, 23 Nov 2004 21:34:16 +0000
In-Reply-To: <ee9e417a041122191933083bdf@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 0a6a1ec8-eace-11e9-9e20-41e7f4b1d025

russcox@gmail.com says:

> Upas/fs really expects that it's manipulating
> a permanent mailbox.  It's not a typical usage
> of pop (the typical usage is download, perhaps delete
> from server, and keep locally even if the message
> disappears from the server) but it usually works.
> Gmail might be breaking the rules.

The upas/fs pop3 code uses message numbers, not UIDs,
to identify messages on the server, and expects that
messages will be in the same order each time the client
reconnects.  I found this expectation wasn't true with
the demon.co.uk server, and indeed it doesn't seem to
be stipulated anywhere in the RFCs.

I made a modification to upas/fs/pop3.c to use UIDs,
which seemed to work reliably with demon - can't
remember whether I submitted it to sources, but I
switched to a different provider soon afterwards so
I stopped using it.

The same modification might help with gmail - if I
had a gmail account I could try it and see ;)

-- Richard