SpamHaus Behind .mail Top-Level Domain

securitas writes "The SpamHaus Project is the group pushing ICANN to create a new trusted-sender system and the .mail top-level domain. SpamHaus proposes that registrants under the .mail TLD would pay at least $2000 per year to and 'agree to abide by certain anti-spam mailing practices.' The interesting twist is that companies that comply with the US CAN-SPAM act - which SpamHaus opposed due to the legalization of bulk unsolicited commercial e-mail - would not be eligibile to register a .mail address. The .mail TLD proposal was recently discussed on Slashdot."

Comments

$2000 is the upper limit

[alanw]

In this posting to news:news.admin.net-abuse.email Steve Linford of Spamhaus says:

the $2000 quoted in the application is the highest estimate, given at the deadline because ICANN rules don't allow you to increase a price later

and in this posting he says

(we'd prefer it in the region of $250)

Re:Goodby home mail server

[RetroGeek]

But there is nothing stopping an ISP from allowing mail from your domain, as long as there is a certificate attached to it.

So then you need to buy a certificate. And there will be competitino for these certifiicates which should drive the price down to a reasonable level.

Re:Goodby home mail server

[aderusha]

just like competition has driven down the price of ssl certificates? that's outrageous.

like the original poster, i run about 10 domains on a mail server at home for myself and some friends. at $250 for a 2 year cert (bargain basement prices), that's going to cost me $1250 a year, which i think is unreasonable for the "little guy" who isn't running a company.

keep in mind that there are plenty of people happily using the internet that have no commercial intent whatsoever. i know it's very un-american of me, but none of my websites and domains are intended to make money.

competition is only going to drive down prices if there is true competition, which currently isn't the case with certificates. basically, microsoft has de facto control over who can issue certificates as they control which trusted root certificates are going to ship with their browsers. until this situation has changed, i'll take my chances with either un-secured connections or educating my users on how to install a root certificate into their browser before i pay into the verisign cartel.