An industry organization representing heavyweight e-mail providers Yahoo Inc., Microsoft Corp., America Online Inc. and EarthLink Inc. released recommendations yesterday for ending spam e-mail.
The Anti-Spam Technical Alliance's (ASTA) statement of intent, posted on the individual sites of members, includes a list of suggestions and best practices for Internet service providers, e-mail providers, governments, corporations and bulk e-mail senders.
Among other things, ASTA recommended that ISPs shut down so-called open relays, or e-mail servers that allow parties that don't own the mail server to relay mail through them without needing to log in first. The group also suggested that ISPs crack down on virus- and worm-infected computers on their networks and closely monitor features that let people automatically register for ISP accounts.
If implemented, the recommendations could greatly reduce the amount of spam, the group said. The guidelines are the product of more than a year of collaboration between member companies and focus mainly on ISPs, whose networks are often used to distribute spam.
ISPs that host Web pages should also remove simple programs that can generate e-mail messages, like formmail.pl, a popular and free program for providing feedback from a Web page. ISP customers should also be required to authenticate before sending e-mail from the ISP's network, ASTA said.
For bulk e-mail senders, the group discouraged the practice of harvesting e-mail addresses without the consent of the e-mail sender, as well as other common spamming practices such as source-address spoofing and sending e-mail containing information that is false or misleading.
Consumers were generally let off the hook. While e-mail users have a duty to educate themselves about spam, ISPs and others with a stake in e-mail need to do a better job of providing consumers with tools and information to stop it, the group said.
Many of the technical suggestions have long been accepted wisdom within the technical community, said John Levine, a member of the Internet Research Task Force's Anti-Spam Research Group. "This is all kind of motherhood and apple pie," said Levine, who noted that AOL and most other ISPs have been following many of the stated best practices for years.
Even so, the recommendations are still useful if they can reform the small number of organizations with sloppy mailing practices whose systems are frequently exploited by spammers. "It's too bad that the first thing you have to do is tell people not to do something stupid, but there are still a lot of small companies with mailing lists and loosely administered mail servers," Levine said.
ASTA acknowledged that its antispam measures have already been adopted by most "responsible organizations," but it said group members hope to encourage broader global adoption of secure e-mail practices and reduce the number of opportunities for spammers.
While not exciting, common-sense recommendations like those laid out by ASTA are a welcome relief to the Internet community, Levine said. "Generally [the recommendations] are reasonable. It demonstrates that the technical management of ISPs do understand the e-mail situation well," he said.
Recommendations that are in line with best practices are more likely to find acceptance than new schemes or standards intended to stop spam, he said. "There was always some concern that [ASTA] was going to come up with something weird. The fact that you can look at this and say 'Yeah. Sure,' is good, because it means that they're not going off on some tangent."
Plans to stop spam have taken on a new urgency in the past year, as the volume of unwanted e-mail has begun to eclipse legitimate traffic. In recent months, leading companies such as Microsoft and Yahoo have proposed competing plans for e-mail sender authentication, which allows e-mail recipients to verify the source of an incoming message and stop spam e-mail messages that display forged, or spoofed, sender addresses.
In May, Microsoft agreed to merge its recently announced Caller ID antispam proposal with the Sender Policy Framework, or SPF. The company reached an agreement with SPF's author, Meng Weng Wong, to roll the two proposals into one specification.
Under the merged proposal, organizations that send e-mail will publish the addresses of their outgoing e-mail servers in the Domain Name System (DNS) using XML. Companies will be able to check for spoofing at the envelope level, as proposed by SPF, and in the message body, as proposed by Microsoft, the statement said.
A separate plan backed by Yahoo, called DomainKeys, uses public/private encryption keys to create a unique signature based on the content and origin of each e-mail message (see story).
The ASTA document doesn't back either authentication scheme but says both are promising and can be used to prevent address spoofing.
Behind the scenes, the document masks a heated battle within the Internet Engineering Task Force's MARID (Mail Transfer Agent Authorization Records in DNS) group over the scope and details of the e-mail authentication proposals, Levine said.
Despite disagreements within the group, those involved consider spam an urgent problem and plan to have a sender authentication plan ready for public viewing by the end of August.
"I can't ever think of a situation where there's been a feeling of urgency like there is with this. There's really a feeling that if we don't do something soon, people will give up on e-mail," Levine said.