Recent content by xml

Xen: This part is likely inspired by the Greek word xenos, meaning “stranger” or “foreigner.” It’s often used in English to convey something new, different, or out of the ordinary. Foro: This appears to be a nod to the word “forum,” referring to a place where people gather to discuss topics.

The easy solution I use is: 1. /etc/dovecot/conf.d/10-auth.conf # Time to delay before replying to failed authentications. auth_failure_delay = 20 This will make brute force attacks harder by slowing them down by increasing the number of seconds bitween login attempts in the same live session...

That directive is for postfix while the command "openssl s_client -connect mail.domain.com:993" is specifically for testing the connection to the Dovecot mail server using the IMAPS protocol which operates over port 993

will not work for the first connection. I’m curious if the Dovecot team thoroughly tests their Fail2Ban "how-to" guide before publishing it on their website.

That's true for services like SSH, where after 3 failed attempts, the connection is terminated, and Fail2Ban blocks the IP on any subsequent connection attempts. Unfortunately, that's not the case with Dovecot. Dovecot doesn’t terminate the connection after a certain number of failed attempts...

Unfortunately Fail2Ban can take action starting from the second connection, but during the first live connection, Fail2Ban cannot intervene. That's why I am struggling to terminate the first connection

I'm running a LAMP VPS with AlmaLinux 8 and Apache, and I've installed a mail server using Postfix and Dovecot. Everything works fine for sending and receiving emails. However, I noticed that an intruder can establish a connection to Dovecot (e.g., using openssl s_client -connect...

My new settings to minimize the damages

OOOUUUCCHHH 😬😬

How to disable watched content alerts/emails for all members? any option for that in the ACP? I received from my email provider they will block the outgoing mails from my email account because of this watched content alerts/emails feature!

Doing more research I found out the following: Removing the provider files solve the problem and MariaDB is up and running normally now

Many tutorials out there on google: https://www.hostwinds.com/tutorials/backup-restore-mysql-databases-using-mysqldump

No, and I checked the forums was working fine before I run php upgrade I have to prepare my self for the day when the only free open source OS is Debian. I dont use control panels for my server, I do every thing by command line. Here is what ChatGPT suggested and it worked for me: I am not...

On Debian12 upgrading from php8.1.28 to php8.1.29 cause MariaDB failure to start

I just restored a backup from MariaDB-10.6 to MariaDB-10.11 and it seems the forums is running normally. Any complications or side effects could happen?