Search results

Make sure that the Plesk firewall and fail2ban is installed and enabled. You can install them with the command: plesk installer add --components psa-firewall fail2ban See here for more information...

@Peter Debik It works now as long as you import the new GPG key.

Username: TITLE The GPG keys listed for the "grafana extension repository" repository are already installed but they are not correct for this package. PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Product version: Plesk Obsidian 18.0.51.0 OS version: CentOS 7.9.2009 x86_64...

@Liwindo The dark mode state is stored in a cookie. Just make sure that you aren't deleting the cookie and it will remember it.

@manipogo Plesk also includes mod_cloudflare packages in their extras yum repository so on RHEL based distros installing it is as simple as : yum install mod_cloudflare For Debian/Ubuntu you can install the mod_cloudflare packages that Cloudflare provides: https://pkg.cloudflare.com/index.html

Email scanning is not sequentially / single-threaded. Maybe this will help you: https://www.danami.com/clients/knowledgebase/189/How-can-I-optimize-the-performance-of-Amavis-for-processing-large-volumes-of-email.html You can also disable outgoing scanning if you want (leaving incoming scanning...

1) Why Warden wasn't telling me that I needed to enter this key somewhere. We do have an input for filling in the API key under Settings -> Plugin Settings -> SH . I have included a screenshot. 2) How this is supposed to be maintained if SpamAssassin is updated and installs a new SH.cf file...

What OS are you using? Debian/Ubuntu are /etc/amavis/ and AlmaLinux/RHEL is /etc/amavisd/

Amavis needs the fully qualified domain name and it gets it from the `hostname --fqdn` command . You can manually set by using the $myhostname option in the Amavis config. On Debian/Ubuntu $myhostname is set in /etc/amavis/conf.d/05-node_id: use strict; # $myhostname is used by amavisd-new...

Try setting it to a fully qualified domain name using the hostnamectl command https://www.vernalweb.com/kb/change-fully-qualified-domain-name-centos-7/

@floh what do you get when you run the command: hostname --fqdn

@floh try looking directly at the file /etc/hostname and make sure that it's a fully qualified domain name.

@zwankie Then you are out of luck then as the Plesk repair tools can't handle the postscreen configuration. Also Warden already allows you to be able to whitelist servers from Plesk DNSBLs so if you do have a server that's blocked you can whitelist it or it's CIDR easily.

@zwankie Setting up postscreen will break the Plesk mail repair tools the last time I checked. Also most of the postscreen restrictions are fully supported directly by Postfix anyway. You can see the Postfix restrictions that Warden supports here...

> Danami firewall / warden anti spam configuration issues may create some conflicts? After upgrading from Ubuntu 18.04 to Ubuntu 22 you should use the following KB articles: Juggernaut Firewall...

@cyxxnet Open a support ticket with us: Plesk Anti-spam and Virus protection, Plesk Firewall, Plesk Extensions, Plesk Security | Danami

@W4ru You should note that our Warden Anti-spam and Virus Protection extension allows you to whitelist/blacklist by IP addreses / CIDR, envelope senders, envelope recipients etc. This all happens at the postfix level. So you instead of having to remove the whole RBL you can just add the IP...

Damn you will be missed @IgorG. You were a true professional!

SpamAssassin 4.0 has been released! The release announcement can be found here. We've added the final release of SpamAssassin 4.0 for RHEL/AlmaLinux/CloudLinux/RockyLinux 8 and 9 to the danami-warden-testing repository. Admins wanting to upgrade to SpamAssassin 4.0 now can follow the...

Thanks for the kind words. I'm glad that it's working for you :)