https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7755
Riccardo Alfieri <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] | |m --- Comment #6 from Riccardo Alfieri <[email protected]> --- That rescoring is done with a purpose, ie: Deep test the received chain and check if an IP is in XBL/SBL and adjust the score accordingly. That is to check if the original sender ip is compromised in some way (XBL and SBL have different listing policies, hence the different scores) However, if the last untrusted relay is listed in ZEN, then tag the email as sure spam (we have a 0% FP rate on ZEN's last untrusted relay). PBL is a list mantained directly by ISPs where they are effectively declaring that they *don't* want any IP listed there to be authorized to directly send emails. URIBL_DBL_SPAM hits when a domain tagged as spam source is found, and that, in our opinion, should automatically flag an email as spam. Of course I could have done some errors, but the expected behaviour should be what is expressed above. But, even if the OP didn't use our plugin, the fact that "example.com" queries DBL for "here.to" should be investigated in my opinion. Unfortunately, due to my own lack of experience, I didn't really understood Henrik explanation of why it happens. -- You are receiving this mail because: You are the assignee for the bug.
