Twitter Puts Its Foot Down, Takes Five Biggest Spammers To Federal Court

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

no-spam

A warning: You can only spam Twitter so much before it brings in the law. As Twitter grows — the company now claims to have 140 million active users — naturally, it’s become an attractive target for spammers, which have collectively made their drek a familiar part of the social network’s user experience. Now Twitter is officially putting its foot down and enlisting the help of the federal courts, filing a suit in San Francisco today against its five most aggressive spammers. In pursuing legal action, Twitter said in a statement on its blog, it believes it’s going “straight to the source”.

By shutting down tool providers, we will prevent other spammers from having these services at their disposal. Further, we hope the suit acts as a deterrent to other spammers, demonstrating the strength of our commitment to keep them off Twitter … While this is an important step, our efforts to combat spam don’t stop here. Our engineering team continues to implement robust technical solutions that help us proactively reduce spam.

So, not only is Twitter pursuing legal action, it’s using other tools at its disposal to silence the peanut gallery, launching anti-spam measures that, among other things, specifically target @mention spam. Twitter also said that it has been using its link shortener, a.k.a. “t.co” to analyze data on spammy content and its origins, and give it the kabosh.

Obviously, spam has become a real problem on Twitter, and its taking legal action definitely functions as a clear signal that the company is taking the problem seriously. Nothing like “federal courts” to drive home the point. As Twitter users know, spammy followers are a routine occurrence, like those one-link spam tweets that end up in your “mentions” tab, for example. Twitter does implement sweeps to reduce the overall reach and tally of these spam accounts — one of the reasons we see our follower numbers periodically drop.

Of course, this is not a problem they can fight alone. The company is also asking users to help police its network, and users can find out how to report and block spammers here.

Will be updating.



April 6th 2012 Mobile, spam, Twitter

The ethics of SEO

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

The type of SEO I help my clients do and promote to you using this blog is often labeled white hat SEO because it stays within Google’s and other search engines guidelines. Other SEO’s don’t care about Google’s guidelines as much and do what’s called “black hat SEO”. Far too often though, black hat SEO is confused with the hacking of sites and the use of other tactics not outside the laws of Google but the laws of our lands. I think it’s time for me to explain where I stand in this.

My background

As a former Theology student and as someone raised in the Christian tradition, I have a fairly specific (and in some eyes: stringent) set of ethics. I don’t work on gambling or porn related sites because of that. I’m aware that others have different opinions on this and I don’t judge others when they have other ethics with regards to their work. To each his own. Sometimes though, I draw the line.

Among my friends are some of the world’s best black hat SEO’s. These are also guys that will never break a law or willfully hurt other people to get their rankings, they just game Google’s algorithms. I know  href="http://mattcutts.com/blog/">Matt knows at least some of them and there’s even a form of “honor” among them: he seems to appreciate their ability to outwit their algorithm. Unfortunately not everyone in the SEO “community” is that clean: some people are willing to break laws or hurt other people.

After the last SES conference in Amsterdam, which I arranged the speakers for, one of the speakers (not the keynote :) ) admitted to me he wouldn’t mind teaching other people how to hack sites or how to build trojans to gain links. I was too startled to give a proper response but decided later that day that I would never allow him back on a conference I arranged speakers for.

Spammy Link Building in the Netherlands

The last few days there’s been  href="http://www.molblog.nl/bericht/douwe-egberts-kpn-pon-en-randstad-betrokken-bij-icomment-spam-i/">an outcry in the Netherlands over several companies using comment spam and forum spam as a method of gaining links. They’d been caught creating fake profiles on all sort of sites and pretending to interact while really only inserting their links. I had to laugh a bit, as would most of my UK, American and German friends, as that’s so common outside of the Netherlands nobody would be surprised to see that anymore.

There was  href="http://www.molblog.nl/bericht/de-buzzmollen-van-groupon/">one specific case though that “hurt” more than others (which was by another company by the way). Someone had willfully created an account on a forum for MS (multiple sclerosis) patients, claiming to be a patient, while was spamming links there to health related offers. That’s so low that it hurts.

Outing Non-ethical SEO practices: immoral?

Recently Joe Hall, whom I respect a lot, did a post saying  href="http://joehall.me/seo-outing-is-immoral/29/">SEO “outing” is immoral. He mentions that while the outed practices themselves might be non-ethical, those people have families too, etc. Basically: people lose their jobs because of it. That’s true. And that’s sad. Especially as most of those people will not know what hit them.

I will counter that though: those companies have grown by using their unethical methods, costing other people their jobs in other companies. This is a zero-sum game in most cases. Google doesn’t tell people what to buy, it helps them find where they can buy it. Keep this in your mind at all times: search doesn’t create demand, it merely funnels it. I refuse to let people who use unethical SEO methods “win” because they support families, simply because their more ethical competitors support families too.

I recently  href="http://yoast.com/godaddy-link-building/">outed GoDaddy over using spammy link building techniques and got a lot of flack for that from other people in the industry. Some seem to think that it’s all of “us” (SEO’s) against “them” (Google). I wholeheartedly disagree. GoDaddy was using its paying customers to strengthen their own SEO without consulting them, in fact, they were specifically hiding what they were doing in their editor.

I don’t mind them “playing” Google’s algorithms. I mind them abusing their customers websites without their consent. The only way of making that stop is to ask Google to remove the value that abuse has. In the same way I loathe WordPress plugin developers who add links to their users sites without consent.

I will not ”out” people for buying high quality, relevant links from high quality websites related to their own topic, I have less issues outing people who hack into my website to gain a few links. This happens more often than I dare to admit.

Policing the web

Joe goes further and says:

“If your paycheck doesn’t say “Google” on it, it’s not your job to police the web.”

My paycheck doesn’t say Google. I’m not policing the web. Neither is Google. Google is trying to maintain a set of rules within its own index. It has all the rights in the world to do that. My paycheck doesn’t say “WordPress” either, yet I help develop that project because we all benefit. There really is such a thing as “the common good”.

That’s entirely different from outing every SEO I find that does something outside of Google’s guidelines, I’m smart enough to create my own set of ethics. I hope you are too. I for one intend to help them battle unethical SEO’s because I think we all benefit from that.

href="http://yoast.com/ethics-seo/">The ethics of SEO is a post by rel="author" href="http://yoast.com/author/joost/">Joost de Valk on href="http://yoast.com">Yoast – Tweaking Websites.A good WordPress blog needs good hosting, you don’t want your blog to be slow, or, even worse, down, do you? Check out my thoughts on href="http://yoast.com/wordpress-hosting/">WordPress hosting!

April 4th 2012 SEO, spam

Why Gmail Messages Are Marked as Spam

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

If you wonder why a certain message is flagged as spam by Gmail, you can find the reason from Gmail’s web interface. When you open a message from the spam folder, there’s a new section titled “Why is this message in Spam?” which offers “a brief explanation about why that particular message was placed in Spam”.


Here are some of the explanations you might see:

1. “You previously marked messages from info@example.com as spam.”

2. “You clicked ‘Report spam’ for this message.”

3. “It’s written in a different language than your messages typically use.”

4. “It contains content that’s typically used in spam messages.”

5. “It’s similar to messages that were detected by our spam filters.”

6. “Many people marked similar messages as spam.”

7. “We’ve found that lots of messages from info@example.com are spam.”

8. “Be careful with this message. Our systems couldn’t verify that this message was really sent by amazon.com. You might want to avoid clicking links or replying with personal information.”

9. [Phishing] “Be careful with this message. Similar messages were used to steal people’s personal information. Unless you trust the sender, don’t click links or reply with personal information.”

#4 and #5 are the most common explanations and they’re rather vague. It’s interesting to notice that the messages written “in a different language than your messages typically use” could be flagged as spam, but this shouldn’t be the only explanation.


“We hope that this is not only interesting, but also helps you learn about scams and other harmful messages that Gmail filters out. Whether you prefer to leave your spam folder untouched or do some educational digging, the information will be there for you. And if you’re interested in learning more, check out our new series of spam articles in the Gmail help center,” informs Google.

{ Thanks, Venkat. }



March 22nd 2012 spam

Text Spam Class Action Against Jiffy Lube Moves Forward – In re Jiffy Lube Int’l, Inc., Text Spam Litigation

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

[Post by Venkat Balasubramani]

In re Jiffy Lube International, Inc., Text Spam Litigation, 11-md-2261-JM-JMA (N.D. Cal.; Mar. 9, 2012)

Plaintiffs filed a class action against Jiffy Lube (a multi-location franchisee Heartland Automotive Services) and TextMarks alleging TCPA violations based on text messages sent by TextMarks on behalf of Jiffy Lube:

JIFFY LUBE CUSTOMERS 1 TIME OFFER:REPLY Y TO JOIN OUR ECLUB FOR 45% OFF A SIGNATURE SERVICE OILCHANGE! STOP TO UNSUB MSG&DATA RATES MAY APPLY T&C:JIFFYTOS.COM.

The court denies Heartland’s motion to dismiss. The big takeaway from the order is that text message-based marketing is something that companies often screw up, and these screw-ups end up being costly. Given the draconian provisions of the TCPA (statutory damages, stringent consent provision, no free pass for the initial message, and liability for any unsolicited message that is sent with certain equipment), rulings like these make me think companies should consider avoiding text message-based marketing altogether.

TCPA Provides for Derivative Liability:

Heartland’s first argument was that it should not be held liable because it did not actually send out the text messages (TextMarks did). The court cites to Satterfield v. Simon & Schuster and notes that the Ninth Circuit had no problem imposing liability on Simon & Schuster despite the fact that Simon & Schuster did not physically send the messages. The court also cites to an unsolicited fax case for the proposition that “congressional tort actions implicitly include the doctrine of vicarious liability.” If advertisers were allowed to escape liability by not actually sending the messages, this would allow advertisers to make an end-run around the TCPA’s prohibitions.

Heartland also argued that plaintiffs failed to sufficiently plead vicarious liability, but the court says that plaintiffs’ allegation that Heartland “engaged TextMarks to send the messages” is sufficient.

Plaintiffs’ Prior Consent:

Heartland produced invoices and sought to rely on the invoices to demonstrate that plaintiffs consented to receive the messages. The court rejects Heartland’s request that the court take judicial notice of the invoices, saying they stand for the opposite of what plaintiffs allege in their complaint. The invoices are not central to plaintiffs’ claims; therefore, they are not properly the subject of judicial notice in the same way that contractual terms—which the plaintiff relies on in the complaint—are. In passing, the court expresses skepticism as to whether the invoices would satisfy the TCPA’s strict consent requirements.

Were the Messages Sent Using an Auto-Dialer:

The TCPA only imposes liability for text messages that are sent using equipment that has the capacity to store or produce random numbers. Heartland argued that plaintiffs should only be permitted to allege the use of an auto-dialer on in formation and belief if (1) the content of the message was impersonal, and (2) the text message was sent by a specific SMS-short code. I think what Heartland is trying to argue is that only if the text messages bear indicia of being transmitted en masse should a TCPA plaintiff be entitled to allege the use of an auto-dialer on information and belief. The court rejects this, noting that in Simon & Schuster the Ninth Circuit only required that the equipment at issue have “the capacity” to store or produce numbers using a random or sequential number generator. Under Satterfield, it does not matter whether this capability was actually used to send the messages.

First Amendment Challenge:

Heartland also brings a First Amendment challenge, arguing that the broad definition of auto-dialer would mean that friends who text each other dinner invitations could incur TCPA liability, and this would render the statute overbroad. As expected, this argument doesn’t get much traction with the court. The court says that the statute is intended to protect consumers against the costs and privacy invasions that accompany unsolicited text messages, and regulating texts sent through auto-dialers adequately serves this interest. The court also says that the prospect of friends incurring liability under the TCPA for texting each other dinner invitations is fairly remote. At worst, this type of a text message lies at the fringe of the statute and thus the statute does not suffer from overbreadth issues.

Plaintiffs’ Cannot be Compelled to Arbitrate Their Claims:

Heartland finally argued that one of the plaintiffs who signed an agreement with Jiffy Lube (and other class members who fell into the same category) should be required to arbitrate their dispute. This plaintiff entered into an agreement while obtaining services at Jiffy Lube which contained the following provision:

[the parties] agree that any and all disputes, controversies or claims between Jiffy Lube and [the customer] (including breach of warranty, contract, tort or any other claim) will be resolved by mandatory arbitration according to the terms of this Mandatory Arbitration Agreement (“Agreement”), except that any such dispute can be resolved by a small claims court if and for so long as the dispute is within its jurisdiction. By this Agreement, Jiffy Lube and [customer] also agree to only bring disputes against each other in an individual capacity and not as a class representative or class member and waive the right to a jury trial.

The court says the arbitration language is “incredibly broad,” and application of the clause to disputes unrelated to the contract would raise conscionability issues. The court cites to a Judge Posner opinion and concludes that if enforced as drafted, “absurd results would ensue.” Heartland asked the court to construe it narrowly but the court declines, saying it is not authorized to do so. Even if the clause were construed to be limited to disputes “arising out of or relating” to the contract, the court says that the TCPA claims would not fall within the clause.
__

As mentioned above, text message litigation has been brutal for marketers and advertisers, and this decision is no different. (Liability for spam email in contrast has been much more limited.) To my knowledge, the issue of dervative liability hasn’t been squarely argued by a TCPA defendant, but decisions have implicitly recognized that the TCPA provides for derivative liability in rejecting the requests to dismiss filed by advertisers who did not transmit the messages in question. From that standpoint, the ruling is not significant, but it is still worth nothing.

Outsourcing your text message-based marketing was a risky proposition to start with, but as this decision squarely allows for derivative liability (albeit under somewhat vague standards), this makes it an even riskier proposition. Marketers may labor under the perception that the initial text message is a freebie (from a liability standpoint) and including an opt-out from receiving future texts absolves the marketer or advertiser from liability under the TCPA. It’s worth repeating that this is not the case.

Previous posts:

Group Text Services Grapple with TCPA Class Actions
Text Spam Lawsuit Against Citibank Moves Forward Despite Vague Allegations of Consent — Ryabyshchuk v. Citibank
Court Rejects Constitutional Challenge to TCPA Based on Vagueness in “Prior Express Consent” Exception — Kramer v. Autobytel, Inc.
Another Court Finds that TCPA Applies to Text Messages — Lozano v. Twentieth Century Fox Film Corp.
Court Finds that SMS Spam Messages are Subject to the TCPA and Rejects First Amendment Defense — Abbas v. Selling Source, LLC
Ninth Circuit Revives TCPA Claim–Satterfield v. Simon & Schuster
Cellphone Spam Violates TCPA–Joffe v. Acacia Mortgage

March 18th 2012 spam

Group Text Services Grapple with TCPA Class Actions

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

[Post by Venkat Balasubramani]

Pimental v. Google Inc., No. 11-2585 (N.D. Cal.; Mar. 2, 2012)

Plaintiffs sued Google (and Slide), asserting that text messages sent via the “Disco” service offered by Google violated the Telephone Consumer Protection Act.

As I understand it, Disco allows anyone to create a group for group text messaging purposes. According to the complaint, any time someone’s number is added to the group, Google sends out a service advertising its Disco services:

Disco is a group texting service. Standard SMS rates may apply or chat for FREE w/ our app – http://disco.com/d . . .

Plaintiffs sued for TCPA violations, but alleged that the messages sent by Disco violated the TCPA (they did not sue for the underlying texts).

The court rejects Google’s motion to dismiss, noting that the TCPA only requires that the text message be unsolicited (sent in the absence of prior express consent or pursuant to another exception) and sent using equipment that has the capacity “to store or produce telephone numbers to be called, using a random or sequential number generator.” Citing to the Ninth Circuit’s decision in Satterfield v. Simon and Schuster, the court says that plaintiffs’ allegations are sufficient to state a claim under the TCPA.

Defendants also raised a First Amendment argument, saying that the text messages were “informational” in nature. As with First Amendment arguments in spam litigation generally, the court was skeptical of this argument.

Glauser v. Twilio, No. C 11-2584 PJH (N.D. Cal.; Jan. 27, 2012)

A separate class action involved Twilio and GroupME, who were sued in a putative class action alleging TCPA violations. In that case, defendants successfully moved for a stay pending resolution of the FCC’s rulemaking procedures around TCPA issues. Because the FCC was considering rules clarifying (1) what constitutes an “auto-dialer” for TCPA purposes; (2) the scope of the prior express consent exception; and (3) the applicability of the “common carrier” exception to liability under the TCPA, the court granted a stay. Although the court has not lifted the stay, plaintiff recently filed a notice of decision from the FCC, and argued that as to GroupMe, the stay should be lifted, and the FCC’s rulemaking did not affect GroupMe’s liability. The court has not considered whether to lift the stay, but if plaintiff is correct, it looks like the lawsuit will go forward with respect to GroupMe. Interestingly, plaintiff did not seek to have the stay lifted as to Twilio.
__

I took a quick look at the FCC’s final regulations, and nothing in the rules offer much of an out for group text messaging services. With respect to the equipment used and the type of consent that is required, the final regulations do not seem to change much. Given the stringent nature of the TCPA rules (as articulated by Satterfield and other cases), those who send text messages are advised to procure consent through means other than the initial text message informing recipients that they can opt-out from receiving further texts. Also, this did not come through in the court orders resolving the claims against Disco or Twilio, but group texting services suffer from the flaw that they can be used by spammers, absent adequate validation measures. I haven’t seen a validation mechanism that is foolproof, and the best approach is to procure consent over the web or through some other means before any texts are sent (e.g., if you sign me up to receive texts, tell me to go to a website and validate my phone number, and only after this validation is complete should I receive texts). Courts seem warm to the idea that even the initial text saying people can opt-out from receiving further texts is sufficient to create TCPA liability, and nothing in the statute says otherwise.

The platforms may also have a viable section 230 defense if they provide “interactive computer services.” Given the broad definition of interactive computer services, they should qualify, but only as to messages sent by third parties. The lawsuit against Slide is aimed at texts sent by the Slide service (arguably automated and triggered by other users of the services), so Slide probably has a tougher argument to make based on Section 230. To the extent the claims are based on text messages transmitted by customers, Section 230 should come into play.

Other coverage:

Jeff J. Roberts (PaidContent/Giga): “Spam Lawsuits Weigh On Twilio, Group Texting Apps

March 10th 2012 spam

California Appeals Court Says Emails That Don’t Identify Sender Violate State Spam Statute – Balsam v. Trancos

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

[Post by Venkat Balasubramani]

Balsam v. Trancos, Inc., 2012 WL 593703 (Ca. Ct. App.; Feb. 24, 2012)

It seemed like most emailers and anti-spam activists have moved on from worrying about spam email to other things, such as social networks, but a few disputes continue to linger. One of them involves Dan Balsam, of danhatesspam.com fame, who is a lawyer and self-proclaimed anti-spam activist.

Balsam sued Trancos in 2008, alleging that he received numerous unsolicited emails from Trancos. After a bench trial, the trial court awarded Balsam $1,000 in liquidated damages for each of seven emails. (Here’s the prior blog post on this case: “Plaintiff Wins $7,000 Following Bench Trial on Claims Under California Anti-Spam Statute — Balsam v. Trancos.”) The trial court also awarded Balsam $81,900 in attorneys’ fees. The trial court rejected Balsam’s claims under California’s Consumer Legal Remedies Act and held that Trancos’ CEO, Brian Nelson, could not be held personally liable. Trancos appealed, alleging that the emails did not violate California’s anti-spam statute (B&P 17529.5(a)(2)). Trancos also argued that Balsam’s claims were preempted by CAN-SPAM. On appeal, the appeals court rejects both of Trancos’ arguments. Balsam cross appealed on the trial court’s resolution of the CLRA issue and rejection of personal liability to Nelson personally. The court also rejects Balsam’s arguments on cross appeal.

Violations of Cal. Code Sec. 17529.5(a)(2)

Section (a)(2) makes it unlawful for anyone to advertise in an email sent from or to a California email address where the email “contains or is accompanied by falsified, misrepresented, or forged header information.”

According to the opinion, Trancos’ company sent out emails from various “nonsense” domain names (e.g., misstepoutcome.com; modalworship.com; moussetogether.com) that were registered to Trancos via a privacy proxy. The emails did not identify Trancos, but mentioned that if recipients wanted to opt-out, they could forward the emails to USAProductsOnline, or click on a link provided in the email. USAProductsOnline was not a separately existing entity, but it had registered a PO Box. Nelson, the CEO of Trancos, testified that he registered the domain using privacy protection services because he and Trancos had been harassed in the past.

The court focuses on whether the California Supreme Court’s decision in Kleffman v. Vonage, which construed section 17529.5(a)(2), lets Trancos off the hook here. (See “Use of Multiple (Even Random or Garbled) Domain Names to Bypass Spam Filter Does not Violate Cal. Spam Statute — Kleffman v. Vonage.”) Kleffman involved emails sent on behalf of Verizon using nonsensical or random domain names that were designed to evade spam filters. Kleffman made a variety of unsuccessful arguments why using garbled or random domain names constituted “misrepresentation.”

The appeals court distinguishes Kleffman, saying that in Kleffman, all of the emails were sent using domain names that were “traceable” to Vonage’s marketing agent. In contrast, in this case, the court says the emails were not traceable to Trancos because Balsam could not determine the identity of the sender using a “publicly available database,” and thus Trancos’ email had misrepresented header information. The emails listed “USAProductsOnline” as the sender and provided a street address for USAProductsOnline, but this turned out to be a PO Box, and Balsam had to subpoena the information provided to the PO Box company to obtain the information provided by USAProductsOnline. The court also distinguishes the Fourth Circuit’s decision in Omega World Travel v. Mummagraphics saying that, in that case, the identity of the sender was readily obvious to the recipient, who had no trouble tracking down the sender.

Preemption Under CAN-SPAM

Trancos also argued that Balsam’s state law claims were preempted by CAN-SPAM. The court notes the split of authority in federal courts regarding whether CAN-SPAM preempts claims which fall short of common law fraud, or whether CAN-SPAM only preempts claims which do not involve “falsity or deception.” Citing to the California Appeals Court’s decision in Hypertouch v. Valueclick, the court says that claims which allege any sort of falsity or deception escape preemption under CAN-SPAM’s preemption clause. Balsam’s claims therefore aren’t preempted.
__

The thrust of the court’s decision is that emails have to identify some actual person or entity they are sent by or on behalf of, whether in the “from line” or the email body. Emails that do not so identify themselves violate the statute. There are a few problems with this from my perspective.

First, it broadens the definition of “header information” to include not just the from line but also the body of the email. The California statute does not define “header information” but Kleffman looked to CAN-SPAM’s definition, which clearly talks about either the human or computer readable parts of the “from line.” The overall structure of CAN-SPAM lends weight to the view that the header information prong does not deal with information in the actual body of an email.

Second, it injects the element of concealment into the California statute. It’s fair to presume that if the legislature intended the statute to cover not just misrepresentations of facts regarding an email’s origin but also concealment, the legislature would have made that explicit.

Third, the FTC rules interpreting CAN-SPAM allow the use of private mail boxes (that the sender registers with a commercial mail receiving agency established under US Postal Service regulations) to satisfy the requirement of listing the sender’s street address. The FTC announcement of these regulations indicate that the regulation accommodates the two interests of (1) law enforcement being able to track down the sender (ostensibly with a subpoena) and (2) recipients being able to communicate with the senders (by sending paper correspondence). Not only is the issue of identifying the sender comprehensively regulated by CAN-SPAM, CAN-SPAM regs allow the practice Balsam complained about.

The court distinguishes Kleffman. but I wasn’t persuaded by this. Everyone agreed in Kleffman that the emails were fairly traceable to Vonage, but importantly, the emails were traceable not to Vonage directly, but to its “marketing agent.” Because the emails all identified Vonage (who was being advertised in the emails), it’s tough to say for sure, but as far as identifying the actual sender of the email, Kleffman says nothing more than that if the emails can be identified as having been sent by some entity (e.g., Vonage’s “marketing agent”), that’s sufficient. Here, the problem seems to have been that the entities identified in the emails as senders were not actual legal entities.

The court’s decision slams the use of private registration services in the context of email marketing. Balsam previously tried to hold Tucows liable for emails sent via a domain name registered (privately) through Tucows. (See “Domain Name Privacy Protection Services Not Liable for Failure to Disclose Identity of Alleged Spammer — Balsam v. Tucows.”) Balsam was not successful in that case, but the court’s decision here contains plenty of bad juju towards the use of private registration services.

Although the California Supreme Cout may have better things to do with its time, this looks like a good candidate for review so it can clarify the scope of Kleffman v. Vonage.

It’s unclear how much mileage Balsam and company will get out of this ruling. As the court notes, several cases have held that claims such as this one are preempted, and it’s a likely bet that Balsam’s subsequent defendants would remove on the basis of preemption and try to get the claims dismissed on this basis. This is undoubtedly a significant ruling, but it’s unlikely to open the floodgates for judgments against emailers.

Previous posts:

Plaintiff Wins $7,000 Following Bench Trial on Claims Under California Anti-Spam Statute — Balsam v. Trancos
Use of Multiple (Even Random or Garbled) Domain Names to Bypass Spam Filter Does not Violate Cal. Spam Statute — Kleffman v. Vonage
An End to Spam Litigation Factories?–Gordon v. Virtumundo
Fourth Circuit Rejects Anti-Spam Lawsuit–Omega World Travel v. Mummagraphics
Domain Name Privacy Protection Services Not Liable for Failure to Disclose Identity of Alleged Spammer — Balsam v. Tucows

March 1st 2012 spam

Old School Spam Plaintiff Rebuffed in the Ninth Circuit

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

[Post by Venkat Balasubramani]

Gordon v. BMG Columbia House, 10-35180 (9th Cir. Nov. 28, 2011)
Gordon v. Inviva, 10-35283 (9th Cir. Nov. 28, 2011)
Gordon v. Commonwealth Mktg. Group, 10-35030 (9th Cir. Nov. 28, 2011)

James Gordon has generated more than a few blog posts as a result of his quixotic quest to hold bulk emailers liable under CAN-SPAM, despite not fitting within the categories of persons or individuals who have standing under that statute to bring private causes of action. He was the plaintiff in the Virtumundo case, in which the Ninth Circuit rejected his claims and effectively put an end to the budding spam litigation cottage industry. (“An End to Spam Litigation Factories?–Gordon v. Virtumundo“; “CAN-SPAM Defendant Awarded $111k in Fees/Costs–Gordon v. Virtumundo.”) Following Virtumundo, Gordon was the subject of some collections efforts, where he may have lost his home and belongings. (DirectMag: “Anti-Spammer Loses More than His Lawsuit.”)

It turns out, despite his stunning string of failures in court, Gordon is still at it! But he doesn’t seem to be making much progress. The Ninth Circuit recently rejected his appeal in three pending cases. Proceeding pro se, Gordon appealed three district court grants of summary judgment against him. In all three cases, the court affirmed the district court judgments on the basis that Gordon lacked standing to sue under CAN-SPAM and his claims under Washington’s spam statute were preempted. He brought a few additional state law claims (consumer protection act, breach of contract) but the court doesn’t give those more than a cursory sentence.

Virtumundo, along with Mummagraphics, the two leading appellate cases construing CAN-SPAM preemption, left a small window available to spam plaintiffs. There has been some attempts by plaintiffs to advance state law claims in California (“CA Appeals Court: Claims Under State Spam Statute Not Preempted by CAN-SPAM“; “Plaintiff Wins $7,000 Following Bench Trial on Claims Under California Anti-Spam Statute“), but for the most part, plaintiffs suing under state anti-spam laws have been shut down elsewhere.

December 23rd 2011 spam

GoDaddy’s spammy link building techniques

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

Over the last few months, I’ve seen GoDaddy rise up in the rankings for a lot of hosting related terms. At first I suspected they were finally using their very strong domain in a smart way, but then I noticed they ranked for terms I know you can’t rank for without a lot of external links, no [...]

href="http://yoast.com/godaddy-link-building/">GoDaddy’s spammy link building techniques is a post by rel="author" href="http://yoast.com/author/admin/">Joost de Valk on href="http://yoast.com">Yoast – Tweaking Websites.A good WordPress blog needs good hosting, you don’t want your blog to be slow, or, even worse, down, do you? Check out my thoughts on href="http://yoast.com/wordpress-hosting/">WordPress hosting!

December 16th 2011 SEO, spam

Text Spam Lawsuit Against Citibank Moves Forward Despite Vague Allegations of Consent — Ryabyshchuk v. Citibank

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

[Post by Venkat Balasubramani]

Ryabyshchuk v. Citibank, 11-cv-1236 – IEG (S.D. Cal.; Nov. 28, 2011)

Plaintiff alleged that he contacted Citibank and inquired about a credit card. Later that day, he alleged he received the following unsolicited text from Citibank:

Free Text Msg: Citi Cards needs to talk with you regarding your recent application. Please call 866-365-8962. To Opt-Out reply STOP.

Plaintiff replied “STOP” and alleged that he received the following from Citibank:

Free Text Msg: Per your request you will no longer receive text alerts from Citi Cards Credit Dept. If you have any questions call 866-365-8962.

Plaintiff sued for violations of the Telephone Consumer Protection Act, seeking statutory damages ($500 per text) and treble damages. Citibank moved to dismiss.

The court says that text messages are “calls” within the meaning of the TCPA, and any text sent with equipment which has the capacity to store or produce telephone numbers using a random or sequential number generator falls within the TCPA. (See Satterfield v. Simon & Schuster.)

Citibank argued that plaintiff “consented” to the text and first relied on plaintiff’s initial complaint where he alleged that he “provided his cell phone number” to Citibank in connection with the credit card application. Plaintiff amended his complaint to avoid any implication that he provided his number, instead alleging the second time around that he “contacted Citibank … by telephone” in connection with a possible credit card. The court says that plaintiff should be allowed to revise his pleadings and there is nothing in the rules which prohibit plaintiffs from making inconsistent or even contradictory allegations in successive pleadings.

Citibank also relied on two FCC pronouncements to argue that plaintiff consented. The FCC stated in 1992 that people who “knowingly release their phone numbers have . . . given their invitation to . . . be called . . . absent instructions to the contrary.” The FCC also stated in a 2008 ruling that calls to wireless numbers “in connection with an existing debt” fall under the ‘prior express consent’ exception to the TCPA. Specifically, the FCC stated:

the provision of a cell phone number to a creditor, e.g., as part of a credit application, reasonably evidences prior express consent by the cell phone subscriber to be contacted that that number regarding the debt.

The court says that it’s unclear at the pleading stage whether plaintiff released his number “knowingly,” and what limitations he attached to the release of his number. The court also says that the FCC has recognized the burden consumers may face in proving that they did not provide consent, and thus senders should bear the evidentiary burden of showing that consent was provided. Given the state of the pleadings, the court says the consent issue is better suited for adjudication at the summary judgment stage, rather than the pleadings stage.
__

Ouch. Not only does the initial text violate the TCPA (in the absence of consent), even the text which confirms Ryabyshchuk would not receive any further text messages can violate the statute.

The rules governing unsolicited text messaging leave little room for those who send unsolicited texts. Despite the texts relating to a proposed transaction which plaintiff admitted he contacted Citibank about, and despite Citibank apparently honoring plaintiff’s opt-out request, Citibank may still be on the hook! Relying on a check-the-box opt-in that says “please send me text messages regarding various topics to XXX-XXX-XXXX” would seem to be the prudent choice. The defense that the recipient provided a phone number in the course of a proposed transaction does not insulate Citibank here. Although Citibank may ultimately prove consent, the fact that it was unable to get rid of the lawsuit at the pleading stage means that it has to deal with the expense of discovery and summary judgment.

The odd thing about this case is that Ryabyschuck obviously anticipated or implicitly requested additional contact with Citibank. He filled out a credit card application and included his phone number. Citibank would have to comply with certain restrictions, but it could have avoided the prospect of liability by calling Ryabyshuck on the phone. Because it chose to text him–which some would say is less intrusive–Citibank got tagged with a lawsuit.

Related posts:

Ninth Circuit Revives TCPA Claim–Satterfield v. Simon & Schuster
Cellphone Spam Violates TCPA–Joffe v. Acacia Mortgage
Another Court Finds that TCPA Applies to Text Messages — Lozano v. Twentieth Century Fox Film Corp
Debt Collection Text May Result in Liability under the Telephone Consumer Protection Act — Gutierrez v. Barclays Group

December 13th 2011 spam

Yahoo! Mail – 1, Spammers – 0

Comments Off
http://www.xseo.com.au/wp-content/plugins/sociofluid/images/digg_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/reddit_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/stumbleupon_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/delicious_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/google_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/facebook_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/sphinn_48.png http://www.xseo.com.au/wp-content/plugins/sociofluid/images/twitter_48.png

Today Yahoo! announced a big milestone in the fight against spam – we were awarded a $610 million judgment against spammers responsible for creating a fake Yahoo! lottery email scheme. This scheme was perpetrated against email users and led them to believe that they were being offered a lottery prize from Yahoo!. You can read about the actual case and the judgment issued by a New York judge here.

As a leader in anti-spam protection, we are constantly looking at how we can win the war on spam, and take several different approaches to help keep our 300-million Yahoo! Mail users as safe as possible. On the technology front, we are continually updating our technology engine to stay one step ahead of spammers. In fact, Yahoo! Mail blocks more than 600 billion spam messages each and every month (that’s over 7.2 TRILLION spam messages we block each year.) And, since introducing an updated version of Yahoo! Mail in May this year, we’ve reduced the amount of spam reported by our Mail users by an additional 60%.

More importantly, today’s ruling shows that Yahoo! goes after spammers. In a big way. We initially started building this specific case back in 2008 and have diligently been pursuing it since then. Why? Because we are vigilant about protecting you, every other Yahoo! User and the online industry in general. We do not, nor will we in the future, hesitate to bring legal action against wrong doers who are engaging in fraudulent activities across our platforms.

Is the fight against spam over? Not by a long shot. Every day the spammers try to figure out how to stay one-step ahead of the good guys, and every day Yahoo! employs the latest technology we can to stop them.

But what we can say is that today Yahoo! won a major round against spammers.

December 8th 2011 spam