what I want
with tagmatch & _AWL* tags !
Paul, will be awesome to be able to do gt/lt (of course for now I can deal
with regexp to achieve this)
--
SimpleRezo
https://www.simplerezo.com/
-
--
SimpleRezo
http://www.simplerezo.com/
--
View this message in context:
http://spamassassin.1
- this requires my users to configure this, and most of them are already
finding IT too much complicated :)
--
Clement
SimpleRezo
http://www.simplerezo.com/
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/Custom-rule-based-on-AWL-score-tp123087p123102.html
Sent
My understanding is that AWL is helping frequent senders who are known to not
send spam to "reduce" their spam score, preventing false positive. That's
exactly what I want to rely on for my rules: adding score for mail with
"invoice" pretention and an attachment but only for very unknown users (or
Because our users cannot easyly add all theirs contacts to whitelist.
AWL is a great feature, and it's working well: so it would be nice for us to
put some restrictives rules only active for "unknown" users (example:
"invoices" ...).
--
View this message in context:
http://spamassassin.1065346
Hi,
Is it possible to write rule based on AWL score?
We have some customs rules that we don't want to enable for "well-known"
contacts...
I tried this:
metaSR__AWL ( AWL <= -1 )
describeSR__AWL AWL is at least -1
score SR__AWL -0.01
B
You are totally right, fixed! Thank you!
2016-05-25 13:24 GMT+02:00 RW :
>
> It sounds like you haven't setup internal_networks and trusted_networks.
>
> https://wiki.apache.org/spamassassin/TrustPath
>
>
Hi,
We are expecting a problem when emails are coming from our MX2 with the SPF
plugin, because the SPF test is made on the last "Received" IP and not the
first one (as we can expect for a SPF test).
So if the domain is one of our domain, the result is always SPF_PASS when
the email arrived from
