Robert Felber writes:
The default output of policyd-weight for your matter is:
08:16:35 info: decided action=PREPEND X-policyd-weight:
NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5
CL_IP_EQ_HELO_IP=-2 (check from: .theglaziergroup. - helo:
.smtp03.bis.na.blackberry. - helo-domain: .blackberry.)
FROM/MX_MATCHES_NOT_HELO(DOMAIN)=1 <client=216.9.248.50>
<helo=smtp03.bis.na.blackberry.com> <[EMAIL PROTECTED]>
<to=> <helo_ips: 207.99.47.96 207.99.47.95 207.99.47.95 207.99.47.96
69.36.44.5 216.9.248.50>, rate: -5.5; delay: 3s
Actual score for a few blackberry scenarios were:
-8.5
-8.5
-7.6
Sample output:
Apr 4 10:25:35 mx15 postfix/policyd-weight[73726]: decided action=PREPEND
X-policyd-weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5
NOT_IN_BL_NJABL=-1.5 CL_IP_EQ_FROM_MX=-3.1 <client=204.187.87.60>
<helo=smtprelay11.na.blackberry.net>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>,
rate: -7.6; delay: 0s
Thus others do not experience the behaviour which you see.
Newbie mistake on my part.
Would it be ok to set
$REJECTLEVEL = 2;
instead of 1?
I rather let some spams through.. but be cautious of what I trap since this
is an ISP environment.
____________________________________________________________
Policyd-weight Mailinglist - http://www.policyd-weight.org/
