On Montag, 8. Mai 2006 21:52 Mike Jackson wrote: > DNS_FROM_RFC_ABUSE > but to have your #1 *ham* rule be one > that's supposed to identify *spam* doesn't speak well for the rule
Isn't the intention of RFC_ABUSE to list any site that abuses RFC? So you can't really believe that it wants to identify SPAM, but rather domains which do not "play within the rules". For the same reason, SPF cannot be used to identify SPAM or HAM. It's to see if a message is forged, nothing more. Of course, it hits for SPAM trying to forge messages, so that way it helps a lot... mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660/4156531 .network.your.ideas. // PGP Key: "lynx -source http://zmi.at/zmi3.asc | gpg --import" // Fingerprint: 44A3 C1EC B71E C71A B4C2 9AA6 C818 847C 55CB A4EE // Keyserver: www.keyserver.net Key-ID: 0x55CBA4EE
pgpVjG2VFd6gf.pgp
Description: PGP signature
