Is this actually going out and doing a DNS query or reading from the
header of the message?
I think I want to actually do the DNS query and I will cache locally to
avoid issues and increase performance.
That is what dns servers do, cache. If you have your local dns, these
requests are probably faster than spamassassin rule processing.
just don't use forwarding nameserver, it would
The last part of my question is, here we score and then based on scoring
the next part can either quarantine the message or deliver it, but is
there a way from SA to simply say reject it right there?
you can reject with SA ad MTA level, just use one of milters available.
spamass-milter, amavisd-milter or others.
Just don't reject with standard spam score, with well-trained BAYES I reject
score over 8 (10 without proper BAYES training)
On 28.06.22 18:56, Marc wrote:
Why not use the dns blacklist at the mta? And reject the messages even
before they are using spamassassin. Imho you should apply
simple/basic/fast checks first and at the end use resource intensive tasks
like spamassassin.
you can use multiple DNS Blocklists at MTA level (it's often not safe enough
to accept match from single DNSBL) and use them within SA too.
Since SpamAssassin does deep header scanning, it's more effective than just
use incoming IP at MTA level.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Atheism is a non-prophet organization.
