On 08/26/2014 08:08 PM, Reindl Harald wrote:
Am 26.08.2014 um 18:11 schrieb Axb:
On 08/26/2014 05:42 PM, Reindl Harald wrote:
they are *not* i sepecially added the following lines
to prevent the automatic adding to "trusted_networks"
since the IP range is outside
clear_trusted_networks
trusted_networks 192.168.168.0/24
there was no trust at all in the headers and no
hint why the DNSWL was skipped at all
ADVANCE_FEE_4_NEW
ADVANCE_FEE_4_NEW_MONEY
ADVANCE_FEE_5_NEW
ADVANCE_FEE_5_NEW_MONEY
BAYES_99
BAYES_999
DEAR_SOMETHING
DKIM_ADSP_CUSTOM_MED
FREEMAIL_FROM
LOTS_OF_MONEY
SPF_SOFTFAIL
T_MONEY_PERCENT
URG_BIZ
comment out
#tflags RCVD_IN_RP_TLDNS1 net
run that msg against spamassassin -D dns
see what it spits out
sorry, no idea what you mean with "run that message against"
spamassassin is running spamd and spamass-milter and no way
to get the message passed over SMTP to that box with
another configuration
fact is that the message has no "ALL_TRUSTED" in the headers
and it makes little sense that DNSWL lists are skipped only
because the client is in the same network range because
that makes behavior hard to test and compare
that's (partly) how are the processes started
/usr/bin/spamd -c -H --max-children=25 --min-children=10 --min-spare=5
--max-spare=15 --port=10027
/usr/sbin/spamass-milter -p /run/spamass-milter/spamass-milter.sock -g sa-milt
-r 10 -- -s 1048576 --port=10027
fact is: you're making assumptions without making use of the basic
spamassassin command line debugging features.
good luck!
