Rspamd: replace reject_unknown_client_hostname with Rspamd HFILTER_HOSTNAME_UNKNOWN and make it configurable#3248
Conversation
The new Rspamd configuration tackles the reverse DNS now.
add check on RSPAMD_HFILTER_UNKNOWN_SCORE & check if the var actually is a number and show an error if not
5824010 to
c6335db
Compare
c6335db to
87ccf1d
Compare
|
Documentation preview for this PR is ready! 🎉 Built with commit: 87ccf1d |
|
@GoliathLabs how do you feel about this replacing your Postfix usage from: #2691 ? Are you using the rspamd feature, if not do you plan to adopt it at some point? Or do you need the feature to remain in Postfix? (@georglauterbach may still drop it by the end of the year once he switches rspamd on as a default enabled feature) |
I have already used rspamd on one of my older mailserver instances, so I plan to use rspamd with docker-mailserver as well. I wouldn't mind replacing my reject_unknown_client_hostname configuration with the configurable one of rspamd. |
|
Correct me if I am wrong. This PR removed the feature |
We had requests and complaints that this might be too restrictive. If you want me to, I can make this configurable for Postfix again - via an ENV like Another rationale is that with Rspamd, this will all be a factor for the spam score metric, which is IMO desirable. |
Not sure, if that represents the majority and justify removal. For me this works perfectly and avoids a lot of SPAM.
Yes, please 👍 |
Description
Please quickly read over #3228 :) Removes
reject_unknown_client_hostnameand (re-)add the test to Rspamd (viaHFILTER_HOSTNAME_UNKNOWN).Fixes #3228
Fixes #2970
Type of change
Checklist:
docs/)