On 2021-09-18 6:10 p.m., Christian Schmitz wrote:
On Saturday 18 September 2021 10:13:41 ludic...@gmail.com wrote:
Hi,
pcre header checks we use. Not all the time, depends on spam volume from
these valuable enterprises.
#/sjmedia.us/ REJECT A mass mail service abused by criminals
#/bmsend.com/ REJECT A mass mail service abused by criminals
#/mailgun.net/ REJECT A mass mail service abused by criminals
#/rsgsv.net/ REJECT A mass mail service abused by criminals
#/mcsv.net/ REJECT A mass mail service abused by criminals
#/sendgrid.net/ REJECT A mass mail service abused by criminals
#/crsend.com/ REJECT A mass mail service abused by criminals
#/zcsend.net/ REJECT A mass mail service abused by criminals
I forgot if all those can be catched by limiting it to the Received-Line.
Greets,
Ludi
-----Ursprüngliche Nachricht-----
Von: owner-postfix-us...@postfix.org <owner-postfix-us...@postfix.org> Im
Auftrag von Christian Schmitz
Gesendet: Freitag, 17. September 2021 14:41
An: postfix-users@postfix.org
Betreff: Spam pass the filter
Hi everyone:
Normally when i identify a host spammer i block entire server. Today
i receive one spam email. The origin is "mailgun.net", i already have a
rule to block him, but the email pass with no problem. I want stop the
email, what is wrong?
The header, config and rules are the following.
Best Regards and thanks in advance
Christian
Thanks to all. I do not use spamassasin since the spam and mail level is too
low in my server ( 2~5 emails at day). I take the policy of block entire
spammer mail server.
I will read and adapt my rules.
Thanks to everyone.
Christian
Hi Christian,
It's still worth running SpamAssassin on a low volume server. You are
correct that you will not have enough spam to train Bayes but
SpamAssassin ships with rules that can catch spam based on regex's,
DNSBL queries and do forth.
It's also a handy platform for writing your own site-specific rules,
which also function in the absence of Bayes.
- J
