I suggested the group thing previously, whereby if people were in a certain
unix group, they could use leave-copy-on-server. Or vise-versa.
At 10:53 PM 7/18/2001 -0700, Randall Gellens wrote:
>At 11:12 PM -0400 7/18/01, Forrest Aldrich wrote:
>
>> There simply is NO WAY I'm going to create (and maintain) per-user
>> .qpopper-options files.
>
>You only need to create them for users who are the exception. In your
>case, you'd add 'set auto-delete' to a global configuration file, and then
>you'd only need per-user files for those users who are allowed to leave
>mail on the server.
>
>>
>> What we need is a configure (compile-time) or other option that will
>> allow us to fine-tune this feature.
>>
>> A global configuration file that has a list of names of people ALLOWED
>> to leave-a-copy-on-server would suffice -- in a larger situation, you
>> might need a *.db file for faster lookups.
>
>Or perhaps group membership, such as is available for server mode. A
>database isn't a bad idea, it's just more work to do it generalized.
>Presumably all available per-user options would be settable using the
>database. There would have to be a UI to update user options, something
>like what's now down for APOP.
>
>
>
