On Thu, 2008-05-15 at 10:46 +1200, Kathryn Kleinschafer wrote:
> I run the update via a crontab entry (set when logged in as root) how do
> I specify who its done by and what the umask is?
Edit the crontab as the user you want it to be run. Alternatively, have
a look at 'man crontab'.
> spamassassin is run by postfix user - all this part of the setup should
> be fine as I haven't played with the config files and it had all been
> running well.
>
> I run the test as user postfix to ensure I get the same results as when
> the automatic tests run.
> David B Funk wrote:
> > Also look to see what User-ID your SA filtering process runs as
> > and then check to see if there are some parts of your SA setup or
> > your Perl installation that aren't properly readable/usable by that
> > User-ID.
> > (for example, if an update was done as 'root' with a umask of 077
> > then the installed rules/updates would not be useable by anybody
> > else).
The debug output pasted earlier seems to hint that the updates are at
least readable, I believe. Though the debug output only showed a tiny
fraction of the very first part:
dbg: config: read file /var/lib/spamassassin/3.00x00y/sought_rules_yerp_org.cf
Does it actually read the files in the update channel dirs? Something
like this, below the point where the debugging output has been snipped.
dbg: config: read file
/var/lib/spamassassin/3.00x00y/sought_rules_yerp_org/20_sought.cf
guenther
--
char *t="[EMAIL PROTECTED]";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
