• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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