Aarp
Mainstream spam wrap-up
Over the last week Steve and I have posted about the AARP hiring affiliates to send spam on their behalf: starting with the poorly done email message, moving through the process of identifying the responsible entity and then walking through the details of how we tracked the spammer.
Why spend a week writing about the AARP spamming? I initially posted about the AARP spam because it was such a horrible example of email marketing. Not just that it was spam but it was careless spam. Plus, in a lot of my interactions with marketers, clients and delivery experts I hear a lot about how “real” companies don’t spam, don’t support spam and wouldn’t ever let someone spam on their behalf. This isn’t true, not even a little bit.
The post actually came to the attention of the AARP and someone from their national headquarters commented that it was “just spam” and had nothing to do with AARP. I’ll be honest, I was annoyed with their reaction. I did my homework before calling the AARP out and was convinced this mailing was authorized by them.
Over the next 2 days Steve investigated the spam and reported on his findings. He only documented the full investigation on one of the emails I received (yes, there were multiple emails sent to the same address, most of them coming from different domains owned by the spammer). We did this to document that yes, mainstream companies do hire spammers and that trail can sometimes be tracked. We also wanted to show the lengths spammers and their customers will go to in order to get through filters and spam blocks.
A lot of mainstream groups do support spam and hire other people to send it on their behalf. Many of these same companies expect ISPs to hurry up and let mail through because “we’re a legitimate company” when their mail is blocked.
To be fair, some companies may not initially intend to support spam, but when they see the money rolling in they can’t stop. Some may pay lip service to no-spam policies, but deliberately turn a blind eye to spam advertising their company. Some hire spammers, but with enough distance between themselves and the spammer that they can deny they knew about the spam.
Every company using email for acquisition without actively managing the email program is at risk of spammers being hired on their behalf. There are some things that can be done to lower the risk of spammers being used to send spam, but the spammers are clever and if the payouts are high enough they will spam on your behalf.
There are things a company can do to minimize the chances that an affiliate program will attract spammers. Check back tomorrow for some processes that have proven effective for my clients.
What Happens Next…
or Why All Of This Is Meaningless:
Guest post by Huey Callison
The analysis of the AARP spam was nice, but looking at the Mainsleaze Spammer Playbook, I can make a few educated guesses at what happens next: absolutely nothing of consequence.
AARP, if they acknowledge this publicly (I bet not) has plausible deniability and can say “It wasn’t us, it was an unscrupulous lead-gen contractor”. They probably send a strongly-worded letter to SureClick that says “Don’t do that again”.
SureClick, if they acknowledge this publicly (I bet not) has plausible deniability and can say ‘It wasn’t us, it was an unscrupulous affiliate”. They probably send a strongly-worded letter to OfferWeb that says “Don’t do that again”.
OfferWeb, if they acknowledge this publicly (I bet not) has plausible deniability and can say ‘It wasn’t us, it was an unscrupulous affiliate”. And maybe they DO fire ‘Andrew Talbot’, but that’s not any kind of victory, because he probably already has accounts with OTHER lead-gen outfits, which might even include those who also have AARP as
a client, or a client-of-a-client.
So the best-case result of this analysis being made public is that two strongly-worded letters get sent, the URLs in the spam and the trail of redirects change slightly, but the spam continues at the same volume and with the same results, and AARP continues to benefit from the millions of spams sent on their behalf.
I’m not a lawyer, but I was under the impression that CAN-SPAM imposed liability on the organization that was ultimately responsible for the spam being sent, but until the FTC pursues action against someone like this, or Gevalia, corporations and organizations will continue to get away with supporting, and benefiting from, millions and millions of spams.
As JD pointed out in a comment to a previous post: sorry, AARP, but none of us are going to be able to retire any time soon.
Analysing lead-gen spam
Yesterday I showed how major companies hire hard core spammers.
Today I’m going to show you some of the technical details as to how I found that data. This is a fairly quick and shallow analysis, the sort of thing I’d typically do for a client to help them decide whether the case was worth pursuing before expending too much money and time on investigation and legal paperwork. I’ve also done it using standard command line tools that are available on pretty much any unix command line (and windows, with a little effort).
There are several questions to answer about the email in question.
AARP, SureClick, Offerweb and Spam
On Tuesday Laura wrote about receiving spam sent on behalf of the AARP. The point she was discussing was mostly just how incompetent the spammer was, and how badly they’d mangled the spam such that it was hardly legible.
One of AARPs interactive advertising managers posted in response denying that it was anything to do with the AARP.
Spam from mainstream companies
Yesterday I wrote about spam I received advertising AARP and used it as an example of a mainstream group supporting spammers by hiring them (or hiring them through proxies) to send mail on their behalf.
My statement appears to have upset someone, though. There is one comment on the post, coming from an IP address allocated to the AARP.