We use cookies to provide you with a better experience. If you continue to use this site, we'll assume you're happy with this. Alternatively, click here to find out how to manage these cookies

hide cookie message
80,259 News Articles

AOL logs out of Sender ID

ISP rejects Microsoft antispam plan amid concerns from open source community

AOL has decided not to fully support Microsoft's Sender ID spam-fighting plan after the Internet Engineering Task Force and the open source community expressed intellectual property concerns.

"AOL will now not be moving forward with full deployment of the Sender ID protocol," spokesman Nicholas Graham said in a statement sent via e-mail Thursday. Instead, the ISP will support only the Sender Policy Framework to fight spam by verifying the source of email sent to its users, he said.

AOL's rejection comes a week after an IETF group considering Sender ID as a standard said the proposal needed rewriting. Earlier this month, the open source groups Apache Software Foundation and Debian Project dismissed Sender ID because the license would prevent them from supporting the technology.

AOL is concerned about the lack of acceptance for Sender ID in the open source community, Graham said. Additionally, the ISP is afraid that recent changes to Sender ID will make it incompatible with the original SPF specification, he said. AOL had endorsed Sender ID when it was submitted to the IETF in June.

While AOL's decision could be seen as another setback for Sender ID, Microsoft said AOL's action is fully in line with the Sender ID proposal, which is being revised.

Support for SPF essentially equals support for Sender ID, said Microsoft spokesperson Sean Sundwall. "AOL's decision to conduct just the SPF check reflects exactly the flexibility provided by the Sender ID proposal. Sender ID is still alive and there are two ways to do the checking," he said.

Sender ID combines SPF, developed by Meng Weng Wong of Pobox.com, and the Microsoft-developed Caller ID specification. In May, Microsoft and Meng agreed to merge their proposals and submitted it to the IETF a month later.

The Sender ID proposal to the IETF is being rewritten to allow flexibility on which checking method is used, either the SPF method or a check for the Purported Responsible Address, which was first published as part of Microsoft's original Caller ID plan, Sundwall said. "AOL's news is much ado about nothing," he said.

Microsoft and Wong propose Sender ID as a standard for email authentication, designed to prevent faking of email addresses and the origin of a message. Criminals have used the ability to forge the origin of an email, for example, in schemes to send email that looks like it is from a bank and tricks users into giving up personal information.

With SPF, organisations publish a list of their approved outgoing email servers, called an SPF record, in the Domain Name System. That SPF record is then used to verify the source of email messages sent to other internet domains. Microsoft's Caller ID works in a similar way.

AOL is not completely backing out of Sender ID. While it won't check Sender ID records on mail coming in, it will publish Sender ID records for outbound mail, Graham said.

AOL said it is also looking at Domain Keys, a technology developed by rival Yahoo, for possible use in tandem with SPF. With Domain Keys each email gets a digital signature to verify its source.


IDG UK Sites

Best Christmas 2014 UK tech deals, Boxing Day 2014 UK tech deals & January sales 2015 UK tech...

IDG UK Sites

Apple's 2014 highlights: the most significant Apple news of 2014

IDG UK Sites

See the festive spots creative companies have released for Christmas

IDG UK Sites

Ultimate iOS 8 Tips: 35 awesome and advanced tips for using iOS 8 on iPhone and iPad