• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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