Am 26.08.2014 um 21:08 schrieb Martin Gregorie: > On Tue, 2014-08-26 at 20:08 +0200, 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 >>> >>> 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" >> > Under the same directory as spamass-milter run: > > spamc -your_normal_spamc_options <message_to_be_tested
are we really talking about the same? that won't involve the network * the rule works * it is skipped from client IP 192.168.196.6 while SA runs in 192.168.196.19 * it is not skipped if the client comes from 62.178.103.85 outside the own network * "192.168.196.0/24" is not defined as trusted because to avoid that the only trusted configuration is the non-existing/involved "192.168.168.0/24" clear_trusted_networks trusted_networks 192.168.168.0/24 ______________________________________________________ the question was how to tell SA not skip any RBL rule in no case to make it easier test implementations when client and SA server are on the same network
signature.asc
Description: OpenPGP digital signature
