• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Spamassassin error

M

marcosacramento

Guest
Hello,

I'm getting this error in my log:
Cannot open bayes databases /var/qmail/mailnames/domain.com/user/.spamassassin/bayes_* R/O: tie failed: Permission denied

Could anyone help me to solve this?

Thanks in advance.
 
Did you go to the dir in question and check if the bayes_seen and bayes_toks files exist? Also they should be owned by popuser.


-rw------- 1 popuser popuser 12288 Dec 17 12:11 auto-whitelist
-rw-r----- 1 popuser popuser 12288 Jan 2 22:23 bayes_seen
-rw-r----- 1 popuser popuser 94208 Jan 2 22:23 bayes_toks
-rw-r----- 1 popuser popuser 55 Dec 17 12:05 user_prefs
 
I was looking for this files and some had user root and group root.
why did this happen?

Some users don't have this files.
Can this be because they don't have spamassassin activated to their accounts?

Thanks in advance.
 
I was looking for this files and some had user root and group root.
why did this happen?

Either...

a) someone changed the permissions
b) spamassassin was running as root (did someone start the spamassassin service rather than psa-spamassassin?)
c) possibly the domain is disabled

Some users don't have this files.
Can this be because they don't have spamassassin activated to their accounts?

It is a possibility, also it is possible they never received mail. If SpamAssassin is enabled you can look at the .qmail file in the user's mail directory and you would see it piping into psa-spamc.
 
Ok. I solved the problem.
The user didn't have spamassassin enabled and the domain had been disabled, so i gess that was it.

Changed the user and group, enabled spamassassin on the account and everything went well.

Thanks
 
Back
Top