Yahoo Submits DomainKeys Draft To IETF 350
NetWizard writes "According to a mailing list post at the IETF, Yahoo's website and a Wired News story, Yahoo has made the DomainKeys draft public and submitted to the IETF." Russ Nelson explains "Basically, your MTA uses RSA-SHA1 to sign the headers and body of your email and inserts that signature before sending the email. The recipient MTA looks up $selector._domainkey.$domain in the DNS, gets your public key, verifies it, and inserts a notice. There's also a SourceForge project for a DomainKeys library."
An anonymous reader asks "It seems to me that it doesn't offer anything more than the Sender Policy Framework by pobox.com, other than doing relay-based signing of the messages to provide the sender verification. SPF has already grown to over 14,000 domains so far and only requires an addition to your DNS to support (from the sending side). Verifying messages on the receiving MTA is as simple as doing a DNS lookup, most MTAs can support SPF now, the code is available and well tested. What advantages to people see in Domainkeys over SPF that are actually useful, and what standard should people implement?"
If it ain't invisible, it's crap (Score:2, Funny)
God fuck me in the ass if I'm going to be required to do all that other crap.
Re:PGP? (Score:1, Funny)
Re:To understand... (Score:5, Funny)
Re:Here you are (Score:3, Funny)
Clue Stick (Score:1, Funny)
Technical solutions to a problem that shouldn't be a problem are fine but I would prefer the direct approch myself.
Spammer sends spam. You accept spam. Track down spammer and rearrange his personality by rearranging the bumps on his head. With a blunt Instrument of your choice. I would think a trumbone would do nicely but in a pinch a tuba would suffice.