Okay, I see what you're saying now.
This still isn't a very scalable solution to the problem.
There simply is NO WAY I'm going to create (and maintain) per-user
.qpopper-options files.
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.
_F
At 06:17 PM 7/18/2001 -0700, you wrote:
>At 08:53 PM 7/18/2001 -0400, Forrest Aldrich wrote:
>>I've been using Adobe Acrobat to search the GUIDE.pdf about auto-delete
>>in the configuration file, as you suggested I do. I am unable to find
>>any reference about how to use auto-delete in a configuration file to
>>allow certain people to leave-a-copy-on-server and vise-versa.
>>
>>Perhaps you could point me to a page number or?
>
>Configuration files inherently allow most options to be set per-user; it's
>not specific to auto-delete.
>
>The auto-delete option seems to be missing from the table on page 28, I
>apologize. (It is mentioned as a configuration file option on page 13,
>but that's no substitute.)
>
>You can use the '-U' command-line option (page 26) or the 'spool-options'
>option (page 36) in a global configuration file to enable per-user
>configuration files in the spool directory. The file should NOT be
>writable by the user.
>
