Subject: | Re: Problem using reject_with: in access block
| Date: | Wed, 1 Oct 2003 10:35:41 +0000 (UTC)
| From: | jeff@litech.org (Jeffrey M. Vinocur)
| Newsgroups: | news.software.nntp
|
In article <blcet1$jkl$1@antonio.escomposlinux.org>,
Antonio <antonio@escomposlinux.org> wrote:
>
>Hi. I am trying to add new functionality to my readers.conf file (I'm
>using inn 2.4) by using the reject_with: feature in one of my access
>blocks.
Keep in mind that most clients are prepared to handle a 480
authentication required message (which they will get if all of
your auth blocks have an auth line and no res line) by prompting
the user for appropriate information. You probably want to save
reject_with for when you want to permanently deny someone for
some reason.
>Well, every user conecting to my server must provide a suitable
>user/pass pair; otherwise he won't be able to read/post at all. I
>have created several user/pass databases so that each user is matched
>to one of several existing "auth:" blocks and given different access
>rights to the server by means of corresponding "access:" blocks.
Ah ha, here's your problem. If all of the password databases
apply to all IP addresses, you need to put them all in a single
auth block. (You can have multiple lines in an auth block.)
Note that you probably don't want to be using the key: parameter.
--
Jeffrey M. Vinocur
jeff@litech.org
|