Slashdot Mirror


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."

304 comments

  1. Maybe a Good Thing? by Liselle · · Score: 5, Insightful
    I never get to be the one who says "but wait, this is a GOOD thing", so I'll toss it out there now, flamebait be darned.

    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.
    This could probably be worded a little more clearly. Complying with the CAN-SPAM act is as easy as not doing anything at all. I think what the submitter means, correct me if I'm wrong, is the "one-shot" bulk mail that a company is allowed to send you under CAN-SPAM. Obviously, SpamHaus considers this spam, still, even though it's technically legal (I would tend to agree).

    This new TLD proposal, according to their FAQ, is not aimed at stopping spam, or replacing the email infrastructure from the ground up. It's more towards legitimizing non-spam email. It may not be technically possible (not my area of expertise, I remember some nay-sayers in the last article discussion who at least sounded like they knew what they were talking about), but I still think their hearts are in the right place. Am I wrong?

    I'm looking forward to the whitepaper they've promised on it.
    --
    Auto-reply to ACs: "Truly, you have a dizzying intellect."
    1. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 4, Insightful

      Not good. We can't trust to filter our mail based on some fixed definition of "spam". I want to choose *my* definition, or choose whose definition I want to use (people can publish black lists and I can choose the black list I want to use).

    2. Re:Maybe a Good Thing? by Liselle · · Score: 2, Insightful

      Since .mail wouldn't define spam, only "not spam", isn't it a fancy/expensive whitelist? Like anything else, you can choose to filter email from .mail however you like.

      The only exception that comes to mind if your ISP took the decision out of your hands. However, they would ONLY do this if it became massively widespread (otherwise they'd be throwing out 99% of valid email). I'd like to think that if .mail ever reaches the kind of penetration that would make ISPs take notice, we wouldn't need to worry about it. An ISP that wants to keep its customers can't afford too many false positives.

      --
      Auto-reply to ACs: "Truly, you have a dizzying intellect."
    3. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 3, Insightful

      > isn't it a fancy/expensive whitelist?

      Yes it is, and its yet another attempt to get a service out of the control of the end user.

    4. Re:Maybe a Good Thing? by slither_1 · · Score: 2, Interesting

      Why don't ISPs force authentication on their SMTP servers to cut down on spam? wouldn't this make sense? I mean, I work for an ISP, and they have a banned IP list from within their domains. When they get a complaint, these userser a put on the list and can't send mail anymore using our servers (or any other SMTP servers on port 25)... the problem with that practice, is that they can only ban people on static IPs, and most of their customers are on DHCP and dynamic IPs. Seems to me, if they force authentication on their SMTP servers, ISPs would have more control when it comes to blocking spammers from withing their network... oh well, just my 2 cents!

    5. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      Nothing is being taken away from the end user. It just gives you a new option.

    6. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 5, Insightful

      When big isps only accept mail from servers registered in the .mail tld, then that takes away my ability to run my own mailserver for my own private domains. How do you mean nothing is taken away from the end user.

    7. Re:Maybe a Good Thing? by Monkelectric · · Score: 1

      ok, I own 10 domains ... thats a cool 20,000 dollars for me to be able to send emails from them and have a reasonable chance of getting through.

      --

      Religion is a gateway psychosis. -- Dave Foley

    8. Re:Maybe a Good Thing? by squiggleslash · · Score: 1

      Most email clients do not support any of the SMTP authentication non-standards.

      --
      You are not alone. This is not normal. None of this is normal.
    9. Re:Maybe a Good Thing? by timmyf2371 · · Score: 1

      I've never had a problem connecting to any SMTP server which requires authentication.

      --

      Backup not found: (A)bort (R)etry (P)anic
    10. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      What's to stop them spammers from spoofing their from addresses as being .mail domains?

    11. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      It doesnt take away your ability, it forces you to rely on your upstream provider for support and their .mail domain which can be directed to with our good friend the MX record. this is the same upstream provider that you already rely on for your connection in the first place.

    12. Re:Maybe a Good Thing? by silas_moeckel · · Score: 1

      Why nobody else said the mail had to come from an address with .mail just a server, you forward your email via a smarthost that you ISP should be providing for you. Your server dosent need a .mail address to receive mail. Your ISP could be doing this for you allready it's not hard to do with a router, but few do and arguably more should. I have been using a smarhost for outgoing mail for years several in fact. I've never had an issue with my mail being denied or marked as spam because it all goes though a nice relay with proper reverse DNS and thats not a dynamic IP.

      I dont realy agree with making a 2k a year buy in server white list but it's not the worst idea on the table.

      --
      No sir I dont like it.
    13. Re:Maybe a Good Thing? by Zak3056 · · Score: 2, Interesting

      work for an ISP, and they have a banned IP list from within their domains. When they get a complaint, these userser a put on the list and can't send mail anymore using our servers (or any other SMTP servers on port 25)... the problem with that practice, is that they can only ban people on static IPs, and most of their customers are on DHCP and dynamic IPs.

      I wonder why they don't take this to the next level and use the information in PPP or DHCP logs to blacklist the ones with dynamic addresses?

      --
      What part of "shall not be infringed" is so hard to understand?
    14. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 3, Insightful

      THis most certainly is NOT a good thing.

      I own my own mailserver. I built it myself. I run it myself. I'm the only one with an account. It is for my large site that has about 100,000 registered accounts. Not one single piece of spam has ever been sent from my servers nor would it. It is used merely to send notices and account registration confirmations and the like to users who have accounts and rely on these notices and emails as part of the functionality of our site.

      It is a non-commercial site. I make zero dollars. In fact, I pay for everything out of my own pocket to the tune of about $2,500/yr.

      Now, on top of this, I need to pay $2,000 for some stupid .mail domain? Why? I'm not guilty of spamming. Why should I be treated like a spammer when I'm not? And why should AOL get to spend only $2,000 for a .mail domain while I have to spend $2,000 for a mail domain? Certainly my hobbiest, free, non-commercial persuit should not have to pay $2,000 the same as a mega ultra-billion dollar corporation does?!

      This is just another step closer to a world where only the mega corporations control anything on the internet and the rest of us - even those who used to produce and distribute free content - are nothing more than consumers.

    15. Re:Maybe a Good Thing? by timmarhy · · Score: 1

      err and you work for an isp? tell me sir, what currently stops me telneting into any smtp server, saying helo and sending a user a message? now what if i write a perl script to do this for me, read addresses from a database and send messages on a massive scale? oh wait i just became a spammer.

      --
      If you mod me down, I will become more powerful than you can imagine....
    16. Re:Maybe a Good Thing? by Bilestoad · · Score: 1

      The basic idea is good but the implementation (as reported here) is not so good.

      People send spam because the cost is incredibly low. Requiring fees of $1000 or $2000 or $any,000 is wrong because it just means the spammer has a target, has to send out x number of messages to make the proposition attractive _before_ getting caught.

      What is a better idea is a system where prepaid credits are used to send emails. Legitimate users are issued prepaid certificates good for a small volume of email. As their standing as good netizen goes up through repeated patronage of the .mail system the number of emails allocated per certificate goes up, perhaps to the point where they can renew annually and carry over credits for unused email allocation to the next allocation period. Each issue of certificates costs an appropriate amount of money.

      Where spammers win is by exploiting the fact that the cost of email is fixed but the number of emails that can be sent for that cost is not. To defeat spam the marginal cost of email must be increased. This scheme would achieve that.

    17. Re:Maybe a Good Thing? by damiangerous · · Score: 1

      Outgoing port 25 filtering. Cox, for one, does it. I can't connect to any SMTP server besides theirs unless I use a non-standard port. Very irritating.

    18. Re:Maybe a Good Thing? by slither_1 · · Score: 1

      Exaclty... unfortunately, my position is not important enough to make any positive changes to the company policies. My company implements a block on port 25, to block home made SMTP servers (not very effective). But I still think forcing authentication would be a good first step in the fight against spam.

    19. Re:Maybe a Good Thing? by timmarhy · · Score: 1

      blocking port 25 doesn't stop examples such as my perl script. like i said there is no way to stop spam completely, but we sure could cut down on the volume

      --
      If you mod me down, I will become more powerful than you can imagine....
    20. Re:Maybe a Good Thing? by Geoffreyerffoeg · · Score: 0, Flamebait

      When big ISPs block your SMTP ports?

      When the US declares it a crime (mail fraud, I think?) to open others' mailboxes and stick mail in there?

      Is nothing taken away from the end users there?

      So sorry. The Internet is growing larger than the old methods can handle. I too would love to have my own mail server, but it's probably becoming less and less practical; who knows if I'm a spammer or not?

    21. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 1

      Yes, and I realy want to keep it to only relying on them for the connection and nothing else.

      Also, what you'd need is configuring a smarthost, no MX records get involved.

    22. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 2, Informative

      Well, I have been running both private and business smtp servers for the last 12 years, so I am somewhat aware of what is possible...

      A smarthost stops working the day your ISP decides that all mail from their servers must have a from address that they controll or are authorative for. Something that happens to be a rather obvious step also in combination with a .mail TLD setup.

      Don't tell me that won't happen, It happened to me with 2 ISPs already and is the main reason I decided to do my own delivery besides it giving a much better insight in the delivery status of mail.

      Last but not least. it forces me to depend on my ISPs servers. Those have shown a lot less reliable then the connection.

      So, while a smarthost may work in quite a few cases, it doesn't always and forcing it on people will take away the possibility to run their own mailserver.

    23. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 1

      Heh, I do not mind at all a system that requires proof of being able to configure a mail server and that excludes those who abuse it.

      I do not see how paying 2k makes sure of that, while it makes sure that only businesses can run mailservers

    24. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      why should we assume that an AC who doesn't know the diff. between maii and the web would somehow understand how to solve the spam problem?

    25. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 2, Insightful

      A good thing? This is one of the most f***** ideas I have ever heard. $2000? Just so I can send email to 1 or 2 customers a month? I can't afford that. Which means I would have to go back to back to paying someone to host my website and email and back to getting getting spam on an hourly bases. I have tweaked my spam filters and blocks to better than 99.7%, do they think a site host or ISP is going to take the time that I do to get rid of spam. Not at a price I can afford. This makes as much sence as a screen door on a $%#^% submarine.

    26. Re:Maybe a Good Thing? by EndlessNameless · · Score: 1

      I believe that properly configured servers wouldn't accept .mail messages without a proper originating IP address for the server (easily checkable via reverse DNS... if the source IP doesn't match a server registered with a valid .mail TLD, the message gets dropped).

      --

      ---
      According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
    27. Re:Maybe a Good Thing? by Script0r · · Score: 1

      uhhh.... I have cox internet and I use outside smtp servers all the time. Maybe the problem is you.

    28. Re:Maybe a Good Thing? by jwkane · · Score: 2, Insightful

      How about getting a .mail subdomain from an ISP? A few bucks extra and you have yourdomain.yourisp.email ready to go.

    29. Re:Maybe a Good Thing? by Desert+Raven · · Score: 1

      No, he's right. And you're right.

      Cox has implemented outbound port 25 blocks, but not uniformly throughout their entire network.

      For me, it wasn't too big a deal, since I have my own mail servers at a colocation facility, I use a non-standard port for my outgoing mail.

    30. Re:Maybe a Good Thing? by firewood · · Score: 2, Insightful
      When big isps only accept mail from servers registered in the .mail tld, then that takes away my ability to run my own mailserver for my own private domains. How do you mean nothing is taken away from the end user.

      It does not take away your ability to run your own mail server. You can still run it on your private network... or maybe to communicate with systems run by people who trust you to not misuse an obsolete protocol. But nothing currently says that my mail server (or that of my ISP) has to talk to yours, especially if you don't take sufficient measures to differentiate yourself from joe spammer.

    31. Re:Maybe a Good Thing? by Angry+Pixie · · Score: 2, Insightful

      How could the ISP take the decision out of my hands? The way I see it, .mail is just another TLD. It means no more to me than a .cn or a .tv does. I would never ever set an email filter to automatically accept any emails coming from a particular domain. I get plenty of spam that purports to come from .edu, and as a matter of fruitless civil disopedience, I block all .gov addresses.

      When it comes down to it, isn't it still about me deciding whether I want to read an incoming email or filter it out?

      How would an ISP use a .mail as a whitelist anyway? I'm not clear on how it all works, but my understanding is that my ISP isn't blocking any TLDs, so what would the benefit be to a registrant since there's still no guarantee that people will accept solicitations?

    32. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      Moderator: I could not help but notice that your interest in wasting three sets of moderator points modding down the above three posts might reflect an inability to confront the issue of penis.

    33. Re:Maybe a Good Thing? by pinkUZI · · Score: 2, Insightful

      Not to mention this would have a horrible effect on any of us running our own self-serve linux boxen. Redhat might have to take sendmail off their list of applications installed by default if all email gets blocked that doesn't have a .mail domain associated with it. I doubt many home users are going to cough up $2-3k!

      Has anyone else noticed how hard it is to get smtp service these days? Go ahead, register a domain & pay for email service. If they offer smtp service at all they won't give it to you up front. They'll have you make a special request and then ask why you don't use your ISP's smtp service. DUH - my ISP is not going to let me send email from me@mydomain.com to anywhere! This proposes to make it even more difficult.
      --
      You are receiving this message because your browser supports Slashdot Sigs and you have Slashdot Sigs enabled.
    34. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      Hello Moron.

      You know as well as I that what you say is 1. rather obvious, and 2. utterly pointless.

      Mail is a means of communications in case you never noticed. What the fuck is the point of what you are saying?

      And explain to me how paying $2k is in any way a guarantee that someone is not going to spam?

      Clueless moron.

    35. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 1

      > who knows if I'm a spammer or not?

      Like I already explained in other posts as well:
      1. I do not mind a new protocol, rather the opposite.
      2. I do not mind a whitelist or similar measures.
      3. I DO mind a senseless measure like havign peopel pay $2k because it will not stop any spam but will put control in the hands of bigger corporations.

      Whenever they come up with the suggestion that paying a lot of money to a domain registry will stop spam I suggest lookign very carefully at if they actually want to stop spam or just see it as a rather easy way to get a new revenue stream.

      At any rate, I don't object to protocol changes, whitelists, and anti spam measures in general, I do object to a measure that will just cause more proffit for a few while takign away usefull features from the enduser and not solving the real problem.

    36. Re:Maybe a Good Thing? by FictionPimp · · Score: 1
      I would rather see them just placing a header in each email address for domains that dont have a .mail. But if I have to choose between running my own mail server or no more spam, I would rather be able to run my own mail server. I can filter the spam.

      In any case, no isp could do this because of the fact I still havn't seen anyone address the fact of disputed domian names.

      Note to self, save 2000.00 to register aol.mail

    37. Re:Maybe a Good Thing? by TheRaven64 · · Score: 2, Interesting
      How about getting a .mail subdomain from an ISP? A few bucks extra and you have yourdomain.yourisp.email ready to go.

      The ISP's .mail domain could be revoked if a single one of their subdomain customers broke the conditions of use for the .mail domain. I doubt an ISP would risk this (sell a subdomain to 1000 people, one violates the T&Cs, ISP's domain is revoked, ISP has 999 very irate customers who now can't send mail.)

      I doubt AOL, for example, could get a .mail domain, since they would not be able to guarantee that all of their customers would abide by the terms. The same is true of most ISPs. This leaves large corporations as the only ones who could get one, individuals would not, meaning that you would still have to let through other email, completely defeating the point.

      Finally what's the response time on closing a .mail domain? A day? Does a spammer make more than $2000 in a day? Probably. So we're left with:

      1. Buy .mail domain.
      2. Send spam from it solidly for a day, or until it's revoked.
      3. Repeat. (Oh and profit. Probably quite a lot)
      The people this kind of thing would hurt, are the ones that don't make money from sending email. The people who make the most from sending email are spammers.
      --
      I am TheRaven on Soylent News
    38. Re:Maybe a Good Thing? by yulek · · Score: 2, Insightful

      But nothing currently says that my mail server (or that of my ISP) has to talk to yours, especially if you don't take sufficient measures to differentiate yourself from joe spammer

      differentiating how? by coughing up $2000? that's crazy.

      --
      in this age of communication i'm just not getting through
    39. Re:Maybe a Good Thing? by silas_moeckel · · Score: 1

      Either way it's still just an expensive whitelist. How long before spammers buy up a random .mail domain use it for a week before the spam cops catch on? Even if it's a day can the spammers make it worth there 2 grand? How many spammers will just use there stolen credit cards they are allready using to snag accounts with anyway?

      --
      No sir I dont like it.
    40. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      "who knows if I'm a spammer or not?"

      Yeah, your clearly right!!!

      At the same time, who knows if you are an Al-Qaeda terrorist? I think I should kill you under the "preventive measures act".

    41. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      "and as a matter of fruitless civil disopedience, I block all .gov addresses. "

      Then you probably will understand this:
      If a .mail TLD is really accepted as a kind of whitelist, how long do you think your goverment will last to pass a law so mail will *only* be allowed from blessed .mail servers?

      * Government will be happy: they will say that way they can control the tipical binladen guy (and they won't need things like Carnivore no more: they'll just tap ISP mail exchangers)
      * Corporations will be happy: they will be able to squeeze people in new and interesing ways

      The only one to loose (as almost always) will be John D. Citizen, both in his moneybag and in his civilian liberties.

    42. Re:Maybe a Good Thing? by Herkules · · Score: 1

      "DUH - my ISP is not going to let me send email from me@mydomain.com to anywhere!"

      Yes but use reply-to then!!! Thats what its for!

      "When the "Reply-To:" field is present, it indicates the mailbox(es) to which the author of the message suggests that replies be sent."

      From http://www.cse.ohio-state.edu/cgi-bin/rfc/rfc2822. html

      (I hope this helps =)

      --
      CIA Factbook 2002 (US):"Since 1975, practically all the gains in household income have gone to the top 20% of households
    43. Re:Maybe a Good Thing? by Herkules · · Score: 1

      "A smarthost stops working the day your ISP decides that all mail from their servers must have a from address that they controll or are authorative for."

      Why dont you use reply-to ? Its there when you want replys to a address other than that you send from.

      (I hope this helps =)

      --
      CIA Factbook 2002 (US):"Since 1975, practically all the gains in household income have gone to the top 20% of households
    44. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      Yes, but often reply-to doesn't show up as the sender. I want me@mydomain.com to be my identity, not stupidusername@mylameisp.com

    45. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 1

      because I actually want the mail to show up as being from me@mydomain maybe?

    46. Re:Maybe a Good Thing? by Anonymous Coward · · Score: 0

      Hey, don't forget the .mail registrars and their profits...</conspiracy>

    47. Re:Maybe a Good Thing? by elemental23 · · Score: 1

      How do you expect to send this mail if you can't make outbound port 25 connections?

      --
      I like my women like my coffee... pale and bitter.
    48. Re:Maybe a Good Thing? by CableModemSniper · · Score: 1

      His perl script obviously opens port 5 twice, thus opening port 5^2, which is the same thing as 25, but it 'tricks' the computer.

      --
      Why not fork?
    49. Re:Maybe a Good Thing? by mgbastard · · Score: 1
      When big isps only accept mail from servers registered in the .mail tld, then that takes away my ability to run my own mailserver for my own private domains. How do you mean nothing is taken away from the end user.

      So you'll have to trunk your email through your ISP's upstream mail server, which is configured to trust yours.

      Boo hoo. I prefer this too. Maybe you bastards will start encrypting your mail if your worried about somebody sniffing it's traffic.

      $2000 a year seems pretty high though. I understand ICANN fees are very expensive, and they need to recoup this, but a way for small businesses to become certified and not pay the same tax as exxon might be a step forward.

      At $2000 a pop, that would be a HUGE cash cow for spamhaus, and I'd have a problem that. I'll do it for donations, I'm 100% sure I could get several datacenter operators to donate rack space and bandwidth to run a TLD registry. That and a team of trusted hackers together (a real hacker, not a cracker you kids...) to run the ops - no problem. SSL cert signing verification is already a problem solved, and the same front-end for issuing a .mail domain is done - just issue it to whomever has the domain.

      That all being said, this is really no different than the SPF proposal, it just formalizes it the way DNS is designed. More meta like SPF provides can be tagged into TXT records or other RR's created to handle the problem. I think I'd like to see either a .mail TLD go through - or a IETF std for DNS records to handle the trusted sender problem.

      --
      Anyone seen my low uid? last seen 10 years ago while panning the #@$# out of Taco's 'web based discussion system'
    50. Re:Maybe a Good Thing? by firewood · · Score: 1
      differentiating how? by coughing up $2000? that's crazy.

      Every add up how much your parents spent on snail mail postage over their lifetime, adjusted for inflation? Friends send me letters using first class postage; bulkrate stuff goes directly into the recycle bin.

    51. Re:Maybe a Good Thing? by Geoffreyerffoeg · · Score: 1

      > At the same time, who knows if you are an Al-Qaeda terrorist? I think I should kill you under the "preventive measures act".

      I am Indian by race and have almost Arabic skin color. I would question the security of any airport that doesn't look at me twice.

    52. Re:Maybe a Good Thing? by SillyNickName4me · · Score: 1

      I don't mind the idea of a whitelist for smtp servers, what I simply fail to see is why it has to cost $2000.

      I run my own DNS, and before I can tell my registar that I want to use it, I have to register the DNS itself as a valid DNS. That however is free.

      I don't see any reason why we cannot have a similar solution (with or without .mail TLD) for smtp servers in that domain and why I'd have to pay some seperate entity an insane amount for it.

      Best would be imho an IETF standard for DNS records to handle trusted/authoritive smtp servers for each domain.

      SPF doesn't discriminate based on if you can pay a fee or not, and puts it into the hands of the domain owner to publish which servers can send mail for a specific domain.
      That seems to be a much better solution then havign someone run a TLD for this purpose. The whole idea of a central authority on this is alien to the nature of the internet.

    53. Re:Maybe a Good Thing? by damiangerous · · Score: 1

      They just didn't get to your area yet. Port 25 is officially blocked in both directions.

  2. Correction by rgmoore · · Score: 4, Insightful
    .' 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.

    That's not quite correct. The SpamHaus rules wouldn't ban anyone who obeyed the CAN-SPAM act. Presumably most ordinary companies obey CAN-SPAM by refusing to do anything that vaguely resembles spamming, and they'd be just fine under the SpamHaus rules. What SpamHaus wants to do is to use a stricter definition of what constitutes spam, so that some senders who meet the terms of CAN-SPAM still wouldn't qualify.

    --

    There's no point in questioning authority if you aren't going to listen to the answers.

    1. Re:Correction by eaolson · · Score: 1
      That's not quite correct. The SpamHaus rules wouldn't ban anyone who obeyed the CAN-SPAM act

      I belive you are mistaken. As I understand CAN-SPAM, you can spam all you want, so long as you have a postal address in the mail, a working opt-out mechanism, and dont forge anything. Note: complying with CAN-SPAM just means your email is legal, not that it isn't spam.

    2. Re:Correction by Anonymous Coward · · Score: 0

      The companies I work for are interperting the CAN-SPAM requirements as:

      Postal Address(no P.O. Box)
      Clearly worded opt-out in the same font as the rest of your email
      Clear subject line(That indicates that this is in fact an advertisement of some type)

    3. Re:Correction by rgmoore · · Score: 2, Informative

      I think that you're misreading what I wrote. The point is that there are two ways of obeying the CAN-SPAM act:

      1. Putting a legitimate address in the mail, having and opt-out, etc.
      2. Refusing to spam.

      My point is that the original article seems to say that neither group 1 (spammers who follow the rules) nor group 2 (non-spammers) would be allowed to register under .mail. This would obviously be stupid, and isn't what SpamHaus is saying.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    4. Re:Correction by bug-eyed+monster · · Score: 1

      Agreed. This is all to say: The rules for owning and keeping a .mail domain will be more restrictive than those imposed by CAN-SPAM.

      The summary is a bit misleading, it's missing one key term which I've added here in bold: "... companies that comply with the US CAN-SPAM act ... would not necessarily be eligibile to register a .mail address." (or "automatically" I suppose).

    5. Re:Correction by eaolson · · Score: 1
      The companies I work for are interperting the CAN-SPAM requirements as: Postal Address(no P.O. Box) Clearly worded opt-out in the same font as the rest of your email Clear subject line(That indicates that this is in fact an advertisement of some type)

      And if they're interpreting these when they send unsolicited commercial bulk email, then they're spamming.

    6. Re:Correction by Anonymous Coward · · Score: 0

      Buy your definition of SPAM. Ready the CAN-SPAM and as per that document (which is law) it's not SPAM.

      Spamhaus drives me nuts. They are Zelots that want to "Purify" the world of what they think is SPAM.

      Be honest with yourself. Out of 100 SPAMs that you get how many of them are "legal" as per CAN-SPAM? Maybe 5 or less I'd guess. CAN-SPAM is quite well designed since most bulk spam is has faked email headers, no mailing address, invalid return address etc etc etc.

      If all that's gone then SPAM would not be a problem and then Spamhaus should not need to treat everyone as guilty until proven innocent (or pays the appropriate fee)

    7. Re:Correction by eaolson · · Score: 1
      Buy your definition of SPAM. Ready the CAN-SPAM and as per that document (which is law) it's not SPAM.

      No, that is the industry-standard definion of spam and has been for over a decade now. This business about "it's not spam if you can opt out" or "it's not spam without faked headers" or "it's not spam unless it's fraudulent" is incorrect.

      I'm not saying CAN-SPAM-compliant spams are illegal, just that they *are* spam. Yes they have a (presumably) valid opt-out mechanism. How am I supposed to tell the difference between the CAN-SPAM compliant mom-and-pop-drustore-selling-cheap-viagra.com and the chinese-hucksters-selling-powdered-rhino-horn.com? They'll both look the same in an email, but unsubscribing to one will get me off a list, and unsubscribing to the other will added to dozens more.

      The idea that there are many different definitions of spam, as I heard one claim on CSPAN when CAN-SPAM was being considered, is FUD put out by the DMA.

      If all that's gone then SPAM would not be a problem and then Spamhaus should not need to treat everyone as guilty until proven innocent (or pays the appropriate fee)

      No. If all the "illegitimate" spam went away overnight, the problem would get worse. Spam would no longer be considered to be a haven of scammers and frausters, and it would be seen as a legitimate marketing tool.

      There were 22.9 millions businesses, in the US alone, in 2002. If 1% of those businesses sent you one email just once per year, you'd be getting over 600 per day.

      And thanks to CAN-SPAM, you'd have to opt-out of each one, individually.

      A gentle reminder. SPAM is Hormel's trademark for their potted meat food product. Spam is unsolicited bulk email.

  3. $2000/year by BoomerSooner · · Score: 0, Flamebait

    Give me a fucking break. I'll stick with my .com for now.

    1. Re:$2000/year by dealsites · · Score: 2, Insightful

      I wouldn't pay it either, but Id be happy to accept all mail from www.*.mail if I could be sure it wasn't spam. It would be good for Yahoo, MSN, and other web mail places to get a .mail domain.

      --
      Hot deal search engine. Better than google, froogle, pricewatch, pricegrabber, etc!

    2. Re:$2000/year by BitWarrior · · Score: 1, Insightful

      Actually, this fee would be counter-productive IMHO. Spam or borderline spam companies can easily fork over 2 grand to dump a few million e-mails before having their domain revoked. My little company can't afford it though so anyone allowing only .mail addresses in will block my legit e-mails. A lower fee combined with ultra-fast shut downs of offenders and tough identity checks going in would go farther I think. Even with all of this, it sounds like yet another pie in the sky idea of spam blocking that will end up on the shelf with all the other unimplemented "good" ideas.

    3. Re:$2000/year by Saeed+al-Sahaf · · Score: 3, Insightful

      Yup. And Varisign will LOVE slurping up those .mail fees, too. By the way, Varisign is in the process of trying to destroy ICANN, which by itself would not be a bad thing *IF* ICANN's responsibilities shifted to the UN. But I'm sure that has zero chance of reality.

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    4. Re:$2000/year by DAldredge · · Score: 1

      Like the UN could do any better.

    5. Re:$2000/year by Saeed+al-Sahaf · · Score: 2, Insightful
      Like the UN could do any better.

      Perhaps not. But at least it get's it out of the grubby hands of VariSign and the corporate dog ICANN.

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    6. Re:$2000/year by ToodlesX · · Score: 1

      Wow, that's amazing. Really cool. Blah Blah.

      spamtroll@segerdahlgraphics.net

    7. Re:$2000/year by Anonymous Coward · · Score: 0

      How about you stop spamming Slashdot first?

      That's not a sig. Knock it off.

    8. Re:$2000/year by dgatwood · · Score: 3, Insightful
      Not to mention that this would likely eliminate all mail from non-profit organizations and open source groups. Since many of those non-profit organizations are small political groups, any ISP that decided to block all mail not coming from such an expensive ".mail" domain would almost certainly end up in court as a violation of various U.S. laws that give the ultimate protection to political speech....

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    9. Re:$2000/year by Wog · · Score: 1

      But see, they *couldn't* get it, at least not for their free service. Because the moment you make it free, it becomes much more attractive to spammers, and you can't trust all your non-paying customers.

      This is all so silly. What's going to stop them from spoofing the headers to look like legit mail anyway? They already do it.

      In order to make a whitelist TLD usable, you have to have verification that email *actually* comes from where it says it does.

      And if we did that, we'd have fixed the problem anyway.

    10. Re:$2000/year by ComputerSlicer23 · · Score: 1
      Last time I checked, the constitution didn't guarantee anything about ISP's not limiting speech. As a general rule, the First Amendment only applies to the Government limiting your right to speech (specifically Congress as I recall).

      The first Amendment doesn't guarantee that the people you want to talk to have to listen. If the ISP has a policy, it's not a problem. This isn't like it's a "Voting Tax". Just like you have to pay $2,500 to get IPs, I'm not sure how $2K for a domain is limiting your free speech. Especially given that you could easily register with a forwarding system for $2-5/month to have your mail to have a sent and received by a trusted agent. A number of my friends use odd services (SpamCop, but ironically I hear they started sending Spam to people). The ACM used to do it for anyone who was a registered member.

      You could use Yahoo, HotMail, or any other number of services. You aren't being denied service. If that works, Spammers will say, well my free speech is being limited because they won't accept my mail. It's a slippery slope, you'll have a hard time winning that case.

      Kirby

    11. Re:$2000/year by schon · · Score: 1

      Id be happy to accept all mail from www.*.mail if I could be sure it wasn't spam.

      So would I - the problem is that's a *HUGE* 'if'.

      Here's what will happen if the .mail domain gains widespread acceptance:

      Spammer (say, someone like Monsterhut) will buy one of these domains. Spammer will set it up, then immediately start spamming with it.

      Then, when they get a warning from the registrar, they'll file a lawsuit against the registrar, claiming that they're not spamming, and they'll get a preliminary injunction against the registrar, stopping them from following through on the suspension.

      The lawsuit will take a year or two to wend it's way through the courts, during which time, the spammer happily continues spamming.

      But don't take my word on this - it's already happened - go read about it for yourself.

      To get around the fact that people will start adding a "whitelist exception" to block this particular .mail domain, the spammer will go and get another domain (and another, and another), and start all over again.

      The end result? The .mail domain becomes useless.

      Yes, it would be nice to have a domain you can guarantee isn't spam, but (to paraphrase Suzie Derkins,) as long as you're dreaming, you might as well wish for a pony.

    12. Re:$2000/year by Anonymous Coward · · Score: 0

      I agree with your comment and am posting this for probably the same purpose. However I think an address with spam in the name is likely to be rejected by an address harvester.

      tiab@invtools.com

    13. Re:$2000/year by DAldredge · · Score: 1

      This is the same UN that could not manage the Oil for Food program in Iraq. You know the same program that SH stole 5-10 BILLION USD from.

      Yea, I want a bunch of petty dictators controling the future of the net. Would it then fall under the US charter/UNDHR there by outlawing any speach that the UN feels is contray to the goals of the UN?

    14. Re:$2000/year by Saeed+al-Sahaf · · Score: 1
      This is the same UN that could not manage the Oil for Food program in Iraq.

      A political statement not backed up by any kind of creadible fact...

      --
      "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  4. Goodby home mail server by HaeMaker · · Score: 4, Interesting

    This is bad, as I host my own domain and send mail from it. I don't want to have to pay someone to host my mail server, and you know that plenty of ISPs will block mail that doesn't come from a .mail domain.

    I certainly can't pay $2000 a year.

    1. Re:Goodby home mail server by gcaseye6677 · · Score: 1

      Goodbye free email as well. I'm sure there will be various administrative costs associated with this new system (to ensure that your server can never be used for spam) that will be a lot more than 2 grand a year. It will be a lot harder for Hotmail and Yahoo to justify having free email access.

    2. Re:Goodby home mail server by Anonymous Coward · · Score: 5, Insightful

      I certainly can't pay $2000 a year.

      Nor can a lot of people, which is why this propsal will never work.

    3. Re:Goodby home mail server by technomancerX · · Score: 4, Insightful

      Heh one domain? You're lucky. I host 5 and handle email for all of them. I REALLY can't afford $10,000 just to provide my family with email addresses. This entire proposal is insane.

      --
      .technomancer
    4. Re:Goodby home mail server by gl4ss · · Score: 3, Insightful

      which also pretty much means it won't go through.

      it would also rely on spammers actually playing by the rules.

      --
      world was created 5 seconds before this post as it is.
    5. Re:Goodby home mail server by RetroGeek · · Score: 3, Informative

      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.

      --

      - - - - - - - - - - -
      I am a programmer. I am paid to produce syntax not grammar. Deal with it.
    6. Re:Goodby home mail server by aderusha · · Score: 3, Informative

      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.

    7. Re:Goodby home mail server by Anonymous Coward · · Score: 1, Interesting

      I certainly can't pay $2000 a year.While spammers certainly can afford the fee.

      Disclamer : I didn't read the article, so take this (as usual) with a grain of salt (at least as most as you do with the slashdot news reports - you know how much it can be misleading sometimes).

      I suppose the system would be efficient enough to suppress abuse quickly enough. Yet, I wonder how big players like yahoo or hotmail could become members of this, without resetting their whole user bases and restricting their membership policies. So I guess this is not aimed at free mail account providers, nor small enterprises like yours.
      OTOH, Perhaps there's a business opportunity for new mail account providers targeting small and medium societies.

    8. Re:Goodby home mail server by Anonymous Coward · · Score: 0

      And that is why it will not sell. It is gread drive. And as far as I am concerned, blocking whois so you can't easiliy find out who the spammers are kind of irks me. You don't thing Verisign turned off interactive whois for security for honest types?

      Heck, you could mail bomb the spammers domain.

      If we are really serious about spam, it is simple. DON'T let business run it. Although we all hate government, we let them give us drivers licenses. Would anyone trust the driving system if we let it up to for profit driven enterprise on who gets to drive through school zones?

      And if you get your internet license pulled for missuse. They can fine the heck out of you, maybe even jail. Give out spamming tickets like traffic tickets and maybe an anti-spam firewall for $29 will not seem so expensive.

      As for the spammers, take them downtown, chain them to a poll with a sign saying spammer. Lets see how long they last and if the viagra will hold up.

    9. Re:Goodby home mail server by dioxide · · Score: 4, Insightful

      Only the smtp server needs to have a .mail domain, right? You can host an indefinite ammount of domains for email on one server, I don't see any reason why you would need a .mail domain for every email domain.

    10. Re:Goodby home mail server by Anonymous Coward · · Score: 0

      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.


      Well, you haven't shopped around much. Openssl.org will sell you a certificate for US$50 per year. It works in any reasonably modern browser (netscape 4 or later).

      And if GoDaddy gets into the cert business (like they've announced) prices will drop further.

      Unless you like paying Verisign/Thwate's high prices.

    11. Re:Goodby home mail server by mdfst13 · · Score: 4, Interesting

      I used to administer a mail server that had 40,000 users give or take (IMAP only, not web). The hardware cost about $200,000. I wouldn't be surprised to find out that the support contract was $2000 a year.

      Yahoo/Hotmail both have far more users than that. $2000 is not going to be a big deal for them (for example, with 2 million users, it would be a tenth of a penny per person). I'm sure that they are already spending far more than that on hardware, software, and administration.

    12. Re:Goodby home mail server by Dinosaur+Neil · · Score: 1

      The law of unintended consequences strikes again. Maybe the cost could be graduated though; i.e. based on e-mail traffic, rather than a flat rate. It would accomplish the same as a per e-mail cost which would still have the disadvantage of dinging anyone who does mass-mail (legit SIG mail as well as spam), but it would also make things affordable for people who just run their own system.

      The question that I have still not seen answered is this; what will keep the spammers from spoofing the headers to appear to be from legit .mail domains? I've looked at this and previous articles and haven't anyone even address this. I know that spammers already alter stuff; will this new schema actually prevent that?

      --
      "I'm a scientist! I don't think, I observe!" - Dr. Clayton Forrester
    13. Re:Goodby home mail server by tverbeek · · Score: 2, Interesting
      Heh one domain? You're lucky. I host 5 and handle email for all of them.

      I'll see your 5 and raise you another 7. A few of those are actual paying customers; the rest are a personal domain, domains I and some friends use to do business with, and a few domains I host as freebies for organisations I like. This scheme would make the cut of my gross income that I give to Uncle Sam (and his state and local nephews) seem rather small in comparison... and at least for that I get free police service, road construction, and tobacco subsidies. For this I'd get nothing I don't currently have.

      --
      http://alternatives.rzero.com/
    14. Re:Goodby home mail server by justMichael · · Score: 3, Insightful

      You should really shop around...

      InstantSSL sells 2 year certs for $89.

      And they are trusted by the same 99.3% (who came up with that number) of browsers as Verisign.

    15. Re:Goodby home mail server by zapp · · Score: 1

      I don't think you can have it both ways...

      Either anyone and everyone can run their own mail server (home users as well as spammers), or only select people are allowed to run a mail server (selected by buying a certficate, or a domain, or whatever).

      As long as people are allowed to run their own mail servers, some of those will be open due to ignorance, and some of those will be used by spammers. Just a thought.

      --
      no comment
    16. Re:Goodby home mail server by cfuse · · Score: 1
      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.

      You're new here, aren't you?

    17. Re:Goodby home mail server by jrockway · · Score: 2, Insightful

      Interestingly spammers CAN pay that, so I don't see how this is a good idea!!

      --
      My other car is first.
    18. Re:Goodby home mail server by XorNand · · Score: 2, Interesting

      I've used InstantSSL. It works, no question about that. However, I was able to get it without really doing anything more than providing a credit card number. I hate Verisign with a passion, but I have to admit that their SSL certs mean a hell of a lot more to the end-user. An applicant has to jump through a lot of hoops to get a cert with them. I've had to fax them business verification paperwork and other ID. They then take the time to verify that this paperwork is kosher by cross-referencing it with state records. (At least this is how it was a few years ago--maybe things have changed). Verisign should market this aspect of their certs to the general internet-using public more. Or better yet, a less evil CA should enforce a strict verification process and then market it like crazy.

      --
      Entrepreneur : (noun), French for "unemployed"
    19. Re:Goodby home mail server by Anonymous Coward · · Score: 0

      Agreed...I own a small business, I could never afford that. I also host a lot of other businesses that could not afford that, and would not pay for it if they could. Stupid idea, to hell with Spamhaus. These assholes are just as bad as the spammers, and uppity to boot.

    20. Re:Goodby home mail server by dasmegabyte · · Score: 1

      Why not?

      To your webserver, the only difference between some smartpants linux guy running home email server and a compromised machine running a spam worm is -- well, there are probably no references to v14_ga_ra! in the email from the guru.

      --
      Hey freaks: now you're ju
    21. Re:Goodby home mail server by Anonymous Coward · · Score: 0

      Another thing: The phrase of the day is "joe job".

    22. Re:Goodby home mail server by dasmegabyte · · Score: 0, Flamebait

      And *I* don't see why small companies like myself wouldn't take the chance to lower their email hosting fees by a dollar and offer guaranteed delivery of non-spam. I already police my users (so no worries about losing access to .mail), all I'd have to do is outlay $2000 per year. I only need to host 33 email domains at $5/mo each to cover that. I already have TRIPLE that in email domains, so I'd do it. In yet another fact, I could probably get my coloc admin to grant me relay on one of his servers...and make him pay the $2000 (or rather add it to his operating costs, which are 1000 times mine).

      I mean, why the FUCK do you need an smtp server at your house anyway? I don't have a UPS Store in my basement. SMTP at home is the reason we have so much spam, plain and simple.

      --
      Hey freaks: now you're ju
    23. Re:Goodby home mail server by dasmegabyte · · Score: 1

      Which is the major advantage of .mail over certificates...certs only work on one domain string. Add mail. to the front, your cert is invalid.

      With .mail, any second or third levels would be okay. Which means you can run multiple servers, and sell offshoots to recoop your $2000.

      Furhtermore, it decreases the number of requests for authentication -- just one, to reverse lookup the domain, which you're already doing.

      And you don't have to run one SMTP server per domain, you know. Use MX records, damnit!

      --
      Hey freaks: now you're ju
    24. Re:Goodby home mail server by jnicholson · · Score: 3, Interesting

      Spammers can't afford to pay that every time they have to register a new domain because the old one got taken down due to violation of the spam rules of the hoster. And you can bet they would be taken down, if SpamHaus has anything to do with writing the rules.

      --
      "Do not drill any holes in your cat - it will not like it."
      -- Nick Davies
    25. Re:Goodby home mail server by SnappleMaster · · Score: 2, Insightful

      The reason why we have so much spam is that the protocol is shit, not that people run it at home. Spam cannot be blocked unless we fix the protocol, or at least band-aid it with some kind of OOB lookup.

      --
      Be happy. Nothing else matters.
    26. Re:Goodby home mail server by Anonymous Coward · · Score: 0

      The catch is what Government. You do know the internet extends past the US Border right?

    27. Re:Goodby home mail server by damiangerous · · Score: 2, Informative
      I hate Verisign with a passion, but I have to admit that their SSL certs mean a hell of a lot more to the end-user.

      First, when does the end user ever have any idea of what company your cert is from? That information is never even presented to the user unless the CA is unknown. The end user knows when the little padlock is closed in his browser status bar and that's it.

      Second, even were the end user to know which CA is being used, how would they have any idea of the relative difficulty of getting a Verisign cert? They would have to have gotten a cert from Verisign and someone else themselves to be able to make that distinction, or known someone who has and what end user has ever done that?

      Your choice of CA is meaningless. As long as the major browers come with the root certificate preinstalled it's all the same from the end user's perspective.

    28. Re:Goodby home mail server by Felinoid · · Score: 1

      You know that $2,000 a year is going too eather kill the preposal or kill e-mail.

      --
      I don't actually exist.
    29. Re:Goodby home mail server by 1lus10n · · Score: 2, Insightful

      Sure they can. I get spammed by plenty of people who can afford that. ISP's, banks, Amazon, partners of some company I bought a product through online, porn sites etc... All of which HAVE money. They can afford to send snail mail, they can afford 2k to spam me.

      No matter what way you cut it this problem wont be solved by political bullshit, or bussiness bullshit. Its a technical issue, it will be solved by technical means. Some hacker needs to sit down and spend a few months writing an open standard for mail that takes SPAM into account. If a company does it, it'll hurt competition and the little guy, if the gov't does it, privacy will be gone.

      This is a political solution with bussiness over-tones. I own several domains (nothing major) and want to spring up a few more over the summer. I dont spam anyone, and noone spam's people through my mailservers. But I cannot afford 2k. And I cant afford to be blocked by every major domain 'cause I cant afford 2k. Most major domains dont have mailservers setup in a way that is useful to me, so that idead is useless. This idea will screw over all small bussiness owners, and personal domain holders. Its a crock of shit.

      Give me a technical solution, written by a technical person.

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    30. Re:Goodby home mail server by thogard · · Score: 1

      Want to bet? Do you know how much professional spamers are charging to send out 500,000 messages? An idiot down the road paid them $1500 for 50,000 targetted messages to people who opted-in. Funny thing is when they 1st started talking to him, they did a "free run" of only 100 email address. He got 25 unique hits on his web site from that and some orders even. He paid up the $1500 and got 13 hits and no orders. The spamers of course got the $1500 (minus what they sent back in the form of orders) and 1/2 million peoples email boxes might have gotten more junk.

      I know computer science is the worst at looking at its history, would if you support this concept, please look into why x.400 failed.

    31. Re:Goodby home mail server by firewood · · Score: 3, Insightful
      > This is bad, as I host my own domain and send mail from it. I don't want to have to pay someone to host my mail server, and you know that plenty of ISPs will block mail that doesn't come from a .mail domain.


      Nor can a lot of people, which is why this propsal will never work.

      The current email system already doesn't work. There's no way people who get 1000's of spam emails per day will ever find email from your domain in their mail filter logs. So this plan doesn't have to work. It just has to be less broken then the status quo.

    32. Re:Goodby home mail server by Arker · · Score: 1

      Its a technical issue, it will be solved by technical means. Some hacker needs to sit down and spend a few months writing an open standard for mail that takes SPAM into account.

      I think the technical means are already in place. It's just a matter of getting everyone that runs a mail user to implement them. SMTP traffic should always be encrypted and authenticated, if every SMTP server did that the cost of SPAM would go through the roof.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    33. Re:Goodby home mail server by Anonymous Coward · · Score: 0

      "The current email system already doesn't work. There's no way people who get 1000's of spam emails per day will ever find email from your domain in their mail filter logs."

      Yup. I am close to pushing 1000 per day, and I am just a single user on my domain :(

      Cheers,

      Tels

    34. Re:Goodby home mail server by 1lus10n · · Score: 1

      please explain how I authenticate myself to hotmail.com or the like ? pgp style public key encryption is subject to key hijacking/stealing. same with any other public key crypto.

      I like the idea, but I dont see the implementation. And if we encrypt all our mail how will the gov't track terrorists ? (sarcasm is so fun.)

      --
      "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
    35. Re:Goodby home mail server by aonaran · · Score: 1

      Not everyone who runs a server is a commercial entity that can afford co-loc (or needs co-loc)
      I pay $37/month (Canadian) for a DSL connection with Static IP that I can run a mail server off of. Considering just a DSL connection is about that much anyway, that is well within my budget. Off that Server I currently host 2 domains with plans to expand into several more, but none of them are for-profit business domains, and thus increasing my monthly outlay by $166 per month is out of the question.

      There are a number of reasons why I host my own mail, one of them being increased privacy and security. Another, I admit is Vanity, (why else would one get their own domain names for personal use?) but regardless of the reasons, I fully support keeping the internet open to everyone, if you want a corporate controlled network get on AOL and leave the internet alone.

    36. Re:Goodby home mail server by aonaran · · Score: 1

      If it's just for you and your friends you can publish your own certs for free and just have your buddies install your CA certificate.

    37. Re:Goodby home mail server by aonaran · · Score: 1

      I have to disagree with you there.
      I work for a municipal government and we chose Verisign over Thawte for our site that actually takes credit card payments (despite it being twice the price) simply because of brand recognition. You can publish a Verisign Logo that links to your certificate and people DO notice it and DO trust the site more because of that. Like it or not Verisign in a lot of people's minds = trustworthy.

  5. Just cut to the chase by siliconbunny · · Score: 5, Funny

    Set up a .spam level, and we can block everything from that if we want.

    1. Re:Just cut to the chase by ewhenn · · Score: 1

      Actually, I know you were joking, but how about passing a law that all UCE would HAVE to come from a .spam domain. Nice and easy to block that way. Toss that into the CANSPAM law.

    2. Re:Just cut to the chase by Anonymous Coward · · Score: 0

      People in Hawaii could include it on their "whitelist" :-)

    3. Re:Just cut to the chase by siliconbunny · · Score: 1

      That is *exactly* what I was thinking...

    4. Re:Just cut to the chase by Anonymous Coward · · Score: 0

      Mmmmm.... Spam. I'm hungry.

    5. Re:Just cut to the chase by Dai-Sho · · Score: 1

      What's your definition of SPAM? 10 people in a room would probably define SPAM 10 different ways.

    6. Re:Just cut to the chase by SnappleMaster · · Score: 1

      I would vote for any politician at any level who was for:

      1) all UCE must be sent from a .spam domain
      2) mandatory capitol punishment for any violation

      I'm 98% serious. :)

      --
      Be happy. Nothing else matters.
  6. This is dumb by Michael+Hunt · · Score: 3, Insightful

    This is a retarded idea from the get-go.

    We already have a perfectly good, workable proposal for sender validation. It's called SPF. It's free. It will work, like this proposal, when people adopt it.

    Seriously, $2k to prove that you're not a spammer, by one organisation's definition of the phrase? That sounds like profiteering to me, much along the lines of Ironport's dodgy Bonded Sender (tm) program.

    No thanks.

    1. Re:This is dumb by ryanwright · · Score: 1

      That sounds like profiteering to me

      Really? Surely you would receive $2000 worth of services in exchange for your hard earned money!

      1. Spam everyone like crazy.
      2. Extort^H^H^H^H^H^HSell a $2000/year TLD.
      3. Profit!

      Doesn't the mob do something like this?

      --
      -Ryan, with the unoriginal sig
    2. Re:This is dumb by Anonymous Coward · · Score: 0

      Profiteering? I can't see how that's possible if it's run by a non-profit body that doesn't do anything else.

    3. Re:This is dumb by rgmoore · · Score: 3, Interesting

      But this proposal is quite different from SPF. Under SPF, anyone with a domain is allowed to define which computers are valid mail senders for that domain, but there's no further restriction. That would prevent spammers (and email worms) from falsifying their sender address, but it doesn't directly confront the issue of spam. A spammer with his own domain, presumably hosted by a spam-friendly service provider, can still define his own computers as being permitted senders for that domain and send out spam. He'll presumably be stopped once people recognize the domain and start blocking mail from it, but that just makes it a matter of playing whack-a-mole; the spammer just buys new domains in bulk from a cheap registrar and switches every time people start blocking the old one.

      What .mail does is different. It defines a known, and defended, whitelist domain. Mail from a .mail address should be safe, because the registrar actually takes steps to make sure that spammers aren't allowed to register there. One part of the proposal that I haven't seen mentioned here is that all mail sent to abuse@somedomain.mail is directed to the .mail registrar, rather than the domain owner. That means that spam complaints will be sent to a third party with the power to revoke the domain if the complaint is valid. Obviously what would be really good would be to combine the two proposals, so that somebody couldn't forge mail from a .mail server, but they do address different points.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    4. Re:This is dumb by larry+bagina · · Score: 1
      non-profit doesn't mean extra money won't be used on lavish offices, company cars, christmas bonuses, meetings in the cayman islands, fancy artwork for the executive washroom, etc.

      Alternatively, money can be transferred to for-profit businesses which are owned/run by the same executives.

      Both of those practices are common in non-profit and profit-regulated businesses (ok, it's common in all businesses).

      --
      Do you even lift?

      These aren't the 'roids you're looking for.

    5. Re:This is dumb by ahodgson · · Score: 1

      There's another issue, of course, which is that .mail cannot work without widespread adoption of SPF (or another forgery-prevention mechanism).

    6. Re:This is dumb by Dai-Sho · · Score: 2, Informative

      True. But you can then trace the money. If he authorizes a mail server via reverse DNS then he obviously has a relationship with the owners of the IP (ie a customer) so he must be paying. ie there is a trace back to the originator. Can't be anonymous anymore.

  7. So basically, this is a $2000 whitelist. by Bombcar · · Score: 5, Interesting

    Because the cost of entry is high, and perhaps policed, it basically becomes a way of saying, "It's from a .mail domain, so it must NOT be spam."

    Whatever. Just like many whitelist methods, it has the standard flaws.

    But I guess it couldn't hurt! Companies with the big bucks or with donors (I'm thinking Samba mailing lists, etc), could afford it.

    The rest of us slobs would continue to crawl around in the .com, .net, .org, and .dust domains.

    As an aside, could you have the same problem with this domain as with AOL's spam filtering, i.e., false reports? What are the punishments for violating the rules of the .mail domain? Death?

    1. Re:So basically, this is a $2000 whitelist. by leviramsey · · Score: 1
      What are the punishments for violating the rules of the .mail domain?

      Presumably loss of domain...

    2. Re:So basically, this is a $2000 whitelist. by spellraiser · · Score: 2, Funny

      From the article:

      SpamHaus probably won't have many hurdles from a technical stability standpoint. The organisation is tapping VeriSign, which has more experience operating TLDs than any other company, to provide the back-end infrastructure.

      Be thankful; $2000 is VeriSign cutting-their-own-throats :-)

      --
      I hear there's rumors on the Slashdots
    3. Re:So basically, this is a $2000 whitelist. by aralin · · Score: 1

      Why cannot we just all agree to have reverse MX records and everybody can make their own whitelist and no need to pay $2000 or even $250 to anyone.

      --
      If programs would be read like poetry, most programmers would be Vogons.
    4. Re:So basically, this is a $2000 whitelist. by Bombcar · · Score: 1

      Hmm.... I guess $75 a year for a domain name is not enough for VeriSign/NS, now they want the bad old days of $2000 domains back..... hmmm.....

    5. Re:So basically, this is a $2000 whitelist. by rw2 · · Score: 1

      Can someone please mod up the parent. This is one of a handful of technological solutions that will virtually eliminate spam, but require community acceptance.

      For christs sake people, the solutions exist. It's time to stop talking as if this is a hard problem and start acting like we know what we're doing.

    6. Re:So basically, this is a $2000 whitelist. by jdhutchins · · Score: 1

      They don't realize that while for a normal person, $2000 is a lot of money, but for a company, $2000 is pocket change not worth picking up if you drop it. The entry price isn't giong to stop ANY spammers.

      It also makes it much easier for spammers. Spammers know how to forge IP's. So now they know that if they make it seem like it's from .mail, people will automatically accept it, and they won't have to worry about spam filters.

      You can't beat spammers at the network. They will ALWAYS find a way around it becuase there's just too much money floating around. You have to filter it yourself, which isn't terribly difficult to do. Spam's a part of life, just like viruses (well, if you use MS, that is)

    7. Re:So basically, this is a $2000 whitelist. by zalm · · Score: 1

      If SpamHaus really wants to do this, they don't have to wait for a .mail TLD. They can use .mail.com now.

      --
      If at first you don't suceed, try RTFM or Man pages.
    8. Re:So basically, this is a $2000 whitelist. by platipusrc · · Score: 1

      For some reason I bet that the folks at Mail.com Corp wouldn't just hand over their domain to SpamHaus.

      --
      And the muscular cyborg German dudes dance with sexy French Canadians
    9. Re:So basically, this is a $2000 whitelist. by RobertB-DC · · Score: 1

      The rest of us slobs would continue to crawl around in the .com, .net, .org, and .dust domains.

      I'd love to be able to register a .dust domain. It would be perfect for ephermeral sites whose content won't be needed by future generations -- archive.org could safely ignore any content blowing in the .dust.

      I've been at work too long to come up with any creative domainname.dust ideas, though.

      --
      Stressed? Me? Of course not. Stress is what a rubber band feels before it breaks, silly.
    10. Re:So basically, this is a $2000 whitelist. by zalm · · Score: 1

      Shouldn't be too hard for SpamHaus to come up with an alternate variation that isn't taken.

      --
      If at first you don't suceed, try RTFM or Man pages.
    11. Re:So basically, this is a $2000 whitelist. by Anonymous Coward · · Score: 0

      tapping VeriSign, which has more experience operating TLDs [and trying to screw the world with sitefinder, etc]

      If SpamHaus wants to continue to be taken seriously and maintain whatever good will they have built up by "fighting the good fight", why, why, why would they get in bed with Verisign?

      What about the group that put in to take over the .org TLD, they seemed technically competent and non-evil .can't.find.their.website.aaaahhhh....

    12. Re:So basically, this is a $2000 whitelist. by arcade · · Score: 1

      It also makes it much easier for spammers. Spammers know how to forge IP's. So now they know that if they make it seem like it's from .mail, people will automatically accept it, and they won't have to worry about spam filters. .. they now how to forge IP's? The only way I can see that happening is by first getting access to and then violating the BGP-network. Spammers doing this would hopefully lose their access to BGP kinda quickly.

      Especially if they started announcing other peoples prefixes.

      Now, to forge a TCP connection which a mail server requires is quite another task. If you can show us how to do that in a simple way - I think many people would cheer and start patching. The problem is, I don't think you'll be able to blindspoof most modern TCP implementations.

      --
      "Rune Kristian Viken" - http://www.nwo.no - arca
  8. $2000 - one time, or per year? by That's+Unpossible! · · Score: 3, Interesting

    The register article says $2000+ per year, the spamhaus faq just says they will cost $2000+. So is it a one-time fee (sounds good), or an annual fee?

    I am guessing it is a one-time fee, and the renewal will be less. Spamhaus states the up front cost is high as the first roadblock for spammers -- why pay $2000 for the domain when you are going to get shutdown almost immediately after using it to send spam? It also is going to cost them more than normal to run this sTLD. So a large one-time fee makes sense.

    --
    Ironically, the word ironically is often used incorrectly.
    1. Re:$2000 - one time, or per year? by Anonymous Coward · · Score: 0

      Fuck you, idiot.

    2. Re:$2000 - one time, or per year? by dasmegabyte · · Score: 2, Funny

      A beautiful rebuttal, in pure slashdot fashion.

      Newbies could learn well from this: if a poster states a valid, insightful argument that goes against the idea that all information should be free, your first line of defense should be anonymous cuss words.

      If these fail, call them Micro$oft lovers. Or Mac zealots.

      --
      Hey freaks: now you're ju
  9. not great! by Roger+Keith+Barrett · · Score: 4, Insightful

    This is just great... create a two-tiered system with "trusted" and "untrusted" e-mail servers. Guess who will own the "trusted" servers... corporations who can afford to pay the fee!

    I would like the ability to run my own servers and web sites as an individual, please. We don't need ANY system of top level domains that favor corporations over non-corporations. Find another way around the problem, please.

    --

    Why don't you embrace your slashbotness instead of living in a dreamworld?
    1. Re:not great! by SupaZeph · · Score: 2, Insightful

      This is just great... create a two-tiered system with "trusted" and "untrusted" e-mail servers. Guess who will own the "trusted" servers... corporations who can afford to pay the fee!

      Because we all know that big corporations would never, ever, ever let spammers use their network, misconfigure a mail server, get hacked, etc.
      *cough* AOL spam *cough*

    2. Re:not great! by benna · · Score: 1

      It would be better if they just charged the regular 15 bucks a year or whatever. Then they could just make rules that if you used the domain to send spam you lose the domain. This is what they were already going to do when charging $2000. The price tag isn't going to stop any spammers but it will stop some legit people from getting a domain.

      --
      "It is not how things are in the world that is mystical, but that it exists." -Ludwig Wittgenstein
    3. Re:not great! by cipher+chort · · Score: 2, Insightful

      I'm in agreement. There is a frightening trend on the Internet to "centralize" and "take power from the Edge(TM)". What that really means is "commercialize" and "make non-free/non-open". It's going counter to the very basis of the Internet, which is free sharing of information.

      It's happening with ISPs that do draconian port filtering to prevent their paying users from being able to host their own content, to VeriSign attempting to own typos, to Microsoft wanting to decide how e-mail "postage" is used, and now the most unlikely (and disheartening) instance is Spamhaus wanting to create a new serfdom of "unclean" Internet users, where "unclean" translates to "didn't pay us".

      The Internet isn't supposed to be about who can most ruthlessly separate people from their money, it's supposed to be about lowering the threshold of entry to information sharing/gathering, not raising it!

      --
      Someone is WRONG on the Internet!
    4. Re:not great! by bahwi · · Score: 1

      $2000/yr is not a lot of money and believe it or not, most companies (hosting, colo, and webservers) generally provide mail servers for you to use. Just because some techie wants to run their own qmail-patched-hacked-whatever (I love qmail, btw) doesn't mean they should. If they mess up, it could mess up the system. $2000/yr comes out to $166/mo. I pay more for satellite and DSL than that.

    5. Re:not great! by cipher+chort · · Score: 1

      So what you're saying is that people are too stupid to communicate on their own and they need to have someone hold their hand to make sure it gets done "right"?

      Hmm, let's see how well that translates to other areas:
      You're too stupid to procreate correctly, we'll regulate that
      You're too stupid to pick the right career, we'll do that for you
      You're too stupid to own a vehicle, we'll take care of transporting you
      etc...

      --
      Someone is WRONG on the Internet!
    6. Re:not great! by Roger+Keith+Barrett · · Score: 1

      If they mess up, it could mess up the system.

      wow... you managed to insult over half of the Slashdot community in one fell swoop.

      I have run my own e-mail server since about 1997. I think I can configure it correctly... jessh.

      --

      Why don't you embrace your slashbotness instead of living in a dreamworld?
    7. Re:not great! by jnicholson · · Score: 1
      Driving a vehicle does require a license. I think that's as it should be.

      Picking your career will usually depend on at least some other people's input - an employer or an investor, an educator, or some other party.

      And procreation by those who turn out to be incapable of caring for those offspring is generally considered to be a sad thing, even though it's a right.

      It's been demonstrated that there are people to stupid - or rather, too ignorant, because it doesn't necessarily require stupidity - to be trusted to run an email server. There are open relays/proxies out there, and even if there weren't there are plenty of 0wn3d PCs. Creating an area where people who are members are held to a higher level of responsibility can be a positive thing, provided the low responsibility option is still out there, albeit it with some penalties (ie, sometimes your mail is blocked as spam - just like it would be without the new area).

      --
      "Do not drill any holes in your cat - it will not like it."
      -- Nick Davies
    8. Re:not great! by cipher+chort · · Score: 1

      So then you're saying that responsibility = money? Some of the richest people in the world are the most irresponsible, so I don't see how that follows...

      You don't get licenses to speak to people on the street, you don't get licenses for having the privilege to talk on the phone, why should you have to get what amounts to an e-mail license? It's pretty much the same thing, after all. While phones do have monthly charges, so do ISP accounts so that part of it is already taken care of.

      Clearly, money is not a problem for many spammers, but it *is* a problem for lots of responsible hobbiests and other people who don't want their private e-mail being snooped on (yay for TLS!). Since money is not a differentiating factor between spammers are reponsible non-spammers, this idea is certainly not a good one.

      Even the revised estimate of $250 is still ridiculous, I'm not going to pay $250/year (~$20/month, which is more than many pay just for connectivity) to some vigilante organization as "protection money". I pay for my bandwidth and IPs, that's enough, damnit! This amounts to little more than licensing protocol usage, which will just start down a slippery slope. Next you'll have a fee to visit web pages that promise they won't use unsigned scripting code and install spyware, or you'll have to pay for the "privilege" of having an FTP site, etc. That's not the Internet I grew up with and I won't stand for it.

      --
      Someone is WRONG on the Internet!
    9. Re:not great! by Sapwatso · · Score: 1

      The price tag isn't going to stop any spammers but it will stop some legit people from getting a domain.

      Maybe they could stop spamers without financially burdening legit people by using a long set-up time instead of a high initial fee. They would have to only allow one application per person or organization at a time, but if it took a month to get a .mail domain, it wouldn't be worth it to a spammer who would probably be shut down quickly anyway.

    10. Re:not great! by bahwi · · Score: 1

      Or..

      You're too stupid to drive on your own, you need a license and we will implement traffic lights, stop signs, lane divisions, and speed limits.

      You're too stupid to procreate, reason 50% of children are born out of childbirth.

      You're too stupid to pick the right career, why not let the market decide for you?

      You're right, they are too stupid to communiate on their own. We need a business-reliable network, not, "Look ma, I done it mesself."

      Not something infested with so much crap.

  10. $2000 is the upper limit by alanw · · Score: 4, Informative
    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)
    1. Re:$2000 is the upper limit by alanw · · Score: 2, Informative

      Oops - those links are both the same - the second one should have been to this posting

  11. So unless you pay $2000... by Anonymous Coward · · Score: 0

    You can't send email anymore from yourdomain.com?
    Is that what this is essentially saying?

  12. 2 Large? No way by doormat · · Score: 1

    I run my own correctly configured personal mail server, and paying $2000 a year for a .mail address is a ripoff for the three or four email addresses I've made myself (a firstname@lastname.net address and other various spam oriented addresses). I first thought it would be a good idea, but the $2000 makes it unreasonable for all but medium to large businesses. I definately dont see small companies of 10 people paying that much for a mail domain.

    --
    The Doormat

    If you're not outraged, then you're not paying attention.
  13. US $2000 for .mail domain! by IO+ERROR · · Score: 1

    They want to charge me $2,000 for this? Come on, if I have a personal little domain for myself and the only people I ever email are my friends and cow-orkers, I have to pay $2,000 to be sure I'll get past spam filters? Ridiculous.

    --
    How am I supposed to fit a pithy, relevant quote into 120 characters?
    1. Re:US $2000 for .mail domain! by athakur999 · · Score: 2, Interesting

      And who exactly gets this $2000? And why do they deserve the $2000? I'm not paying a $2000 registration fee just to have a domain name, there had better be more to the deal.

      --
      "People that quote themselves in their signatures bother me" - athakur999
    2. Re:US $2000 for .mail domain! by dasmegabyte · · Score: 1

      If the .mail domain is intended to be a policed system, consider that $2000 as a deposit ensuring that you won't spam, and guaranteeing you a chance to plead your case when complaints come up.

      And remember: only the smtp server delviering the mail needs a .mail domain. Thousands of hosting companies would be willing to outlay $2000 to certify all of their servers, then give you access to relay your mail through trustedrelay6.somecompany.mail. It'd be no different than paying for bandwidth...

      --
      Hey freaks: now you're ju
  14. Leaves me out by ColdBoot · · Score: 1

    $2K/yr is too rich for my blood. Other than the major ISPs, us little guys can't swing that. And unless they shut us out, they never will really stop the small servers so in the end, either the small guys close or this is an interesting waste of time.

  15. Take your fee and shove it. by ---s3V3n--- · · Score: 3, Insightful

    Registration fees to send mail via .mail?! No way, I know lots of small shots that wouldn't be able to afford that.

    Beyond that $2000 is chump change for spammers. It hurts no one but the honest guy, which is what government lately seems to be for, so perhaps it'll get pushed as a law. *sigh*

  16. What we really need... by ackthpt · · Score: 4, Funny
    What we really need is a .spam tld. All mass emailers not using .spam must have testicle or nipple placed in a vice and slowly tightened until...

    Oh, wait, that's the divorce tactic.

    What the heck, it'd probably work for spammers, too.

    --

    A feeling of having made the same mistake before: Deja Foobar
  17. why new TLD for paid reputation service? by jdunlevy · · Score: 4, Insightful

    Why not just create a paid whitelist (or lists) along the same lines as a dnsbl, charge companies to register and require that they abide by certain practices for being listed? What does a new TLD add other than additional ICANN bureaucracy?

    1. Re:why new TLD for paid reputation service? by Anonymous Coward · · Score: 1, Informative

      Why not just create a paid whitelist (or lists) along the same lines as a dnsbl, charge companies to register and require that they abide by certain practices for being listed?

      What? You mean like bonded sender.com?

      It works really well. The sender puts cash on deposit with a third party, and if the third party gets to many spam complaints, the sender looses cash. Of course, since most AOL users are idiots, they don't count complaints from AOL against you.

    2. Re:why new TLD for paid reputation service? by mdfst13 · · Score: 2, Insightful

      Another point is that such a whitelist could use current systems to operate (just add the parameters to the current blacklist system). This .mail TLD would require new software to check for the existence of a .mail TLD. Thus, a .mail TLD is *worse* than the whitelist that you propose.

    3. Re:why new TLD for paid reputation service? by cipher+chort · · Score: 2, Insightful

      Except that Bonded Sender is run by IronPort Systems, which is a notorious spammer supplier. Since they started selling "anti-spam" products, they've removed most of the blatant references to spamming from their website, but they still prominently feature their "A series" which are nothing other than screaming spam cannons. Their literature claims to "help you with marketing campaigns". A lot of the spam you get every day comes from an IronPort box.

      It's in IronPort's best interest to keep signing up spammers, and it's in the spammers best interest to sign up (if enough people subscribe to Bonded Sender to make the by-pass worthwhile, which currently isn't the case). Maybe IronPort will hand out some slaps on the wrist, but they wouldn't want to delist too many companies because that wouldn't leave an incentive for more companies to sign up.

      In short, IronPort is doing a tight rope walk between spammers and spam recipients. They can't totally please either parties, and I suspect in the end they won't satisfy either on. Of course, that's assuming anyone actually signs up, which so far they have had only very limited interest (much like their so-called "anti-spam" product).

      Of course, the parent posted anonymously so we're only left to guess at their affiliation with IronPort Systems.

      (PS if you're one of my friends who works there, no offense ;)

      --
      Someone is WRONG on the Internet!
    4. Re:why new TLD for paid reputation service? by Anonymous Coward · · Score: 0

      Yeah, so the spammer just charges a bit more for his service since the bonding is just part of the cost of doing business now. He can get away with charging more, too, since he has the power of Ironport's whitelist program behind him!

      Follow the money. Look at who really prospers here.

    5. Re:why new TLD for paid reputation service? by Anonymous Coward · · Score: 0

      Except that Bonded Sender is run by IronPort Systems, which is a notorious spammer supplier. Since they started selling "anti-spam" products, they've removed most of the blatant references to spamming from their website, but they still prominently feature their "A series" which are nothing other than screaming spam cannons. Their literature claims to "help you with marketing campaigns". A lot of the spam you get every day comes from an IronPort box.

      Most of my spam comes from broadband home users (trojaned or otherwise). Ironport sells hardware that lets you send lots of email quickly. Qmail and postfix can be used for the same purpose. It's just a tool.

      It's in IronPort's best interest to keep signing up spammers, and it's in the spammers best interest to sign up (if enough people subscribe to Bonded Sender to make the by-pass worthwhile, which currently isn't the case). Maybe IronPort will hand out some slaps on the wrist, but they wouldn't want to delist too many companies because that wouldn't leave an incentive for more companies to sign up.

      I have yet to receive spam that was listed in bondedsender's whitelist. I have received lots of spam that uses the Habeas 'warranteed' email headers by comparison.

      In short, IronPort is doing a tight rope walk between spammers and spam recipients. They can't totally please either parties, and I suspect in the end they won't satisfy either on. Of course, that's assuming anyone actually signs up, which so far they have had only very limited interest (much like their so-called "anti-spam" product).

      Dell is a client of bondedsender, although I have no clue how successful bondedsender is.

      Of course, the parent posted anonymously so we're only left to guess at their affiliation with IronPort Systems.

      Some people just don't have slashdot accounts.

    6. Re:why new TLD for paid reputation service? by cipher+chort · · Score: 3, Interesting

      People don't pay several hundred thousand dollars for Qmail. Obviously, it's not "just a tool" but it's a tool with an extremely specific purpose. Have you seen the interface? It allows extremely granular tracking of the success or failure of each "campaign" and what the specific error codes were. You can configure up to 254 IP addresses per box (hmm, why would you want to do that???), etc...

      Now most folks don't have to send 500,000 msgs/hr from one box, which is what IronPort claims to do. They also don't need to have specific breakouts and reports of how their messages to each recipient was transmitted and received.

      Don't take my word for it. Look at their customer list, Viacom (advertising), click.doubleclick (hello???), etc...

      Qmail and Postfix were designed to generically send and receive e-mail, and their only special purpose was to be more secure than Sendmail. IronPort bends over backwards to put in spammer friendly features like the ability to spread a "campaign" over multiple source IP addresses and tracking how successful they were in delivering their spam.

      --
      Someone is WRONG on the Internet!
  18. Yeah But... by aduzik · · Score: 5, Insightful
    Spammers are a crafty bunch. They've defeated just about every mechnaism for preventing unauthorized mail server use/relaying/etc. How long until they find a way to get their own .mail server? And also, I would venture to say that most legitimate orgs -- small businesses, personal web site owners, and non-profit organizations in particular -- will not want to, nor be able to shell out two grand for YAD (yet another domain).

    I think recent innovations -- SPF being my favorite so far -- offer a lot more promise than a new TLD. But that's just me :-)

    --
    If it's not one thing it's your mother.
    1. Re:Yeah But... by taustin · · Score: 2, Offtopic

      How long until they find a way to get their own .mail server?

      Spammers have been using their own mail servers for years. And now they're using virus zombie networks anyway, which this won't stop.

    2. Re:Yeah But... by mdfst13 · · Score: 2, Insightful

      About the same amount of time that it would take them to get an SPF domain. That's what blacklists are for. It is a lot easier to blacklist spam.mail or spam.com (in the SPF case) than it is to blacklist every IP that sends spam (especially with DHCP).

      The thing that I like least about a new TLD is that it brings back relaying. Since it is going to be impractical to get a .mail for everyone who maintains a personal email server, most people who do this now are going to hire a relay server.

      There is a current (not foolproof but good) method of checking validity in DNS: checking for a PTR record (and A record). I don't use it on the mail server that I administer now because it would block some of the email that I want to receive. PTR records are free, but not everyone uses them. Why is this more reliable?

  19. Why a TLD? by The+Famous+Brett+Wat · · Score: 3, Interesting

    Why do they need the .mail TLD to pull this off? Why not just go right ahead and do it under mail.spamhaus.org? Is it the air of official legitimacy associated with a TLD that they're after?

    --
    proof, n. A demonstration that a conclusion is implied by certain premises and axioms.
    1. Re:Why a TLD? by SydShamino · · Score: 3, Insightful

      Can you imagine a company like Charles Schwab ever sending out mail with a domain like schwab.mail.spamhous.org? I can't either. However, a company like that would buy a schwab.mail domain. This has everything to do with companies demanding a professional look and feel to their image.

      No, I don't think this is a good idea. But I see why a top level domain is necessary to pull it off.

      --
      It doesn't hurt to be nice.
    2. Re:Why a TLD? by The+Famous+Brett+Wat · · Score: 2, Informative
      With a little research, I've managed to pretty much answer my own question, and the answer is, "yes, they're doing it for the air of official legitimacy" -- more or less. The answer is in the .mail TLD FAQ, question 15, which I'll reproduce here for your convenience, so you can see it in their own words.
      15) Couldn't this be done using a normal example.com type domain instead of creating a TLD?
      Yes... but in reality no. In truth, *any* TLD could really be a SLD (second level domain). In fact, many are (example.co.uk). The concept behind TLDs is to differentiate them, and their users - especially in the case of an sTLD (sponsored TLD) - from the internet at large and the other TLDs.

      There are also other reasons:

      Setting up the system behind .mail as a TLD will also help insure its acceptance and its longevity. It will be an ongoing effort run by a sponsoring organization rather than just a smaller entity. Also, psychology tends to show that "example.com.mail" will be accepted more readily than something like "example.com.this-is-not-spam.com"

      Running a system like this on an existing TLD would also bind it to the rules and regulations of that TLD. Each existing TLD has some rules and regulations that are not compatible with the stated rules and regulations of the .mail TLD as it is to be used in anti-spam.

      On the technical side, a TLD's infrastructure is also set up to be more robust and attack resistant than a normal domain from the outset. Whenever dealing with spammers, one must expect some level of attack.

      --
      proof, n. A demonstration that a conclusion is implied by certain premises and axioms.
  20. Comment removed by account_deleted · · Score: 1, Insightful

    Comment removed based on user account deletion

  21. Goodbye semi-professional mail server by fearlezz · · Score: 4, Insightful

    I have a server of my own, hosting my personal site, some sites for family and for a few charity organisations. Total income for hosting: $0. If I would need to buy another domain like this, just to be able to send mail, my costs will triple.

    I cannot afford this. Meaning I will have to close all sites.

    .mail is NOT an option if it costs more than $5!!!

    Personally, I think SPF is the best solution so far. It may not stop spam, but at least it stops forging headers, like the headers of 99,9% of spam in my inbox are.

    --
    .sig: No such file or directory
    1. Re:Goodbye semi-professional mail server by Anonymous Coward · · Score: 0

      I'm surprised that the problem of forging headers has not been raised as a security issue in the American Homeland That-Is-Blessed-By-God. By now, I would have expected Bush to declare that forged emails can easily be used by those opposed to the American Way-Of-Life as instruments of terror, and should be stopped ASAP.

    2. Re:Goodbye semi-professional mail server by tmbg37 · · Score: 1

      Look, this proposed .mail TLD is just a whitelist. Mail from other domains still goes through, it would just be subjected to regular spam filters which your mail shouldn't be getting caught by anyway. You can still host your mail server, just don't send any spam from it. (Which I'm sure you're not doing anyway.)

      --
      This comment was thought up very late at night and does not necessarily reflect my views at a more reasonable hour.
    3. Re:Goodbye semi-professional mail server by bkirkby · · Score: 1

      Current hosting cost = $0
      Triple your costs = 3 x $0

      I'm guessing you can still afford it :)

    4. Re:Goodbye semi-professional mail server by flatface · · Score: 1

      He said income, not cost.

    5. Re:Goodbye semi-professional mail server by ragnar · · Score: 1

      I agree that $2000 is high, but have you considered that spam is costing you now? Maybe not directly, but your ISP is passing along the added bandwidth cost in some manner. If it works, and I'm saying it will, it might be a bargain.

      --
      -- Solaris Central - http://w
    6. Re:Goodbye semi-professional mail server by Anonymous Coward · · Score: 0

      ".mail is NOT an option if it costs more than $5!!!"

      But if it is only 5$, you will see $BigMegaCorp or $BigPornSpammer register simple thousands of .mail domains, hereby render the system unusable.

      It like with normal domains, good for $JoeAverage that a domain is 10-20$ per year, but the ebay/amazon/whatever domain spammers simple buy 10000 of them, point them to each other and bring google users to their knees by spamming the search results :/

      Cheers,

      Tels

    7. Re:Goodbye semi-professional mail server by Anonymous Coward · · Score: 0

      well my ISP sure as hell isn't charging me 2000 $/year, so i'll stay with "whatever it's costing me now", thanks all the same.

  22. What mail I want to recieve by Alan · · Score: 1

    Having rules for who can spam (or send bulk email, whatever) but I really dont' care about that. What I want is a reliable way to accept the mail I want. Right now it's using a spam filter, because even "legitimate" mail from companies that have opt out mechanisims are mail that I don't personally want to see. So they get filtered out with all the rest, and I'm left with (mostly) the mail that I want to get from friends, family, mailing lists, and whatnot.

    Even having a legit .email domain isn't going to solve this, because people don't trust bulk email. No one should click on the unsub links that you get in mail simply because you never know if it's going to add you into a 'good emails' list or actually do what it says it's doing.

    -1 rambling

  23. Wonderful, we finally have the motivation... by pla · · Score: 2, Insightful

    for a major schizm of internet mail protocols.

    Which will leave "companies able to pay $2k/year" on one side, and "individuals capable of installing their own mail server" on the other.

    This will cause a bit of disruption at first, as a few competing standards emerge, but in the long run, it will make blocking corporate traffic far easier (yeah, I get soooo much legit email from non-individuals... I think I can count the past year's on one hand). And with a bit of care, the non-corporate protocol will finally include several of the oft-discussed but as-yet-unimplemented techniques for completely locking out spam (or at least making it trivial to identify the source).

    And encryption. Don't forget encryption. The non-corporate protocol should include end-to-end crypto, now that Big Brother can watch us on a whim right from the privacy of our own ISP's back door.

  24. Need to get stories strait by madweb · · Score: 3, Interesting

    Ok, then they need to update their FAQ, question 9 "What does a domain cost and why?":

    The use of each domain will cost over US$2000. The price may vary depending on the registrar one uses.

    This high cost will insure that most spammers will not bother and attempt to sign up for one, and if they do, it will be a high cost for what will be a very short time period of spamming.

    The cost also pays for the much greater than normal vetting procedures places requesting this domain will go though before one is granted to them.

    Emphasis mine. Sounds to me like $2000 is the lower limit.

  25. Insane by Anonymous Coward · · Score: 0
    WHY the hell should ISPs and businesses fork over an additional US$2000 to be able to send email? What the hell kind of shortsighted thinking is this? Not to mention personal mail servers that AREN'T spamming, or permitting relaying?

    *sigh*

  26. 2000 per year? by fdawg · · Score: 3, Interesting

    Wouldnt that cost be pushed to the end user? Doesnt that mean we're going to have to pay for email?

    Sounds like a recipe for email tax. I think the only way to really stop this is to stop the 200 or so people per spam message that actually respond to spam and make it a profitable business.

  27. This is just stupid by njcoder · · Score: 1
    .mail tld? You got to be kidding me!?!?! Not only will it not work but why give a stupd TLD when there are more important ones for things people really care about.

    Why can't they make important ones like .bg, .gg, .mfm, .ffm, .fist, .bound, .gaged, .pets? I mean why do only TransVestites get to have their own TLD?

    1. Re:This is just stupid by Anonymous Coward · · Score: 0

      Very funny, imagine .bush or .alqaida as new TLD:s.

  28. $2000/year would ruin free email by TheChucklesStart · · Score: 5, Insightful

    Do you think that Yahoo! or Microsoft's Hotmail would pay that $2,000 just so people could send email from them. Would smaller free e-mail companies even be able to afford it?

    Even if those free email places did pay for a .mail domain, would that stop spam? How much spam do you get already that comes from Yahoo! or Hotmail or some other free email survice.

    This would either get rid of free email or let spam live, both while closing down the small free email services. I don't like either option, we should do something else.

    1. Re:$2000/year would ruin free email by dasmegabyte · · Score: 1

      Um, $2000 per year isn't much. I spend more than that on just bandwidth. $2000 to guarantee that all the mail coming out of my server wasn't spam would be worthwhile.

      Problem is, this idea isn't worth $2000, because it doesn't guarantee that. It's DOMAIN based, when it needs to be server based. Otherwise, I gotta pay $2000 per DOMAIN? That's $100,000 per server!

      --
      Hey freaks: now you're ju
    2. Re:$2000/year would ruin free email by Iamnoone · · Score: 1

      It's DOMAIN based, when it needs to be server based.

      Except that for the big companies it is the opposite - MSN, yahoo, hotmail, etc it is much cheaper per domain since they have many servers for a single giant mail spewing domain - $2000 bucks for 20 or 200 or how many ever servers and suddenly they have trusted mail servers, that is a great deal for them...

    3. Re:$2000/year would ruin free email by SnappleMaster · · Score: 1

      If every mail sender had to pay $2000 a year to send email that had a chance of getting through it would be the beginning of true corporitization (is that a word?) of the internet. Currently big and small entities can have a web presence, including email. This would ensure that only major players can host a series web presence. Who in their right mind wants that?

      The next thing someone would come up with is a $2000/year fee to host a web server.

      No thanks!

      --
      Be happy. Nothing else matters.
    4. Re:$2000/year would ruin free email by Geoffreyerffoeg · · Score: 1

      > Do you think that Yahoo! or Microsoft's Hotmail would pay that $2,000 just so people could send email from them.

      Yahoo exec: Poink. That's about...1/100 of one banner ad for one day? For the ability to send mail? Consider it paid.

      > How much spam do you get already that comes from Yahoo! or Hotmail or some other free email survice.

      None. All of this is from spammers using zombies forging yahoo.com or hotmail.com domains. Which, incidentally, .mail will probably not solve.

    5. Re:$2000/year would ruin free email by Celandine · · Score: 1
      > None. All of this is from spammers using zombies forging yahoo.com or hotmail.com domains. Which, incidentally, .mail will probably not solve.

      No, because that's not its job. .mail is meant to be used in conjunction with a spam filter; all it provides is a way of bulk whitelisting. Any competent spam filter will flag up forged yahoo and hotmail addresses.

    6. Re:$2000/year would ruin free email by meringuoid · · Score: 1
      Even if those free email places did pay for a .mail domain, would that stop spam? How much spam do you get already that comes from Yahoo! or Hotmail or some other free email survice.

      Zero. None at all.

      I get lots and lots of spam with Yahoo or Hotmail in the 'From:' header, but the 'Received:' headers tell a very different story. I also get lots of spam using Yahoo or Hotmail for their dropboxes - those get closed down really fast, and hopefully the spammer gets cut off from his 'Yes! I am a sucker! Please charge my card' replies.

      --
      Real Daleks don't climb stairs - they level the building.
  29. So eventually... by .@. · · Score: 4, Insightful

    the only email that'll make it past everyone's spamfilters would be that from MXes in the .mail TLD. ...and those of us who can't shell out $2k/year just to have our private domain in .mail are just screwed.

    Brilliant idea. While we're at it, why don't we just let ICANN authoritatively say who can and can't send mail, and be done with it? It's not like their board is captured or anything.

    --
    .@.
  30. Worthless by macdaddy · · Score: 3, Interesting
    I can't for the life of my figure out what the hell Steve is thinking.

    If a company or provider isn't sending or supporting spam then why the hell would give a damn about someone else's spam filters? That is the only reason for this whitelist. I mean if they aren't sending spam then why should they be concerned about loosing mail to someone else's spam filters? Why would they want to drop $2k per domain for another whitelist? If perhaps I was a company that did mass mail customers like Sears, JCPenny's, or Amazon then maybe I would want to get on a popular whitelist. That said, why in the hell would I as an average joe or I as a typical ISP give a hoot about what someone else's spam filters do with my non-spam? If their filters are mistakenly tagging my mail as spam their customers will bitch and the problem will get fixed. It doesn't concern me.

    I really don't see the point in a .mail TLD. Steve is a smart guy. Even at that I absolutely can not see his reasoning here. This is really a dumb idea. I make a point to personally blacklist domains that use tools that break email such as TMDA. I guess I'll just have to add another check to my rules.

    1. Re:Worthless by macdaddy · · Score: 3, Interesting
      Yes, I'm replying to my own post now.

      I was just reading the .mail STLD RFP application and am finding myself suprised by the people associated with the hair-brained idea.

      Initial Board of Directors

      Steve Linford, founder of Spamhaus.org

      Joseph E. St. Sauver, Ph. D, Director, User Services and Network Applications Unv of Oregon

      Already consented to be special advisors to the SO

      John Levine, Chairman of the Anti-Spam Research Group (ASRG) of the Internet Research Task Force (IRTF)

      Wietse Zweitze Venema, Ph.D, Postfix author among other things

      Other

      Justin Mason or Daniel Quinlan of SpamAssassin.org

      Eric Allman of Sendmail.org

      Ted Galvin of SpamCon.org

      Suresh Ramasubramanian of OutBlaze.com

      That list amazes me. I can't believe those people would have anything to do with this project. I also can't believe they are intentionally involving Verislime. I wonder if this is an attempt to counter Microsoft's e-stamp proposal...

    2. Re:Worthless by SpacePunk · · Score: 2, Insightful

      You wanna know what he's thinking? KA-CHING!

      1. Get into the anti-spam biz.
      2. Talk ICANN into a .mail TLD with your org as the registrar!
      3. PROFIT!

      If you wish to debate #2 just think about it for a bit.

      The .mail TLD will not stop spam, spam-trojans, or anything of the like. It would be trivial for a spam trojan on a compromised machine to look into the configuration of any email software installed, extact the SMTP server name and just simply send through that server instead of sending directly to the recipients server. Most ISP's allow relays off of their network through their mail server with no authentication.

      Won't change a damn thing, just the method if that method is not already used.

    3. Re:Worthless by Anonymous Coward · · Score: 0

      I mean if they aren't sending spam then why should they be concerned about loosing mail to someone else's spam filters?

      You've heard of 'false positives', right?

      The idea works like this:
      - You can continue sending mail from whatever the hell domain you like, and it'll continue to get randomly filtered and bounced depending on how brain-damaged your recipient's spam filter is.
      - Many of the more intelligently maintained spam filters will whitelist anything that authetically comes from a .mail domain.

      So .mail TLDs would make sense for people who aren't spammers, but often send mail to people they don't know. Like, for instance, anyone who wants to order from your company, to discuss something on your website, or continue a discussion from Usenet or even Slashdot in private.

      Seems like a good enough idea to me.

    4. Re:Worthless by Anonymous Coward · · Score: 0

      Won't change a damn thing, just the method if that method is not already used.

      Bingo! The current method of spamming will have to mutate into a much harder to acomplish method.

      Harder 4 spammmers = better 4 us!

    5. Re:Worthless by Anonymous Coward · · Score: 0

      You've probably answered your own question, smart people must know something you don't?

      Sorry "macdaddy (38372)", but I'll go with what Linford and this group are into before your ideas... nothing personal okay?

      ac#39393939

  31. What, the, fuck. by autopr0n · · Score: 3, Insightful

    This is the most asinine thing ever. First of all no one is every going to implement something like this that requires someone not to comply with US law. It just won't happen.

    Secondly, wtf. $2000 a year? That's insane. Right now, I can use my own mail server and only pay the $8/year domain registration fee. And that's the way it should be. People with enough tech savvy (and it doesn't take much these days) should be running their own mail servers. Open relays aren't an issue with modern mail servers (you have to work pretty hard to create one these days), and running your own mail server gives you a lot of fine-grained control over how you filter Spam for yourself (for example, using a catch-all email and using a different email for everything, letting you track how your address gets disseminated, and blocking addresses that get 'liberated')

    It seems like some of these anti-Spam people hate Spam so much they completely lose track of what Email is for and the people it's supposed to be used by, everyone. Email black holes are one thing, but it's wrong to apply them as filters for people without their knowledge or consent. I read a salon article about a woman who, when roadrunner implemented RTBL she lost out on tons of email, including email from potential employers (she was a freelance author). She still got tons of Spam, of course.

    I don't believe that technical solutions alone will stop Spam, but they, with real legal enforcement can probably reduce it a lot.

    I'm also tired of these top-down authoritarian systems that put a few people in control of email (like e-stamps, or this insane plan, etc) before we even get good solutions like SPF working. Once people start checking SPF records a lot of this crap will get a lot better.

    --
    autopr0n is like, down and stuff.
    1. Re:What, the, fuck. by Peer · · Score: 1

      This is the most asinine thing ever. First of all no one is every going to implement something like this that requires someone not to comply with US law. It just won't happen.

      This does not require people to break US law. It only requires people abide even stricter rules. Also (you may not know this) the internet is used by non-US citizens as well.

  32. Not on its own. by autopr0n · · Score: 1

    Spam that complies with CANSPAM would not be affected by SPF, actualy, as there are no forged headers. But it would be obvious who sent it and it would allow much better prevention.

    One change I'd make, though, is rather then using IP address, use digital signatures.

    --
    autopr0n is like, down and stuff.
    1. Re:Not on its own. by rw2 · · Score: 1

      Spam that complies with CANSPAM would not be affected by SPF, actualy, as there are no forged headers. But it would be obvious who sent it and it would allow much better prevention.

      Of course it would be affected. It would be complying with the law and *no longer anonymous*. Far in excess of 95% of the spam I receive is untraceable. This would change if SPF (or it's peers) were in place.

      Suddenly spam would have a known origin and be subject to effective blocking.

      IOW, think of SPF as the most powerful tool in a toolchest against spam instead of a single stand alone solution for the entire problem.

      The problem is anonymity. Remove it and the problem essentially goes away.

  33. When will everybody just implement SPF by jonwil · · Score: 2, Interesting

    SPF is close to the best anti-spam idea out there.

    1. Re:When will everybody just implement SPF by ziggamon · · Score: 0

      Sun Protection Factor? Well, I try to use at least 40 to preserve my geek-ish look. Doesn't seem to make me get spammed less.

    2. Re:When will everybody just implement SPF by Anonymous Coward · · Score: 0

      SPF is close to the best anti-spam idea out there.

      WTF? SPF doesn't do anything to stop spam. Its hype, pure and simple.

    3. Re:When will everybody just implement SPF by Anonymous Coward · · Score: 0

      Not hype, only the talk that it "stops spam" is hype, SPF is a very nice idea to identify that the email is coming from who it says it's coming from.

      Does away with a spammer's ability to forge.

      Yes, spammers must now use SPF records, but so what, that's what blacklists and whitelists (like the subject of this thread) are for!

  34. I propose this: by ziggamon · · Score: 2, Funny

    Everyone on Slashdot sends one email to spamhaus.org.

  35. They don't need too. by autopr0n · · Score: 1

    Step 1) Schwab sends email

    Step 2) mail client verifies that mail.schwab.com points to the same server as mail.schwab.com.mail.spamhaus.org.

    Step 3) profit.

    --
    autopr0n is like, down and stuff.
  36. zombies anyone? by rbird76 · · Score: 1

    I haven't RTA, but how does this exactly deal with the spam that comes from zombied computers and/or spoofed email addresses? While I wouldn't waste $2K to send spam, a spammer (who is paying for almost nothing else that he's using to send the crap anyway) wouldn't care about that money because it's not his. Thus he has no incentive (in fact, he has a larger incentive) to commit illegal acts - because spam that is whitelisted is likely to be more effective that spam that isn't.

    At best, this seems like a large fine for not having sufficient security on your server (or for getting a virus that exploits an unpatched hole), which could be done more fairly by some other authority. At worst, it would be a cash cow for the certifying authority while driving legitimate email (since most mail is probably from nonservered or clueless people) elsewhere. This doesn't seem like a good idea, but I could be mistaken.

  37. I can do better. by krray · · Score: 1

    I can beat their offer and simply block .mail email to my .com and .us domains. It'll cost me nothing ($0) but a good laugh.

  38. simple solution... coop by laugau · · Score: 2, Insightful

    So I buy personal.mail and then I sell you
    lastname.net.personal.mail for $1. I sell freakiedeakie.org.personal.mail to someone else for $1 and so on and so forth until I get my $2000 back?

    I could hack bind so that I can throttle reverse lookups per domain so that I can keep my bandwidth low and target the small market.

    Since ANYONE could do this, there is no reason to jack up the price. However, for SLA would be best-effort only (since I am not a real company)

    And if I get my 2001st subscriber, I would be in the black (Woo hoo)

    1. Re:simple solution... coop by macklin01 · · Score: 1

      Yes, except that if any one of your 2000 members abuses the system, you'll be the one in trouble for it. (Since personal.mail is registered to you.) And then you'll be facing the money-back demands of the other 1999 members who suddenly lost their service. -- Paul

      --
      OpenSource.MathCancer.org: open source comp bio
  39. ambiguous english by Stephen+Samuel · · Score: 2, Insightful
    ... companies that comply with the US CAN-SPAM act - ...- would not be eligibile to register a .mail address.

    That should have been "might not be eligible to register a .mail address.

    In all probability, most people would be compliant with both CAN-SPAM and the .mail requirements (modulo being willing to pay $2K/year to send email).

    --
    Free Software: Like love, it grows best when given away.
  40. $2000 for a valid mail domain? by Anonymous Coward · · Score: 1, Insightful

    As someone who frequently runs up 'cheap' linux servers for various network services, I enjoy the ease with which I can put up a mail server. $2000 may not be much for corporate mail domains, but this will be very restrictive for people like myself. One of the big points in linux/open source has always been the accessibility of enterprise-class technology for the cost of source tar download. I'm all for castrating the spammers, but when the solution negatively affects legitimate users there is a problem.

  41. Bah! by shatfield · · Score: 1

    I think this is terrible. I run my own mail server, because ISP's are generally terrible at delivering mail. They have to worry about thousands (or hundreds of thousands, or even millions) of users, I have to worry about... well... me. If my server goes down, it's probably my fault. If their server goes down, it's their fault and I get to put up with it. I don't like that.

    Furthermore, since when should it be a requirement to spend thousands of dollars to serve content to the Internet? Doesn't this go against what the Internet has stood for since its inception?!

    --
    "To make a mistake is only human; to persist in a mistake is idiotic." Cicero
  42. 2k ? by 1lus10n · · Score: 3, Insightful

    Someone please explain to me exactly how a smal/mid-size locally owned bussines can afford 2k to send mail ? They claim spammers wont pay the 2 grand on their webpage, thats bullshit. Spammers can and will pay this. You will however be excluding small bussiness's and personal domains.

    And also exactly WHERE the money is going to ? The last thing we need is one governing body trying to control mail for the "betterment of all, so long as it helps our bottom line". We dont need a spam czar, or a spam conglomerate. We need the existing people to work together to prevent spam. ALL spam.

    This is a half assed idea.

    --
    "Two things are infinite: the universe and human stupidity; and I'm not sure about the the universe." --Albert Einstein
  43. Does a different job than SPF by billstewart · · Score: 2, Interesting
    SPF doesn't say you're not a spammer - it just prevents spammers from pretending to be you, at least without doing extra work. That makes it harder for them to impersonate you if you're widely whitelisted (like Dave Farber or Declan) or joe-job you if they're mad at you. Dot-Mail will need to use something like SPF or Reverse-DNS lookups to discourage impersonation, but Spam-R-Us.com can use SPF to tell you that a message really came from Spam-R-Us.com, while they can't be Spam-R-Us.com.mail for very long without losing their $2000 investment. (Neither of these methods will work well without DNSSEC, because spammers who are willing to forge lots of other things will forge DNS records to hide behind other people's SPF or .mail records.)

    Yes, it does sound a lot like profiteering, and like Ironport's Bonded Sender or Habeas's Not-A-Spammer Haiku headers. It's a bit easier to check at SMTP Envelope Time instead of parsing headers after receiving an email message (though BondedSender.org has a DNSWL server you could use.) But the big difference between one .MAIL for the entire world vs. many .My-Whitelist.com businesses is that Linford thinks they can talk more receivers into accepting the One Centralized ICANN-Blessed Solution than the crowd of decentralized competitors can, and therefore they can talk more people into paying them to get bonded.

    I much prefer decentralized competitive approaches, but if I were running a mail server, I'd rather only put in a couple of whitelist or blacklist checks, rather than needing to keep track of which 50 whitelist services were real, which were out of business, which were bogus fronts for spammers, which were free to mail receivers, which charged money to receivers, which were aggregators of other services' information, etc. It's probably harder to get most mail systems to check N whitelists and accept the message if at least one of them hits than it is to get them to check N blacklists and reject if at least one of them hits, but it's also a lot safer to trust a random whitelist than a random blacklist, because if it goes flaky and over-aggressive like some of the DNSBLs, you're not throwing away real messages - you're accepting messages from people you might not want, and giving them a lower level of spam filtering, but a moderate level of false negatives, while annoying, is much less of a problem than false positives, and it warns you that there's a problem you need to fix.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:Does a different job than SPF by Anonymous Coward · · Score: 0

      Well said Brainwash boy, I'd put you on my friends list if I could figure out how to work the damn thing...

    2. Re:Does a different job than SPF by Michael+Hunt · · Score: 1

      It doesn't really do a different job to SPF if you consider that the 'job' of both approaches is to use data published in DNS to cut back on spam.

      SPF works because, well, if I'm a spammer, i'm not going to be wanting to spam from domains which I own, as these are likely to get blacklisted rather fast. Additionally, whois data can make tracing me rather easy and painless. After said domain gets blacklisted, i need to purchase another domain in order to keep spamming.

      If you think about it, what this system is basically saying is 'this message is guaranteed not to be fucked because somebody paid spamhaus $2k to say so'. What SPF says is 'this message, likewise, is guaranteed to be decent because the originating IP address matches the SPF records.'

      In the absence of a mail.com record AND SPF records, the only information you have is 'this domain is PROBABLY bogus.'

      So, no, I don't see the two systems being fundamentally different on an informational level. Just a financial and political one. And come on... the 'bus lane' for your email messages?

      Spamhaus have jumped the shark.

  44. Spoofing .mail by Anonymous Coward · · Score: 0

    Right, this will work wonderfully, because no spammer would ever think of spoofing their headers so they appear to be coming from a .mail domain...

    -A. Coward

  45. What exactly is SPF? by Ride-My-Rocket · · Score: 1

    I've heard it mentioned a few times in the replies to this article, but no links. Can anybody hook me up with some informational goodness?

  46. Good for somebody... by globalar · · Score: 1

    This plan serves several purposes:

    1. Sell a new TLD to millions
    2. Overcharge behaving customers
    3. Create a fee for running a mail server
    4. Make unwanted $big-company-name email legit

  47. I don't see the point... by eaolson · · Score: 4, Insightful

    I'm just not getting how this proposal would do much. I read through the text of the proposal, which is written in fairly obtuse language I just couldn't quite plod through right now.

    • OK, so we'll have this .mail TLD. Since any domain name just resolves to an IP address, this proposal would just boil down to keeping a list of trusted IP addresses. In other words, a list of trusted mailservers, which can easily be done with what exists now.
    • What happens when spam originates from a .mail address? Because it will, if only from a virus-compromised machine. It seems the only recourse would be the revocation of the .mail domain.
    • And if so, what is to stop a spammer from signing up, sending off a one-shot spam run, and losing the domain? It will just raise the cost of each spam run by the cost of registering the .mail domain. That certainly might *help* reduce spam, but it depends on the amount of spam they could send through before losing the domain.
    • I assume each ISP will have a .mail domain of the sort isp.com.mail, and their customer's email will be routed through it. So what happens when a customer of an ISP decides to spam? Will this committee be tasked with determining whether the ISP terminates their spamming customer within an "acceptable" timeframe?
    • It is already known that there are a number of less-than-entirely-responsible ISPs and even some that are explicitly spam-friendly. For a sufficiently large organization, they could afford to go through .mail domains at a fairly high rate.
    • The cost also seems to be a problem. It seems that this proposal can ONLY work if the cost of the .mail domain is fairly high. It seems that the cost will probably be somewhere between $200 and $2000. This seems prohibitive for individuals, non-profits, and third-world orgs.
  48. Law? What jurisdiction? by billstewart · · Score: 1
    Laws depend on guys with guns announcing that they can find the right people and shoot them so everybody'd better listen up and obey. (In more civilized countries, like England, they don't use guns, they just use clubs to beat you senseless if you resist, unless of course you're Irish, in which case they'll still shoot you.)

    The US government doesn't have any jurisdiction outside its borders, so US laws that don't stop spam now wouldn't stop anything if you required the spam to have a .spam domain name. Other countries may let you send your soldiers in to hunt for Osama, but they haven't found him, and they're not going to support armed raids looking for something as trivial (if annoying) as spammers.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  49. my idea by mabu · · Score: 1

    I only came up with this idea a year ago, and have been aggressively promoting it on slashdot, but a new TLD would be useless. No self-respecting mail system can afford to shut out all other domains in such a trusted system. The whitelist system needs to be applied to the Internet proper, with SMTP licensing. Now if spamhaus wants to limit just SMTP relays for .mail, that follows my plan, but ALL users should subsidize the effort and not just the domain holders... that's not fair as it would really be the general populace that would benefit from a whitelisted SMTP network.

    1. Re:my idea by Alioth · · Score: 2, Interesting

      No, I came up with that idea!

      In fact, my original MTAs must be licensed was really more of a way to see if I could get a troll modded up to +5 than a serious post. However, over the last year, I've started thinking that it might actually be a good idea. The licensing I had in mind was rather like the way amateur radio operators are licensed, with a fairly heavy technical content (but not aimed at a particular MTA). Email abuse coming from the MTA could result in suspension or revocation of the MTA operator's license. License data (i.e. who's ticket the email went under) would be added to the headers of email in the form of a digital signature, which the receiving MTA would be required to check (under the conditions of its operator license) for validity and against a certificate revocation list.

  50. $2000??? by linuxtelephony · · Score: 1

    So if I want _MY_ server to be "legitimate" I have to cough up two grand and pay them?

    I don't think so!

    --
    . 62,400 repetitions make one truth -- Brave New World, Aldous Huxley
  51. give me a break by timmarhy · · Score: 1

    this is even worse then microsofts ideas on stopping spam. realisticly you cannot stop large amounts of mail or the ability to send email to anyone without cutting down on the usefulness of email. you can however do some things to all but wipe it out. 1: have governments pursue spammers to the ends of the earth, catch them and make them do jail time, then have them on a good bahavour bond which forbidds them from using a computer. 2: have all mailservers do reverse look ups. this makes it easier to enforce rule 1. 3: isp's instigate spam filtering, VERY loosely. these 3 steps would wipe 99% of spam off the planet, use current technology that works, and won't break anything ( cept the spammers )

    --
    If you mod me down, I will become more powerful than you can imagine....
  52. TLDs and Software by billstewart · · Score: 1
    The software you need for checking in a whitelist isn't much different than what you need for checking in a blacklist - the big differences are that a match means you accept rather than reject the message (duh) and that if you have multiple whitelists, you OR them, while if you have multiple blacklists, you AND them. It's a little bit different, and someone may need to write one extra regexp once per type of SMTP config file, but that's a job for Eric Allman and Dan Bernstein and a couple of other people, and you're just going to copy it from a cookbook. Now, whether you're going to use DNSSEC to validate that the DNS entries aren't spoofed is a different story.

    The purported advantage of One ICANN-blessed Top-Level .mail whitelist is that it would be more obvious to everybody who receives email that this is the whitelist they want, as opposed to keeping track of 50 different whitelist companies (some good, some useless, some bogus spammer fronts), and obvious to everybody who sends large-volume email that this is the whitelist they want to pay, instead of paying 50 different whitelist companies (some popular with large or small mail receivers, some totally ignored by the market). Because after all, this is DNS, it's hierarchical, and There Can Be Only One TLD for that purpose, so there's no need for decentralized ratings and competition and keeping track of the karma of different rating lists, and competition isn't necessary. Maybe Linford's right, maybe he's wrong, but go RTFA so you can see what _he_ says he means rather than just listening to me ranting about what his proposal _really_ means.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:TLDs and Software by schon · · Score: 1

      if you have multiple whitelists, you OR them, while if you have multiple blacklists, you AND them.

      Erhm - what?!?!

      You're saying that if you have multiple blacklists, you don't block something unless it's on all of them?!?!

      I mean, if you have five blacklists, but only four of them say that someone is a spammer, then the mail isn't spam?!?!?

      I think you mean "If you have multiple blacklists, you OR them"

    2. Re:TLDs and Software by Anonymous Coward · · Score: 0
      if you have multiple whitelists, you OR them, while if you have multiple blacklists, you AND them.

      Erhm - what?!?!

      You're saying that if you have multiple blacklists, you don't block something unless it's on all of them?!?!

      I mean, if you have five blacklists, but only four of them say that someone is a spammer, then the mail isn't spam?!?!?

      I think you mean "If you have multiple blacklists, you OR them"


      Hey, I'm twisted, I XOR them!

      Not sure what I'll do with this .mail thing, but it's actually easier to use since it's like a rdns/ptr lookup for a FQDN check. Hmmm, since I do this anyway, I get the lookup "for free", pretty neat.

    3. Re:TLDs and Software by mdfst13 · · Score: 1

      "The software you need for checking in a whitelist isn't much different than what you need for checking in a blacklist"

      If you define the whitelist provider properly, it isn't different at all. That's what I was saying. If you create a whitelist where it returns a bad for all email addresses that are *not* on the list (as opposed to a blacklist, which returns a bad for email addresses that *are* on the list), then you can just plug it into the same software that handles the blacklist. This is just a configuration change that I can do with my *current* server software.

      With a TLD, you do a DNS check on the TLD. This isn't a huge thing, but it is something that is not done now. Therefore, *all* servers would have to be rewritten to do this. Seeing as how some people still use the execrable Mercury servers, this would not see universal use any time soon. Even for those who are willing to update their servers, why should they? There is a perfectly good method for whitelisting now...why not use it instead? Why wait until people have time to set up their software to support this? Why not go with something that can start working immediately?

  53. Imagine this.... by no_nicks_available · · Score: 1

    M$ making this same proposal. Flame on.

  54. just great by SpacePunk · · Score: 0, Troll

    I just love it when a bunch of crazy fuckers with just as much a chip on their shoulder as the spammers have go and push for something like this. 2k a year? bullshit. they can suck my dick.

  55. Let me get this straight by King_of_Crunk · · Score: 1

    ICANN will control tld and Spamhaus will control mail... Sorry this does not sound like a good thing to me. Instead of the one big Satan we have in ICANN (at least according to alot of people I have still yet to pass judgement on ICANN) we will have two once Spamhaus gains control of the would be .mail tld. On one hand we will have ICANN doing their thing which alot of people dont like while Spamhaus forces you to pay $2000 a year to send email... I'm sorry I hate spam as much as the next person but to give control of who can and cant send email to one company just doesnt justify the cost in the end to freedoms on the Internet. Lets face it all it will take is one even medium sized ISP to adopt Spamhauses .mail domain as a filter. God forbid a major ISP adopts this. Once that happens we will now are forced to pay an inflated price for another domain name... I don't know I say screw this if ICANN excepts this one over a what I feel will be more helpful as far as cleaning up the Internet goes such as the .xxx tld... Heck I don't know what I would do at least in the operating system world I have Linux as an alternative to windows...

  56. I said it before, and I'll say it again by dacarr · · Score: 2, Insightful

    Like I mentioned in the prior discussion on this, just because you have a .mail TLD won't stop spammers. TLDs are in DNS, and in the final analysis, it's all arbitrary, as you can use ANY word as a top level domain. That's why you have alternate roots like OpenNIC.

    --
    This sig no verb.
  57. Re:Law? What jurisdiction? by siliconbunny · · Score: 2, Insightful
    The US government has plenty of jurisdiction outside its borders. The Sherman Act, for one, operates outside the US's borders.

    What you are referring to is enforceability of those laws. True, the US may not be able to enforce its laws against those resident in other countries who do not have presence or assets in the USA.

    But it means anyone connected with such an operation better not have assets in the US. Or even visit the US.

    And, depending on how the law is drafted, perhaps no person in the US (or with assets there) better use such an operation to *send* spam, or face being prosecuted, or other consequences. Vide internet gambling.

    So that US laws, alone, could stop (a) American spammers; and (b) anyone in or doing business with America or visiting America or with assets there (NYSE shares, anyone?) from *using* overseas spammers who do not comply with US law.

    And for those that are left, the US can just lean on other countries to enact similar laws, either as part of international treaties (GATT and TRIPS, anyone?) or bilateral trade treaties, or just by leaning on them.

    Methinks that would do a great deal to cut down on spam...

    If you doubt this, see how effectively the US is able to export its copyright laws to other countries. Or Sarbanes-Oxley, as applied to foreign lawyers or accountants. And how it is now doing the same thing with bank secrecy laws (with an emphasis on terrorism; it has done the same previously with respect to evasion of US taxes). There are many relevant links.

  58. Another thing: The phrase of the day is "joe job" by Anonymous Coward · · Score: 0

    Yes it is! And that's one really good thing about this idea, there can be no "joe jobs", the sending server is tied to the domain name. Kinda cool.

    SPF does this too, but spammers can have SPF records, in fact if it gets popular, most will.

  59. $200 is definitely instane.. Flashback to 1999 by ufpdom · · Score: 1

    Back in 1999 I worked in Silicon Valley. EDS who ran some lotus servers at where I worked charged .25 an email. So a Mass mailing about friday company bowling costed $80. I thought that was insane. So I built my own server on a HP-UX box. Saved the company over $1200 a month especially using some fancy aliasing and integrating it into corporate structure. Now I thought 25 cents was INSANE for email. Now this $2k deal is LUDICROUS.. I would almost tend to think some right wing liberal republican movement is behind this (and I am a registered republican). This will never fly, anyone who backs this is insane and for the ones that do. Its all about profit.. Nothing else. It just allows the more elite to send email to each other which the little guys suffer. Dam I feel like a mom and pop game shop watching a bestbuy being built across the street .. hmph :/

    --
    There's no Freedom like UFP-dom
  60. It's "Goodbye" by nonameisgood · · Score: 2, Interesting

    You are correct.

    Spelling notwithstanding, $2000 is irrelevant if it does not work. The only solution is to make it impossible to SMTP mail without some validation of the sender. This must be done with no expense or unusual hoops to jump through, and let's not let the fascists control this one - you know who I mean.

    You can't rely on whitelists; automated blacklists don't work since spammers steal our 'net identity to spam us and others, causing innocents to be blacklisted.

    As it is, I could spam all day using postfix or sendmail with a random domain name as the sending domain. This is just crazy. It is in a sense criminal, since my bandwidth is being used without my permission by all of the attachments coming every hour. LIKE I GIVE A RAT'S ASS ABOUT PHARMACEUTICALS, NIGERIA, OR HOT STOCK TIPS!

    CAUTION! rant follows:
    God Damn It! Get the fuck off the net you cheap-ass cowards. It's like my dog barking at the other dogs until I open the gate - if we can find a way to unmask these spamming motherfuckers, it will stop. (Viral mailings notwithstanding.)

    OK, I'm better now.

    --
    Faith is the very antithesis of reason, injudiciousness a critical component of spiritual devotion. Jon Krakauer
  61. Consider this: by Duhavid · · Score: 1

    Perhaps that is *exactly* what they have in mind. You will not be able to afford it, along with billions and billions ( sorry, channeling Carl there.. ) of others.

    It '133ts up the playing field, leaving many fewer mail servers out there to be compromised.

    --
    emt 377 emt 4
  62. So, by Duhavid · · Score: 1

    The people handing out the domains in your whack-a-mole ( good imagery, btw ), example will hand them out to spammers nilly-willy, but for .mail, they will not.

    I think $2000.00 for a spammer is probably chum change. And maybe an extra little bit to grease the skids a bit would also be chump change.

    --
    emt 377 emt 4
    1. Re:So, by rgmoore · · Score: 1
      The people handing out the domains in your whack-a-mole ( good imagery, btw ), example will hand them out to spammers nilly-willy, but for .mail, they will not.

      It's a different group of people. The ordinary .com/.net etc. registrars are purely for profit organizations. Anyone in the world can go to them with the name of an available domain and some money and get the domain they're asking for. The people running .mail are not the same group. It's being proposed by a group of anti-spam activists who have been devoting a huge amount of time and energy to wiping out spam. There's no particular reason to believe that they will give domains to any known spammer, especially because these are the same people who are doing the best job of tracking down the spammers and all their known aliases.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    2. Re:So, by Duhavid · · Score: 1

      This all assumes that

      A: That the people proposing this end up in control of this.

      B: That they ( over time ) dont end up corrupted, or...?

      --
      emt 377 emt 4
  63. Screw spamhaus and their $2000 TAX by drwho · · Score: 1

    I am sick of people coming up with ways to screw small ISPs, community mail servers, personal domains, and the rest with things like email stamps, and this is the worst I've seen so far. I will now boycott spamhaus and everything they touch. This is just another dishonest grasp at cash in the name of public good, just like ARIN.

    The technology exists to combat spam without becoming elitist corporate arseholes. First, public key crypto, with certificates distributed via DNS, could indicate which IP servers are authorized to originate mail for a given domain/subdomain. Second, asymmetrical computational puzzles can be used with unknown/suspicious senders.

    What we need is credit card processing firms cracking down on their customers who are spammers. Because in the end, it comes down to someone entering their credit card number, and at that point the end-spammer (i.e. the business interest at the head of the spam conspiracy, not the middle men) becomes known.

  64. Blocking .mail emails by imemyself · · Score: 1

    Why don't some people get together, and make a petition type thing, like saying, that if this happens, all the signers will block .mail email's from their mail server. It might encourage some companies and organizations who would be for it to reconsider if their emails will be blocked by quite a few people.

    --
    Every time you post an article on Slashdot, I kill a server. Think of the servers!
    1. Re:Blocking .mail emails by Anonymous Coward · · Score: 0

      Block .com and .biz instead, you'll get far less spam.

      j/x

  65. This doesn't solve anything. by someonehasmyname · · Score: 1

    This won't do any good; it's a whitelist that ISPs will have to pay to be listed on. The problem with that is the ISP's users will still spam if they want to. It dosn't prevent forging headers, so it won't stop spam.

    What will happen when a subscribing ISP's customers send spam? The ISP will be notified, and told that if they don't cancel the user they'll be removed from the whitelist. Blacklists operate under the same premise, and we're still looking for better ways to stop spam. What would make a whitelist any better?

    I work for an ISP, and our users are told before signing up for service that we don't tolerate spamming of any sort. That doesn't stop them from spamming, it just gives us a legal excuse for deleting their accounts when they do.

    --
    Common sense is not so common.
  66. This will not work. by rice_burners_suck · · Score: 2, Interesting
    The "agree to abide" thing is probably good. Perhaps there should be some law (or something similar) that those .mail domain name holders who do not abide by the rules are fined, and after so many fines, they are blocked from using a .mail TLD for a period of 100 years or something.

    On the other hand, the $2000 a year fee isn't going to do jack. Those who send spam do so because it's really darn profitable. To them, the $2000 a year is peanuts. To a service provider who can barely make ends meet and wants to expand its quality of service and options for customers, $2000 may be the difference between breaking even and going bankrupt. That's kind of like trying to protect individual inventors working in their basement by making the patent fees $200,000 or something. That'll only serve to accomplish the opposite of the intended result.

    The bottom line is this: Make it difficult for spammers, not for legitimate users. A certain standard should be devised that includes technical as well as contractual devices to make it extremely difficult for any spammer to last any time at all on the .mail TLD. And mail received from non-.mail TLDs could automatically go into a "bulk mail" folder, or would not be downloaded from the server at all, except for the "From:" address and perhaps a digital signature, so the user (or his filters) can decide what to do with that information. And maybe that needs to happen with ALL mail, not just non-.mail TLD mail.

  67. This is a fine thing by ajs · · Score: 1

    Let em have their fun. .mail tld validation can be yet another test that my SpamAssassin installation will use to determine how likely mail is to be spam. If they implement it well, then the test will even get a largish score over the long haul...

    1. Re:This is a fine thing by Anonymous Coward · · Score: 0

      Agreed! Give me more tools and let me decide how to weight the e-mail. I'm liking this idea more.

      Right now, if you're in Spamhaus SBL you get a fat S.A. score, I'd have no probs doing the opposite if you're coming in via a .mail "pipe".

  68. SMTP + SPF = better solution by Anonymous Coward · · Score: 0
    SMTP + SPF
    • SPF is the natural counterpart of the MX list. It should have been in SMTP and DNS from the beginning.

    • SPF is a voluntary system. If you do not participate, email will continue to work as before.

    • SPF is free and open standard, an extension to SMTP.

    • SPF expects to see support in SpamAssassin v2.70, Sophos, Symantec, BrightMail, MailArmory.com, MailFrontier.com, Declude Junkmail,, and others.

    • SPF has plugins available in Postfix, Exim, Qmail, and Sendmail.

    • SPF is aimed as much at worms and viruses as it is at spam.

    • SPF is a complement to other antispam systems. It strengthens and improves them, and it makes new approaches possible. For example, domain-name blacklists and fine-grained reputation systems.

    • SPF improves the veracity of sender addresses. Sender forgery is the moral equivalent of the open relay. SPF solves that problem.

    • SPF is a permanent solution: after it has been
      installed, you don't have to update your content filters, or keep doing challenge-response. Each domain is responsible for publishing and maintaining its own SPF records, but that
      not much of a burden at all.

    • SPF is being presented to the IETF for RFC consideration.

    • SPF is designed to protect the envelope sender address, the return-path, where bounces go. It can also be used to protect the header "From:" address with some added complexity. If you are not confident of the difference, you will find RFC2821 and RFC2822 enlightening. Protecting the headers is inherently more challenging, because spammers are very good at forging headers, and you have to carefully choose between Sender, From, Resent-Sender, and Resent-From; it's a can of worms.

    • Because SPF protects the return-path, users protected by SPF will stop getting bounces for messages they didn't send --- for example, "Your system sent us a virus".
  69. Missing the point by esme · · Score: 1

    All the people who are complaining about running a small set of domains and not being able to afford $2000 are missing the point.

    This is designed to force all mail to go through the .mail TLD. If you run a small set of domains, you'll need to get mail service (even if it's just forwarding your mail through one of their servers) from someone with a .mail domain. Yes, this makes the net more hierarchical than it is now, but that's the whole idea: a hierarchical system can enforce rules, and we clearly need some rules to break the spammers.

    Now, I'm not sure this is the best way to do it. But it certainly seems like it could be effective.

    -esme

    1. Re:Missing the point by haapi · · Score: 1

      I believe that setting up "SMTP webs of trust" is the right way to go, and would at least allow email to be sorted as it travels between trusted webs of MTAs. Email originating in, and transitting through, trusted MTAs could then be treated preferentially with regards to filtering, or at least, what gets processed/queued first.

      An MTA wouldn't need to be part of .mail to be trusted, but its operator would have to do whatever it takes to join particular webs of trust, which could mean that it meets policies and guidelines similar to what is suggested for .mail.

      Who would run these webs? The answer isn't that hard -- we used to do that for USENET news all the time, really.

      --
      Well, apparently, you only have to fool the majority of people for a little while.
  70. Re:FNORD by Anonymous Coward · · Score: 0

    You kinky mathematicians...

  71. Re:Law? What jurisdiction? by billstewart · · Score: 1
    Actually, no, I'm referring to jurisdiction, which is an assertion about legal legitimacy. The US has more ability to enforce things outside its borders than it has legitimacy for its actions. US forces occasionally do things in other countries, and they engage in lots of piracy on the high seas (err, they usually call that "drug law enforcement".) And it's done a lot of bullying of other countries through trade policy to get cooperation on laws it doesn't have legitimacy for - the bank secrecy issues are especially serious problems.

    The US laws against internet gambling are fairly inappropriate, constitutionally, but it's especially easy to firewall your way around US-based spam laws by using a couple of foreign corporations. You don't need to be personally responsible for spamming - some foreign corporation can do it, and they can also hire you to provide them with perfectly legal services that seem to use up most of their profits from spamming. And you don't even need to go offshore - you spend $100 to set up a Delaware corporation, and you don't do the spamming, the corporation does, and if it gets caught, well, bummer, John Ashcroft can burn its corporate papers at the stake at high noon and you're still not in jail. (OK, you've got to spend another $100 for your next spammer-shell, but you've gotten your couple of thousand dollars cut from selling fake Viagra pills to the hundred suckers who fell for your 10,000,000-message spam.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  72. That just confirms... by warrax_666 · · Score: 2, Interesting

    ... to me that the people behind the proposal are complete morons.

    As someone pointed out in a thread above there is no good reason to just use a reverse blacklist (like DNSRBL et al.) which identifies certain senders as non-spammers instead of identifying them as spammers.

    "[...] set up to be more robust and attack resistant [...]". Oh please. If you get $2k from each and every person/corp. in your whitelist you sure as hell can afford some professional DNS hosting for your whitelist.

    --
    HAND.
  73. Re:home mail server (Use pass-through at ISP) by NKJensen · · Score: 1

    Every ISP will have to provide some pass-through SMTP server for home users, this mail server will be registered as a .mail server.

    Most ISP's already do have such servers.

    Add some virus filters for Microsoft-worm-of-the-week and E-mail begins to make sense again.

    --
    -- From Denmark
  74. Re:SMTP + SPF = DIFFERENT solution by Anonymous Coward · · Score: 1, Interesting

    SMTP + SPF identify the sender as being who he says he is.

    If the sender happens to be a spammer with an SPF record, it'll pass all the tests.

    This proposal adds to an SPF type deal. Now e-mail will not only identify the sender as being who he says he is, but will say "he's not a spammer either".

    Now one can let the e-mail pass. I know if all the list-mail sent to our boxes didn't have to churn thought Spam-Assassin and our own Procmail traps, it'd save mucho time.

  75. $2000 a year is NOT peanuts (& is NOT a year) by Anonymous Coward · · Score: 0

    Do you think anyone, ever the richest spammer could afford $2000 each time he wants to spam for a few minutes? Did you see where the spammer does not control the domain, but the anti-spammers do? Hell, they'll have their hands on both the spammers wallet AND on his "peanuts"! One mistake, and they put the squeeze on both! Me likes!

  76. Bye bye, small, independent mail server by EmagGeek · · Score: 1

    Well, I guess I won't be able to run my own mail server anymore... I guess I'll have to leave that to big greedy corporations who can afford $2k a year for the privelege... oh, and BTW, email will no longer be free, either, because that cost will be recouped...

    YET ANOTHER instance of something open and free being handed over to corporate america for its exploitation...

  77. lets do this with every top level domain by skymester · · Score: 1

    just charging 2000 $ wont stop the spam problem, when someone is caught spamming the domain has to be dropped.

    then again, why cant we drop .com, .net, .org or any other domain name when a spammer is caught?

  78. the Problem is by colk99 · · Score: 1

    if spammers can afford to hop isps every few days they can surely afford the $2000 a year for the .mail domain. This top level domain is worthless and should be shot down before it even gets anywhere.

  79. You should know better by NKJensen · · Score: 1

    Well, if you run a mail server, you should know how to make it relay via your ISP's passthrough server. Which must have a .mail name, if it wants to be able to send mail to me.

    If you spam me, I'll complain to you ISP - simple to find from the headers - and the ISP will handle your case appropriately.

    What will be a thing of the past is hijacked xDSL PC's which are doing mail-zombie work. They don't have a .mail domain - sorry, blocked by default.

    --
    -- From Denmark
    1. Re:You should know better by tadas · · Score: 1
      Well, if you run a mail server, you should know how to make it relay via your ISP's passthrough server.

      That's what I had been doing with my personal domain. Then, about 2 years ago, Verizon DSL changed their mail server configuration to allow only "verizon.net" originating emails, purportedly as a defense against hijacked clients. I quickly learned about sendmail's authentication methods.

      I doubt that most ISPs give a flying fsck about their customers' personal domains, and I don't see many of them providing a pass-thru relay server.

      --
      This page accidentally left blank
    2. Re:You should know better by elemental23 · · Score: 1

      Actually, Verizon is the only major ISP I've heard about who is clueless enough to require that you use their domain name in your outbound mail. I'm sure there are other smaller ISPs doing it, but so far they're the exception, not the rule. Not by a long shot.

      I'm pretty sure all that's meant by "pass-through" in this context is an SMTP server that the ISP's users can send mail through. In other words, the same mail server that you'd be using from your mail client if you didn't have your own SMTP server. I've never heard of an ISP that didn't provide outgoing mail service. With the exception of the aforementioned clueless ISPs (eg, Verizon), you'd be able to sent mail from your MTA just as well as you could from your MUA. SMTP is SMTP.

      --
      I like my women like my coffee... pale and bitter.
  80. This is bad, just like .kids and .xxx by Fastolfe · · Score: 2, Interesting

    The Internet is not e-mail! It is completely inappropriate to base the DNS name of your organization on what is effectively a content label specific to one particular service. This is the same reason .kids and .xxx are bad.

    Heck, let's say I run a porn service, and want to take advantage of this mail feature. I now have to use two different DNS domains? That's stupid.

    Just as PICS can give you digitally-signed content ratings for the web, some other service can give you digitally-signed ratings/labels for e-mail. Extend SMTP to, perhaps, operate over TLS or SSL, or at least perform some sort of mutual check that both sides have a SpamHaus certificate that says they're not a spammer, and you can possibly "secure" the connection.

    Or just digitally sign your e-mail messages and only accept digitally-signed e-mail. Tweak your trust relationships (for PGP-style signatures) or drop your trust from any roots that are seen to sponsor spammers, and you're all set.

  81. Re:Another thing: The phrase of the day is "joe jo by Anonymous Coward · · Score: 0

    SPF does this too, but spammers can have SPF records, in fact if it gets popular, most will.

    Today, 99% of spam is delivered with a forged MAIL FROM value, precisely what spf stops. You say spammers will get SPF records: let them - we'll know their real domains, which we can then blacklist, and which will make tracking them down for legal action that much easier, and having to register a new domain for every two or three spamming runs will change the cost/benefit analysis to spammers - and that will make a difference.

  82. The answer is simple... by Anonymous Coward · · Score: 0

    Money!!!

  83. $2000? Cost of doing business? by Anonymous Coward · · Score: 0

    And does anyone other than spammers know if $2000 per spam run will actually cut out the profits in the game?

    If not, the people getting the $2000 per domain have just found a way to tax the spam industry $2000 per spam run.

    Shoud I do the 1, 2, 3, profit joke here?

    This is a BAD IDEA.

    A Nony Mouse

  84. Dumbest idea yet by Brian+Knotts · · Score: 1
    I seriously don't know which side I dislike more sometimes: the spammers, or the fanatical anti-spammers.

    I receive maybe 5 spams a day, which are almost all caught by spamassassin. It's not hard to keep it down to that, if you are careful about how you handle your email addresses.

    I'd much rather stick with the status quo, than have to pay $2000 for running a mail server.

  85. If it costs any money at all it will fail. by NoMercy · · Score: 1

    Everyone and there dog provides email service, if this address isn't anything other than like the .arpa tld, it will fail totally.

    Perhaps might have hot.mail and yahoo.mail, but I can't see any others signing up for it.

  86. Eliminating SPAM and Viruses: A New Approach by JoshiT+C · · Score: 2, Insightful

    Full story at

    http://www.intechcomm.net.au

    Originally posted 28/1/04.
    Copyright Joshua Leisk. This article may be reproduced, provided it is reproduced in its entirety, without alteration.

    I am posting this story, as the .mail TLD and related concept is remarkably similar to a patent I filed in Australia and it could be the answer to all our email problems, if a few changes are made:

    SPAM. Currently unsolicited email from less than 0.2% of the online community wastes time and impacts the productivity of the other 99.8%, as well as impeding network bandwidth and creating traffic costs. SPAM represents over 65% of all email sent.

    EMAIL VIRUSES. Mass-mailing viruses cause significant financial damage to organisations and individuals alike. At least 60% of all the services my IT outsourcing company currently performs is virus-related.

    I think we have all come to the realization that the problem in eliminating SPAM and email viruses, is that even though it is impossible to verify the legitimacy of all email being exchanged, we still accept mail from any software capable of transmitting mail, as though it were a trusted source of information! Many mail servers are flawed by inept security and administrators, many countries have no anti-SPAM laws, every successful mass-mailing virus has its own SMTP engine and of course we suffer the deliberately configured SPAM email servers employed by dodgy SPAM 'barons' every day to solicit millions of people to buy dodgy 'Viagra', dodgy University degrees and enough porn to humble a veteran pornographic movie star - all for the sake of making a dishonest dollar at every body else's expense.

    The simple fact is, you cannot prevent the shady 0.2% of the online community from targeting the remaining 99.8% of us without a global mail exchanging system that has zero-tolerance for unsolicited mail and an effective way of globally policing the system. Message filtering and 'real-time block lists' will never provide an effective solution, because it is a never-ending race to identify, report and 'block' SPAM and 'rogue' mail servers, which then merely rise like a 'phoenix from the ashes' hours later, under a new domain name, or a new IP address, when shut down by Internet authorities. Currently SPAM recipients are always one step behind the SPAM senders and feeling helpless to their plight. Why should we allow ourselves to be victims of our flawed technology, allowing rogue mail servers to financially impair rest of the Internet community?

    When SPAM and viruses already makes up more than 50% of all email sent, it becomes more logical and far simpler to protect the legitimate email, rather than trying to filter the illegitimate email!

    The only way to permanently eliminate SPAM and email viruses is to establish a mail server authority to register and regulate email servers, in much the same way as the Domain Name System, thus allowing enforceability, financial accountability and liability to those who SPAM, or allow SPAM to propagate. You need a license to own a gun or anything else capable of significantly impacting others, so why not an email server? Currently, Australians pay an average $45 per year to register a '.com.au' domain name, as well as the additional hosting fees to facilitate the DNS system and traffic caused by it, thus creating orderly domain name management. We wouldn't tolerate chaos and anarchy in the Domain Name System, so why should the email system be any different?

    I propose that we MUST construct a global registry of certified closed-relay, 'spoof'-proof email servers, married to the verified details of the server's owner, who are possibly placed under a financial security bond, depending on the age of the domain name and previous history, to operate it SPAM-free and then prevent all 'registered' email servers from receiving email from any 'unregistered' email server (or be cleaned and filed separately - see "'Softer' Variation of the Concept"), or accepting email client submi

  87. some points of .mail by posm22 · · Score: 1
    A lot of people seem to be misapprehending some important aspects of how .mail is to work. Probably the opaque language of the proposal document is at the root. Let's take some of those points:
    • OK, ... this proposal would just boil down to keeping a list of ... trusted mailservers...

      While true, the .mail proposal would make use the DNS service, which is relatively secure, distributed, reliable, and fairly efficient. That helps avoid problems with DOS attacks, which spammer-listing sites have suffered from.

      Also, it gives an immediately obvious and effective place to complain about abuse. You just complain about foobar.com to abuse@foobar.com.mail, and the arbiters at .mail get the message, not the perpetrators at foobar.com.

    • What happens when spam originates from a .mail address? Because it will, if only from a virus-compromised machine. It seems the only recourse would be the revocation of the .mail domain.

      Yes, that's the penalty - if you allow spam to be sent from the mailserver you promised to never send spam from, the mailservers for that domain will no longer be publicized as being spam-free (because they're not).

    • And if so, what is to stop a spammer from signing up, sending off a one-shot spam run, and losing the domain? It will just raise the cost of each spam run by the cost of registering the .mail domain. That certainly might *help* reduce spam, but it depends on the amount of spam they could send through before losing the domain.

      Several things slow the spammer down, if not stop him. First he must have already owned the "key" domain (e.g. "foobar.com") for six months before he is allowed to get the corresponding .mail domain ("foobar.com.mail"). Second, the WHOIS info for both foobar's is investigated by the .mail organization for validity (in several ways unclear to me). Third, the anti-spammers controlling .mail may use measures like spam honeypots and being eagle-eyed to make sure that $2000 doesn't get him much return. The economics of buying throwaway .mail domains aren't likely to pay off.

    • I assume each ISP will have a .mail domain of the sort isp.com.mail, and their customer's email will be routed through it. So what happens when a customer of an ISP decides to spam?

      They hedge some on whether ISPs will do this. They suggest the ISP will have to have tight limits on the number of emails that can be sent by their customers (at least through the ISP's trusted mailserver).

    • It is already known that there are a number of less-than-entirely-responsible ISPs and even some that are explicitly spam-friendly. For a sufficiently large organization, they could afford to go through .mail domains at a fairly high rate.

      The vetting of the WHOIS info is meant in part to make this difficult. You're not going to get many .mail domains under the same or similar registrations. I don't know the extent of the checking, but maybe a spammer would have to set up a new front-person and address as well as domain every three days and maintain each set for 6 months to get a pipeline of throwaway .mail domains. That doesn't seem too likely, especially by a spam-friendly ISP.

    • The cost also seems to be a problem. It seems that this proposal can ONLY work if the cost of the .mail domain is fairly high. It seems that the cost will probably be somewhere between $200 and $2000. This seems prohibitive for individuals, non-profits, and third-world orgs.

      Yes, but I don't think anyone views this as the only way to send mail or fight spam. You can always send without involving .mail; your message w

  88. Wrong - Domains are really cheap by billstewart · · Score: 1
    Spamming from domains you own is fine - a domain name costs you $6-10 from a bulk registrar, and whois data for spammers is usually either obviously bogus or else non-informative, but seldom useful for tracing. Many of the big domain registrars offer whois-privacy services, and most of them don't verify the information, as long as they get paid.

    Sure, that's more expensive than a free yahoo account or a forged address pretending to be at yahoo, but it's still basically free and highly disposable. It's less than the cost of a list of N million freshly verified opt-in spam-free email addresses, and it's less than the profit on that first bottle of fake herbal Viagra you get some sucker to buy.

    SPF doesn't try to guarantee that a given domain is ok - only that mail claiming to be from that domain probably is from that domain. If that's a domain you recognize, that may be meaningful; if it's a domain you don't recognize, it's not highly meaningful. Smalltime spammers aren't going to pay $2K for a Spamhaus certificate, partly because they often don't have the money and partly because they aren't sure it'll make them enough additional profit to justify it; they'll probably pay $10 for yet another new domain name. On the other hand, big legitimate bulk emailers (like commercial newsletter publishers, or product-support mail) might very well pay $2K because they hope to save that much money on email administrator time due to reduced bounces, plus they'll be able to support more paying customers.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
  89. Re:Eliminating SPAM and Viruses: A LAME Approach by Anonymous Coward · · Score: 0
    • "a patent I filed in Australia"
      A patent? On this?! Will you patent the wheel & fire next?
    • ___
    • "the answer to all our email problems"
      It is? This idea is so wrong in SO many ways! Is this post a troll?
    • ___
    • "Currently unsolicited email from less than 0.2%"
      Where did you get this #? Other than out of your arse?
    • ___
    • "when shut down by Internet authorities"
      Who are these "Internet authorities?" Do they have flashy-badges?
    • ___
    • " register and regulate ... enforceability, financial accountability and liability"
      You work for the Gestapo don't you?!
    • ___
    • "need a license to own a gun ... so why not an email server"
      So sending email is like shooting people? Some aren't even sure a license to own a gun is a good idea.
    • ___
    • "MUST construct a global registry"
      "MUST"? So no other idea before or after yours will have merit?
    • ___
    • "email ... sent from an unregistered email server, it is simply rejected "
      Wow! You really want to kill email to save it huh?
    • ___
    • "The mail server owner(s) should also enter into a contract with its users"
      Wow, "contracts with users", why didn't anyone else think of that. Vile spammers would NEVER break a contract. This MUST be a troll post right?
    • ___
    • "binding them to abide by the mail server authority's rules"
      I await your plan to "bind" spammers to any authority's rules!
    • ___
    • "required the new owner to supply a security bond of (suggested) US$2500+"
      So, no email can flow out of a server without a "(suggested) US$2500+" bond? Hey, why not take 10 years per-capita income from some poor asian nation's ISP. You work for the tax department don't you?
    • ___
    • "message tracking and secure password authentication with every sending email client provides end-user accountability and ultimately financial liability"
      So EVERY client software must now be changed? You work for Micro$oft don't you? How about changing the operating systems too?!
    • ___
    • "any user needing to send to more than (suggested) 50 recipients at one time, should be granted by the mail server's administrator on a 'per-user' basis"
      Oh my... yeah, as if admins aren't busy enough, now they must answer every request from the unwashed masses of users who wish to send 51 christmas cards... ouch, that smarts!
    • ___
    • " if a 'standard' user send to more than 300 recipients in 24 hours"
      So EVERY server software must now be changed? You DO work for Micro$oft don't you?
    • ___
    • "Message ID tagging will still provide user accountability"
      Every email is tagged with some special ID huh? You work for the NSA don't you?
    • ___
    • " it will be required to pass stringent tests, certifying it unable to act as an open relay."
      Uh, open relays account for less than .1% of spam on the internet, have you been in a cave for the last 3 years?
    • ___
    • "I further propose that during a 'secure' SMTP mail server transaction ... challenging 'Server X' with a 128 character 'Session ID"
      Ah, finally, the "let's break SMTP" part. We all knew it was coming didn't we!?
    • ___
    • "The admin contact details to be required are: Name, Phone Number, Email Address,
  90. Re:Eliminating SPAM and Viruses: A LAME Approach by JoshiT+C · · Score: 1

    I am going to take the time to address each of those comments, pointless and flamebait as most of them are:

    "a patent I filed in Australia"
    A patent? On this?! Will you patent the wheel & fire next?
    JL> I patented this before I discovered that bondedsender.com or any other similar concept existed. I believe Microsoft has patented the 'Caller-ID' concept, also. I know a lot of people don't like software patents, but until a better way of rewarding inventors is created, what else is there? This is capitalism, not communism, you know.

    ___
    "the answer to all our email problems"
    It is? This idea is so wrong in SO many ways! Is this post a troll?
    JL> So list them. If you take the time to read the whole concept details, you will see its fair for everybody EXCEPT the spammers and email virus creators.

    ___
    "Currently unsolicited email from less than 0.2%"
    Where did you get this #? Other than out of your arse?
    JL> Do the maths. The bulk of the world's spam is apparently sent from less than 5000 people. There are over 36 million domain names registered.

    ___
    "when shut down by Internet authorities"
    Who are these "Internet authorities?" Do they have flashy-badges?
    JL> The sender's ISP's, real-time block lists, government and law enforcement.. I believe there are already lawsuits commenced under the CAN-SPAM act in the USA.

    ___
    " register and regulate ... enforceability, financial accountability and liability"
    You work for the Gestapo don't you?!
    JL> Next you'll tell me you don't believe the DNS is a good thing. I'm not proposing anything significantly different.

    ___
    "need a license to own a gun ... so why not an email server"
    So sending email is like shooting people? Some aren't even sure a license to own a gun is a good idea.
    JL> Do you have ANY idea what the world currently spends to deal with viruses and spam? Do you register your car? Do you have a drivers' license? Do you have a problem with laws and regulation? What's wrong with a gun license? Wouldn't you like to know that someone who owns a gun is adult and responsible and not some psychopath or homocidal maniac?

    ___
    "MUST construct a global registry"
    "MUST"? So no other idea before or after yours will have merit?
    JL> Everything has merit. However, sender accountability is the *only* long-term solution. Besides, without a register of mail servers, how else can you permanently get rid of email viruses?

    ___
    "email ... sent from an unregistered email server, it is simply rejected "
    Wow! You really want to kill email to save it huh?
    JL> SMTP was originally designed for academics and the military. Spam and email viruses came much later. If SMTP has been created with any prior knowledge of the commercialisation of the Internet, it would have been made more secure to start with. Besides, I have also detailed a method that allows the email to be received, yet processed in such a way that it presents no harm to the recipient other than potentially wasting the user's time deleting spam.

    ___
    "The mail server owner(s) should also enter into a contract with its users"
    Wow, "contracts with users", why didn't anyone else think of that. Vile spammers would NEVER break a contract. This MUST be a troll post right?
    JL> You already agreed to some sort of 'Terms and Conditions' when you joined up with your ISP. This is merely a modification of those terms. In some ISP's cases, those terms are already included.

    ___
    "binding them to abide by the mail server authority's rules"
    I await your plan to "bind" spammers to any authority's rules!
    JL> If they are known and accountable, why not? Isn't that the basis of all law?

    ___
    "required the new owner to supply a security bond of (suggested) US$2500+"
    So, no email can flow out of a server without a "(suggested) US$2500+" bond? Hey, why not take 10 years per-capita income from some poor asian