kpapad904

Based on a quick DNS search, it seems that Gmail supports RFC 6186 (but neither of the other two methods): ``` _submission._tcp.gmail.com has SRV record 5 0 587 smtp.gmail.com. _imap._tcp.gmail.com...

This may be a long shot, but if you are assigning a real IP (not private IP RFC1918) to the HestiaCP container under Proxmox, then your host may be using...

Just FYI, failed modules on SA ``` # spamassassin --lint -D 2>&1 | fgrep -i failed Apr 16 06:41:05.882 [8628] dbg: diag: [...] module not installed: Digest::SHA1 ('require' failed) Apr...

> Installing/updating packages over apt is impossible when the "script" is run from inside update it self. It will cause issues that need to be solved via writing a bash...

> This have we seen in the past with for example Roundcube / phpmyadmin and so. In the past. And if we used PHP / Nginx packages from Debian you...

> I haven't actually tested this, but it seems to me that the only change needed would be to add the backports repo and invoke apt with `/buster-backports` appended to...

Here is a quick patch which illustrates what I meant in my original post (it simply adds exim4 v4.94 and spamassassin v3.4.6 from buster-backports to HestiaCP systems running Debian 10)...

> PS: This is just for Debian, I haven't checked the situation with Ubuntu. Apparently Exim has issues on both Ubuntu LTS versions (18.04 and 20.04) supported by HestiaCP. I...

I’ve also been using Rspamd for the past 3-4 years (but not on HestiaCP) and it is very powerful, even though it is significantly harder to configure than SA, also...

> If we gonna to implement rspamd, spamassassin will be replaced - we do not have enough resources to support two different systems. Absolutely agree with HestiaCP focusing on a...