← Compliance & Legal Guides
EXECUTIVE REGULATORY BRIEFING
Published: October 2026 • Author: Fred Dawson • Deliverability & Legal Compliance Architecture

Executive Summary: Comprehensive legal and technical comparison of CAN-SPAM, GDPR, and CASL: consent requirements, opt-out mechanisms, transactional exceptions, and cross-border penalties.

Opt-Out vs Opt-In Consent Model US (Opt-Out) vs EU/Canada (Opt-In)
10 Days vs 48 Hours Unsubscribe SLA CAN-SPAM (10d) vs CASL (10 business d)
Up to $51,744 Max Fine / Email US FTC CAN-SPAM statutory penalty
Up to €20M / 4% GDPR Penalty Tier 2 GDPR statutory maximum

Your email list contains recipients in the United States, the European Union, and Canada simultaneously. Three different laws apply — and they conflict in fundamental ways. CAN-SPAM allows you to email anyone who hasn’t opted out. CASL requires prior consent before the first message. GDPR requires a documented lawful basis for processing the personal data used to send the email. Applying the same sending rules to all three segments is a compliance failure that exposes you to penalties ranging from $51,744 per email (CAN-SPAM) to €20 million (GDPR) to CAD$10 million (CASL).

This guide provides a direct comparison of all three laws on the dimensions that matter for email operations: consent model, geographic scope, penalty structure, opt-out rules, and what each law requires in practice for B2B cold email, marketing campaigns, and transactional messages.

The most important distinction between the three laws is their starting position on consent:

DimensionCAN-SPAM (US)CASL (Canada)GDPR (EU)
Consent modelOpt-out — no prior consent requiredOpt-in — prior consent required (express or implied)Opt-in — lawful basis required for data processing
Cold email permitted?Yes, without consentOnly with implied consent basisB2C: No. B2B: Legitimate interest with LIA
Unsubscribe deadline10 business days10 business daysPromptly / without undue delay
Physical address required?YesYes (+ phone or email)Not specifically mandated
Who it coversSenders to US recipientsSenders to Canadian recipientsProcessors of EU resident data
B2B exemption?No — applies to all commercial emailNo — applies to all CEMsNo, but B2B LI easier to justify
Jurisdiction followsRecipient locationRecipient locationRecipient’s residence

CAN-SPAM in Practice

CAN-SPAM is the most permissive of the three. You can legally send commercial email to any US recipient without prior consent — the law operates on opt-out, not opt-in. This makes it unique among major email regulations globally. The 2025 per-email penalty is $51,744, but what the law actually prohibits is specific deceptive conduct: false headers, misleading subject lines, missing physical addresses, and non-functional opt-out mechanisms.

The critical CAN-SPAM obligation that most senders underestimate: you cannot make unsubscribing harder than a single webpage visit. No password required, no reason selection, no “confirm your email” step after clicking unsubscribe. The FTC’s 2024 enforcement action against Verkada — which resulted in a record $2.95 million fine — cited a non-functional opt-out mechanism as a central violation. Being legally permitted to send does not mean being immune to penalty when you make it hard to stop.

CAN-SPAM also applies to the company whose product is promoted, not just the company sending the email. If you hire a marketing agency or affiliate to email on your behalf, you share liability for their violations.

CASL in Practice

CASL requires consent before the first commercial electronic message. Unlike GDPR, where consent is one of several possible lawful bases, CASL’s consent requirement is the default starting position with specific exceptions. The two consent types under CASL are:

Express consent — the recipient took a clear, affirmative action to receive your messages (ticked an unchecked box, clicked a confirmation link). Express consent never expires until withdrawn.

Implied consent — no explicit opt-in, but a prior relationship or publicly available address provides a basis. Implied consent expires: 2 years from a business transaction, 6 months from a written inquiry, no fixed expiry for a publicly posted address (but the message must relate to the recipient’s professional role).

For B2B cold email to Canadian recipients, the “conspicuous publication” basis is most commonly used: the recipient’s email is publicly posted on a company website without a refusal notice, and your message is relevant to their business role. This three-part test is frequently failed by senders who assume any publicly available email is fair game for any message.

▶ CASL three-part test for B2B cold email (conspicuous publication basis)
1
Email is publicly posted — on a company website, LinkedIn profile, or professional directory. Not scraped from a database without a clear source.
2
No refusal notice — the publication is not accompanied by a statement that the person does not want unsolicited commercial messages at that address.
3
Message is role-relevant — your email must relate to the recipient’s business functions, not just be sent to any address at a target company. A pitch for email infrastructure to a CTO or VP Engineering satisfies this. A pitch for unrelated products does not.

GDPR in Practice

GDPR governs the processing of personal data — and email addresses are personal data. Before you can send a marketing email to an EU resident, you need a lawful basis under Article 6 for processing their email address. The two most relevant bases for email marketing are:

Consent (Article 6(1)(a)) — freely given, specific, informed, unambiguous, and demonstrable. Required for B2C email marketing to EU consumers in most EU member states. Cannot be bundled into terms and conditions. Must be as easy to withdraw as to give.

Legitimate interest (Article 6(1)(f)) — you can process personal data without consent if you have a legitimate interest, the processing is necessary to achieve it, and your interests are not overridden by the individual’s rights. For B2B email marketing, this is the most commonly used basis — but it requires a documented Legitimate Interest Assessment (LIA) that has been actually conducted, not just assumed.

GDPR also interacts with the ePrivacy Directive through the lex specialis principle (confirmed by the CJEU in November 2025): where the ePrivacy soft opt-in exception applies, you do not need a separate GDPR lawful basis. But where it does not apply — such as first-contact B2C cold email — GDPR consent requirements kick in fully.

Managing All Three Laws — The Practical Approach

Most enterprise senders handle multi-jurisdiction compliance with a tiered contact model: segment your list by recipient geography, apply the strictest relevant law to each segment, and use your consent infrastructure to enforce sending rules automatically.

Segmentation approach for multi-jurisdiction compliance
Terminal / Compliance Config Console / Policy
Segment A — US recipients:
  Rule: CAN-SPAM applies
  Requirement: Opt-out mechanism, physical address, honest headers
  Cold email: Permitted without prior consent
  Unsubscribe: Process within 10 business days

Segment B — Canadian recipients:
  Rule: CASL applies
  Requirement: Express OR valid implied consent before first send
  Cold email: Only if conspicuous publication basis satisfied
  Unsubscribe: Process within 10 business days (link valid 60 days)

Segment C — EU/EEA recipients:
  Rule: GDPR + ePrivacy applies
  Requirement: Documented lawful basis (consent or LI with LIA)
  Cold email B2B: Permitted with documented LIA
  Cold email B2C: Requires prior consent in most member states
  Unsubscribe: Process promptly (no fixed day limit, but immediate is standard)

When law is unclear: Apply strictest applicable rule
When contact location unknown: Apply GDPR + CASL standards as default

The worst approach — and the most common — is applying a single global unsubscribe flag and treating all contacts as subject to one law. A contact who unsubscribed under CAN-SPAM (US opt-out) may still be reachable under CASL’s rules if they have an existing business relationship and the implied consent period hasn’t expired. Conversely, a US-based contact working for an EU company may be subject to GDPR for their work email data. Geography of recipient residence, not sender location, determines which law applies.

📋 Real consequence — the purchased list problem across all three laws

Purchased email lists violate all three laws simultaneously, though for different reasons. Under CAN-SPAM, purchased lists may include addresses with prior opt-outs you have no record of. Under CASL, the list seller’s data collection almost never created valid consent for your specific organisation to send commercial messages — the $1.1M CAD fine for purchased list use made this clear. Under GDPR, the original data subjects never consented to their data being processed by you, and there is no documented lawful basis. A single purchased list campaign exposes a sender to enforcement actions under all three frameworks at the same time.

Last updated: March 5, 2026

US State Laws — Beyond Federal CAN-SPAM

CAN-SPAM preempts state anti-spam laws but does not preempt state privacy laws. As of 2025, eight additional broad state privacy laws are in effect across the US — California (CPRA), Virginia (VCDPA), Colorado, Connecticut, Utah, Montana, Oregon, and Texas — each with its own consent provisions, opt-out rights, and data subject access requirements. For email marketing specifically, the most significant is California’s CPRA, which gives consumers the right to opt out of the “sale” of their personal data, a category that may include sharing email lists with marketing partners.

The operational implication: a contact database with US recipients cannot be managed under a single federal CAN-SPAM framework. At minimum, California residents require CPRA-specific treatment. As more states enact broader privacy laws, the trend is toward treating all US recipients with GDPR-equivalent standards as a practical simplification — a higher bar, but a single consistent process.

Record-Keeping — What Each Law Requires

All three laws require you to prove compliance when challenged, but they specify different records:

CAN-SPAM records

  • ✓ Suppression list with opt-out dates
  • ✓ Physical address used in each campaign
  • ✓ Opt-out mechanism functionality logs
  • ✓ Third-party sender agreements

CASL records

  • ✓ Consent records: type, date, IP, form URL
  • ✓ Implied consent basis and expiry dates
  • ✓ Unsubscribe logs with timestamps
  • ✓ Retained for 3 years minimum

GDPR records

  • ✓ Lawful basis documented per processing activity
  • ✓ Consent records with version of consent text
  • ✓ Legitimate Interest Assessments (LIAs)
  • ✓ Data processor agreements (DPAs)
  • ✓ Records of processing activities (Article 30)

The practical recommendation: implement GDPR-equivalent consent and record-keeping across all segments as your baseline. GDPR records satisfy CASL requirements for consent documentation. CAN-SPAM’s opt-out records are a subset of what GDPR records cover anyway. A single robust consent architecture that meets GDPR standards is operationally simpler than three separate compliance systems — and positions you for any future regulatory changes in the US or Canada.

The Practical Compliance Matrix: Sending to Mixed Audiences

Commercial email programmes sending to audiences across the US, EU, and Canada simultaneously face the practical challenge of applying three different legal frameworks to a single sending operation. The compliance matrix approach resolves this by identifying the strictest requirement in each dimension and applying it universally.

For consent, CASL requires the strictest standard — express consent for most commercial messages, with limited implied consent exceptions. Applying CASL-standard consent (double opt-in) to the entire list satisfies CAN-SPAM (which requires no prior consent) and GDPR (which accepts consent as a lawful basis) simultaneously. The double opt-in confirmation rate lost by applying the stricter standard (typically 20-30% of initial signups who do not confirm) is recovered in list quality — the confirmed subscribers have lower complaint rates and higher engagement than single opt-in lists of equivalent nominal size.

For unsubscribe processing, all three laws require processing within 10 business days, but best practice (and implicit GDPR interpretation) is immediate processing. Configuring unsubscribe processing to execute within 60 seconds of any opt-out request — via one-click POST, web form submission, or FBL complaint — satisfies all three laws simultaneously and exceeds their requirements by days.

For record retention, CASL requires consent records be retained for 3 years after the last commercial message sent to that address. GDPR requires records be retained only as long as processing continues plus the statute of limitations for regulatory complaints. CAN-SPAM has no specific retention requirement but FTC enforcement standard requires demonstrating compliance. Applying CASL’s 3-year retention standard universally satisfies all three laws and provides the documentation depth needed for regulatory defence in any jurisdiction.

Production Deliverability & Legal Recommendation

Regulatory compliance is an architectural guarantee, not merely a policy checkbox. Attempting to manage compliance risks through shared email pools or manual suppression spreadsheets inevitably results in statutory exposure, ISP rate limits, and carrier-level blocklisting. Enterprise senders must maintain complete physical IP isolation, cryptographic DNS alignment, and automated in-band suppression processing across dedicated bare-metal MTA infrastructure.

Compliance Engineering Roadmap

Step 1 (Cryptographic & Header Alignment): Enforce strict DMARC (p=reject), FCrDNS reverse pointers, and RFC 8058 one-click List-Unsubscribe headers.
Step 2 (Audience & Suppression Sync): Implement automated webhook hooks to suppress opt-outs and invalid recipients instantly across all fleet nodes.
Step 3 (Continuous Telemetry & Archival): Ingest real-time ISP feedback loops (Google Postmaster, Microsoft SNDS, Yahoo CFL) and maintain tamper-proof, immutable delivery logs.

FD
Fred Dawson

Deliverability Architect & MTA Systems Engineer at AutoSMTP. Specialises in dedicated MTA cluster design, carrier-grade IP warming protocols, and ISP reputation telemetry across high-volume sending fleets.

Enterprise Mail Infrastructure

The AutoSMTP Dedicated Outreach Fleet Advantage

AutoSMTP provisions and manages enterprise-grade PowerMTA and KumoMTA clusters on dedicated bare-metal servers. Complete domain isolation, automated gas-pedal warming, and proactive deliverability telemetry.

Turnkey Dedicated Bare-Metal Clusters

Pre-configured PowerMTA and KumoMTA installations on enterprise hardware with dedicated IPv4 subnets and predictable flat pricing.

Automated Gas-Pedal IP Warming

Dynamic ramp-up algorithms that modulate hourly dispatch volume against real-time deferrals and Google Postmaster spam ratios.

Native FBL & Socket Interceptors

Automated RFC 3464 bounce ingestion, Yahoo/Outlook CFL complaint webhooks, and instant in-band suppression sync across all fleet nodes.

Strict Cryptographic Alignment

2048-bit DKIM key rotation, strict DMARC enforcement (p=reject), FCrDNS PTR verification, and automated TLS cipher hardening.

Ready for Dedicated Sending Infrastructure?

Eliminate shared pool throttle penalties and take complete control over your mail delivery with custom-tuned MTA clusters.

Deploy Dedicated MTA Fleet →