Search results

With no active certificate and disabled SSL there is no such section where I could set this. Do you happen to know in which Plesk db table the checkbox setting is stored?

Domain <domainname> has no active SSL certificates: SSL is disabled in Hosting Settings: The SSL directory was removed: rm -R -f /usr/local/psa/var/modules/sslit/etc/live/<domainname> It is no present on the system any longer: ls -l /usr/local/psa/var/modules/sslit/etc/live/ | grep...

As your post is in the "Onyx" section, I wonder which "last update" you refer to? What's your Plesk version number and your operating system?

I checked out the script samples that ImunifyAV provides, but it seems that it is no longer possible to inform individual user accounts on their individual domain security issues as there are no variables to use for that or they are undocumented. Further, even the simple example shell script has...

In such cases it would be great if you could please also provide the solution as others will find the question and then will be frustrated that the solution, that was obviously found, wasn't made public. The email notification template is located in...

Plesk engineers have confirmed the issue, but it only surfaces on Alma 8. It's now registered as a bug PPPM-14793.

Does the new extension send email notifications by itself at all? I am asking, because I'd not want users to receive messages from it uncontrolled, it would only confuse users.

In the previous ImunifyAV extension, Plesk offered notification settings in Plesk notificates. It was also possible to edit that template to cater for individual needs. In the new ImunifyAV extension however, these settings are missing. Where can we define ImunifyAV notifications?

@Sebahat.hadzhi Please review Issue - SpamAssassin blacklists have no effect on incoming mail Maybe the engineers ran into the same deception that they thought everything is o.k.? I have the problem that black list entries are ignored for user, while the prefs are stored and are correctly...

... ok ... I do see this though: ... ient.tld,uid=30,required_score=2.0,rhost=127.0.0.1,raddr= ... and that required score comes from the general server default value, not from the customer's mailbox setting. So there seems to be a chance that the individual setting is indeed not applied for...

Yes. No. Spamassassin becomes active, but it completely ignores the blacklist: Jan 21 23:27:21 lahn spamd[3673607]: spamd: connection from 127.0.0.1 [127.0.0.1]:34050 to port 783, fd 5 Jan 21 23:27:21 lahn spamd[3673607]: spamd: using default config for someaddress@recipient.tld...

X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on <hostname> X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DKIM_VALID_EF,HTML_FONT_LOW_CONTRAST,HTML_MESSAGE, RCVD_IN_DNSWL_BLOCKED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL...

Spamassassin is turned on with individual settings per mailbox. For the mailbox in question, Spamassassin is turned on. The blacklist contains entries like *@somedomain.tld. The incoming mail is small enough that is is being handled by Spamassassin. The sender is not whitelisted, neither in the...

Thank you for checking. This got me thinking, and I found that indeed, mails are processed by SpamAssassin, I just didn't see it, because on that one server this occurs on, we are using Courier instead of Dovecot. Log entries look slightly different. In the mass of entries I was not aware that...

Username: TITLE Spamassassin ignores mails to mailboxes that contain an ampersand, e.g. d&s@recipientdomain.tld PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Alma 8.10 Plesk 18.0.65 #2 PROBLEM DESCRIPTION A mailbox with an ampersand in its name (e.g. d&s@recipientdomain.tld) is ignored...

Adding Cloudflare IP ranges will enabled unlimied brute forcing against the server. The cause for blacking Cloudflare IPs is that attacks are coming through these IPs. When you whitelist them, you'll enable attackers to bypass Fail2Ban. Cloudflare is good for DDoS protection (in a limited way)...

The date and time of updates are randomized so that update servers cannot be overloaded. For that reason one server might already have updated, the other not yet.

https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk

I suggest to contact Plesk support on it, because it is not the expected behavior.

Set to forbidden. Just to make sure that file permissions and internal permissions are updated.