Recent content by JVG

Sorry for the noob question but, how can I test it like that on my server? I'm not very familiar with fail2ban-regex tests, but that result looks very promising.

Hi, check if there are any forwarding from accounts on the Plesk server to Gmail. The only ocurrence on my server of this exact Gmail error (sometimes blocked, sometimes just delayed) was on forwarded messages only, but maybe it has some impact as well on the rest (I didn't experience this on...

This happened to one of my clients early last year with a major international airline. I did exactly the same, temporarily whitelisting.

Hi, I think it might be because the reject policy is set on the source domain, not the one hosted in Plesk. If source domain policy is reject and for some reason the source mailserver is not properly configured it can lead to this error. If this is so, you could exclude the source domain from...

Hi, wouldn't the SpamAssassin server-wide rules (if active) apply to that user also? Even if the individual user_prefs do not?

I don't think so. Mine is one fresh Debian 12.5 server and fresh Plesk installation and license.

It seems to be the output of the auth.log errors. Why is showing in the console, i don't know. Maybe something related with journald, which seems to be the default logging service for Debian 12.

Thanks, Peter, right now there are 0 domains and 0 mailboxes on the server. Again, I'm just setting up basic configurations before going live (since I've already got the plesk license it'll go sooner than expected). "Plesk Premium Antivirus" (drwebd service) still does not start.

Update: I just purchased the Plesk license and got the same error when installing Premium Plesk Antivirus through the plesk installer.

Hello, I'm starting to set up a new Debain 12 server with Plesk, both brand-new installations: Product version: Plesk Obsidian 18.0.59.1 OS version: Debian 12.5 x86_64 When installing DrWeb the following error shows: Copyright (c) Igor Daniloff, 1992-2024 Doctor Web, Moscow, Russia...

Same thing happened on my new Debian 12 server. It definitely didn't happened on Debian 11. It's my first try with Debian 12, is it a known OS related thing?.

Hi, you're again editing the plesk-apache-badbot jail. You need to edit the apache-badbots filter. In the Jails tab you have the "Manage Filters" button, that's where you need to go to edit the apache-badbots filter. The plesk-apache-badbot jail should remain unchanged.

Also, as @Peter Debik notes, these regular expressions need to be refined for each case, and might need to get updated and refined over time, as you could see, mine is maybe too constrained to the exact text of what my server was receiving at one point. I use this site to test the regular...

No, that's the jail, you have to go to "Jails->Manage Filters": and then select the "apache-badbots" filter:

I usually update the apache-badbots fail2ban filter directly from the Plesk GUI, my entry for Bytespider looks like this: Mozilla\/5\.0 \(Linux; Android 5\.0\).*\(compatible; Bytespider; spider-feedback@bytedance\.com\) Added at the end of the badbots section. I think it will be a great...