At 2:40 PM +0000 7/14/01, Gu�bj�rn Hreinsson wrote:
> I have been wondering what clients would do in this case.
>
> - client accesses maildrop via pop
> - retrives new email but doesn't delete them
> - disconnects and server (qpopper) deletes the retrieved
> messages
> - client connects to maildrop at a later time via pop
> - client doesn't find the mails it had retrieved earlier
> (uidl for this messages are missing)
> ??- client keeps messages deleted by server in local maildrop?
> ??- client deletes messages deleted by server from local maildrop?
>
> The latter would obviously be unkindly to your [non]paying customer...
Eudora will keep the messages, but indicate in the "server status"
column that the messages no longer exist on the server.
This is the same situation as when someone tells the client to
delete certain messages from the server. Other clients for the
same user will find those messages no longer on the server. This
is normal and expected.
The situation is reversed when using IMAP, by the way. In POP, the
local client has the "master" storage of messages. Messages exist
on the server only temporarily. Thus it is quite normal for
clients to have messages that are no longer on the server.
In contrast, with IMAP the server has the master copy of all
messages. Clients have only local cache, presumed to be temporary.
>
> I think this "Leave mail on server" thing is the worst that has
> happened in mail client access, the only benefits are if you are
> accessing your maildrop from many locations/clients... but often
> leads to that clients don't know they are accumulating space on
> the server and don't know even how to get rid of it causing a lot
> of wasted helpdesk resources...
Eudora makes it fairly easy for users to check what's on the server
and delete what they don't want, or delete everything that is on
the server. Just hold down option (on a Mac) or shift (on Windows)
when checking mail. Eudora pops up a dialog with many useful
options.
