Recent content by danami

@Hangover2 I recommend opening a ticket in our client area and we can hook you up with something exciting to test out :)

This is something that really should be handled by Plesk. If you look at that "Internal Mail-Forwarding" extension all it was doing was overriding the default javascript to add the extra restrictions (something that Plesk should add so it doesn't break every time they change things).

My fix was implemented. They set 'mail_attachment_detection_options =' in /etc/dovecot/91-sieve-crash.conf. With the fix there is no need to turn off imap_sieve completely.

Username: TITLE Dovecot-pigeonhole version 2.4.2 used by Plesk Obsidian 18.0.76 causes dovecot to panic crash PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Product version: Plesk Obsidian 18.0.76.1 OS version: Ubuntu 24.04 x86_64 Build date: 2026/02/18 09:00 Revision...

Also when I look up the fix that Google Gemini suggested it says just to set mail_attachment_detection_options = to empty in the dovecot config. So this might be a temp fix for it (untested): echo 'mail_attachment_detection_options =' > /etc/dovecot/conf.d/999_fix_crash.conf systemctl restart...

I've been trying to research this and it looks like it's just a bug in Dovecot's imapsieve plugin (Plesk updated dovecot-pigeonhole to version 2.4.2) . I've attached what Google Gemini says about the issue (I'm not sure if their fix they recommend actually works as I haven't been able to trigger...

Juggernaut Security and Firewall 5.03 has been released with Debian 13 support, bug fixes, and more: https://www.danami.com/clients/announcements/169/Juggernaut-Security-and-Firewall-5.03-Released.html

@Hangover2 Thanks for providing your systemd-journal configuration. I have some additional ideas I we can do for the next release of Warden to optimize things even further.

@Hangover2 I recommend that you open a ticket in our client area and if you can provide us access to a server then I can see if I can optimize things further for you. Things are really going to be server hardware and configuration dependent.

We have released Warden 5.05 which adds Debian 13 support, log parser optimizations, bug fixes, and more: https://www.danami.com/clients/announcements/168/Warden-Anti-spam-and-Virus-Protection-5.05-Released.html

@MacGyver No that wouldn't be practical. You should disable SMTP_AUTH on port 25 and have your clients sending using the submission port 587. Then you can restrict sending to countries that you authorize: https://www.danami.com/clients/knowledgebase/242

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

@Hangover2 Warden will detect if DCC is setup as a service and you will see it listed on the Warden dashboard under the services section. It should run way faster then just using the DCC binary.

@Hangover2 Also make sure that you are running DCC as a service and not just calling the binary. We have instructions here: https://docs.danami.com/warden/user-guide/antispam-plugins/dcc#enable-the-dcc-interface-daemon

@papahausa These are the only settings that you should be migrating across servers are policy settings, blacklists and whitelists. https://www.danami.com/clients/knowledgebase/247/-How-can-I-migrate-Warden-settings-from-one-server-to-another-.html Many settings are OS specific so you will...