• 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 isn't starting after a backup

B

bonsaidouglas

Guest
I just did a backup and once it was complete, spamassassin wouldn't start back up. This is the backup command I used:
/usr/local/psa/bin/psadump -f - | split -b1000m - dump.

And this is what I get when I try to restart spamassassin:
# service psa-spamassassin start
Insecure directory in $ENV{PATH} while running with -T switch at /usr/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/CmdManageSA3.pm line 829.

Starting psa-spamassassin service: [ OK ]
# service psa-spamassassin status
is stopped
0

It errors but then claims to start, then a status indicates it's not running...

Any leads on what the "Insecure directory" is referring to?

Thanks
 
ok got it, my mistake.

when installing some other software I changed the permissions on directories, changed them back and it's all good.
 
I'm having the same problem but i don't remember installing anything :(

So what folders did you have problems with and what did you do to them to make it work :)
 
I think the only directories that may have been affected were:
/usr/local/bin and/or /usr/local/sbin

I set the permissions back to what they were originally. Spamassassin seems to require certain permissions so that its settings can't be tampered with.
 
Back
Top