Constant issus! -- any help would be great!

Jeff Mills Jeff.Mills at versacold.com.au
Mon May 26 23:55:18 IST 2008


	 

>	This server I am trying to fix is having these problems below 
>
>	May 26 10:14:51 jjfw MailScanner[46682]: Using SpamAssassin
results cache 
>	May 26 10:14:51 jjfw MailScanner[46682]: Connected to
SpamAssassin cache database 
>	May 26 10:14:51 jjfw MailScanner[46682]: Enabling SpamAssassin
auto-whitelist functionality... 
>	May 26 10:14:55 jjfw MailScanner[46683]: MailScanner E-Mail
Virus Scanner version 4.67.6 starting... 
>	May 26 10:14:56 jjfw MailScanner[46683]: Read 748 hostnames from
the phishing whitelist 
>	May 26 10:14:56 jjfw MailScanner[46683]: Could not read phishing
blacklist file  
>	May 26 10:14:56 jjfw MailScanner[46683]: User's home directory
/var/spool/postfix is not writable 
>	May 26 10:14:56 jjfw MailScanner[46683]: You need to set the
"SpamAssassin User State Dir" to a directory that the "Run As User" can
write to 
>	May 26 10:14:56 jjfw MailScanner[46683]: SpamAssassin temporary
working directory is /var/spool/MailScanner/incoming/SpamAssassin-Temp
> This happens every single time a update is done in the software. I had
these issues at home and rebuilt my server how ever being this is a
server in major corporation I just can't come in there and reinstall it.


You have the problem when postfix is upgraded, because postfix does not
want /var/spool/postfix written by any other user. During the install
process, the postfix directory has its permissions reset by the
installer.
On my system, MailScanner is running as the postfix user.
The error message also tells you where to look.
Have you set SpamAssassin User State Dir?
If not, set it to a directory that your mailscanner user has write
access to, otherwise it will use /var/spool/postfix, and you will keep
having problems every time postfix is reinstalled or upgraded.



More information about the MailScanner mailing list