Leonardo Rodrigues Magalhães wrote:
i was checking spamassassin definition files, which are updated
daily in my site, and could find some interesting entries with
'lastexternal'.
20_dnsbl_tests.cf:header RCVD_IN_XBL
eval:check_rbl('zen-lastexternal', 'zen.spamhaus.org.',
'127.0.0.[45678]')
20_dnsbl_tests.cf:header RCVD_IN_PBL
eval:check_rbl('zen-lastexternal', 'zen.spamhaus.org.', '127.0.0.1[01]')
20_dnsbl_tests.cf:header RCVD_IN_DSBL
eval:check_rbl_txt('dsbl-lastexternal', 'list.dsbl.org.', '(?i:dsbl)')
20_dnsbl_tests.cf:header RCVD_IN_MAPS_DUL
eval:check_rbl('dialup-lastexternal', 'dialups.mail-abuse.org.')
These make sense. Those last three are lists based on IP type (I don't
remember XBL's definition exactly). A user shouldn't be penalized for
having a dynamic when they are sending through a proper relay.
but ..... the RBL that is giving me headaches, which is spamcop,
seems to NOT have the lastexternal entry:
20_dnsbl_tests.cf:header RCVD_IN_BL_SPAMCOP_NET
eval:check_rbl_txt('spamcop', 'bl.spamcop.net.', '(?i:spamcop)')
question 1 is ..... can i redefine this rule in my local.cf for
example ???
Yes you can.
question 2 is ..... shouldnt this rule have the 'lastexternal' as
several other RBL rules seems to have ???
No, spamcop is for spam sources, not sources based on the type of their
connection. If one of the hosts in the list is a spam originator,
chances are that piece of mail is probably spam as well. Spam sources do
send through relays, so this information is quite valuable.
Richard
