Zbigniew Szalbot wrote:
> Hello,
>
>
>> Try setting 755 on the data directory.
>
> Done. No change so far.
>
>> And how about the permissions on...
>>
>>
>> /var/db/dspam
> $ l /var/db/dspam
> drwxr-xr-x 4 www mailnull 512 Jan 31 22:09 data
>
>> /var/db/dspam/data
> $ l /var/db/dspam/data
> drwxr-xr-x 3 www mailnull 512 Jan 31 22:09 lists.lc-words.com
> drwxr-xr-x 5 www mailnull 512 Feb 1 00:40 szalbot.homedns.org
>
>> /var/db/dspam/data/szalbot.homedns.org
> $ l /var/db/dspam/data/szalbot.homedns.org
> drwxr-xr-x 2 www mailnull 512 Jan 31 21:01 zbyszek
>
>> Also, make sure your cgi-bin/configure.pl matches your setup.
>
> I include the settings that have something to do with paths:
>
> $CONFIG{'DSPAM_HOME'} = "/var/db/dspam";
> $CONFIG{'DSPAM_BIN'} = "/usr/local/bin";
> $CONFIG{'DSPAM'} = $CONFIG{'DSPAM_BIN'} . "/dspam";
> $CONFIG{'DSPAM_STATS'} = $CONFIG{'DSPAM_BIN'} . "/dspam_stats";
> $CONFIG{'DSPAM_ARGS'} = "--deliver=innocent --class=innocent " .
> "--source=error --user %CURRENT_USER% -d %u";
> $CONFIG{'TEMPLATES'} = "./templates"; # Location of HTML templates
>
> $CONFIG{'WEB_ROOT'} = "http://lists.lc-words.com/dspam/htdocs"; # URL
> location of included htdocs/ files
>
> $CONFIG{'3D_GRAPHS'} = 1;
> $CONFIG{'OPTMODE'} = "NONE"; # OUT=OptOut IN=OptIn NONE=not
> selectable
> $CONFIG{'LOCAL_DOMAIN'} = "lists.lc-words.com";
>
> # Add customized settings below
> $CONFIG{'LOCAL_DOMAIN'} = "lists.lc-words.com";
>
> $ENV{'PATH'} = "$ENV{'PATH'}:$CONFIG{'DSPAM_BIN'}";
>
> # Autodetect filesystem layout and preference options
> $CONFIG{'AUTODETECT'} = 1;
>
> #$CONFIG{'AUTODETECT'} = 1;
> #$CONFIG{'LARGE_SCALE'} = 1;
> #$CONFIG{'DOMAIN_SCALE'} = 1;
> #$CONFIG{'PREFERENCES_EXTENSION'} = 1;
>
> $CONFIG{'DSPAM_CGI'} = "dspam.cgi";
>
> Many thanks for taking your time to help. It is probably something obvious
> but not sure what it is. It has something to do with permissions because
> the webui does not display the stat data. So it is not only write
> permission problem but either path or read permission problem, too.
Or possible it can not find the files it is looking for.
I usually investigate these things using sudo. Set yourself up as
a sudo user if you haven't already, and do "sudo -u www -s".
That will start a new shell and you'll be the www user during
that session. Now walk around in your directories and files.
When you try to read, it's the www user trying to read, and
when you try to write...etc.
Also, have a look at the webserver log, it would usually show
you what file it tries to read.
/L