> From dwolfe@risc.sps.mot.com Tue Jan 7 11:50:28 1997
> Subject: Re: Possible bug in access_check
> To: lou@metron.com (Lou Katz)
> Date: Tue, 7 Jan 1997 13:19:09 -0600 (CST)
> [ Lou Katz writes: ]
> >
> > I set restrict_post to the list and its digest:
> > /pathtolist/lists/listname:/pathtolist/lists/listname-digest.
> [...]
> > On inspection, it appears that the section in access_check that looks
> > at the restrict_post prepentds the path, so that by the time the check
> > gets done for the commands, it is looking in
> >
> > /pathtolist//pathtolist/lists/listname
> >
> > which fails.
>
> If it failed opening the files, you'd get a warning message.
> It prepends the list directory *only* when the individual file
> paths *don't* start with '/'.
>
> RESTRICT:
> foreach $file (@files) {
> # add $listdir if not explicitly set.
> #
> $file = "$listdir/$file" if ($file !~ /^\//);
> ^^^^^
>
> --
> Dave Wolfe
>
Thanks, but the code you quoted is in 'check_sender', not in access_check.
In access check the code is different and fails.
jjr@databook.com (Jim Reisert) suggested that I only put
listname:/pathtolists/lists/listname-digest
in the restrict-send variable in config, and that worked.
-=[Lou Katz]=-
~
Follow-Ups:
References:
|
|
