-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Stephen Warren wrote:
| If a forwarder implements SRS, then they probably implement SPF too. In | this case, any emails you receive from an SRS encoded address have | hopefully been SPF checked and hence aren't spam. | | So, simply accept any email from an SRS encoded address...
I don't think this would work for two reasons: (1) spammer domains that have no SPF record, and (2) spammer domains that have valid SPF records.
That's probably enough for most people, but I have my own ugly reason. Spammers forge my address on their outgoing mail. I get replies because of it (e.g., thank you for contacting [EMAIL PROTECTED]). TMDA blocks them pretty well. Content filters can't get them (and I wouldn't expect them to--after all, they're not spam), and SPF checks wouldn't catch them. The only reason TMDA gets them is because (1) I've never heard of them, and (2) they're too automated to answer a challenge.
Anyway, SPF is nice for flagging something as being spam, but I don't expect it to tell me when something is NOT spam.
Kyle.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3-nr1 (Windows XP) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBJkVCzS7R/flctWYRAsb9AJ9aV3JcDpcvvP/NL2fwQYJ4CrvZ2ACfbXBw jDMFafxDkQbaZF9QoVJgJs4= =BDdA -----END PGP SIGNATURE----- _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
