More SPAM FUD?
The Internet Engineering Task Force, which sets the technical standards for the Internet, yesterday approved the DomainKeys Identified Mail standard as a proposed standard (RFC 4871). The specification, a three-year effort pioneered by Yahoo!, Cisco, Sendmail, and PGP, is an email authentication framework that uses cryptographic signature technology to verify the domain of the sender.
From: Dark Reading - Desktop Security - New Spec Could Cut Phishing, Spam - Security News Analysis
I cry bullcrap. Let’s see here… We’ve had both SPF and we’ve had Sender ID, from Microsoft, for quite some time.
Exactly how has my SPAM results lessened? Both of these have been in place for quite some time. Now all three of these are at least listed at IETF and all three may even be ratified standards. I feel that without wide-spread adoption, universal authentication RESULTS, and any of these anti-spam or domain authentication (if you will) processes just muddy the waters and the additional confusion only serves to slow down the process.
With local and server side SPAM filters in place my own personal results are that some accounts get a 10:1 abuse rate. Yeah… That’s actually low and I do a lot of filtering with a variety of methods at both the server end and client-side. Unfiltered? I am not even sure I want to know. Some accounts may well be in the 100:1 range if not much higher.
I know that a lot of people would think that this is something that can only be done with open source, with only non-proprietary, etc… I disagree and, in my opinion; The reality is that it doesn’t have to be any one specific standard but just one specific standard that is in use globally. I don’t care who makes it, I just care who uses it.
BlogMarks
Furl
Newsvine
Rojo
Email This to a Friend
If you like this then please subscribe to the