Spamassassin & amavisd-new

[Joe McDonagh]

Laurent Dinclaux wrote:
> Hello,
>
> I have setup amavisd-new with spamassassin and clamav as stated in
> ubuntu sever documentation.
>
> Virus scanning is ok but not spam scanning. (I don't have spamassassin
> headers in scanned emails)
>
> Logs:
> Apr  9 13:38:27 geckahost amavis[5410]: Using primary internal av
> scanner code for ClamAV-clamd
> Apr  9 13:38:27 geckahost amavis[5410]: Found secondary av scanner
> ClamAV-clamscan at /usr/bin/clamscan
> Apr  9 13:38:27 geckahost amavis[5410]: Creating db in
> /var/lib/amavis/db/; BerkeleyDB 0.34, libdb 4.6
> Apr  9 13:38:27 geckahost amavis[5410]: SpamControl: initializing
> Mail::SpamAssassin
> Apr  9 13:38:27 geckahost amavis[5410]: SpamAssassin debug facilities: info
> Apr  9 13:38:27 geckahost amavis[5410]: _WARN: config: cannot open
> "/etc/spamassassin/local.cf": 13
> Apr  9 13:38:33 geckahost amavis[5410]: SpamControl: init_pre_fork on
> SpamAssassin done
> Apr  9 13:38:33 geckahost amavis[5413]: TIMING [total 8 ms] -
> bdb-open: 8 (100%)100, rundown: 0 (0%)100
> Apr  9 13:38:33 geckahost amavis[5413]: SpamControl: init_child on
> SpamAssassin done
> Apr  9 13:38:33 geckahost amavis[5414]: TIMING [total 7 ms] -
> bdb-open: 7 (100%)100, rundown: 0 (0%)100
> Apr  9 13:38:33 geckahost amavis[5414]: SpamControl: init_child on
> SpamAssassin done
>
> regards
>
>   
The amavis user most likely does not have read privs to 
/etc/spamassassin, the how-to or whatever you used probably listed a 
group or groups that amavis should belong to so this doesn't happen. 
(Among other privilege problems)