-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
!! I'm an idiot. DK_VERIFIED means "signature test passed", DK_SIGNED just means the header was present. so this isn't quite so hot, given that; 92% of the DK sigs in my corpus were still invalid, the message munged, or otherwise failed verification. - --j. Justin Mason writes: > from a mass-check run I did last night. these are more promising; > 12% of ham whitelistable: > > 19992 9999 9993 0.500 0.00 0.00 (all messages) > 100.000 50.0150 49.9850 0.500 0.00 0.00 (all messages as %) > 6.338 0.0500 12.6288 0.004 1.00 0.00 DK_SIGNED > 0.005 0.0000 0.0100 0.000 0.53 0.00 DK_POLICY_SIGNALL > 0.485 0.0400 0.9307 0.041 0.47 -0.00 DK_VERIFIED > 4.627 5.5506 3.7026 0.600 0.06 0.00 DK_POLICY_TESTING > 5.162 6.1206 4.2029 0.593 0.00 0.00 DK_POLICY_SIGNSOME > > this was achieved by adding code which strips off "known appended" > headers from the message, such as X-Spam-*, Status, IMAPBase etc. > > Records that passed verification were: > > 954 gmail.com > 270 yahoo.com > 10 crynwr.com > 9 earthlink.net > 6 space.net > 5 yahoo-inc.com > 5 omniti.com > 1 sendmail.com > 1 altn.com > > and that's it. AFAICS, most of those domains have only one selector, > so that's a puny 9 DNS lookups? looking quite promising. ;) > > --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Exmh CVS iD8DBQFB+b6JMJF5cimLx9ARArIlAJ9FoxCNYHRgo/RqPR+dDTwdOCOn3gCeOqwQ RsGxcb9f6K0uebAcf3ujcDI= =2iCP -----END PGP SIGNATURE-----
