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...
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...
Rgds,
-GSH
Randall Gellens wrote:
> At 1:00 PM -0400 7/11/01, Forrest Aldrich wrote:
>
>> I know there is a ./configure switch to disable this -- however, it
>> might be desirable to have a config file to allow certain users to
>> leave-a-copy-on-server and others not to. I know that adds another
>> level of complexity, but it would be useful.
>
>
> Well, there's 'auto-delete'. You can set that one way as a default (at
> compile-time or in a global configuration file), and set it the other
> way in a user-specific configuration file.
