> ## Documentation Index
> Fetch the complete documentation index at: https://docs.migma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# CAN-SPAM Checklist

> U.S. commercial email requirements and how Migma helps you comply

The **CAN-SPAM Act** sets rules for commercial email in the United States. You are responsible for your sending practices. Migma provides tools that help you meet common requirements, but this page is guidance—not legal advice.

<Info>
  For permission-based sending rules (no cold email), read [Permission-based sending](/get-started/what-you-can-send) first.
</Info>

***

## Before you send marketing email

<Steps>
  <Step title="Accurate header information">
    **From**, **To**, and **Reply-To** must be accurate and identify you as the sender.

    **In Migma:** Configure sender name, from address, and reply-to in project or domain settings. Use a monitored reply address—not `no-reply`—when possible.
  </Step>

  <Step title="Truthful subject lines">
    Subject lines must reflect the content of the message. Avoid deceptive patterns such as fake replies or urgent security alerts for promotions.

    **In Migma:** Email Preflight flags risky subject and content patterns. Use **Fix with AI** to revise copy before sending.
  </Step>

  <Step title="Physical mailing address">
    Commercial email must include a valid physical postal address.

    **In Migma:** Set your business address in compliance or brand settings so footers and preference pages can include it automatically.
  </Step>

  <Step title="Clear unsubscribe">
    Recipients must be able to opt out easily, without login or extra steps.

    **In Migma:** Marketing emails include unsubscribe handling through your sending setup and [Preference center](/audience/preference-center). Honor opt-outs promptly; suppressed contacts should not receive marketing sends.
  </Step>

  <Step title="Honor opt-outs quickly">
    CAN-SPAM requires processing opt-out requests within 10 business days. Faster is better for trust and deliverability.

    **In Migma:** Unsubscribe and suppression flows are designed for immediate effect on marketing sends. See [Suppression list](/sending-domains/suppression-list).
  </Step>

  <Step title="Monitor senders on your behalf">
    If agencies or teammates send for you, you remain responsible for their compliance.

    **In Migma:** Use team permissions and audit sending activity. See [Security & Compliance](/security/compliance) for access controls and logging.
  </Step>
</Steps>

***

## Quick checklist

<Check>Sender identity is accurate and matches your brand</Check>
<Check>Subject line matches email content</Check>
<Check>Physical address appears in the footer (where required)</Check>
<Check>Unsubscribe or preference link is visible and works</Check>
<Check>Contacts opted in to marketing (not cold lists)</Check>
<Check>Preflight run for compliance and deliverability warnings</Check>
<Check>Sending domain authenticated (SPF, DKIM, DMARC where applicable)</Check>

***

## Common mistakes

<AccordionGroup>
  <Accordion title="Promotional email marked as transactional" icon="triangle-exclamation">
    Using transactional sending flags for marketing content violates recipient expectations and CAN-SPAM intent. Send promotions only to contacts with marketing consent.
  </Accordion>

  <Accordion title="Missing or hidden unsubscribe" icon="eye-slash">
    Burying unsubscribe links or requiring login increases complaints. Complaints hurt deliverability for your entire domain.
  </Accordion>

  <Accordion title="Imported lists without consent" icon="file-csv">
    Purchased or scraped lists often fail CAN-SPAM and damage reputation. See [CSV Upload](/audience/csv-upload) and [sending rules](/get-started/what-you-can-send).
  </Accordion>
</AccordionGroup>

***

## Related pages

<CardGroup cols={2}>
  <Card title="Email Preflight" icon="check-double" href="/email-editor/email-preflight">
    Automated compliance, spam, and deliverability review.
  </Card>

  <Card title="Security & Compliance" icon="shield-check" href="/security/compliance">
    Full compliance overview including CASL and GDPR.
  </Card>

  <Card title="Acceptable use" icon="file-contract" href="/legal/acceptable-use">
    Platform policy for permission-based email.
  </Card>

  <Card title="Add sending domain" icon="globe" href="/sending-domains/add-domain">
    DNS authentication for trusted sending.
  </Card>
</CardGroup>