REDI-DATA, INC. v. THE SPAMHAUS PROJECT

CourtDistrict Court, D. New Jersey
DecidedAugust 2, 2022
Docket2:20-cv-17484
StatusUnknown

This text of REDI-DATA, INC. v. THE SPAMHAUS PROJECT (REDI-DATA, INC. v. THE SPAMHAUS PROJECT) is published on Counsel Stack Legal Research, covering District Court, D. New Jersey primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
REDI-DATA, INC. v. THE SPAMHAUS PROJECT, (D.N.J. 2022).

Opinion

Not for Publication

UNITED STATES DISTRICT COURT DISTRICT OF NEW JERSEY

REDI-DATA, INC., Plaintiff, Case No. 20-cv-17484

v.

THE SPAMHAUS PROJECT a/k/a OPINION THE SPAMHAUS PROJECT LTD., Defendant.

John Michael Vazquez, U.S.D.J. This action arises out of Plaintiff’s allegations that Defendant, a foreign nonprofit organization, defamed Plaintiff and tortiously interfered with its business. Currently pending before the Court is Defendant’s motion to dismiss for lack of personal jurisdiction. D.E. 15. The Court reviewed the parties’ submissions1 in support and in opposition and decided the motion without oral argument, pursuant to Fed. R. Civ. P. 78(b) and L. Civ. R. 78.1(b). For the reasons that follow, Defendant’s motion is denied without prejudice so that the parties may conduct limited jurisdictional discovery. I. BACKGROUND Plaintiff, Redi-Data, Inc. (“Redi-Data”), is a New Jersey corporation with its principal place of business in New Jersey. D.E. 1 (“Compl.”) ¶ 6. Redi-Data is a list broker providing direct mail and email marketing services to health-science industry clients in the United States. Id. ¶¶ 12-17. To conduct its business, Redi-Data routes its clients’ marketing communications through

1 Defendant’s brief in support of its motion to dismiss, D.E. 15-1, will be referred to as “Br.”; Plaintiff’s brief opposing the motion, D.E. 22, will be referred to as “Opp.”; and Defendant’s reply brief in further support of its motion, D.E. 23, will be referred to as “Reply.” two internet domain names, “redimail.com” and “redidata.com,” and their associated internet protocol (“IP”) addresses. Id. ¶¶ 13, 16. These domains and IP addresses are serviced by various internet service providers (“ISPs”). See D.E. 22-14 (“Buckley Decl.”) at 5 n.1. Redi-Data maintains full compliance with all federal and state laws, including the CAN-SPAM Act, 15 U.S.C. §§ 7701-13,2 in electronically distributing its commercial marketing communications. Compl. ¶¶

18-20. Defendant The Spamhaus Project (“Spamhaus”) is a not-for-profit limited liability company. D.E. 15-2 (“Linford Decl.”) ¶ 4. Spamhaus tracks spam and related cyberthreats such as phishing, malware, and botnets. Compl. ¶ 22. Spamhaus provides cybersecurity data to “the majority of the Internet’s ISPs, email service providers, corporations, universities, governments[,] and military networks.” D.E. 22-2 (“Carbone Decl.”) Ex. A at 1. Spamhaus is presently headquartered in and incorporated under the laws of the Principality of Andorra. Linford Decl. ¶ 4. Prior to 2019, Spamhaus was headquartered in and organized as the same under the laws of the United Kingdom. Id. ¶¶ 3-4.

Spamhaus maintains blocklists, which are used by internet service and hosting services providers to prevent Spamhaus users from receiving certain emails. Compl. ¶ 23. When Spamhaus detects that an entity has distributed unsolicited bulk email (“spam”), it places the corresponding domains and IP addresses on its blocklists, either automatically or manually by one its researchers. Id. ¶¶ 25-28. This occurs regardless of the email’s legality or compliance with the CAN-SPAM

2 The CAN-SPAM Act governs the transmission of all commercial email and generally prohibits the transmission of false or deceptive messages. See generally CAN-SPAM Act: A Compliance Guide for Business, FED. TRADE COMM’N (Jan. 2022), https://www.ftc.gov/business- guidance/resources/can-spam-act-compliance-guide-business. The Act also requires commercial emails to contain certain disclosures. Id. For example, messages must include the sender’s physical postal address and explain how the recipient may opt out of receiving future messages. Id. Act. Linford Decl. ¶ 9. Removal from the blocklists may be pursued and obtained through procedures established by Spamhaus. Id. ¶ 15. The blocklists, as well as all Spamhaus data, are hosted on Spamhaus servers and may be accessed from the Spamhaus webpage. Id. ¶¶ 7-8. These resources are available, free of charge, to all internet users who wish to use them. Id. ¶ 8. In fact, Spamhaus provides no commercial

goods or services whatsoever, not even to ISPs or other entity users. D.E. 23-12 (“Marin Decl.”) ¶¶ 5-8. Spamhaus does, however, maintain a “strategic partner,” Spamhaus Technology LTD (“Spamhaus Technology”). Id. ¶ 9. Spamhaus Technology and Spamhaus are legally separate entities: they share no income, governing authority, or power to bind or obligate each other contractually. Id. ¶¶ 9-12. Spamhaus Technology, unlike Spamhaus, offers commercial services. Id. ¶ 9. Among them is a fee-based, managed blocklist “datafeed” service, which is offered in North America through Spamhaus Technology’s independent contractor, Security Zones. Id. ¶¶ 9-13. In April 2016, Spamhaus added Redi-Data’s IP addresses to its blocklists; in April 2018,

Spamhaus added Redi-Data’s domain names as well. Compl. ¶¶ 3-4. Redi-Data maintains that these additions were either intentionally or recklessly erroneous and substantially harmed its business operations. Id. ¶¶ 31-36. Specifically, Redi-Data alleges that it has suffered “lost good will, a tarnished reputation, lost opportunities, lost customers, and lost profits,” among other injuries. Id. ¶¶ 5, 33-34. Upon Redi-Data’s request, Spamhaus removed the domain names from the blocklists in June 2018. Id. ¶¶ 37-38. Later that same month, Spamhaus reinstated Redi-Data’s domain names to its blocklists. Id. ¶ 39. Thereafter, Redi-Data repeatedly requested removal and served a letter on Spamhaus demanding the same. Id. ¶¶ 40-42; Ex. A. Redi-Data did not receive an “adequate response” to this letter, and Spamhaus has not removed Redi-Data’s domains or IP addresses from its blocklists. Id. ¶¶ 43-44. Moreover, Redi-Data alleges that Spamhaus has expressly refused to remove Redi-Data’s domain names from the blocklists. Id. ¶¶ 44, 48, 59. Redi-Data asserts that the sum of these harms warrants the award of injunctive and monetary relief. Id. ¶ 53. Redi-Data filed its Complaint on November 30, 2020, asserting the following four counts:

(1) preliminary and permanent injunctive relief; (2) interference with prospective economic advantages and/or business relations; (3) tortious interference with contractual relationships; and (4) defamation. D.E. 1. Spamhaus’ motion to dismiss pursuant to Fed. R. Civ. P. 12(b)(2) followed. D.E. 15. II. STANDARD OF REVIEW Rule 12(b)(2) permits a party to move to dismiss a case for lack of personal jurisdiction. In such a motion, the plaintiff bears the burden of demonstrating “sufficient facts to establish that jurisdiction is proper.” Mellon Bank PSFS Nat’l Ass’n v. Farino, 960 F.2d 1217, 1223 (3d Cir. 1992). In reviewing a motion to dismiss for lack of personal jurisdiction, a court “must accept all

of the plaintiff’s allegations as true and construe disputed facts in favor of the plaintiff.” Carteret Sav. Bank, FA v. Shushan, 954 F.2d 141, 142 n.1 (3d Cir. 1992). But when a defendant raises a jurisdictional defense, “a plaintiff bears the burden of proving by affidavits or other competent evidence that jurisdiction is proper.” Dayhoff Inc. v. H.J. Heinz Co., 86 F.3d 1287, 1302 (3d Cir. 1996). Thus, to withstand a Rule 12(b)(2) motion, a plaintiff may not rely on the pleadings alone, as it “is inherently a matter which requires resolution of factual issues outside the pleadings.” Time Share Vacation Club v. Atl.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

International Shoe Co. v. Washington
326 U.S. 310 (Supreme Court, 1945)
Shaffer v. Heitner
433 U.S. 186 (Supreme Court, 1977)
World-Wide Volkswagen Corp. v. Woodson
444 U.S. 286 (Supreme Court, 1980)
Keeton v. Hustler Magazine, Inc.
465 U.S. 770 (Supreme Court, 1984)
Calder v. Jones
465 U.S. 783 (Supreme Court, 1984)
Helicopteros Nacionales De Colombia, S. A. v. Hall
466 U.S. 408 (Supreme Court, 1984)
Burger King Corp. v. Rudzewicz
471 U.S. 462 (Supreme Court, 1985)
Burnham v. Superior Court of Cal., County of Marin
495 U.S. 604 (Supreme Court, 1990)
Carnival Cruise Lines, Inc. v. Shute
499 U.S. 585 (Supreme Court, 1991)
Goodyear Dunlop Tires Operations, S. A. v. Brown
131 S. Ct. 2846 (Supreme Court, 2011)
J. McIntyre Machinery, Ltd. v. Nicastro
131 S. Ct. 2780 (Supreme Court, 2011)
Dayhoff Inc. v. H.J. Heinz Co.
86 F.3d 1287 (Third Circuit, 1996)
Cybersell, Inc. v. Cybersell, Inc.
130 F.3d 414 (Ninth Circuit, 1997)
Imo Industries, Inc. v. Kiekert Ag
155 F.3d 254 (Third Circuit, 1998)
Young v. New Haven Advocate
315 F.3d 256 (Fourth Circuit, 2002)

Cite This Page — Counsel Stack

Bluebook (online)
REDI-DATA, INC. v. THE SPAMHAUS PROJECT, Counsel Stack Legal Research, https://law.counselstack.com/opinion/redi-data-inc-v-the-spamhaus-project-njd-2022.