Am 26.08.2014 um 14:25 schrieb Joe Quinn: > On 8/26/2014 8:04 AM, Reindl Harald wrote: >> i am tyring to write own RBL rules for blacklisting and >> especially whitelisting using internal DNSBL/DNSWL but >> my first try results in warnings at startup >> >> sadly the Wiki don't refer to check_rbl() >> https://wiki.apache.org/spamassassin/WritingRules >> >> ifplugin Mail::SpamAssassin::Plugin::DNSEval >> header RCVD_IN_TL_DNSWL_HIGH eval:check_rbl('dnswl.thelounge.net') >> tflags RCVD_IN_TL_DNSWL_HIGH net >> endif >> >> Aug 26 13:56:07 mail-gw spamd[19589]: Use of uninitialized value $rbl_server >> in pattern match (m//) at >> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/DNSEval.pm line 156. >> Aug 26 13:56:07 mail-gw spamd[19589]: Use of uninitialized value $rbl_server >> in index at >> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/DNSEval.pm line 156. >> Aug 26 13:56:07 mail-gw spamd[19589]: Use of uninitialized value $rbl_server >> in concatenation (.) or string at >> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Plugin/DNSEval.pm line 162. >> > You can use KAM.cf for reference. > > http://www.pccc.com/downloads/SpamAssassin/contrib/KAM.cf > Search for KAM_FROM_URIBL_PCCC
thanks, looks like the missing identifier as first
params was the reason for the error but the rule
below still don't fire and the connecting IP is
on the list, recently verified again
may the problem be that "header" looks in received
headers and not at the connecting physical IP?
header RCVD_IN_TL_DNSWL_HIGH eval:check_rbl('custom-dns-1',
'dnswl.thelounge.net.', '127.0.0.2')
describe RCVD_IN_TL_DNSWL_HIGH Custom DNSBL/DNSWL
tflags RCVD_IN_TL_DNSWL_HIGH net
score RCVD_IN_TL_DNSWL_HIGH -5
signature.asc
Description: OpenPGP digital signature
