Recent content by OverWolf

Good morning, I've read a lot about 'problems' with Fail2ban sals filter, and the "solution" was to use postfix[mode=auth], but in my case it doesn't work. After a little troubleshooting, I have found this inconsistency beetween what is showed on LoBbrowser and what I found on maillog...

After several searches I have found an answer about this problem that put this thread "as resolved":

Hi mizar, this warning appeared after I've updated Almalinux from 9.6 to 9.7, so my OS is updated. I've tried to check if there is other packages update but nothing.

Hi, after I update to Almalinux 9.7 I have this warning : I have done some test and it seems doesn't affect the use of mail, but I would like to know if Plesk is working to resolve this situation or not. Thank you

Thank you Kaspar for your contribution, but the strange thing is that after I restart the server, no error is present and the emails are working correctly (no duplicate, no restarting dovecot, etc.)

Hi Sabahat.hadzhi, my conf file has already that directive into it #ATTENTION! # #DO NOT MODIFY THIS FILE BECAUSE IT WAS GENERATED AUTOMATICALLY, #SO ALL YOUR CHANGES WILL BE LOST THE NEXT TIME THE FILE IS GENERATED. local_name example.com { ssl_server_cert_file =...

Hi danami, thank you for your reply, but I haven't the error that you have mentioned

This is maillog Oct 12 08:08:41 srv dovecot[1656]: config: Error: Config client not compatible with this server (mixed old and new binaries?) Oct 12 08:08:47 srv dovecot[1656]: config: Error: Config client not compatible with this server (mixed old and new binaries?) Oct 12 08:08:47 srv...

Hi, I've read the problematic (and bugs) with 18.0.73, but I have had some 'new' problem during updating. I was on 18.0.71#2 and I have tried to upgrade to 18.0.73#2 and this is my log : 08:03:19 overwolf.server dovecot[1547]: master: Dovecot v2.3.21.1 (d492236fa0) starting up for imap, pop3...

Hi, now it seems working

Hi, in this moment I have this result :

Other strange thing is that after the update (yesterday) I cannot open Plesk UI via port 8447. This is very strange because I have opened it for upgrade to 18.0.71u1

Hi, I'm on AlmaLinux 9.6 and after update from 18.0.69 to 18.0.70u1 I have this error : Is this a possibile bug ?

Hi Fede Marsell, I've installed ipset 7.11 and iptables 1.8.10, disable nftables and fail2ban works correctly

Hi Kaspar, I wrote the version in the title of my thread, anyway it's the last one (2.2.3-449)