Slashdot Mirror


Stichting Spamvrij (spamfree.nl foundation) Closing

TeVi writes "Stichting Spamvrij.nl (Spamfree.nl foundation), the authority on spam in The Netherlands, has decided to stop. Spamfree.nl gained international attention for their fight against the CyberAngels spammers. More information can be found on their website regarding the shut-down." It's the classic story of too much work to do, not enough time; meanwhile another reader notes: "Some new anti-spam products out there - but everyone seems to agree that even Sender ID ideas and laws won't do much."

4 of 118 comments (clear)

  1. English text by Karamchand · · Score: 5, Informative

    is available here.

  2. They were good at something. by Killjoy_NL · · Score: 4, Informative

    From what I read this morning in the dutch news, they did find out that a notorious dutch spammer didn't stop spamming, so they got him into a lot of trouble. There was also something about some more "detective" work that they were good at, but I can't remember what it was at the moment.

    --
    This is the sig that says NI (again)
  3. Re:CyberAngels? by TeVi · · Score: 4, Informative

    short answer: http://www.cyberangels.nl/

  4. SPF, Caller-ID and Sender-ID by Zocalo · · Score: 4, Informative
    Once again, there seems to be some confusion over this in the linked articles, both of which were written after the situation stabilised, so for those that don't know:
    • SPF (Sender Permitted From) is one of the original DNS based schemes for verifying an IP was authorised to send an email. It is an open standard using text only records that was proposed by Meng Wong of pobox.com and is still going just fine with many big mail domains (Hotmail, Gmail...) using it.
    • Caller-ID is the original closed standard Microsoft proposal that uses XML records. It goes beyond SPF in its scope, but is encumbered by numerous pending patents which Microsoft has yet to adequately disclose.
    • Sender-ID is a derivation of Caller-ID, also by Microsoft, that was proposed to the IETF as a potential "standard" mechanism for acheiving DNS based sender validation. Owing to it sharing many of the same patent issues of Caller-ID and a failure of the parties in the MARID working group at the IETF to arrive at a compromise that open source developers were happy with, Caller-ID was rejected.

    Caller-ID and Sender-ID are currently languishing in Redmond, with Microsoft yet to make any announcements about whether or not it intends to implement them anyway. SPF-Classic on the otherhand is still gaining momentum, with tens of thousands of domains registered as having SPF records, plus an unknown number of unregistered ones. SPF-Classis is also supported by most MTAs and anti-spam solutions, either directly or via a plug-in, and is most likely to become the "default standard" as things stand.

    --
    UNIX? They're not even circumcised! Savages!