BLOG

Poisoning Spamtraps

Today’s question comes from Dave in yesterday’s comment section.

I wonder if spammers might submit harvested addresses to big-name companies known to not use confirmed opt-in just to poison what they believe might be spamtraps?

It’s certainly possible that people submit addresses to forms and big-name companies. But I don’t really think that poisons the spamtrap.

Depending on who is running the trap a couple of things can happen.

  1. The big company is added to a blocklist. I have dealt with SBL listings of multiple Fortune 50 companies and a host of other national and international brands. Major brands do get blocked and blocklisted repeatedly for sending to trap addresses. And in many cases they’ve had to implement confirmed opt-in to get delisted. In a couple cases, the solution involved corporate wide changes in database and email address handling.
  2. The trap is part of a scoring system and the other mail from that same sender doesn’t result in blocking. For instance, Yelp has been spamming the address of mine harvested off the blog. Other people have mentioned they’re getting Yelp mail to trap addresses. But the vast majority of Yelp’s mail is legitimate and the recipients want it. At most places they won’t be blocked for mailing to that address.

In all cases, it is the responsibility of the sender to verify they have permission to mail an address. If they fail to do that, and end up adding a spamtrap (or other address that doesn’t belong to the submitter) to their mailing list, they are not sending permission email. For many trap maintainers this is enough evidence to drive an entry on a blocklist. For scoring systems, it’s more about the overall mail stream than one or two trap hits.

I’d say that the only thing that can really poison a trap is revealing it or publicly admitting a particular address is a trap. Even in those cases I’m not really sure that’s true, though. My own experience suggests that many spammers, particularly the affiliate types, are too incompetent to suppress trap addresses. In a couple of instances, I’ve been working with clients who have delivery problems related to their use of affiliates. Often I will dig into my own spam corpus for examples of spam pointing to my company. I do turn over trap addresses to the spammers. They still send those addresses spam.

===

Have a question you want answered? Tweet them to wise_ laura or send them to laura-questions@wordtothewise.com.

 

 

 

Comment:

Your email address will not be published. Required fields are marked *

  • ReturnPath on DMARC+Yahoo

    Over at ReturnPath Christine has an excellent non-technical summary of the DMARC+Yahoo situation, along with some solid recommendations for what actions you might take to avoid the operational problems it can cause.No Comments


  • AOL problems

    Lots of people are reporting ongoing (RTR:GE) messages from AOL today.  This indicates the AOL mail servers are having problems and can't accept mail. This has nothing to do with spam, filtering or malicious email. This is simply their servers aren't functioning as well as they should be and so AOL can't accept all the mail thrown at them. These types of blocks resolve themselves. 1 Comment


  • Fixing discussion lists to work with new Yahoo policy

    Al has some really good advice on how to fix discussion lists to work with the new Yahoo policy. One thing I would add is the suggestion to actually check dmarc records before assuming policy. This will not only mean you're not having to rewrite things that don't need to be rewritten, but it will also mean you won't be caught flat footed if (when?) other free mail providers start publishing p=reject.No Comments


Archives