Slashdot Mirror


Spammers' Upend DNS

Saint Aardvark writes "eWeek reports on the latest trick of spammers: getting around DNS-based lookups. By registering a domain *after* the spam goes out advertising it, they can get around blacklists. However, that causes all sorts of problems for ISPs and anti-spam services. Paul Judge, CTO at Ciphertrust, says "Even in large enterprises, it's becoming very common to see a large spam load cripple the DNS infrastructure.""

304 comments

  1. Bah by Anonymous Coward · · Score: 0

    I never put valid DNS links in my posts.

  2. Anti-Spam Legislation Is Only Effective Solution by bigtallmofo · · Score: 5, Funny

    Until they pass a law that makes it completely legal to kill spammers, the spam problem will not go away.

    --
    I'm a big tall mofo.
  3. Thats a nice stunt by networkBoy · · Score: 1

    Thats a nice stunt

    How do you combat this? If the e-mail contains an invalid domain name kill it? What about typos?
    -nB

    --
    whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    1. Re:Thats a nice stunt by skaladin · · Score: 2, Insightful

      Who cares about typos? If it doens't exist don't forward it. Plain and Simple.

    2. Re:Thats a nice stunt by 2advanced.net · · Score: 3, Informative

      You've misunderstood the problem ...

      The domains sending the email exist, but the ones advertised in the email do not. Because SpamCop (et. al) punish not only the sending IP block, but also the advertised host/IP block, spammers are advertising sites that won't exist for a few hours, tricking SpamCop (et al) into reporting on domains that don't exist and therefore cannot be penalized.

    3. Re:Thats a nice stunt by Kissing+Crimson · · Score: 4, Interesting

      Yup. If it shouldn't come in, and it can't be returned, drop it on the floor.

      So often times my (l)users ask me why they received an email saying their computer is infected with a virus (bogus bounces due to a virii changing their source addresses)

      My servers drop anything that doesn't seem right: virus infections, RBL tagged connections, obviously forged senders, etc. When a message gets delivered to the bit bucket; no more processing, no more network traffic, no more (l)user complaints.

      And I never get a complaint.

      --
      What's that smell? Ah, that's my karma burning...
    4. Re:Thats a nice stunt by networkBoy · · Score: 3, Interesting

      Overall I agree with this, but my concern is that if you parse the message and find invalid url's then a valid message will be dropped because of a malformed text string. While I suppose that's better than letting more spam through, I would be uneasy about the increase in false positives.
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    5. Re:Thats a nice stunt by DarkTempes · · Score: 2, Insightful

      the problem is that when you have to look up domains that don't exist it tends to take longer, especially for DNS servers, as my understanding they then ask ANOTHER server if it has it, etc and thus when you multiply that times about a billion... you end up killing/lagging DNS servers and the server recieving the mail in the first place ;p

    6. Re:Thats a nice stunt by bentfork · · Score: 2, Insightful
      Good point. I would hate it if this email got stuck in the spam trap

      To Accounting@bla.com:
      Please authorise my PO so I may purchase the domainname OurNewProduct.com

    7. Re:Thats a nice stunt by WoodstockJeff · · Score: 1
      Please authorise my PO so I may purchase the domainname OurNewProduct.com

      Not a problem, unless the sender set their return address to something@OurNewProduct.com, and it doesn't exist. One of the restrictions available on Postfix and other MTAs is, "if you can't find a domain server for the MAIL FROM domain, reject it." It doesn't matter if there are invalid domain names WITHIN the message, because it doesn't parse those.

    8. Re:Thats a nice stunt by bentfork · · Score: 1
      Not a problem, unless the sender set their return address to something@OurNewProduct.com, and it doesn't exist. ... It doesn't matter if there are invalid domain names WITHIN the message, because it doesn't parse those.

      In spam I have seen most of the 'evil' links are contained WITHIN the body of the text. The sending email addresses are from yahoo, gmail &c.

      The problem is catching the spammers email. If you made a simple mail filter would send legit emails containing unregistered domains to /dev/null by default. This would be a badthing(tm)

      It would be funny if you tried to email a DNS provider about your domain that wasn't resolving.

    9. Re:Thats a nice stunt by Gr8Apes · · Score: 2, Insightful

      Seems the simple solution is to cache "bad" addresses in your local DNS server for some specified period of time, probably in a LRU type cache to prevent Spammers from taking it down.

      Adding features in your SMTP server that if a certain source has multiple failing emails, that source could be processed on a queue basis, or even automatically bitbucket anything from that address since spam comes in waves.

      --
      The cesspool just got a check and balance.
    10. Re:Thats a nice stunt by Anonymous Coward · · Score: 0

      No kidding. My god man, this is really quite sinister and clever. It's like natural selection and viruses. No joke. For every defense, the spammers find another way to overcome it. But in a lot of ways, by being so clever, they do in fact point out deficiencies in the current network implementations.

      Say what you will about the ethics of this, in a purely technical way it's just fucking brilliant. And yeah, how DO you combat it? If a lookup fails X times for a given domain, it's added to sort of a non-DNS DNS lookup? Flagged somehow?

    11. Re:Thats a nice stunt by The+Angry+Mick · · Score: 1

      Umm. Why not just use an envelope? After all, we're talking about corresponding with accounting . . .

      --

      I'm not tense. I'm just terribly, terribly, alert.

    12. Re:Thats a nice stunt by Anonymous Coward · · Score: 2, Informative
      You've misunderstood the problem

      Not according to the article:

      One troublesome technique finding favor with spammers involves sending mass mailings in the middle of the night from a domain that has not yet been registered. [...] During the interval between mailing and registration, the SMTP servers on the recipients' networks attempt Domain Name System look-ups on the nonexistent domain, causing delays and timeouts on the DNS servers and backups in SMTP message queues.


      The sending domains *don't* exist.

      Honestly, this seems pretty overrated - any mail coming into our domain gets a single lookup - if the domain doesn't exist, it gets a 500. If the domain exists, but the DNS servers time out, it gets a 450.

      Why anyone would accept mail from a domain that doesn't exist is beyond me.
    13. Re:Thats a nice stunt by Anonymous Coward · · Score: 0

      Seems the simple solution is to cache "bad" addresses in your local DNS server for some specified period of time, probably in a LRU type cache to prevent Spammers from taking it down.

      Congratulations, you've just invented negative caching! You'd better hurry back to 1987 and submit your patent application!

    14. Re:Thats a nice stunt by Anonymous Coward · · Score: 1, Funny

      > "a virii"

      What's the plural of that?

      (viri, virii, viriii, viriv, virv, virvi, virvii, virviii, virix, virx)

    15. Re:Thats a nice stunt by Anonymous Coward · · Score: 0

      If it shouldn't come in, refuse it with a 5xx. Never drop.

    16. Re:Thats a nice stunt by eaolson · · Score: 1
      The domains sending the email exist, but the ones advertised in the email do not. Because SpamCop (et. al) punish not only the sending IP block, but also the advertised host/IP block, spammers are advertising sites that won't exist for a few hours, tricking SpamCop (et al) into reporting on domains that don't exist and therefore cannot be penalized.
      Not quite. By "SpamCop" I assume you're talking about spamcop.net. SpamCop sends reports to the originating IP. It will also send reports to hosts of URLs contained in the body of the spam, but not it they do not resolve to an IP address, IIRC. Therefore, no valid DNS = no SpamCop report.
    17. Re:Thats a nice stunt by sepluv · · Score: 1
      More importantly, should anyone be removing others' email based on its contents? On volume (like USENET), yes, but not on which URIs it includes. Anyone doing this sort of stuff should be given the Internet Death Penalty. Looking at the contents of other people's email and deleting it if you don't like what it says clearly violates RFCs and probably contracts and laws.

      Spammers don't even need to include URIs. They can just give the name of the product (for the user to search for) or an indirect indication of the URI or just tell them how to buy thew product there and then in the email.

      The real problem is there are people out there who are stupid enough to buy their (probably shoddy or non-existent) products.

      --
      Joe Llywelyn Griffith Blakesley
      [This post is in the public domain (copyright-free) unless otherwise stated]
    18. Re:Thats a nice stunt by networkBoy · · Score: 1

      Unless you're the mail admin for a company.
      -nB

      --
      whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
    19. Re:Thats a nice stunt by Gr8Apes · · Score: 1

      It's optional, and evidently not implemented if this is such a problem.

      Obvious solutions don't warrant a patent, despite what the PTO grants.

      --
      The cesspool just got a check and balance.
  4. Fast DNS updates! by Cyn · · Score: 4, Funny

    Thank goodness we can now register domains and have them active within 30 minutes!

    Oh look, my foot's bleeding. Someone must have shot it.

    --
    cyn, free software and *nix operating systems enthusiast.
    1. Re:Fast DNS updates! by 2advanced.net · · Score: 2, Insightful

      Do you stop advancing technology just because the spammers may benefit from it?

      Rapid updates to the .com and .net zones is VERY helpful for a large number of people - punishing them because it also helps spammers is like tearing down skyscrapers to avoid terrorists in airplanes.

    2. Re:Fast DNS updates! by Kissing+Crimson · · Score: 2, Insightful

      Good comparison, but I'm going to pick on it anyway...

      Are terrorism references to become the new Godwin's Law? If so, I'd like to name it Jonesy's Law.

      --
      What's that smell? Ah, that's my karma burning...
    3. Re:Fast DNS updates! by Pxtl · · Score: 1

      Amen. Nobody thinks that IP Multicasting is a bad idea, but to me it has obvious bad ramifications for net send spam and service worms like Sasser. I still want multicasting anyways (but I won't be surprised when it becomes an "trusted-IP-Only" thing much like SMTP).

    4. Re:Fast DNS updates! by dillon_rinker · · Score: 1, Funny

      If you mock Godwin's law, then the terrorists have already won.

    5. Re:Fast DNS updates! by AndroidCat · · Score: 1

      Whippersnappers! In my day we only had Godwin's Rule, and we liked it!

      --
      One line blog. I hear that they're called Twitters now.
    6. Re:Fast DNS updates! by sepluv · · Score: 1

      And pray tell me how the removal skyscraper would stop people who wish to terrify others being in aeroplanes. Possibly, not allowing them to enter an aeroplane or taking away their aeroplanes (e.g.: AirForce1) might.

      --
      Joe Llywelyn Griffith Blakesley
      [This post is in the public domain (copyright-free) unless otherwise stated]
  5. I bet... by wcitechnologies · · Score: 1

    I bet that the barracuda spam blocker would protect against this.

    --
    Electrons are free; it is moving them that becomes expensive.
    1. Re:I bet... by datastalker · · Score: 0

      I bet you get paid to say that. ;)

    2. Re:I bet... by AndroidCat · · Score: 2, Informative

      That's the one that by default, sends spam bounces to forged email addresses?

      --
      One line blog. I hear that they're called Twitters now.
    3. Re:I bet... by matth · · Score: 1

      Naw.. but the ChiliTech SpamCobra would stop this.

    4. Re:I bet... by Anonymous Coward · · Score: 0

      You mean the appliance company run by a known spammmer?

  6. That's not the sky falling... by winkydink · · Score: 5, Insightful

    The article goes on to say that some anti-spam applications do as many as 30 dns lookups. This is a design problem with the apps, not with DNS. Do less lookups, minimize the problem. I'd venture that after checking with a few of the major blacklists, you've pretty much hit the point of diminishing return in distinguishing spam/ham.

    --

    "I'd rather be a lightning rod than a seismometer." -Ken Kesey

    1. Re:That's not the sky falling... by Anonymous Coward · · Score: 3, Interesting

      The problem with DNS is that it is very slow, and does a lot of things that make lookups too slow and unreliable.

      Looking up www.name.com should take no more than three DNS lookups with an empty cache (To root: "com" DNS server has IP 10.1.2.3; to 10.1.2.3: "name.com" has DNS server with IP 10.2.3.4; to 10.2.3.4: "www.name.com" has IP 10.3.4.5). However, because of DNS' poor design, it doesn't work that way; it can take dozens DNS lookups from an empty cache to get "www.name.com".

    2. Re:That's not the sky falling... by HavokDevNull · · Score: 1

      ummm I use mailscanner / postfix on 3 domains, and have my own bind 9 server as a caching DNS server. If admins would only set up caching DNS servers the problem would go away.

      And this is also a good way to defeat this new way to spam. IMHO new (not changed) DNS entries should take a min of 24 hours anyway.

      --
      Sig
    3. Re:That's not the sky falling... by Zocalo · · Score: 4, Insightful
      No, it's a problem with spammers making references to multiple domains in their email, each of which might need to be checked against several SURBLs. Personally, I'm not fretting this one at all; while it's an ingenious work around from the spammers to get around the SURBLs, there's a trivial fix.

      At the moment, each domain referenced in the body of a spam is checked against one or more SURBLs to see if it has been spamvertised - hence the 30 lookups figure. Instead of immediately checking the SUBLS, we can just make a single check to see if the domain exists at all, if it doesn't then skip the SURBL checks and bias the score towards being spam. If it does exist, then we can proceed to check the SURBLs as normal and still nail any spams using known spamvertised domains. If the domain does exist, then it's a single extra DNS lookup which is possibly going to be cached, so a root server query may be avoided. If it doesn't exist, then we skip the SURBL checks and save our 30 DNS queries.

      Yup, it's the old spam arms race again. Give it a month or so and we'll all be moaning about some completely new spammer tactic brought in to replace this one.

      --
      UNIX? They're not even circumcised! Savages!
    4. Re:That's not the sky falling... by Anonymous Coward · · Score: 0

      THis is just poor application design. One of the common sendmail settings is to reject email from domains that don't exist - the envelope email address in the SMTP transaction.

      If you reject email at that stage, you never get the body of the email at all - no DNS problems.

      I love sendmail with mimedefang & spamassassin!

  7. Re:Anti-Spam Legislation Is Only Effective Solutio by 9-bits.tk · · Score: 1

    And you can define how you want to kill them. Then the spammer's family is sued. Then anybody related to the spammer is shot.

  8. Apostrophe by Anonymous Coward · · Score: 1, Funny

    So is the title refering to an "upend DNS" that belongs to spammers? If so, can someone explain what an "upend DNS" is?

  9. Re:Anti-Spam Legislation Is Only Effective Solutio by jellomizer · · Score: 1

    Heck I would love it if they would make it fully legal to hack the spammers computer and forcefully remove you name from the list. But because I don't know exactly where my name is on the list I figure that I will just rename all the domains to point themselfs. or there ISP Leader.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  10. Re:Dammit by punkass · · Score: 3, Insightful

    yeah! and make drugs illegal too! that'll teach 'um.

    --
    "Nobody owns the fucking words man." - James Dean
  11. So which is going to come first... by Anonymous Coward · · Score: 2, Interesting

    Email authentication, or the wholesale abandonment of email as a viable communication platform?

    1. Re:So which is going to come first... by TFGeditor · · Score: 3, Interesting

      ..."the wholesale abandonment of email as a viable communication platform?"

      And the alternative with the same capabilities is...?

      --
      Ignorance is curable, stupid is forever.
    2. Re:So which is going to come first... by stratjakt · · Score: 2, Funny

      A fax machine.

      --
      I don't need no instructions to know how to rock!!!!
    3. Re:So which is going to come first... by Anonymous Coward · · Score: 0

      That makes the choice fairly obvious then, doesn't it?

    4. Re:So which is going to come first... by AndroidCat · · Score: 1

      And which servers are you going to swamp by verifying the authentication?

      --
      One line blog. I hear that they're called Twitters now.
    5. Re:So which is going to come first... by Just+Some+Guy · · Score: 1

      If you count SPF as "email authentication", which it is on a certain level, then I'd go with the former.

      --
      Dewey, what part of this looks like authorities should be involved?
    6. Re:So which is going to come first... by Anonymous Coward · · Score: 0

      Half the problem with SPF is the braindead people who think it checks the "From:" line in their email. The other half is the lack of capability to set TXT strings in commercial nameservers.

    7. Re:So which is going to come first... by freeze128 · · Score: 1

      Lotus Notes!

    8. Re:So which is going to come first... by Kent+Recal · · Score: 1

      Trained doves can carry attachments up to 100grams.

    9. Re:So which is going to come first... by Repton · · Score: 1

      And the alternative with the same capabilities is...? sms. txting s clrly bttr & ds wndrs fr ur splng 2.

      --
      Repton.
      They say that only an experienced wizard can do the tengu shuffle.
  12. Wanted: DNS geek by RealityMogul · · Score: 3, Interesting

    When a DNS query goes to an ISPs DNS server, and the entry does not exist, does it go to the root servers?

    Secondly, do invalid domain names get cached (I'm thinking not)?

    1. Re:Wanted: DNS geek by sqlrob · · Score: 1

      Secondly, do invalid domain names get cached (I'm thinking not)?

      Yes.

      My ISP complained to me about SpamAssassin running on my local server (they called it a trojan in the original mail, but I eventually figured out what they meant after talking with someone with a moderate clue). The negative lookups were pushing positive ones out of the cache.

    2. Re:Wanted: DNS geek by stratjakt · · Score: 2, Insightful

      I don't get it. If this is true, it sounds like a MAJOR MAJOR design flaw in DNS.

      Surely it allows for invalid domain requests, or did they just assume everyone on the net will correctly type the domain name every time?

      Or, is it not the email or DNS itself, but the anti-spam filters that are hammering the DNS servers?

      I don't understand the problem. It sounds like a made up non-issue by the anti-spam crowd, frankly.

      --
      I don't need no instructions to know how to rock!!!!
    3. Re:Wanted: DNS geek by marsvin · · Score: 3, Informative
      When a DNS query goes to an ISPs DNS server, and the entry does not exist, does it go to the root servers?
      Yeah, how else would you know it doesn't exist?
      Secondly, do invalid domain names get cached (I'm thinking not)?
      Nowadays yes, but not for very long (on the order of 5 minutes, usually).
    4. Re:Wanted: DNS geek by ngc5194 · · Score: 2, Informative

      When a DNS query goes to an ISPs DNS server, and the entry does not exist, does it go to the root servers?

      When we make a DNS query, it goes to our name server. If the name server does not have a result for that query cached, it queries a higher-level server for information on which name server is authoritative for that domain. It is possible that any DNS query where no component of the domain name is cached to require a query of the root name servers. This is true for any existant or nonexistant domain name.

      Secondly, do invalid domain names get cached (I'm thinking not)?

      I don't know about all implementations, but contemporary versions of BIND all perform "negative caching" for some amount of time. The invalidity of DNS records can be cached.

    5. Re:Wanted: DNS geek by Malc · · Score: 1

      If SpamAssassin is query the same domain multiple times, then you could do well to run your own version of bind as a caching nameserver.

    6. Re:Wanted: DNS geek by Anonymous Coward · · Score: 1, Informative
      Here is what happens when there is a DNS lookup for a non-existant domain, such as www.thisdoesntexistfuqwehfiufqwehfoewuwfqeho.com

      • The ISP's caching server will probably already have the .com DNS server name and IP cached. If not, it will ask the root server for the .com server name and IP. (OK, the dns server will really ask the root server for www.thisdoesntexistfuqwehfiufqwehfoewuwfqeho.com when the cache is empty, and get a reply from the root server "The .com name server is im-too-lazy-to-run-dig-right-now.gtld.net, and im-too-lazy-to-run-dig-right-now.gtld.net has the ip 10.19.2.83)
      • The caching DNS server will ask a .com name server the ip for www.thisdoesntexistfuqwehfiufqwehfoewuwfqeho.com
      • The .com name server will reply (in a very ugly way involving giving out an SOA answer in the NS section, as I recall) with "thisdoesntexistfuqwehfiufqwehfoewuwfqeho.com. doesn't exist, and remember that fact for one day"
      • The ISP's DNS server will remember that thisdoesntexistfuqwehfiufqwehfoewuwfqeho.com doesn't exist for one day; it will not keep on asking the .com server for this non-existant domain

    7. Re:Wanted: DNS geek by the_rev_matt · · Score: 1

      404

      --
      this is getting old and so are you

      blog

    8. Re:Wanted: DNS geek by hackstraw · · Score: 1

      When a DNS query goes to an ISPs DNS server, and the entry does not exist, does it go to the root servers?

      Yes

      Secondly, do invalid domain names get cached (I'm thinking not)?

      Yes, its known as negative cacheing, its done to reduce the load on the root servers (see question 1).

    9. Re:Wanted: DNS geek by sporty · · Score: 1

      I don't believe it does. If it did, then you could DoS the cache by spamming random crap at it..

      --

      -
      ping -f 255.255.255.255 # if only

    10. Re:Wanted: DNS geek by MavEtJu · · Score: 1

      I don't get it.

      Let me guess, you're not running a mail server?

      If this is true, it sounds like a MAJOR MAJOR design flaw in DNS.

      DNS itself works fine; it are applications and people who are abusing it. Same as SMS works fine; except if tens of thousands of people suddenly start sending huge amounts of them.

      Don't call something a flaw until you realize how it works. We have enough people who know nothing about things calling things flawed despite that they don't know anything about them.

      I don't understand the problem.

      For example, this is what my mail gateway checks:

      - reject_rhsbl_client dsn.rfc-ignorant.org
      - reject_rbl_client relays.ordb.org
      - reject_rbl_client sbl.spamhaus.org

      These three produce only load on the DNS servers of the anti-spam providers

      - reject_unknown_sender_domain
      - reject_unknown_recipient_domain

      These two actively use the root and (cc)TLD servers to check if the domains the email is claiming to come from work. For normal email, which normally comes one by one, one lookup is enough and the result is cached. For SPAM email, which normally comes in batches with different from-addresses, you need a lookup for each and the cached result is useless because it's not reused anymore.

      With regarding to SPF, that's another DNS lookup. Does it mean that SPF is bad? No. It's the people who made us design and implement SPF who are bad. DNS is the best place for information like SPF.

      --
      bash$ :(){ :|:&};:
    11. Re:Wanted: DNS geek by Anonymous Coward · · Score: 0

      The .com name server will reply (in a very ugly way involving giving out an SOA answer in the NS section, as I recall) with "thisdoesntexistfuqwehfiufqwehfoewuwfqeho.com. doesn't exist, and remember that fact for one day"

      No, they will return the NXDOMAIN code. Negative responses are cached at the discretion of the client -- no resolver I know respects the TTL on negative responses.

    12. Re:Wanted: DNS geek by Anonymous Coward · · Score: 0

      This is irrelevant if the isp's dns server would do the same thing.

  13. I RTFA and all I got was this T-shirt by marsvin · · Score: 1

    Item: Sending mail and checking received mail for spam involves DNS lookups. If you send and/or receive a lot of email, you need to do a lot of DNS lookups.

    Item: Spammers use nonexistent domains.

    Where would we be without eWeek?

  14. Crippling DNS? How much does DNS suck? by stratjakt · · Score: 2, Interesting

    I don't get it.

    So I send out a million spams, all saying "go to www.stratjaktsmadeupdomainname.com for hot viagra and lower mortgage payments."

    The domain doesn't exist, and people click on it, which "cripples" dns because the dns servers have to respond with a "no such domain name" reply?

    How does this cripple them? Was DNS not designed to handle fat-fingered domains gracefully?

    What happens, do all the requests for my domain get propogated up the chain, is that the crux of the problem? If so, doesn't DNS update like, quite often (several times a day) now? There's no need to kick all requests up to the top, right?

    --
    I don't need no instructions to know how to rock!!!!
  15. I don't get it. by Anonymous Coward · · Score: 0

    I don't get it. By advertising a domain that doesn't exist, how are they supposed to sell anything? People get the spam, click the link... and get nothing. What's the point?

    1. Re:I don't get it. by stratjakt · · Score: 1

      The send the spam, then register the domain. That way there's no way they can be filtered based on their return address, or any hyperlinks in the message (since the domain doesnt exist, how could it be in a blacklist?)

      What I don't understand is how this breaks DNS. DNS should be able to handle non-existent domains without issue.

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:I don't get it. by Anonymous Coward · · Score: 0

      That way there's no way they can be filtered based on their return address, or any hyperlinks in the message (since the domain doesnt exist, how could it be in a blacklist?)


      Just check to see if the domain exists. If it doesn't, the email gets sent to the 'spam' folder. Simple.

    3. Re:I don't get it. by el_gordo101 · · Score: 1

      Better yet, register the not-yet-registered Domain name yourself before the spammer gets a hold of it. Put up a placeholder page that says "Sorry about the Spam, but the sender has been beaten at his own game." Or something.

      --
      TODO: Insert witty sig
  16. all this just makes me sad... by jxyama · · Score: 2, Insightful
    ...and also mad.

    this is not meant as any kind of informative post, but every time i read something like this, or receive another spam in my Inbox, i feel a bit of both sadness and anger...

    here is a wonderful tool that made communication easy, fast and cheap but is absolutely being ruined by the malicious few with absolutely no morals, ethics or concerns for others.

    just like those orphan traders at tsunami disaster areas... i really would like to have a chance to confront these disguisting people and try to make sense of their thought process...

    1. Re:all this just makes me sad... by Anonymous Coward · · Score: 1, Informative
      here is a wonderful tool that made communication easy, fast and cheap but is absolutely being ruined by the malicious few with absolutely no morals, ethics or concerns for others.

      Sadly it is quite easy:

      1) profit

      cost to spam: (tiny fixed amount) + ($0.00 * number_of_spam)
      means that there is very little cost to the sender of spam. This means that if 1 in 100000 buy their product they have made money.

      (Remember this: There Aint No Such Thing As A Free Lunch. We ate our `free' lunches and now we have to pay.)

    2. Re:all this just makes me sad... by JerkBoB · · Score: 1

      i really would like to have a chance to confront these disguisting people and try to make sense of their thought process

      There's not much to understand.

      1. Situation to be taken advantage of
      2. Lack of morals/ethics
      3. ???
      4. Profit!

      --
      A host is a host from coast to coast...
      Unless it's down, or slow, or fails to POST!
    3. Re:all this just makes me sad... by antifoidulus · · Score: 1

      There is always the joke(and it's variants)
      Normal person to large asshole: How do you sleep at night?
      Asshole:On top of a big pile of money next to a different beautiful woman every night!
      NP:Ok, I was just curious...

    4. Re:all this just makes me sad... by jxyama · · Score: 1

      yeah, i know, but i'd love to have a chance to meet them... i know why they do it, i still want to know what kind of sick mind they have to not care about the malicious consequences of their actions.

    5. Re:all this just makes me sad... by John+the+Kiwi · · Score: 1

      I used to think like that too. Right up until I moved to the States and started to receive more than 15 requests for credit cards and other business services in my mail box once I registered a company.

      Spam doesn't affect trees. And the truth is that spam will always be around as long as there's money to be made from it. It's an end user education problem. As soon as end users are educated enough to know not to buy the things in the spam emails then there's always gonna be someone sending it.

      As soon as the financial incentives are removed there will be no more spam problem. But right now spammers are making money hand over fist because people click on the links and buy the crap the spammers are hawking.

      What could be more capitalistic than spam?

      Kiwi

    6. Re:all this just makes me sad... by Turn-X+Alphonse · · Score: 0, Offtopic

      orphan trading? link please.

      --
      I like muppets.
    7. Re:all this just makes me sad... by Master+Bait · · Score: 1

      Spam will never go away until the government decides that the Direct Marketing Association are not their friends.

      But our governments are in bed with the spammers and so are the credit card companies.

      All that is needed to eliminate spam is to attack it at the other end of the line with a small staff of agents, several honeypot email boxes, and three judges blanketing a 24-hour day to issue subpoenas which freeze the spammer's credit-card merchant account assets.

      --
      "Only in their dreams can men truly be free 'twas always thus, and always thus will be."
      --Tom Schulman
    8. Re:all this just makes me sad... by JaredOfEuropa · · Score: 1, Funny
      a chance to confront these disguisting people and try to make sense of their thought process...
      [voice of Prof. H. Farnsworth]
      Only one way... by disecting its brain! Enough chitchat, restrain the specimen
      [/Prof. H. Farnsworth]
      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    9. Re:all this just makes me sad... by hackstraw · · Score: 1

      i really would like to have a chance to confront these disguisting people and try to make sense of their thought process...

      feel free to do a whois query or whatever and if they are in the US and you have free long distance or whatnot, give them a call. They really appreciate the feedback :)

    10. Re:all this just makes me sad... by jxyama · · Score: 1
      one example...

      http://edition.cnn.com/2005/WORLD/asiapcf/01/04/in donesia.children/index.html

    11. Re:all this just makes me sad... by Anonymous Coward · · Score: 0

      Your anger is legitimate and well-justified, but isn't it displaced? Spam is a free market tool. It is used because it works. If it didn't work, people wouldn't do it. This is a business. Money lubricates the machine. It's the people who buy the spam, that visit the websites, the drive the traffic or fall for the scams that are the spam supporters and financial backers ultimately.

      It is us, as a buying public, that is to blame for spam.

    12. Re:all this just makes me sad... by jxyama · · Score: 1
      being mad about a phenomenon where i receive the same email about refinancing 50 times an hour is, i feel, not displaced nor am i willing to shoulder any of the blame for it.

      another thing that gets me mad is that spammers largely aren't held accountable. what they do, they do without ever being held liable for their actions or consequences. it's so sneaky and hence disgusting. direct mailers actually incur costs. telemarketers actually incur costs. not so for spammers. they inflict all the damages they want and hell with all the consequences because they aren't affected themselves so they don't care...

    13. Re:all this just makes me sad... by Anonymous Coward · · Score: 0

      Welcome to the real world..

      what surprises me is that there are still people who are surprised by this.

      people will usually do what maximizes their profit, or their benefit, or whatever. if you put something out that doesn't have a cost associated with it (email for instance), it will be abused. if you don't enforce a limit on something, people will maximize to infinity. If you don't make good behavior cheap and bad behavior expensive, people will gravitate toward bad behavior.

      this is just how the world works! keep this in mind when designing, well, pretty much anything.

      of course that doesn't mean *YOU* have to be a bad person. Be a good person as your concious allows, but assume everyone else is maximizing their own benefit without regard to what you think is good or bad.

    14. Re:all this just makes me sad... by Anonymous Coward · · Score: 0

      I just wish US people would keep their
      distorted capitalism to themselves.
      That's what!

    15. Re:all this just makes me sad... by Anonymous Coward · · Score: 0

      The normal person was "The Critic," and the large asshole was Rainier Wolfcastle, a.k.a. McBain.

      Jay: Welcome to "Coming Attractions". I'm your host, Jay Sherman,
      thank you. Tonight, we review an aging Charles Bronson in
      "Death Wish 9".
      Bronson: [in a hospital bed] I wish I was dead. Oy!
      Jay: But first, we have a special guest: Rainier Wolfcastle, star of
      the reprehensible McBain movies.
      Rainier: Jay, my new film is a mixture of action und comedy. It's
      called "McBain: Let's Get Silly".
      [cut to clip from movie showing McBain with a microphone in
      front of a brick wall]
      McBain: Did you ever notice how men always leave the toilet seat up?
      [pause] That's the joke.
      Man: [from audience] You suck, McBain!
      [McBain pulls a machine gun and fires into the audience]
      McBain: Now, my Woody Allen impression: I'm a neurotic nerd who likes
      to sleep with little girls.
      Man: [from audience] Hey, that really sucked!
      [McBain pulls the pin on a grenade and tosses it at him]
      Rainier: The film is just me in front of a brick wall for an hour and a
      half. It cost $80 million.
      Jay: [contemptuous] How do you sleep at night?
      Rainier: On top of a pile of money with many beautiful ladies.
      Jay: Just asking. Yeesh!

    16. Re:all this just makes me sad... by DeepHurtn! · · Score: 1
      I don't think that's how spammers make money -- most of them are contract workers, not hawking stuff themselves. They make money by convincing companies that e-mail is an effective "marketing tool" -- it is irrelevant if it actually generates sales, as long as there are enough suckers out there who think it does.

      Another source of profit is selling software, e-mail lists, etc to other spammers. I suspect it's a lot like the gold rush -- the people getting rich aren't the prospectors, but the people who own the shops.

    17. Re:all this just makes me sad... by Anonymous Coward · · Score: 0

      Ok, then be mad. Lot of good that is doing in getting the problem solved. Don't try to understand the bigger picture.

  17. Auto-register domains by crow · · Score: 5, Interesting

    Some anti-spam group should set up a spam filter that looks for domain names, and registers any that it sees that aren't valid. They would point to a web site that politely explains to users how stupid they are for clicking on a link in spam.

    I expect spammers would drop that technique quite quickly if that were done.

    1. Re:Auto-register domains by Anonymous Coward · · Score: 1, Insightful

      Keep in mind that domains are about $10 a pop to register. I am sure many spammers would love to break the bank of anti-spam activists.

    2. Re:Auto-register domains by crow · · Score: 1

      The cost of the registrations could possbily worked out with a deal with one of the registrars.

      I would love to see the reaction the spammer has the first time he tries that trick and finds that someone else beat him to the domain registration.

      It would also provide some interesting data on the click-through and image-view rates for spam.

    3. Re:Auto-register domains by Anonymous Coward · · Score: 0

      .... or see about how to automatically stuff it into a blacklist...

    4. Re:Auto-register domains by sydsavage · · Score: 1
      I predict that competing spammers will start to register these domains out from under their brethren, in an attempt to steal their sales leads. While not directly helping the spam dilemma, at least the spammers will waste some time, effort and money in an escalating war between each other...

      However, what if there was a way to lock the domain for a period of time if the domain is identified as a spam advertised site?

    5. Re:Auto-register domains by Incadenza · · Score: 1

      Some anti-spam group should set up a spam filter that looks for domain names, and registers any that it sees that aren't valid. They would point to a web site that politely explains to users how stupid they are for clicking on a link in spam.

      How about spamjacking: you set up a site for herbal supplements, anti-spamware, rolexes or whatever, and wait for spam with an unvalid domain name to arrive in your mailbox. Then register your site with their domain name: voila! Advertised for free! And no incriminating evidence whatsoever between your company and the spam run. Some spammer will figure this out sooner or later, and they won't worry at all about the domain registration fees.

      Coming soon: the war of the spam kings.

    6. Re:Auto-register domains by BurritoWarrior · · Score: 1

      I would expect spammers to send 10 million false domains within the first day of that going live. You got that kind of cash for domain registrations?

    7. Re:Auto-register domains by crow · · Score: 1

      Obviously you would limit the auto-registration to some small number. If spammers start to send out dummy mail to trigger registrations, just wait until you've received enough spam with the same domain from separate honeypot email accounts.

    8. Re:Auto-register domains by Anonymous Coward · · Score: 0

      Perhaps the costs could be covered using Google's Adsense or a similar program?

    9. Re:Auto-register domains by Anonymous Coward · · Score: 0

      That's actually an interesting idea. If nothing else, it could be useful to gather first-hand data of the kinds of traffic these spammed messages generate. If it is viable, if there is enough traffic to offset the cost with AdSense or whatnot, then the site could be used to shame the user for clicking in the first place. I suspect it wouldn't be viable, but an interesting thought nonetheless.

  18. What about whois? by portwojc · · Score: 1

    I know whois would just get ripped a new one but what about a system like that on verifying a domains true existance?

    It would have to be a true/false response so it would be fast. No vitals returned just if the domain is really regisitered or not.

    DNS time out. Look for in the "quick-whois" for it. It's not there (but whois gave a non-timeout response) drop the message. If they are there (or a "quick-whois" timeout) then queue it like normal.

    It's a rough idea and probably not that good of a one; come up with a better one then.

    Sounds silly to have to double lookup. Maybe a DNS modification would be better... The query should be able to say if a domain is registered or not they all have at least that record right?

  19. spam protocol hogging by Doc+Ruby · · Score: 4, Insightful

    DNS could play a role in beating spam. DNS servers suffering from "spam overload" can see that they're handling a lot of the same lookups, that are overloading them. They could flag their responses back to the isolated SMTP servers that are processing the spams, which can tell that they're all the same message. So the distributed network can identify spams, and at least require the senders to share some of the processing load (through another extension to the SMTP and DNS protocols). A more severe response that might affect mere mass-mailers (different from "spam" because content is either noncommercial, or was solicited by the recipient) would be to report such spam-suspects to blacklist servers, which in turn inform users spam filters.

    Having had several mass-mailed (big Cc: lists) urgent messages filtered out by corporate spam filters in the past couple of months, I know we need a much better system. Spam is taking down DNS, blocking SMTP, and, even worse, censoring legitimate message needles in the spam haystack. We need network protocols to get smarter, taking advantage of the distributed intelligence that can kill spam. Can the IETF overcome its interest in perpetuating the spam that pays for so much of the Internet, in leading us out of the spam trap?

    --

    --
    make install -not war

    1. Re:spam protocol hogging by okigan · · Score: 1

      Now i am not a pro in SMTP protocol so correct me if i am wrong.

      Speaking from a simple point of a DSL subscriber, when i want to send email i have to login with my login/passwd into the assigned SMTP server. Once I login all messages I sent have my name stamped on them.

      Now if i would choose to send spam, it could be easily blocked just by black listing the name stamped on the messages.

      So, now the 64B$ question: why in the world many SMTP servers allow a spammer to sign in with one name and send emails with a different "from" name???? (note, that it seems to be not a problem of DNS but SMTP).

      (now, before we get into a war, I do see some scenarios that would require that, but they represent much smaller fraction, and could be taken care by some trust relation between a limited number of mail servers, or is not it?)

    2. Re:spam protocol hogging by Doc+Ruby · · Score: 1

      One of the biggest problems in the spam architecture is "open relays": SMTP servers that don't require (or authenticate) any "logins" before sending. So a single SMTP server might not have the info that a thousand messages it's been asked to send in the past second (to different recipients) are the same spam, or even from the same spammer. A minimal first step, that most SMTP servers have taken, is to require login, if not authentication of the "From:" header.

      It would also be good for SMTP servers to notice that many "different" senders have asked it to send the identical message body. That could be a legitimate activity, but it's so rare, and so typical of spammers "spoofing" fake "From:" headers (or just sending from the same user), that the SMTP server should at least notify the POSTMASTER who controls it. There's lots of network/protocol warnings that a spam wave is under way - we can cut it all down to managing the unavoidable holes with a little work. Which will go a long way towards retaming the Internet.

      --

      --
      make install -not war

    3. Re:spam protocol hogging by CustomDesigned · · Score: 1
      why in the world many SMTP servers allow a spammer to sign in with one name and send emails with a different "from" name?

      The spammers run their own SMTP servers - usually on 100,000 or so Windoze Zombies that they control. Recipients that check SPF on the forged messages, however, can detect and reject them. Caveat, if the recipient uses forwarders, then either the recipient or the forwarder has to be technical enough to properly configure forwarding (like SRS for the forwarder or a trusted forwarder list for the recipient). If the spammer publishes SPF, then the domain can be safely blacklisted without worrying about an innocent party getting joe jobbed.

    4. Re:spam protocol hogging by tabrisnet · · Score: 1

      Possibly b/c I have many "role" accounts? I have half a dozen different domains I have accounts under. Mind you, they all forward to the same mailbox, but I have to be able to send back email using the same From that it was sent To.

      And fwiw, the problem you speak of is handled quite nicely with SPF and/or SPF/PRA. And I can even deal with it by setting my MX as a valid relay for all of those "role" accounts.

    5. Re:spam protocol hogging by Rich0 · · Score: 1

      The spammer doesn't log into an SMTP server, but runs their own.

      Nothing annoys me more than the fact that I need to log into my ISP's mail server. I should be able to run my own outgoing mail. The problem is that because of spam most ISPs would block my mail if I did that (since I'm using a dynamic IP).

      Don't get me wrong, I understand completely the need to block dynamic IPs doing direct SMTP (I spam filter them myself). However, this isn't an ideal situation. In an ideal world, people wouldn't send spam and so nobody would have to block what would be an otherwise legitimate use of SMTP. In a slightly less ideal world I could publish an SPF record for my dynamic DNS entry, and then everybody wouldn't need to block me simply for having a dynamic IP.

    6. Re:spam protocol hogging by Anonymous Coward · · Score: 0

      welcome to 1996.

    7. Re:spam protocol hogging by snorklewacker · · Score: 1

      One of the biggest problems in the spam architecture is "open relays"

      Actually they're becoming a rather minor issue compared to open proxies, and those have taken a backseat to zombies.

      That could be a legitimate activity, but it's so rare, and so typical of spammers "spoofing" fake "From:" headers (or just sending from the same user), that the SMTP server should at least notify the POSTMASTER who controls it.

      Believe me, the postmaster isn't interested. It'd just add to the backscatter they constantly have to deal with from antivirus programs that insist that THEIR machines sent a virus, because it was on the From: line after all. Warning the postmaster at the outgoing site isn't helpful -- the spammer is the postmaster.

      --
      I am no longer wasting my time with slashdot
    8. Re:spam protocol hogging by Doc+Ruby · · Score: 1

      The first SMTP server in the line is the spammer (and postmaster). But the ones down the line from them are not (necessarily) spammers, such as me, the postmaster of the last (incoming) SMTP server in the chain. I'd like to get messages from my SMTP server telling me that it was processing a message identical to hundreds of copies in other SMTP servers across the Net, except the To:/From: headers had been changed to protect the spammer (and reach the spammee). That would be easy to prioritize over other traffic, as it has corroborated other suspicious details, clueing me into info otherwise available only to the spammer at the center of their web.

      --

      --
      make install -not war

    9. Re:spam protocol hogging by Desert+Raven · · Score: 1

      The first SMTP server in the line is the spammer (and postmaster).

      Whoops, no, it might not be. More than one spammer app inserts bogus SMTP Received headers into the message before actually sending it. Sometimes, they're darned difficult to tell from valid headers.

      The *only* Received header you can trust is the last one, the one *your* server wrote.

    10. Re:spam protocol hogging by Doc+Ruby · · Score: 1

      The *first SMTP server line* in a particular email might be spoofed. But I'm talking about the actual network topology: the first SMTP server in the *sequence of SMTP servers that actually forwarded the message was a spammer's (though subsequent ones might also have been). So what if you get "spam flag" messages from other servers that aren't your own? I suppose that spammers might start hoaxing real messages, flagged as spam, but that would require their passing those real messages. Such a topology might put all the burden of authentication trustable headers on the *upstream* server, not to send a real message to a downstream SMTP server which will flag it as spam without reason, before sending it to the recipient (eventually). Seems a big cost for spammer SMTP servers, with little gain, except spannering the entire works a little, and forcing end-to-end trust relationships that will eventually force them out of the chain entirely. Maybe that's the only way, but until then, it's cheaper to use semitrust, and upgrade later. That's how NP-complete problems work.

      --

      --
      make install -not war

  20. On the topic of spam by RealAlaskan · · Score: 1
    This suggests that some mail systems are already parsing links in emails and rejecting those which are to known spamvertisers? That's a good idea, but it must put a bit of a load on a mail server.

    We need to be going after the spamvertisers, not the spammers. Legislation outlawing spamvertising, with penalties for the advertiser and the spammer, not just the spammer, would be far more effective than merely shooting all spammers. After all, spammers can hide and work from offshore, while the advertiser has to have some way to collect the cash. He can't hide nearly so well.

    Yes, there would be joe-jobs, but our legal system is already familiar with the idea of ``framing'' innocent parties, and they know how to deal with it.

    On the topic of spam and spammers, I think the fortune at the bottom of the page is wonderfully appropriate:

    No one can have a higher opinion of him than I have, and I think he's a dirty little beast. -- W.S. Gilbert .

    1. Re:On the topic of spam by ScentCone · · Score: 1

      penalties for the advertiser and the spammer

      A manufacturer/seller can easily (and honestly, and legitimately) point out that someone who has joined their affiliate program has violated their terms, and is spamming against the rules. The person running the program can certainly pull the plug on that affiliate account, and the big affiliate engines (Commission Junction, Performics, et al) can torpedo user accounts and do... but not in an instantaneous way. You'd think that these folks (the affiliate program and system managers) would have a vested interest in legitimizing their affiliate traffic (yes, they make money indirectly off of even the bad actors), and could find ways to detect the patterns that surely show up when one of those major broadcasts happen. The big boys have some pretty elaborate 'bots that already check member web sites to see if the affiliates are playing by their content rules. I would imagine that positioning some mail server plug-ins at a number of very willing partners would help them detect the waves that are set off when an affiliate spammer launches lets loose.

      --
      Don't disappoint your bird dog. Go to the range.
    2. Re:On the topic of spam by gad_zuki! · · Score: 1

      >We need to be going after the spamvertisers, not the spammers.

      Exactly. It blows my mind that very few people want to ask who the men behind the curtain are. Spammers are just nerds for hire. Its the marketers, businesses, and investors who must be targeted also. The same is true with spyware. Follow the money, people.

    3. Re:On the topic of spam by robogun · · Score: 1
      This suggests that some mail systems are already parsing links in emails and rejecting those which are to known spamvertisers? That's a good idea, but it must put a bit of a load on a mail server.

      It does, but it's worth it.

      Windows users have SpamPal which does lookups on spammed URLs. You can use the RegEx & URL Body filters and get 99% of spam with no falses. If you're getting hard core spammed, add the RBL lists. & it's free.

  21. Re:Anti-Spam Legislation Is Only Effective Solutio by freedom_india · · Score: 0

    Why is it modded as Funny?
    It should be modded as Insightful.
    Bah ! slashdotters... always confusing the interesting with important and necessary with coulda', shoulda', woulda'...

    --
    "Doing what i can, with what i have." ~ Burt Gummer
  22. Negative Caching by whoever57 · · Score: 4, Insightful

    BIND, at least, does negative caching. Surely this means the load on DNS servers due to looking up the non-existent spam domains is minimal.

    Also, once the mail server has decided that a bounce reply is undeliverable (because of no DNS records), surely it is going to dump the email immediately, rather than continuning to attempt to deliver it?

    So is this a case of SOME brain dead implementaions of DNS and mail servers, or a real problem for all?

    --
    The real "Libtards" are the Libertarians!
    1. Re:Negative Caching by Anonymous Coward · · Score: 0

      Also, once the mail server has decided that a bounce reply is undeliverable (because of no DNS records), surely it is going to dump the email immediately, rather than continuning to attempt to deliver it?

      You have obviously never used Exchange.

    2. Re:Negative Caching by mortonda · · Score: 1
      Also, once the mail server has decided that a bounce reply is undeliverable (because of no DNS records), surely it is going to dump the email immediately, rather than continuning to attempt to deliver it?



      No, it will put it in the defered queue and try again later, finally giving up after 5-7 days, and potentially filling a mail queue with 20k-50k deferred bounce messages.

    3. Re:Negative Caching by whoever57 · · Score: 1
      No, it will put it in the defered queue and try again later, finally giving up after 5-7 days, and potentially filling a mail queue with 20k-50k deferred bounce messages.

      Well, this seems to be implementation dependent. Postfix does not do this (I just checked). Perhaps Exchange does (another poster suggested this), in which case it is merely an implementation problem in SOME MTAs (as I suggested in my original post)

      --
      The real "Libtards" are the Libertarians!
    4. Re:Negative Caching by jayed_99 · · Score: 1
      Part of the problem seems to be that people running mail servers and tools like SpamAssassin aren't running their own caching nameservers locally.

      I actually run two caching nameservers. One for email servers and the other for everything else. The DNS lookups for email have a different *context* than web browsing -- which indicates to me that they should be in separate caches. Negative responses for an email lookup shouldn't pollute the positive information about web lookups.

      ::shrugs:: It's hard to say if this is a case of "brain dead implementations of DNS and mail servers". The biggest problem with an email/DNS setup is that there are so many possibilities and complexities that it's hard to make generalized statements about how site deals with things over another.

    5. Re:Negative Caching by mortonda · · Score: 1

      Postfix *does* do this. I have had to clear out 20k messages because of this. "Bounce" messages will queue up. OTOH, if the server answered with a "reject" message to the original message, then no bounce message is generated.

      Granted, this is usually a problem when a server is under a dictionary attack, and doesn not have a proper recipient_map set up to reject unauthorized recipients.

      A properly configured postfix server would reject unknown recipients, and the dns load would be handled by a local caching dns server. The eweek article is just plain wrong.

    6. Re:Negative Caching by morzel · · Score: 1
      You have obviously never used Exchange.
      Or Sendmail, or Postfix, or about any mail server...

      A DNS lookup failure is considered to be a transient error, and the mail is deferred for re-transmittal on the mailserver. Only if the mail can't be delivered for a preconfigured amount of time (usually 5 days), the mail bounces.

      --
      Okay... I'll do the stupid things first, then you shy people follow.
      [Zappa]
    7. Re:Negative Caching by DavidTC · · Score: 1
      My mail server defers mail coming in that doesn't have a valid email address domain.

      So, basically, this is great for me. Spammers don't use open relays anymore, and thus the email isn't queued anywhere. So if I defer it at that point, they've lost.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    8. Re:Negative Caching by whoever57 · · Score: 1
      Or Sendmail, or Postfix, or about any mail server...

      A DNS lookup failure is considered to be a transient error, and the mail is deferred for re-transmittal on the mailserver

      I think this is a configuration option in Postfix. Why do I think this? Because I tested it on my own MTA, running Postfix before posting. Here is an entry from my logs after trying again. You will see that the status is: "bounced":

      Jan 13 20:26:38 mail postfix/smtp[10474]: EBC601DE0D8: to=, relay=none, delay=1, status=bounced (Host or domain name not found. Name service error for name=lajfjlajldjaljf.com type=A: Host not found)

      --
      The real "Libtards" are the Libertarians!
  23. Spam by clinko · · Score: 2, Funny

    I hate this new trend! I have to wait until morning until I can order my v!@gra!!!

    What happened to the good old days, when I could order B0n3r Juic3 as soon as I got my mail!

  24. Old News by Obsidian+Dagger · · Score: 1

    The article was posted on Monday and was sent out to those who subscribe to the FREE e-mail newsletter. This not intent as flamebait or a troll so please don't reply with fames; I just wanted to vent and the fact that thissite is usually GREAT at supplying up to the minute information. I guess I'm just upset that I went to the link expect new information and got disappointed with the same article I read Monday.

    --
    "It is not my intent to offend, but if offense is taken, the fault lies with the audience." attributed to Patrick Henry
    1. Re:Old News by Anonymous Coward · · Score: 0

      Hey if the domain doesn't exist yet, then it has no reverse lookup in DNS (PTR), simply force the dropping of connections without a reverse PTR record, one DNS lookup and bam drop connection, solves many problems

  25. Re:Crippling DNS? How much does DNS suck? by 2advanced.net · · Score: 2, Informative

    Failed requests (non existent domains) always go to the root servers.

  26. RMX/SPF would stop this cold. by delmoi · · Score: 1

    Without a domain to check the SPF record of, the mail would never be delivered. Easy.

    On the other hand, it could result in far, far more DNS lookups for an organization, but in theory they would never need more DNS capability then they have mail capability.

    --

    ReadThe ReflectionEngine, a cyberpunk style n
    1. Re:RMX/SPF would stop this cold. by finse · · Score: 1

      I agree with this opinion. I absolutely agree SPF is very reliant on dns, with each inbound message creating at least one dns query. However, if SPF catches on, and systems are configured to drop non compliant SPF emails, email/dns could weather this latest tactic.

      --
      Paranoid tinfoil hat crowd say Y here, everyone else say N.
  27. Re:Dammit by jxyama · · Score: 1

    making something that cannot effectively be controlled illegal does nothing. the value of making something "illegal" comes from being able to hand out effective punishments for the violations, not in the simple act of "labeling" it illegal. something being illegal is hardly a deterrant on its own...

  28. Re:Dammit by Anonymous Coward · · Score: 0
    yeah and make killing illegal too! that will also teach 'em.

    oh wait, that law gets broken frequently too. damn, i guess your political satire fails to stand up to reason.

  29. Re:Crippling DNS? How much does DNS suck? by stratjakt · · Score: 1

    Only once, then their cached with some sort of default timeout (ie; check again in a few hours), or does this vary from implementation to implementation?

    What I'm thinking, is that this is a big problem for (since this is slashdot) Microsoft ActiveDNS 2005, but not for BIND or OSS implementations, which have no such flaws.

    Is this the case, or is it an inherent problem that DNS is just a shitty outdated protocol, like SMTP?

    Will moving to IPv6 change anything?

    --
    I don't need no instructions to know how to rock!!!!
  30. Is it really true - I don't think it's fully true by thundergeek · · Score: 1

    A comment at the bottom of the article holds validity regarding DNS. He says that if a spammer registers the domain, it makes them easier to track down.

    I don't think the author of the story quoted people correctly.

    From what I learned from DNS, whether the domain exists, or not, the same amount of queeururueeing is done.

    M$ wants you to have redundant DNS servers, they get more $$$, you buy more CALs, licenses, and headaches.

  31. Bogus article by SSpade · · Score: 2, Interesting

    Either the journalist drastically misunderstood and misinterpreted what they were told, or one of the people interviewed is launching some magic snake-oil product that'll "solve" this non-existant problem. (Yes, I know exactly what spammers do. That's my job. I know exactly what DNS does, that was my previous job. This article is fiction.)

    1. Re:Bogus article by Anonymous Coward · · Score: 2, Funny

      Yes, I know exactly what spammers do. That's my job

      Helpful suggestion: work on the phrasing a little bit, there, when you update your resume.

    2. Re:Bogus article by SSpade · · Score: 0, Offtopic

      Someone should definitely mod that +1 funny.

      (What I actually do is anti-spam forensics, tools and legal consulting.)

    3. Re:Bogus article by whoever57 · · Score: 1
      one of the people interviewed is launching some magic snake-oil product that'll "solve" this non-existant problem.

      How about "sitefinder" -- the wildcard in the .com domain?

      --
      The real "Libtards" are the Libertarians!
    4. Re:Bogus article by Anonymous Coward · · Score: 0
      This frightens me more:
      I know exactly what DNS does, that was my previous job.
      And you thought your job was bad . . .
  32. Slashdot Writers' Learn Punctuation by blueg3 · · Score: 1, Offtopic

    Slashdot writers (and editors) are still a lot worse than spammers, but their punctuation has some room for improvement.

    1. Re:Slashdot Writers' Learn Punctuation by DustyShadow · · Score: 1

      It appears that your punctuation also has room for improvement as the apostrophe in "Slashdot Writers' Learn Punctuation" does not make sense.

    2. Re:Slashdot Writers' Learn Punctuation by nojomofo · · Score: 0

      I wish there were a "-1 Clueless" mod. Hint: grandparent is making fun of Slashdot's title for the article and mocking it. It was intentional.

    3. Re:Slashdot Writers' Learn Punctuation by blueg3 · · Score: 1

      Thank you. I, too, am apparently clueless, though. I was notified of this message being posted and not of its parent (or so it seems to me). So I thought, "Why am I being clueless?" I started looking for posters named "grandparent". Eventually it all sort of worked itself out. Perhaps I need more coffee.

      Yes, I intentionally repeated the apostrophe misuse that I accuse the Slashdot editor/writer of making. In retrospect, I should have put [sic] after "Writers'" so that at least this little conversation could have included what "sic" means.

    4. Re:Slashdot Writers' Learn Punctuation by blueg3 · · Score: 1

      I'd like to correct an error I made here. My apologies to all Slashdot writers and editors. What I intended to write was that "Slashdot writers (and editors) are still a lot better than spammers..." Instead I wrote the opposite!

      Just to clarify, spammers are worse than Slashdot editors and writers. You didn't need me to tell you that.

  33. I noticed I am getting spam again by Billly+Gates · · Score: 2

    With Yahoo mail.

    I typically get 80 messages a day which the builk mailer always finds. These last 2 or 3 weeks only half the spam is being caught and my mail box is becoming loaded again. I was wondering why the fail rate was going up.

    My guess is Yahoo used dns lookups in its anti-spam software.

    1. Re:I noticed I am getting spam again by Tripster · · Score: 1

      The spammers have been streamlining the spam more lately to get around blocks, this means they are making them look more and more confusing to bayes filters, etc.

      They're also using different subjects these days that almost require you to check to make sure they are not legitimate emails, things like "order status" means if you are expecting a shipment of something your ordered you are going to open that message.

      I manage a couple ISP MTA frontends that use SimScan and SpamAssassin to drop anything scoring 10+ at SMTP level. This was working well for the nasty spammers but of late it is becoming much tougher again to block because the incoming messages are becoming less spam looking and more legitimate looking all the time.

      As more of us install these types of blocking systems the spammers are of course going to adjust to get passed them. I am sure it must be quite frustrating to them to see a 100% block with certain domain/ISP addresses and the will focus on those domains until they find a message that will get through.

    2. Re:I noticed I am getting spam again by Anonymous Coward · · Score: 0

      Spammers are building programs that have SA stuff built in. A friend of mine used to be a spammer, he still knows a lot of people. They write their programs with SA built in, and check to see if a message will pass the filter or not. It will only send out the message if it has a max score of 2. They don't check the RBL's though, so i have been catching them on that.

    3. Re:I noticed I am getting spam again by Billly+Gates · · Score: 1

      What SA?

    4. Re:I noticed I am getting spam again by Tripster · · Score: 1

      Enabling Razor2, DCC, Pyzor and the SURBLs in 3.x series of SA seems to help a lot. Those are tougher for them to get around it seems.

      Still, doesn't surprise me they'd be prechecking in SA before sending.

  34. Re:Crippling DNS? How much does DNS suck? by Anonymous Coward · · Score: 0

    If it existed, the first such lookup would get passed up to the root servers, send the right address down, and it would be cached locally, and the next million lookups would get the cached version, with minimal network traffic.

    If it doesn't exist, the first lookup goes all the way up to the root server, and so does the second, the third, and the millionth, because you don't want to cache "that doesn't exist", you want to keep trying until it does, so that the instant it exists you get the correct value.

    If you did cache "that doesn't exist", you would minimize traffic, but break in the case where a site is legitimately advertised before existing (by a stupid person who hits 'send' before hitting 'register me a domain'); like most protocols, DNS attempts to maintain correctness even when costly, rather than minimizing cost at the expense of correctness.

  35. Two words: RICO Prosecution by swb · · Score: 2, Insightful

    Spam involves criminal activity (fraud at the least). It involves many people (mail-senders, product suppliers, and some legitimate businesses like credit card processors, banks, and ISPs).

    Smells like a Racketerr-Influenced Corrupt Organization to me. Anyone even remotely involved gets a ticket to the proverbial Federal PMITA prison for 20 years, $100k in fines.

    These penalties and a wide net are all that can influence spam.

  36. Who ARE these people? by Matey-O · · Score: 1

    And who wired their brains to think this way? As much as I hate the stuff they do, ya gotta give them credit for being masters of manipulating The System(tm)

    --
    "Draco dormiens nunquam titillandus."
    1. Re:Who ARE these people? by bsd4me · · Score: 1

      If your livelyhood depends on it, then they will find a way. If you read the specs, study implementations, read up, and start to flowchart things, then ideas like this are likely to fall out. As much as it sucks in cases like this, it is an engineer's job to figure out ways to do things that "can't be done."

      --

      (S(SKK)(SKK))(S(SKK)(SKK))

  37. Re:Crippling DNS? How much does DNS suck? by Anonymous Coward · · Score: 0

    Will moving to IPv6 change anything?

    Wow. I thought you were pretty retarded in the Apple threads, but this just goes to show that you are a fucking moron. Just stop posting and save everyone the hassle of having to read your tripe.

  38. Re:Is it really true - I don't think it's fully tr by idontgno · · Score: 1
    From what I learned from DNS, whether the domain exists, or not, the same amount of queeururueeing is done.

    That's not accurate. An existent domain can be quickly resolved, possibly at the first-level nameserver. A non-existent domain requires upchannel querying all the way up to the TLD root, before deciding the lookup failed. That's a lot of elapsed time, and a lot of extra traffic. And I don't think DNS systems cache "does not exist" lookups, do they? So if an email refers to a non-existent domain 5 times, it could wind up with 5 different time-consuming failed lookups.

    --
    Welcome to the Panopticon. Used to be a prison, now it's your home.
  39. Yet Another Silly Article. by ngc5194 · · Score: 2, Insightful

    Wow. The article itself is ... stunning. On a per-word basis, I don't know where I've seen a higher concentration of misconceptions about DNS.

    Most modern MTAs have the ability to reject email purportedly coming from domains that aren't registered. Just as one example, sendmail does this by default. Not registering domain names makes it *much* *easier* for me to avoid spam. I encourage spammers to adopt the practice described in this article.

    Moreover, the costs of looking up nonexistant domains is roughly comparable to the costs associated with lookup up existing domains.

    Of course, despite the article being worthless, it's still more than enough cause for the /. regulars to get whipped up into a frenzy.

    1. Re:Yet Another Silly Article. by Tassach · · Score: 1

      It's not the spamming domain which is not registered, it is the spamvertized domain which is unregistred at send time.

      --
      Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
    2. Re:Yet Another Silly Article. by wereHamster · · Score: 1

      The problem is, the mail comes from a perfectly valid domain (yahoo etc), but the link inside points to an invalid domain.

      So unless sendmail scans the message for links, this isn't going to work.

    3. Re:Yet Another Silly Article. by Halo1 · · Score: 1

      It don't understand the problem with that. Most blacklists based on spamvertized links (like surbl) are text-based, not IP-based. They should need any DNS lookups.

      --
      Donate free food here
  40. Simple change in the root dns servers needed by Anonymous Coward · · Score: 0

    They only need to auto-register the domain once they get > 100 (put apropiate threshold here) enquiries about a non existent domain, point it to a web page telling the user please do not support spam, and, once the domain is registered, the secondary dns servers will be able to cache it as regular, and the spammers won't be able to use it later, because it is already registered.
    Then, after a couple of months, the domain could be automagically removed.

  41. Re:Dammit by Pxtl · · Score: 1

    While I do agree with you, its not like it would be that hard to track these people down. The very core nature of spamming demands some level of locatability. After all, they're selling products. Just subpoena the names of the people that the penis enlargement pill wholesaler has hired to advertise for them (force their cooperation with the threat of an accessory charge), and then prosecute the spammers into the dirt.

    The fact is that spamming for anything practically demands a paper trail - any scam requires a point of sale. The only reason that, if it was illegal, it wasn't prosecuted, is that law enforcement people haven't been told to give a shit yet. There are tons of laws that are not enforced ever, even when police have a case fall in their lap. Many laws are only prosecuted if you confess to or commit in front of a cop.

    The problem is that law enforcement needs to have their priorities forceably adjusted from busting pot-dealers and speeders to enforcing crimes that actually hurt people (although I think fighting street violence and large-scale financial crimes rates a damn sight higher than spam).

    Hell, hire handful of devoted nerds and accountants onto a police squad and give them access to the resources needed to get search warrants and subpoena computers and you could probably get the evidence thrown together to nail dozens of spammers and scammers in a matter of weeks. Of course, the legal process would be a whole other matter, but still, I'm sure that tracking down scammers isn't that hard if you follow the money trail.

  42. all this just makes me sad...Crapping the Nest. by Anonymous Coward · · Score: 0

    "here is a wonderful tool that made communication easy, fast and cheap but is absolutely being ruined by the malicious few with absolutely no morals, ethics or concerns for others."

    Welcome to illegal file trading. The story is basically the "Cold War, tit for tat" that gave us the bomb and MAD, as well as dictatorships. What wonderfull things will the "P2P vs content providers, tit for tat" bring us? How about the "SPAM vs Anti-SPAM, tit for tat"?

    Maybe we'll have the hard reality that it's not the technology that needs fixing, but us?

  43. Re:Is it really true - I don't think it's fully tr by thundergeek · · Score: 1

    But with the advent of dydns services, hasn't caching all but been reserved for corps?

    If a system has a dns expire time set real low, wouldn't it still look up the full domain, even back to the tld?

    Just wonderin, still learning ya know.

    Thanks

  44. Re:Crippling DNS? How much does DNS suck? by Twanfox · · Score: 1

    You miss the point of what they're doing.

    Spammer sends out email with a link to www.joeblowscompany.com except that domain does not yet exist.

    Spam software scans the email for URL's and domain names to check against. It validates the sender as a registered domain (not forged), finds a few more URLs, but they don't exist so it cannot check to see if those domains are known spamvertisers or not.

    Mail system delivers the mail, certifying it as 'not spam' as far as it can tell.

    Spamvertiser registers the aforementioned domain name, putting their warez up there.

    User now has a spam message that could have been caught but wasn't because the spammer knew how the filter worked, found a loophole, and used it to deliver the message.

    That is the crux of the problem, not the DNS load. Most spam-detection software is already doing this level of DNS lookups, pounding on the system to validate information. Not much changes there. What does change is that now, instead of being filtered, the messages get through.

  45. Re:Anti-Spam Legislation Is Only Effective Solutio by Anonymous Coward · · Score: 0

    How about a deadpool? Set up a website where we can all place a 'bet' on when we expect each spammer to eat it. Eventually, each spammer is worth more dead than alive... Then someone will guess a time that proves to be exactly right (perhaps with some help to ensure it) and earns the pool of thousands or millions of dollars... We just need a way to pay the winner anonymously. I've got a $20 for each person on the ROKSO list ready to go!

  46. Re:Anti-Spam Legislation Is Only Effective Solutio by dreamchaser · · Score: 0

    You were modded as +5, Funny. I'd submit to the crowd that it should have been +5, Insightful!

  47. Re:False positive when dropping invalid link by Anomalyst · · Score: 1

    One has to ask how useful a "bona fide" email would have been with an invalid link? I can not work up a lot of sympathy for the few clowns who cant be bothered to properly cut/paste a valid URL from a browser.

    Another point: If it is coming from a legit SMTP server then they should get a clue from the NDR sent to them when the email is rejected.

    ...but it is a DRY heave. -- me

    --
    There is no right to feel safe thru security vaudeville at the expense of everyone's freedom, privacy and tax money.
  48. Re:Crippling DNS? How much does DNS suck? by mOoZik · · Score: 1

    So why can't spam software be made immune by denying the message if it finds that the URL returns an error message, indicating it doesn't exist?

  49. Re:Is it really true - I don't think it's fully tr by whoever57 · · Score: 1
    And I don't think DNS systems cache "does not exist" lookups, do they? So if an email refers to a non-existent domain 5 times, it could wind up with 5 different time-consuming failed lookups.

    BIND certainly does cache NXDOMAIN ["does not exist"] for some period of time. I am not sure how long though.

    --
    The real "Libtards" are the Libertarians!
  50. We need a "wildcard" in the .com zone...... by whoever57 · · Score: 1

    If we had a wildcard, then all these lookups would resolve! Problem solved

    Let's go ask Network Solutions to add a wildcard to .com.

    [the above is a lame attempt at humor]

    [or is it--tinfoil hats on -- could it be that NS is behind the article in an attempt to promote the "sitefinder" wildcard entry?]

    --
    The real "Libtards" are the Libertarians!
  51. I have not noticed this problem by lorcha · · Score: 1

    But then again, I use SpamAssassin, which handles this type of thing gracefully. If the DNS tests are taking too long, SA will quit them. This has a throttling effect, so it hasn't hosed my DNS server.

    --
    "Avoid employing unlucky people - throw half of the pile of CVs in the bin without reading them." -- David Brent
  52. Re:Crippling DNS? How much does DNS suck? by Anonymous Coward · · Score: 0

    IPv6 uses a different DNS system, dopey.

  53. Legal countermeasures by earthforce_1 · · Score: 2, Interesting

    Standard IANAL disclaimer, but:

    Couldn't the spammers be sued for causing what amounts to a DOS attack on the recipient mailserver?

    Also, if sexual predators and hackers can be barred from going online, and if corrupt executives can be barred from acting as corporate directors, why can't judges ban unrepentant spammers from going online, or carrying on an internet related business? (And extradited if they subsequently set up shop offshore)

    --
    My rights don't need management.
  54. Costs money though by Sycraft-fu · · Score: 1

    The spammers could easily step up the pace and cost them a considerable amount.

    1. Re:Costs money though by Feztaa · · Score: 1

      Verisign's sitefinder could be adapted for this purpose... ;)

  55. The answer?? by SlinkyToad · · Score: 1

    I've been randomly experiencing some issues with phantom emails sent to my domain. People swear up and down that they sent me an email (sometimes a reply to an email I sent) and I don't recieve it. Futhermore they don't receive an undeliverable or waiting for delivery response. I've checked spam filters - everything I can think of. The evidence is that the email is getting dropped somewhere in the chain. Could overloaded DNS servers on either end be causing this issue? BTW - I'm not using my domain to send SPAM. No really, I'm not, I SWEAR! -- Rock and Roll ain't no riddle man...

  56. Re:Crippling DNS? How much does DNS suck? by stratjakt · · Score: 1

    That is the crux of the problem, not the DNS load.

    Then why is the article suggesting that spam is bringing DNS to it's knees and the sky is falling?

    Sounds like a problem with the spam filter.

    If the spam filter encounters an non-existent domain, then IT should cache it, and not bother DNS with subsequent requests. If it delivers it fine, the user marks it as spam, and bayesian algorithm doesn't allow "stratjaktshotsexviagramortgagesite.com" again.

    --
    I don't need no instructions to know how to rock!!!!
  57. Spam blocker immunity? by mOoZik · · Score: 1

    Why can't spam software be made immune by denying the message if it finds that the URL returns an error message, indicating it doesn't exist? If it finds a web site doesn't exist (and I'm not referring to the domain, but the actual URL, in its entirety), it should simply reject it. Does this not make sense?

    1. Re:Spam blocker immunity? by DarKry · · Score: 1

      What a wonderful idea. Then any domain without a website won't be able to have a mail server either. Believe it or not we don't all use gmail buddy. Seriously though the solution is in more DNS lookups instead of less. Someone put together a patch for qmail which does an MX lookup for the incoming addresses and denies if it fails. If you are really concerned about extra DNS lookups (Not exactly sure why you would be) you could even keep a list of failed domains and check against that first. Although the type of people who wrote this article in the first place will be telling me next that the 50 extra instructions this would take are going to slow down servers. If you want to see bloat look at Sendmail and stop complaining about DNS lookups.

  58. WHOIS, not DNS by jmason · · Score: 1

    Actually, it appears likely that the article is getting the wrong end of the stick entirely, confusing WHOIS and DNS. more details...

  59. Re:Crippling DNS? How much does DNS suck? by stratjakt · · Score: 1

    in the case where a site is legitimately advertised before existing (by a stupid person who hits 'send' before hitting 'register me a domain')

    That's not a problem, a site that doesn't exist yet is not "legitimately advertised".

    BIND caches misses.

    It sounds to me like the spam filter should be doing the caching though, not DNS.

    --
    I don't need no instructions to know how to rock!!!!
  60. Choices by toby · · Score: 1
    Even in large enterprises, it's becoming very common to see a large spam load cripple the DNS infrastructure
    Only if it's misconfigured or running inferior software.
    --
    you had me at #!
  61. Registrars need to check with the spam lists by Animats · · Score: 1
    This should be easy to fix. Domain registrars should be required to check the spam databases during domain registration. If a domain has been recently associated with spam, extra validation of the ownership of the domain should be required. ICANN can require this. They've been tightening up on phony domain registration info already.

    Incidentally, any "domain hiding" service which assists a spammer could find themselves liable under the "conspiracy" clause in the CAN-SPAM act. CAN-SPAM is weak on spamming but tough on identity forgery.

    1. Re:Registrars need to check with the spam lists by CatherineHelzerman · · Score: 1

      I've noticed that an increasing amount of registrars have stopped offering "un-listed" domains. Some still do though...I believe you can get unlisted at register.com. Couldn't you also "sell" your domain to a fake person? Some registrars are pretty lax about domain transfer.

    2. Re:Registrars need to check with the spam lists by Animats · · Score: 1
      ProtectFly now says "All verified spam complaints will result in your Protectfly service being terminated, consequently your domain ownership information will revert back to yours." They also have much tougher indemnification clauses.

      They seem to have changed the terms of service shortly after I quoted the relevant section of the CAN-SPAM act to them.

      Registrars who falsely list themselves as domain owners make themselves lawsuit targets. If there's a problem, the registrar ends up in court. Then they have to convince a judge that they're an innocent intermediary who just happened to sell some essential service to a criminal. This is not a good legal position to be in.

  62. bye bye spamhaus by Anonymous Coward · · Score: 0

    From the spamhaus website:

    "it's suprisingly easy to shut down a spammer..."

    Well you know how the old saying....

    Easy come, easy goes.

    Tricks like this just show how naive steve linford is...

  63. Re:False positive when dropping invalid link by statusbar · · Score: 2, Insightful

    The invalid link may be a link to an internal website. For instance http://wiki.local./ is valid in the office but invalid outside the firewall.

    Jeff

    --
    ipv6 is my vpn
  64. Re:Two words: RICO Prosecution by Anonymous Coward · · Score: 0

    Right...so when you leave your Windows box wide open on the internet, and someone installs a spamming trojan, do you get to go to prison? Because I think we already have enough problems with prison overcrowding.

  65. Re:Anti-Spam Legislation Is Only Effective Solutio by Anonymous Coward · · Score: 0

    spam lists on cd-r, must be able to physically destroy their system and storage media....

  66. Re:Anti-Spam Legislation Is Only Effective Solutio by mogul · · Score: 1

    It will work even better when it becomes illegal NOT to kill a spamer.

  67. Re:Anti-Spam Legislation Is Only Effective Solutio by mattyrobinson69 · · Score: 1

    beat the spammers to death, and then sue the family for the cost of the bat used to beat them with.

    this was dont in blackadder iirc (UK comedy), where some french people had to pay for their own relatives execution

  68. beat them to the punch... by Anonymous Coward · · Score: 0

    Register the domain they are using and they will be forging messages.

  69. Re:Dammit by johnbeat · · Score: 0

    When over 30% of people in the United States have murdered someone at least once in their lifetime, and 10% have murdered someone in the last month, and they are willing to admit this to a cold-calling phone researcher, your counter argument will make more sense.

    Jerry

  70. Re:Negative Caching (diff from positive cache) by 42.5 · · Score: 1

    Too bad DNS does have the ability to offer different caches for positive vs. negative pools. The the hit rate for positives wouldn't be affected by negatives.

    DBs allow a DBA to define different memory areas for different tables/structures/etc so why not DNS?

    --
    Non illegemati carborundum est!
  71. Correction: this is not a problem with the DNS by ttul · · Score: 1

    Spammers are not "up-ending" the DNS, they're simply causing poorly designed anti spam systems to consume inordinate resources as a result of their naive assumption that DNS lookups don't need to be managed intelligently. I'm sure this is something that the anti spam vendors are looking at, but probably not something that will be fixed soon, since it's really quite a difficult problem to address.

    Interestingly enough the same technique can be used against spammers. Take a look at what these guys are doing -- the site's content a bit slim but it looks like they're using a kind of DNS aliasing that could really hurt spammers in much the same way. I imagine techniques like these that operate at the DNS level are the next step in the evolution of anti spam.

  72. Re:Negative Caching (diff from positive cache) by whoever57 · · Score: 1
    Too bad DNS does have the ability to offer different caches for positive vs. negative pools. The the hit rate for positives wouldn't be affected by negatives.

    Well, for positive caching at least the cache time is defined by the data received (the TTL), not by the nameserver (or at least that's the way the RFC is written -- some ISP's run broken nameservers that ignore TTLs)

    For negative caching, I think is is the same, there is a TTL for ".com" (and other TLDs) and this TTL defines how long the negative hits should be cached.

    --
    The real "Libtards" are the Libertarians!
  73. The article is wrong. by mortonda · · Score: 3, Informative

    The article is just wrong, and there's a feedback post on the same page that explains why very well. (Although, what's with the stupid formatting?)

  74. You're missing the effect... by Anonymous Coward · · Score: 0

    Remove the load of the estimated 80% spam that ALL mail servers currently deal with, replace it with authentication for email claiming to be from said server... Something tells me there isn't going to be a performance loss.

    1. Re:You're missing the effect... by AndroidCat · · Score: 1

      You only remove the 80% of the spam when the spammers give up sending it. Previously they've just cranked the engines of spam up a few more notches. I'm not saying it won't eventually stop them, just that you'd better be prepared for a fight.

      --
      One line blog. I hear that they're called Twitters now.
  75. Re:A bounty... by BawbBitchen · · Score: 1

    The fact of the matter is that the American correction system is quite nice to people. Things would change if we had public floggings and hung murders, rapist and child pornographers. Murder is only a 7-10 year sentence around here. We give our criminals cable TV! Prison should be like military boot camp. Hard physical labor, no free time, and because I do believe in paying your debt and reform, schooling to teach and educate so the person can get a job and make a contribution to the society they have harmed. BTW, I am not in anyway a 1) Republican, 2) Born-again Christian. I just think it is time we start forcing people to be RESPONSIBLE for their actions. All this touching feeling shit is killing me. Oh, there should be less stupid laws - the drug and prostitution laws need to. Legalize and regulate.

    And spammer should still be shot. If you kill a few I will bet spamming would stop.

  76. Not URLs in Email Content! by spookyfluke · · Score: 0

    The DNS queries are to verify the domain that sent the message is valid. It's not a system to query every URL that shows up in the content of the email.

    --
    you.bases.each{|base|base.are_belong_to=us}
  77. Re:Anti-Spam Legislation Is Only Effective Solutio by Anonymous Coward · · Score: 0

    who removed your sense of humour? they did a bang-up job

  78. Re:A bounty... by Blitzenn · · Score: 1

    You completely missed the point. It isn't a matter of ANY penalty being effective, it's a matter of removing the causes. The spammer makes money, that is the root of the problem. Why does he make money? How do I stop SPAM from making money. hmm. ponder that and you may find the answer. Making prison harsher is not going to solve anything. making prison the answer OBVIOUSLY doesn't solve anything. Removing a person from society doesn't fix the problem with the society to begin with. It's a fantasy that taking away the person who took advantage of a problem fixes the problem is downright moronic! Fix the damned problem and the issue is closed. Gosh, at what point are we going to start applying common sense to these type of issues and stop throwing incarceration and penalties at them. It's so stupid and the greater majority of the people can't see it. I feel like we live in the stone ages, but we just got a bunch of cool stuff to get us through it. God forbid we should change anything because we know a better way, we have always done it this way whether it works or not. It's so frustrating. I am not opposed to make laws and regulating, but the 'punishment' for breaking those laws is simply ridiculous. Once we see that we have an issue. Pass the laws in a necessary fashion to remove the cause of the problem, not to remove the effect of the problem. that's trying to backend the issue and that never works.

  79. Misleading description by bigberk · · Score: 1

    The blacklists we have been using for a long time -- SPEWS, Spamhaus, CBL, SORBS do work on DNS and they continue to work fine whether or not the spammer registers a domain after the spamrun. These blacklists work by looking up the connecting IP address that is sending mail, and that IP address can not be forged in TCP/IP. Whether or not the mail body contains IPs or domain names that are invalid or not, forged, etc is an auxiliary issue. Most spam can be blocked at the entrance point, the mail transfer (SMTP).

  80. OT: Scummy people by Just+Some+Guy · · Score: 1
    just like those orphan traders at tsunami disaster areas... i really would like to have a chance to confront these disguisting people and try to make sense of their thought process...

    This isn't a popular view these days, but it's always been generally accepted that their are bad people. Not people who are inwardly good but act poorly, but genuinely bad people. One relatively modern name giving to such people is "sociopaths". They have no regard for other people, if they even see other people as fellow human beings at all.

    These people have always existed, and to them the idea of whether a certain profitable action is moral is moot, because morality doesn't really have a place in their worldview. As long as their are sociopaths (or Bad People), there will be spam, orphan traders, and personal injury lawyers. Do not try to understand their thought process. First, it's usually amazingly simple ("What course of action will benefit me the most?") and you'll get all tied up in trying to find a hidden meaning in their rather straightforward behavior. Second, you really don't want to go there - seriously.

    --
    Dewey, what part of this looks like authorities should be involved?
    1. Re:OT: Scummy people by Anonymous Coward · · Score: 0
      it's usually amazingly simple ("What course of action will benefit me the most?")
      The problem I have with that, is that often, not being totally bad is the course of action that will benefit you most. Pissing everyone off tends to come back and bite one in the ass. What I mean is, a sociopath can act like a very nice person, even if they're not. So if they don't, what's really wrong with them is that they're not just bad -- they're stupid too.
    2. Re:OT: Scummy people by Just+Some+Guy · · Score: 1

      In CompSci terms, a greedy algorithm is often not the optimal solution to a problem - you and I are in complete agreement there. Most of the "bad people" I've known, though, were so convinced of their own inherent and obvious superiority that it simply never occurred to them that the sub-humans around them could ever catch them in their lies or otherwise hold them accountable.

      --
      Dewey, what part of this looks like authorities should be involved?
  81. Re:A bounty... by Anonymous Coward · · Score: 0

    Luckily people like you aren't in power and there are checks and balances to ensure people like you cannot use your power to the extent you would.

    I detest anyone who attempts to tell me how to behave and that there is one way that people should be socialized into society. You'll get a gun in your face before you force me to conform to your methods.

  82. Re:There will never be need.... by Anonymous Coward · · Score: 0

    to abandon email due to spam. Those worst hit own email servers but cant or aren't willing to invest in antispam technology.

    By: Sir Old News
    W/S: recycledbits.job

  83. Re:Crippling DNS? How much does DNS suck? by MavEtJu · · Score: 1

    Then why is the article suggesting that spam is bringing DNS to it's knees and the sky is falling?

    Because it's the spam which caused us to implement spam-filters and doing all kind of nifty technical solutions against a (anti)social problem.

    --
    bash$ :(){ :|:&};:
  84. Re:Crippling DNS? How much does DNS suck? by Dahan · · Score: 1
    IPv6 uses a different DNS system, dopey.

    GO Away, Troll

  85. Re:A bounty... by katenysh · · Score: 0, Offtopic

    I'm sorry but I do not think that making prison something like a Nazi work camp will lower crime. Most people do not think that they will be caught when committing a crime. If you want something to rehabilitate criminals do not send them to "criminal school". Instead it might be a nice idea to legalize LSD-imprinting reversal research started by Timothy Leary. He had an over 80% success rate before the US government stepped in and stopped his criminal actions....

    --
    Think for yourself, question authority
  86. Re:Crippling DNS? How much does DNS suck? by tabrisnet · · Score: 1

    And you have missed the point as well. Even assuming that the negative result is cached, that is still per cache. So although you DO reduce the load somewhat (tho chances are, the negative is being cached already) you are forgetting breadth. You still have this spam sent to 10million email addrs, and to say 100,000 domains.

    Say there is an average of 2 domains per MX server (number pulled out of ass. however it is probably reasonable), you now have 50,000 requests. per mailing.

    And these requests will likely all be made over a one hour, mebbe two hour period. Which doesn't sound so bad. But now consider the following.
    Now add in the fact that there are, say, 1000 of these emails sent out with different domains. You now have 50million requests.

    Which probably will have a spread of (for example, this is another number pulled out of ass) maybe 6 hours.

    True, this might not be so bad, but it certainly is not good. and you certainly didn't remember this problem. Depth isn't our only concern, but also breadth.

  87. Re:Dammit by Anonymous Coward · · Score: 0

    I'm going to hate myself for asking this but how can you murder someone more than once? You'd think once would be enough.

  88. (l)users??? Perhaps that is you. by Saeed+al-Sahaf · · Score: 1, Offtopic

    I think it's really sad to refer to Users as Losers. It's very disrespectful and ignores that fact that just because you have to use a computer does not mean that you should have to be a computer professional and monitor Slashdot 24/7.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
    1. Re:(l)users??? Perhaps that is you. by Anonymous Coward · · Score: 0

      You've obviously never worked in a helpdesk situation then... If you had you'd realise that there is something about computers that turns even normally smart people into complete blubbering retards

    2. Re:(l)users??? Perhaps that is you. by tewmten · · Score: 0, Funny

      Oh you've got it all wrong, "luser" is just another word for "local user", not "loser".
      You see, admins don't want to waste precious typing time so they just type "luser" instead.

    3. Re:(l)users??? Perhaps that is you. by QuickFox · · Score: 1

      If you work at a helpdesk, those users are the reason you have a job. They are the ones who pay your rent and food.

      From the viewpoint of an architect or a lawyer, you and I look just as foolish, if we start asking technical questions about their fields. Believe me, I've had a few different jobs. Almost always people from the outside look foolish.

      Of course I do agree that users can drive you raving mad. The only solution is to be extremely, extremely patient, breathe deeply, smile, try to see it from the user's viewpoint, and always remember that the person you're talking to at the moment is paying your bills.

      And get out before it drives you totally mad.

      --
      Terrorists can't threaten a country's freedom and democracy. Only lawmakers and voters can do that.
  89. Could you explain that? by pjc50 · · Score: 1

    Why would that take more, and what's wrong with the design?

  90. Re:Anti-Spam Legislation Is Only Effective Solutio by Anonymous Coward · · Score: 0

    How about finding indivudal spammers and their homes and attaching, with a dagger, to their door, a recently dead chicken and a suitable, neatly handwritten message?

    C'mon: They gotta live somewhere.

  91. Re:False positive when dropping invalid link by jacksonj04 · · Score: 1

    Surely as long as the mailserver can see internal DNS the domain would still resolve though?

    --
    How many people can read hex if only you and dead people can read hex?
  92. Re:Dammit by irc.goatse.cx+troll · · Score: 1

    "hile I do agree with you, its not like it would be that hard to track these people down. The very core nature of spamming demands some level of locatability. After all, they're selling products. Just subpoena the names of the people that the penis enlargement pill wholesaler has hired to advertise for them (force their cooperation with the threat of an accessory charge), and then prosecute the spammers into the dirt."

    Prosecute them with what? Commiting legal mail based advertising?

    Prosecuting them once caught is why we want it illegal.

    --
    Pain lasts, kid. Its how you know you're alive. Sometimes I think this growing up thing is just pain management-TheMaxx
  93. Re:Anti-Spam Legislation Is Only Effective Solutio by lcsjk · · Score: 1

    'Funny that you would read it that way!

  94. Re:False positive when dropping invalid link by uberdave · · Score: 1

    And, praytell, how does your mail server see my internal DNS server?

  95. Simpler spam solution... by Anonymous Coward · · Score: 0

    So much legislation focuses on the spammers, but it seems to me that's a pointless target. Spammers spam because of the response they get. It means there's a small group of idiots out there that respond to the spam and make it all worthwhile. Why not make it illegal to respond to SPAM e-mail? A misdemeanor, perhaps.

    Think of a prostitution sting. Your ISP is getting tired of SPAM, it simply sets up a filter that redirects the URLs in a randome percentage of identified SPAMs (which are passed on to the recipient) to the authorities who then fine / publish names of the "Johns". Certainly, this tactic hasn't gotten rid of prostitution, but for spam it ought to work (because proactively seeking out the things in a SPAM and sellikng the things would still be legal, just not the response to the spam).

    In the US, there's plenty of precedent for such legislation...

  96. Sitefinder? by myov · · Score: 1

    I'd almost like to see sitefinder return, simply to be /.'ed. Network Solutions deserves to drop off the face of the earth.

    --
    I use Macs to up my productivity, so up yours Microsoft!
  97. Talkback to TFA says article is wrong. by bturnip · · Score: 1

    After I did a quick RTFA, some guy claiming to be behind www.dnsstuff.com. The commenter is basically saying the article got it dead wrong. link [eweek.com]

  98. Re:Crippling DNS? How much does DNS suck? by TheRaven64 · · Score: 1

    No they don't. In the example given, the DNS cache performing the query will not need to query the root servers since it almost certainly has the address of the authoritative server for the com. top level domain cached. It will query this server, which will return NXDOMAIN. The only time the top root servers need to be queried is if the top level component of the domain (com, org, uk, etc) doesn't exist or if the cached SOA record for that domain has exceeded its TTL.

    --
    I am TheRaven on Soylent News
  99. Re:Anti-Spam Legislation Is Only Effective Solutio by Blitzenn · · Score: 1

    I agree spam is a large nusiance and a time and money waster for our economy, but prison time for the offense seems quite extreme to me. Stealing your television, raping your wife, killing your kids, those are prison offenses. I think we are going overboard.

  100. Just Greylist! by emil · · Score: 2, Informative

    OpenBSD's spamd will initially reject all mail from previously unknown sources. It will only permit access to sendmail after an attempt at redelivery. This has brought my spam load down to about zero.

    Unless a spammer using the above trick attempted redelivery (which is unlikely), it would not cause a DNS flood.

    spamd is only one of a great many reasons to consider OpenBSD on your critical servers.

    1. Re:Just Greylist! by Greyfox · · Score: 2, Informative
      There's a similar daemon out there called postgrey which does pretty much the same thing. If you run Debian and your own mail server, you can just apt-get install postgrey.

      It doesn't work 100% of the time but betweem that and SPF checking, my spam load has been reduced to 3 or 4 a month. I could ban hotmail and yahoo and that'd pretty much eliminate spam from my mailbox completely.

      They'll figure this trick out eventually though, then I'll have to come up with something else.

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  101. The ONLY way to stop spammers by Anonymous Coward · · Score: 0

    Hot. Pokers. In. The. Eyes.

  102. CmdrRetard by ubikkibu · · Score: 1

    Explain, please, how the word Spammers is possessive in the title?

  103. SPF or bust by Twillerror · · Score: 1

    All this reverse crap means nothing.

    We need to push SPF or something else forward so people are required to do work in order to send an email.

    This makes the from address mean something, and harder to spoof.

    Now spammers can register a valid email server, but then they have a place to be tracked to. If they are offshore we could do something about that.

    Speaking of which, being able to categorize my mail by country would help alot.

    Is there a standard for the mail servers to give their clients IP information about the server that delivered the message? This would help alot.

  104. Re:False positive when dropping invalid link by jacksonj04 · · Score: 1

    It's not my mailserver which does the filtering. It should only be the terminating server which does any form of filtering, ergo the one on the corporate network.

    --
    How many people can read hex if only you and dead people can read hex?
  105. Re:Crippling DNS? How much does DNS suck? by Anonymous Coward · · Score: 0

    1. Recieve spam with unregistered domain name
    2. Register domain name *before* the spammer does
    3. ????
    4. Profit

  106. Re:Crippling DNS? How much does DNS suck? by CrackerJackz · · Score: 1

    Also part of the problem is that if you send out a few million spams with links to www.stratjaktsmadeupdomainname.com most of the virus filters that this will pass thru will do a lookup on the domain, since it does not exist it wont be listed in any bind caches for you local dns server, they then have to query their parent servers (all the way back to the root servers)

    say your typical poorly written spam program checks all the links (and for easy math you have 10 links in your spam)

    10,000,000 emails x 10 links = 100,000,000 dns lookups ... plus a few more for the people that click on the emails... since it will have to try and load the images in the email, etc.

    Its a nasty problem, since the first 100,000,000 hits would occure within a short period of time.

    In short DNS can handle fat-fingered mistakes, just not on this scale...

  107. No big deal by SCHecklerX · · Score: 1
    You can still reject most spam. I found that my spamhaus filters weren't getting called much because before that check (using mimedefang milter) I was:
    1. making sure the helo had a . in it. (It should be a fqdn or IP address...spammers love to use a single word instead)
    2. rejecting if they claim that their server is my server in their helo
    3. rejecting if helo claims that their address is rfc1918 address

    Those rules don't get hit much (really not at all), because I moved them below my spamhaus check. But if messages get through that check now, I'm sure that those reject rules will catch most of the cruft.

    And of course spamassassin then analyzes what gets through all of that.

    1. Re:No big deal by DarkKnightRadick · · Score: 1

      I've not had any problems just using SpamAssassin at the inbox. All spam gets caught, very few false-positives.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
    2. Re:No big deal by SCHecklerX · · Score: 1

      True, but you have to accept and then analyze all of that. That takes bandwidth and CPU cycles. Probably not a big deal for your home server, but in a corporate environment that receives 50-100,000 messages a day, you want to reject as much crap as possible. This also stops the mail from having to be analyzed by antivirus software (again, a big deal in a corporate environment), which eats up cpu.

    3. Re:No big deal by DarkKnightRadick · · Score: 1

      This is true, and while I don't get 50K messages a day, I probably get around 2-3K messages a day, if not more (I'm on several high volume mailing lists). While SA is doing the job after the mail is accepted, I don't trust it enough to reject mail before it's accepted. The very few false-positives keep it like that. I don't know of any spam-filter that is 100% free of false-positives and even false-negatives.

      --
      "There is a way that seems right to a man, but its end is the way of death." Proverbs 16:25 (NKJV)
  108. Point taken.. however.. by Anonymous Coward · · Score: 0

    This would be a fairly definitive measure... Instead of guessing the veracity of the content of a message, we would instead verify the physical origin of the message. While I concede that there will almost certainly be some sort of attempt at circumvention, it's a hell of a lot more difficult to get around then your average bayesian filter (which is the best thing going next to black/whitelists IMO).

    We're talking about a fundamentally different approach here, treating the cause (unsecure, unverified protocol) instead of the symptom (spammers taking advantage of said protocol).

    1. Re:Point taken.. however.. by AndroidCat · · Score: 1
      There's still a few reefs to steer past. Is the verification process expensive in CPU and/or bandwidth? Who certifies the verfication, someone central like Network Solutions (we trust them with .com and .net after all), ICANN, Verisign, Diebold or Microsoft? Can anyone certify keys, and if so, can you trust them? For spammer pink money, ISPs have hopped spammers from IP block to IP block and other games. (That's part of the reason for aggressive blockslists like SPEWS.) Will certifiers take spammer money, and then what? Will they yank verification for spammers? Will verification be by ISP or by email address? Will I have to buy a certification from someone? Can the spammer buy a whole stack of throwaway certifications for cheep? If you want to track down the spammer who's been sending verified spam, do you need a court order to get ISPs to divulge name and address? (And is it a real name and address?)

      There's a lot of practical details that have to be checked off before this could fly.

      --
      One line blog. I hear that they're called Twitters now.
  109. Re:A bounty... by BawbBitchen · · Score: 1

    I understand your point. I just do not always agree with it. People are dumb, and some will buy stuff from spammers. So do we pass a law to make that a 10-15 year sentence? How do we fix the root cause of spam? Get rid of profit or money. If you want to make someone think twice about doing something you need to make the punishment not work the reward.

    As to removing the cause, sure make drugs legal, I am in favor of that. That would solve a few issues. But at the end of the day, there will always be people that want more then they have. You cannot fix that. Communisim is a great idea except is it 100% against human nature and does not work. Tell me how do you fix the root cause of bank robbery? Or someone that likes to rape? You cannot.

    We need to teach responsiblity for ones actions - and the punshment for not being responsible should be harsh.

    If you can solve the problems like you talked about you are a smarter man they everyone else that has been trying since the dawn of time. Me, I am just trying to be realistic.

  110. Re:Crippling DNS? How much does DNS suck? by Sloppy · · Score: 1
    If you did cache "that doesn't exist", you would minimize traffic, but break in the case where a site is legitimately advertised before existing (by a stupid person who hits 'send' before hitting 'register me a domain')
    I don't see why anyone should care about that. No one should expect a brand new domain name to become immediately visible.
    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  111. Re:Anti-Spam Legislation Is Only Effective Solutio by Moofie · · Score: 1

    I understand that in China, prisoners' families are billed for the bullets used to execute them.

    --
    Why yes, I AM a rocket scientist!
  112. Re:A bounty... by BawbBitchen · · Score: 1

    Hum, don't remeber telling you how to behave, except for maybe asking for you to be responsible for you actions. If you are not willing to do that then I hope someone cuts your life short before you hurt someone else. I am a compete libertarian. You can do whatever the fuck you want as long as it does not mess with my right to do whatever the hell I want.

    The key to a peacefull world is personal responsiblity on everyone part.

  113. Re:False positive when dropping invalid link by ermon · · Score: 1

    I think you missed the point.

    Say we both work for some company X, and we use a server that is within the firewall and called foo.local

    I am at home, and the e-mail I read at home is a@isp and not a@corporate.

    You want to send me an urgent message to log onto the company VPN and check out something on foo.local, but I have to send it to a@isp.

    The @isp mail server can't resolve foo.local and will therefore drop the message, meaning I will never get your message.

    There are times when you want to send e-mail about internal domains to e-mail addresses residing outside of the domain, where the MX server at the end of the line cannot resolve the internal domain, but the person reading the e-mail can (through access to the internal servers).

  114. Even worse by phorm · · Score: 1

    Then it would fark any email in which somebody mistyped a URL, or if it interprets something as a url and it comes up invalid.

    Could be as bad as if I wrote "I'll meet you 8pm@work." It might interpret the 8pm@work as an email address and scan for valid domain. Or I might just have a typo such as http://www.slahsdot.org which would also bork an email. Perhaps even a domain that isn't in DNS (one specific though a local shared HOSTS file)

    Remember, antispam is not only designed to crapfilter out spam, it should be priority to allowing legitimate emails.

    1. Re:Even worse by Anonymous Coward · · Score: 0

      No crap, I'm particularly annoyed at a particular group of UK ISPs which have taken it upon themselves to refuse if the sending mail server's name includes an underscore in the name.

      So you're going to reject legitimate email by anally interpreting an RFC, because some spammer, somewhere, used an underscore in their server name? A quick check of all the spam that's hit my mail accounts shows zero underscores in any of the mail headers - and my server accepts underscores - so the problem isn't widespread.

      Gotta love screwed up priorities.

  115. Close, but not quite... by msauve · · Score: 0

    you need to kill anyone who buys any product or service advertised with spam. Without a market, spammers are out of business.

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
  116. Editors' slacking off by Glamdrlng · · Score: 1

    I know the, flamebait mods' get thrown; around when slash:dot users' give the editors' crap but c'mon guys'! Do your freakin jobs'!(_

    --

    Yes, my only tool is a hammer. And you're starting to look like a nail.
  117. the gratiutous' apostrophes' award goes' to:... by snorklewacker · · Score: 1, Funny

    ... the slashdot editors'!

    --
    I am no longer wasting my time with slashdot
  118. What mail server... by misleb · · Score: 1

    What mail server even allows mail from unknown/unregistered domains? Isn't that, like, one of the most basic anti-UCE checks? I hope spammers employ this tactic because I know my mail gateways will drop all of the spam.

    -matthew

    --
    "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
  119. Up-end of spammers? by Anonymous Coward · · Score: 0

    I think it has something to do with finding the top halves of the people sending me all those Cialis ads.

  120. Blog spam, too by kitzilla · · Score: 1

    Been seeing something like this for a while in my blog's comment spam: an apparently innocuous note with a URL that looks like the author's name (maybe something like "http://joeshmoe.com"). The URLs go nowhere. I'm sure they get redirected to pr0n and veye-ah-gra sites a few days after posting.

    --
    This is my post. There are many others like it. If you don't like what you read here, go try one of the others.
  121. Re:Anti-Spam Legislation Is Only Effective Solutio by amuro98 · · Score: 1

    When you've got companies spending millions of dollars a year on extra equipment to deal with the spam problem, you've gone beyond being a "large nuisance."

    And this is WITH the horribly lenient joke law that is "CAN-SPAM".

  122. Re:Anti-Spam Legislation Is Only Effective Solutio by tdhillman · · Score: 1

    " Until they pass a law that makes it completely legal to kill spammers, the spam problem will not go away."

    Ah no- that would only make it worse= the ones left alive would know that you were still there to annoy.

    --
    befuddled (noun) 1. Unable to create a pithy sig
  123. Re:Anti-Spam Legislation Is Only Effective Solutio by The+Ultimate+Fartkno · · Score: 1

    Bollocks. Find individual spammers and attach them, with a dagger, to a chicken. Then slip a note into the spammer's mailbox indicating where where the family can pick up the remains along with their last free meal.

  124. It does and does not by Anonymous Coward · · Score: 0

    All depends on the DNS server. Note most DNS servers have set able limits on valid and invalid DNS cache. So spamming a DNS cache correctly setup spamming random crap does not work because it does not effect the number of vaild sites stored in the DNS server just fills the invalid section. Default on a lot is 0 for invalid but it can be set higher note with users using spam filter programs it is a good idea to set this higher due to caused load from doing not required lookups.

  125. Re:A bounty... by Anonymous Coward · · Score: 0

    Yes, let's not criminalize spamming, because clearly organized crime enforcement over the past few decades hasn't stopped organized crime.

    Oh crap, I forgot, organized crime has been forced so far into a corner that the average city dweller's only interaction with an organized crime figure involves a TV. Well, that or eBay.

    Why not simply enact appropriate fines & terms based on the negative impact a person's actions have on society

    If you simply put a new system in place, the spammers will find a end-run around the new system. So we'll just keep rolling out new system after new system until they give up?

    These antisocial types are always going to exist. They will always find a way to scam people out of money. All you can do is make them live under a rock because their actions carry real world penalties.

    They won't be buying nuclear bunkers from the government and running servers from them. They won't be buying large houses in ritzy sections of town and putting servers in their basement. They'll be forced to maintain a low profile.

  126. bayesian, anyone? by SanityInAnarchy · · Score: 1

    Hey, ISPs! Download dspam!

    --
    Don't thank God, thank a doctor!
  127. Re:False positive when dropping invalid link by sepluv · · Score: 1
    This would be true if the domain name was
    wiki.local
    but it is
    wiki.local.
    and
    .
    indicates the Internet root servers. For instance, the full domain name of slashdot is
    slashdot.org.
    but assuming you do not have local domains set up
    slashdot.org
    will redirect to
    slashdot.org.
    --
    Joe Llywelyn Griffith Blakesley
    [This post is in the public domain (copyright-free) unless otherwise stated]
  128. I'm going to say this once.. spammers, fuck you by Anonymous Coward · · Score: 0

    i mean that personally, fuck you. if you've spammed once, or many times i already dislike you as a person.

  129. Readable version by Anonymous Coward · · Score: 0
  130. Re:Dammit by johnbeat · · Score: 1

    Try a different parser...

    To reasonably compare drug laws to murder laws, as the previous poster did, 30% of the people in the United States would have to have committed at least one murder in their lives. 10% of the people in the United States would have to have committed at least one murder in the last month. And they would have to care so little about breaking the laws against murder that they'd be willing to let a federal researcher (NIDA, in the case of drug laws) know.

    Unless and until those numbers are true, the comparison to murder laws makes no sense.

    Jerry

  131. Re:False positive when dropping invalid link by statusbar · · Score: 1

    With Rendezvous on macinosh, it normally comes up with names such as 'jeffs-computer.local.' with the extra dot, and it works. What is the specific standard for HTTP URL's and the extra dot?

    --jeff++

    --
    ipv6 is my vpn
  132. Sophos PureMessage not vulnerable by Anonymous Coward · · Score: 0

    Sophos PureMessage is not (and never was) vulnerable to this trick. That is because it works off URI's rather than IP addresses.

  133. Alert! Astroturfing! by Anonymous Coward · · Score: 0

    The above post is by Ken Simpson (aka President Simpson) of mailchannels.com

    http://mailchannels.blogspot.com/

  134. Re:Dammit by ozmanjusri · · Score: 1

    Just subpoena the names of the people that the penis enlargement pill wholesaler has hired to advertise for them (force their cooperation with the threat of an accessory charge), and then prosecute the spammers into the dirt.

    No, that's wrong. What you need is to follow the money trail to the people who are benefiting from the spam. That is, those who commission it.

    If you make spamming a misdemeanour offence, but receiving income from the activities of spammers a criminal offence, just as receiving stolen goods warrants a more severe punishment than theft, then you will begin to have an effect.

    It is not the idiots who buy from spammers you have to control. It is not the senders of bulk email you have to control (although I'd like to see some serious jail time for them, sending spam is too easy, and there will always be more who'll do it). It is the companies that pay for the spam and which derive the most benefit from the spam that must be charged and severely punished.

    --
    "I've got more toys than Teruhisa Kitahara."
  135. Re:Anti-Spam Legislation Is Only Effective Solutio by smartdreamer · · Score: 1

    SPAM should be considered crime against humanity. But then, what do you get for this kind of crime? Some media coverage at most.

  136. Re:False positive when dropping invalid link by sepluv · · Score: 1
    No idea what Rendevouz is, but if you don't believe me try setting up a local domain and testing it in your WWW browser. An FQDN (fully qualified domain name) (i.e.: absolute non-relative domain name) must be a rooted domain name (i.e.: end with the domain name of the root server which is "."). An FQDN can only refer to one server in the world.
    What is the specific standard for HTTP URL's and the extra dot?
    There is no specific standard for HTTP URIs. However the dot rule I give above is in the RFCs for HTTP 1.1, URI syntax, the DNS, and probably many others.
    --
    Joe Llywelyn Griffith Blakesley
    [This post is in the public domain (copyright-free) unless otherwise stated]
  137. Re:False positive when dropping invalid link by statusbar · · Score: 1
    I understand what you are saying, but Rendezvous - aka ZeroConf allows me to do the following:

    Last login: Thu Jan 13 20:48:21 on ttyp4
    Welcome to Darwin!
    You have mail.
    $ ping clplap.local.
    PING clplap.local (192.168.0.96): 56 data bytes
    64 bytes from 192.168.0.96: icmp_seq=0 ttl=64 time=0.255 ms
    $ links http://clplap.local./~jeffk/


    My original point is that urls with local intranet domains in this form would break mail scanners that checked for valid urls in emails. Hell, even when I email a friend something like: "Your router admin page is accessible via http://192.168.32.1/ " would end up getting filtered as spam!


    --jeff++

    --
    ipv6 is my vpn
  138. Spammers registering domain after spamming by Anonymous Coward · · Score: 0

    But what happens if someone who sees the spam happens to register the domain first - the spammer would be SOL.

  139. Don't astroturf just say its yer site & come c by Anonymous Coward · · Score: 0

    Thanks for the alert by AC about the astroturfing.

    Ken don't be an ass, you have a couple of interesting FOSS things on your site - but it looks like the other stuff is smoke and mirrors that businesses will find awesome but techies would see through.

    What really is this DNS/mail voodoo that you are peddling?

  140. Re:A bounty... by Blitzenn · · Score: 1

    I don't proposed removing all jail terms for all crimes, but I just feel that the penalty is stiff only because people irritated by a high level of inconvienience. Granted there are cases where it is justified, but we already have laws that can handle those instances. If irritation is a jailable offense, I don't think you would ever see anyone take a job in the airline industry. We seem to have been running down a road where we need to severely punish people for irritating other people. Take for instance the Road Rage law in New York. If the anger results in an accident or a fatality, I think it may be justified, but people are being charged for getting upset over being issued a speeding ticket. Talk back to the cop and you can be charged with rage. It fits the context of the law as it is written. At what point do we draw a line on the nonsense? I agree with you stance on responsibility and feel strongly that it supports my point more than yours. If people took responsibility for their actions as they should, then we should have to have any laws at all. Perhaps if we made the punishment more reasonably fit the nature of the crime, we could avoi a lot of the criminal element that we breed with our current system.

    As far as someone being smarter and finding an answer. That will not work in our society either. Smart people are looked at suspiciously. They have the ability to take advantage of us and we can't see it until it's all over. We don't trust them and therefore we will not listen to any 'plan' they might have to correct the same system that we use to keep them in check. I think there are a lot of smart people out there who understand the problem have better solutions, but understand the high cost we have placed on speaking out. They are smart and will do the smart thing, stay quiet. We are building a system of failure. We have to change that course somewhere along the way, or we will all fail as a whole.

  141. Re:Two words: RICO Prosecution by swb · · Score: 1

    We have a supersized prison population because:

    * We can't see the light on the victimless crime of drug consumption and insist on sending people growing pot to prison for 20 years.

    * "Tough on crime" legislators have implemented such corrections gems as "3 strikes and you're out" so that a shoplifter who takes 3 items from 3 departments in a store gets nailed with 3 counts of shoplifting and goes to prison for life as a career criminal.

    * The same legislators have also implemented manditory sentencing (which the Supreme Court just modified), requiring the above pot grower's wife to be considered a co-conspirator and sent to jail for 20 years, whether she knew he was growing it or not.

    NONE Of this makes punishing the organized fraud known as spam some kind of exercise in penalty escalation. Computer hijacking, relay hijacking, falsifying information deceptive advertising, ineffective products, fake products, undelivered products -- at what point is punishing people for stealing wrong? Because someone can sit in their basement and do it on a computer doesn't make it any less impactful or less deserving of punishment.

    Criminal punishments involving prison time have to be meted out at least initially so that the people involved won't just chalk up civil fines as the price of doing business and keep doing it.

  142. Re:Don't astroturf just say its yer site & com by ttul · · Score: 1

    You're right -- this was astroturfing. Thanks for keeping me honest and I apologize to the greater Slashdot community for having done so.

    What we have built is an automated system for creating and managing domain-based email aliases. What does "domain-based" mean? Basically this:

    Regular Address: username@domain.com
    Domain-based Alias: username@alias.domain.com ... where the alias part is a pseudorandom sequence that acts as a shared secret between one or more parties who wish to communicate with each other.

    Because the MX entry for the alias subdomain is consulted each time a message is delivered, it's possible to have a different MX entry for different aliases. In this way, mail traffic can be routed differently at the network level depending on who it originates from.

    The use case that has received the most traction so far is to separate customer traffic so that it can be treated more kindly by the spam filter -- or bypass the filter altogether. In this way, you never lose a message from a customer (i.e. no false positives).

    We are in the middle of a site update that will explain all. If you're interested, visit http://www.mailchannels.com in a few days' time or watch for a press release.

    BTW -- the Apache::SMTP bits are a genuinely cool innovation courtesy of our CTO Will Whittaker. Look out for some articles showing up soon on this topic.

    Regards,
    Ken

    CEO, MailChannels (and convicted Astroturfer)

  143. Re:Two words: RICO Prosecution by Blitzenn · · Score: 1

    Amen! Your last point, although valid, lacks any historical presidence of ever taking place. We have rarely ever decreased to penalty for a 'crime' that is on the books, (except for prohibition). It would be wonderful if we had a system that allowed us to reduce a penalty where it was deemed as reasonable, but the basis of our politcal system voids that as a possiblity. Politicians, as a rule, will not lobby their peers for reductions because it always becomes politcal fodder for the re-election process. The sound bite era has made that problem even worse, as it is easy to point a finger in 30 seconds, damned hard to explain why in that same amount of time, and secondly it puts that politician in an imediate defensive position, just where they don't want to be.

  144. Re:Two words: RICO Prosecution by swb · · Score: 1

    Amen! Your last point, although valid, lacks any historical presidence of ever taking place. We have rarely ever decreased to penalty for a 'crime' that is on the books, (except for prohibition).

    This really isn't true. Historically cattle rustling and horse stealing were capital offenses. I'd be surprised if a first time cattle rustler even went to jail for more than six months, the same with horse stealing.

    Legislators even saw the light to some extent with marijuana decriminalization in the 1970s -- what was once a guaranteed jail sentence for small amounts of pot is now a traffic-ticket offense. Of course this is counterbalanced with the extreme federal sentencing for other aspects of drug posession.

    I think what we're seeing today is the beginning of the end of the "tough on crime" initiatives that began in the early 80s as an antitode for the increases in crime in the late 70s. Historically we began "reforming" instead of "punishing" criminals in the 1950s and by the mid-70s the demographics of the baby boom produced a lot of crime and a lot of public outrage at the "revolving door" of the prison system.

    By the early 80s, polticians were eagerly lining up to vote on measures that made life without parole a common punishment. When the legislators discovered that judicial sentencing discretion wasn't implementing this mandate, they (temporarily, at least) eliminated this as well and we got to where we are now.

    I think that the economic pressures of this are starting to show (if not the lack of rationality). When you jail 1 in 20(?) people, it costs money. A lot of money. Unfortunately we probably still aren't smart enough to figure out that some people SHOULD be jailed for a long time for both retribution and public safety (robbery, rape, assault, murder, kidnapping) and some people really shouldn't (most drug posession charges).

    We'll either figure out that permanently jailing a significant portion of the population is at the very least economically untenable or we'll use terrorism and the war on $arbitrary_social_paranoia to just continue sliding into a police state.

  145. Re:A bounty... by Trillan · · Score: 1

    I was just in a country that executed rapists. Let me tell you, it doesn't work very well. Basically, it turns every case of attempted rape or rape into a murder because it is so important to the rapist not to be caught.

    While I was there, a man nabbed a little girl (10 years old) just down the street from me. She screamed for help, so he stabbed her five times in the chest and ran. Her mother was within earshot, but (obviously) ran to the girl instead of after the man. The little girl died in her mothers arms within seconds, and the man got away.

    Isolated incident? No. I asked -- it happens all the time. They have fewer incidents there, but if a woman is attacked, she can pretty much knows she won't live through the experience.