Search results

Warden Anti-spam and Virus Protection 4.01 has been released: https://www.danami.com/clients/announcements/143/Warden-Anti-spam-and-Virus-Protection-4.01-Released.html This release adds Debian 12 support, new command line interface, and more!

@Peter Debik I checked and all the domains have their domain keys in /etc/domainkeys/<your domain>/default and the server is using Postfix+Dovecot already so I guess I'll open a ticket with Plesk on Monday.

@dash Yes that's what I thought as it will connect using the socket when you use localhost. Unfortunately I couldn't see a quick easy fix without overriding the mariadb unit file like this...

Username: TITLE Arc errors in maillog PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Product version: Plesk Obsidian 18.0.58.0 OS version: AlmaLinux 8.9 x86_64 Build date: 2024/01/05 08:00 Revision: ec671a07e896ad1b354270e5a4c8597163abfc66 PROBLEM DESCRIPTION...

@Peter Debik Not sure if this is related but there is a bug on newer versions of MariaDB/MySQL where it refuses connections to the socket with SELinux enabled. I've been tracking it and it doesn't look like the fix has made it's way to OS builds yet. https://jira.mariadb.org/browse/MDEV-24941...

@Peter Debik I've converted two servers so far and there were only a few issues to sort with rsyslog after the conversion. So far I'm pretty impressed and it saved us a tonne of time :)

It's not recommended to just stop the ClamAV daemon because Amavis will just fall back to using the ClamAV binary instead which will actually cause more server load (clamav signatures need to be loaded into memory with every email scanned with the binary). Admins can disable the fallback backup...

Just a follow up to this. If you want to disable Amavis temporarily without having to uninstall Warden you can uncheck the SMTP milter and Non-SMTPD_Milter check boxes under Warden -> Settings -> Milter Settings. This will disable any scanning from Amavis and ClamAV. Here is our KB article for...

@kkevin93 Yes this is possible. You just have to set the spam kill level for the policy. This KB article should help you: https://www.danami.com/clients/knowledgebase/251/How-can-I-enable-the-policy-spam-kill-level-in-order-to-reject-mail-over-a-certain-score.html

Here is some info on the content-type header as to why these might be getting wrapped: https://www.w3.org/Protocols/rfc1341/rfc1341.html It states: (4) Lines longer than 76 characters may be wrapped or truncated in some environments. Line wrapping and line truncation are STRONGLY DISCOURAGED...

@Kaspar No he said that DMARC still failed with the amavisd-milter removed from the Postfix config.

@Alex Presland You can uncheck the "SMTP milter" and "Non-SMTP milter" checkboxes under Settings -> Content Filter Settings -> Milter Settings to remove the amavisd-milter from Postfix for testing and see if DMARC will pass with it disabled.

@FutureX Sorry I'm not sure about Digital Ocean's DNS servers. You should be able to test it out with: dig 2.0.0.127.zen.spamhaus.org +short https://check.spamhaus.org/faqs/?id=simple_command_line_test_of_your_dns_resolver

Honestly when Warden is properly setup you really shouldn't need to add any custom rules. You already have a tonne of network tests like Razor2, Pyzor, DCC with daily rule updates from the KAM ruleset so spam already scores well above the default spam level.

No it shouldn't conflict. Also we have two week free trials so you can test things out before hand and see if it works for you.

Custom rules can only be added by the administrator. Yes it does. You can't run both at the same time.

@FutureX Yes Warden does have a rules area where admins can add custom rules to match keywords, subject lines, any mail headers. There are pre-built templates for most rules.

@Maarten. No the Sitejet extension isn't installed (we removed it after the upgrade). This definitely seems related to the new pager. Maybe they are trying to pull in more information with the buttons on the right hand side. > Do you see any timeouts in the browser console? We are seeing an...

@Peter Debik Unfortunately a lot of the slowness seems in relation to the new pager that was introduced in 18.0.57.1 (We do not have the Xovi SEO Toolkit extension installed). After upgrading the pager defaulted to displaying all domains so when you click the domains page it would take over 10...

It looks like this was fixed in Plesk Obsidian 18.0.56 Update 3 :) https://docs.plesk.com/release-notes/obsidian/change-log/#plesk-18056-mu3 Remember that you have to run plesk bin apache --listen-on-localhost true again after updating.