danami

@MacGyver No that wouldn't be practical. You should disable SMTP_AUTH on port 25 and have your clients sending using the submission port...

@Hangover2 Yes we've optimized the journald log parser in the next version of Warden so log lookups are almost instant now reguardless...

@Hangover2 Warden will detect if DCC is setup as a service and you will see it listed on the Warden dashboard under the services...

@Hangover2 Also make sure that you are running DCC as a service and not just calling the binary. We have instructions here...

My stats are a bit better... It looks like you're using IPv6. I wonder if that has any effect. The DCC webpage might offer some help...

@Bobbbb Thanks for the suggestion — switching to IPv4 did the trick. # 11/13/25 16:34:34 CET /var/lib/dcc/map # Re-resolve names after...

@papahausa These are the only settings that you should be migrating across servers are policy settings, blacklists and whitelists...

@MacGyver You can hover your mouse over every setting in Juggernaut to get detailed information about what each setting does...

@MacGyver You should always use the IPtables search on the dashboard or using the command line instead of trying to search the Logs ->...

This is because dovecot 2.4 logs to a different format that doesn't match the old filter. As a temp fix you can replace the old filter...

You should also check for any customizations to the dovecot configs in /etc/dovecot/conf.d/ . Plesk 18.0.73 upgraded to dovecot 2.4...

Check the systemd-journal for errors with the command: journalctl -xeu dovecot.service If you see the error below then you have to...

@Alexander Bien Make sure that you have updated to Plesk Obsidian 18.0.73 Update 2 as they should have fixes for that: From the Plesk...

I recommend that you tail your maillog and then do a send a receive with your email client and check for any errors: tail -f...

Check and make sure that the dovecot service is running properly on the server with the command: systemctl status dovecot