Maybe a special Unix "group" could be configured -- and then qpopper would
refuse to leave-copy-on-server for them only?
_F
At 09:48 AM 7/11/2001 -1000, Clifton Royston wrote:
>On Wed, Jul 11, 2001 at 02:15:20PM -0400, Forrest Aldrich wrote:
> > My biggest reason for this is that we have some users who connect via
> > dialup, and continue to complain that their connection drops -- and
> after X
> > times explaining to them that their mail file is 10meg (etc), they
> continue
> > the same pattern.
> >
> > In a case like that I just assume have a config file
> >
> > [ /usr/local/etc/qpopper.conf ]
>
>This of course you can do just by pointing qpopper at it from the
>command line: -f /usr/local/etc/qpopper.conf
>
> > leavemailauth: user1, user2, user3
> >
> > And the rest would not be permitted to leave-copy-on-server.
>
> Hmmm, I like the intent. A problem I see is that this doesn't seem
>like it would scale very well to large numbers of users. It also
>doesn't seem to generalise for the reverse (which I'd prefer) of
>denying leave-mail to a small list of users, or generalise for the
>other types of parameters one might want to set on a per-user basis.
>
> I'd really like to come up with a more general solution that fits the
>current clean config file design, but allows one to adjust a range of
>settings per user from a centralised file or files instead of one per
>user. I am thinking about a possible way to implement that with clean
>syntax and acceptable performance.
>
> -- Clifton
>
>--
> Clifton Royston -- LavaNet Systems Architect -- [EMAIL PROTECTED]
> WWJD? "JWRTFM!" - Scott Dorsey (kludge) "JWG" - Eddie Aikau
