At 3:22 PM -0400 7/19/01, Forrest Aldrich wrote:
> Either way, we do need a better solution to the all-or-nothing
> approach (and some alternative to individual .qpopper-config
> files)....
As I said, a general database of user options could be built
without too much work; something like what is now done for APOP. A
simple Berkeley database with the username as the key (same as for
APOP) and one or more options as the value. A tool something like
popauth would be used to set and query options for users. It could
even be added to the APOP database, but for security and other
reasons it may be better not to.
