IWETHEY v. 0.3.0 | TODO
1,095 registered users | 1 active user | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Groklaw on Sender ID for e-mail.
[link|http://www.groklaw.net/article.php?story=20040905212754195|Here]:

Sender ID, as you no doubt know, is [link|http://www.microsoft.com/presspass/press/2004/jun04/06-24SIDSpecIETFPR.asp|a proposed IETF email standard] that combines Microsoft's Caller ID with Meng Weng Wong's popular SPF. The combo is designed to make it difficult if not impossible to spoof an email sender address. It's also an [link|http://www.cio.com/archive/090104/phish.html|anti-phishing technique]. The problem is that Microsoft evidently -- at least so far -- believes that because it is offering to contribute a portion of the standard, and it has applied for [link|http://article.gmane.org/gmane.ietf.mxcomp/4590|a patent on the PRA algorithm], it should be able to control all of the standard by attaching restrictive licensing terms to their contribution, terms that would exclude GPL software from being able to use the standard.

Sounds fair to them.

Some in the FOSS community have already issued statements that they will not deploy Sender ID with its current we-hate-the-GPL license, including [link|http://www.apache.org/foundation/docs/sender-id-position.html|the Apache Foundation] and the [link|http://www.linuxelectrons.com/article.php/20040905111040681|Debian Project]. As Greg Stein, Chairman of the Apache Foundation writes at the end of their statement of nondeployment:

"[N]o company should be permitted IP rights over core Internet infrastructure."


It's a long article with lots of links.

Apparently the IETF needs to have comments by Friday.

Something needs to be done about e-mail address abuse, but I have concerns about tying things to a MS patent.

Cheers,
Scott.
New TheInq: Spammers love Sender ID
[link|http://www.theinquirer.net/?article=18367|Here]:

The science is pretty easy. Under the Sender Policy Framework (SPF), companies publish a list of authorised E-mail servers for the domains they control. This is used by those receiving E-mail to make sure the purported server of origin matches the one listed in the message header.

All the spammer has to do is forge the header information to disguise the origin of their messages and sail through the checks.

More than 16 percent of spam already carries SPF records says MX Logic.


Gee. Whoda thunkit.

Cheers,
Scott.
New That article was written by an idiot
The way that Sender ID, SPF, and their ilk work is simple, they add to DNS information about what IPs email from that domain might come from. If you forge your header it does you no good unless you come from the right IP address. Forging your IP address (or the DNS record) is, of course, substantially harder than forging the header on an email.

So their, All the spammer has to do line is trivially wrong.

Now MX Logic really did the study that is referred to. But that study shows something different than the Inquirer's piece of garbage claims that it does. I think that it also shows something different than MX Logic thinks that it does, but that is more debatable.

The study is based on a sample of 400,000 emails that MX Logic's spam filter classified as spam. Of those emails, 16% had published SPF records. Their claim is that "spammers" are adopting SPF in a big way.

Now there are some major methodological problems that they don't clarify. The first one is that I don't know whether or not they were saying that the domain has an SPF record, or whether it passed an SPF check. Consider the problem of forged Yahoo! addresses to see why this would affect numbers in a big way. Furthermore for this to be meaningful, you want to focus on passed SPF in strict mode. A lot of people use SPF right now, but have it in a transitional mode where they say, "Our email should come from these IPs, but please don't throw it away if it doesn't." A month or two after you do this and see that it works, you're supposed to switch to strict mode where people actually drop your email if it doesn't match the SPF record. Passing SPF until you're in strict mode is no biggie.

Given that they have a vested interest against other spam solutions, I'm not going to assume that they actually made either judgement call like I would want. For one thing, it would have made their numbers a lot smaller!

But methodological issues aside, their fundamental point has truth to it. I believe that "spam" probably has good uptake of SPF records. The reason that I put the quotes on is that they are defining spam as, Failed our filter. That pretty much means that something looks like marketing email. Lots of fairly legitimate marketing email is out there, things like confirmation messages from Amazon, catalogs from L.L. Bean and the like. While it makes good publicity for MX Logic to call it spam, it may or may not be. The real test, of course, is whether the recipient would have considered it spam. And this key question is not answered.

These companies have a big problem - they don't think of themselves as spammers but they tend to fail spam filters. They want to get whitelisted. Generally speaking, the ISPs would like to whitelist them as well - recipients generally dislike false positives more than false negatives when it comes to spam filtering. But the problem is that if, for instance, it was known that anything labelled Amazon gets through at Hotmail, then every spammer would spam Hotmail from "Amazon" emails.

SPF solves this problem with whitelisting. (SPF does more, of course.) SPF makes it easier to hold domains accountable for what they send. Which makes it possible to identify people as bad or good. So if you're a company that sends what you think is legitimate marketing email, of course you're going to want to use SPF. And of course MX Logic is going to flag your emails as spam. Hence you're now "evil spammers" for their rhetorical point.

Disclaimer: I work for [link|http://www.rent.com|a company] that is in this position. (Our emails are lists of apartments for people who've signed up to search for apartments.)

Cheers,
Ben
To deny the indirect purchaser, who in this case is the ultimate purchaser, the right to seek relief from unlawful conduct, would essentially remove the word consumer from the Consumer Protection Act
- [link|http://www.techworld.com/opsys/news/index.cfm?NewsID=1246&Page=1&pagePos=20|Nebraska Supreme Court]
New Thanks. I learned a lot. :-)
New ObAOL: Me too.
     Groklaw on Sender ID for e-mail. - (Another Scott) - (4)
         TheInq: Spammers love Sender ID - (Another Scott) - (3)
             That article was written by an idiot - (ben_tilly) - (2)
                 Thanks. I learned a lot. :-) -NT - (Another Scott)
                 ObAOL: Me too. -NT - (CRConrad)

I've never been so insulted in all my week!
65 ms