Inconsistent SpamAssassin report

[Peter Lemieux]

On most implementations only root will have access to /root/.spamassassin 
since /root usually has 700 permissions or more limited ones.

Is MailScanner running as the postfix user or as root?  If the latter, those 
permission errors shouldn't arise during scans run from MailScanner.

What happens if you run your tests as root?

Did I miss it, or did you not identify which platform you're running 
MailScanner on?  I stick with CentOS for servers.  In my experience 
MailScanner has installed and run flawlessly on that distribution for years.

Peter


On 02/07/2017 12:54 PM, Diederik van den Burger wrote:
> Thanks for your help by the way. When I run the following command:
>
> spamassassin -t -d -C /etc/MailScanner/spamassassin.conf < spamemail
> or even
> sudo su postfix -p -c "spamassassin -t -d -C
> /etc/MailScanner/spamassassin.conf < spamemail"
>
> I still get the following warnings:
>
> Feb  7 17:52:36.156 [4359] warn: config: path "/root/.spamassassin" is
> inaccessible: Permission denied
> Feb  7 17:52:36.157 [4359] warn: config: path
> "/root/.spamassassin/user_prefs" is inaccessible: Permission denied
> Feb  7 17:52:36.157 [4359] warn: config: default user preference file
> /root/.spamassassin/user_prefs not accessible: Permission denied
>
> And furthermore, I also don't get a spam report anymore. It says:
> "(no report template found)"
> Is this expected behaviour?
>
>
> Best regards,
> Diederik