Newsletter provider closes the account

What this means

The provider may have detected abuse, a compromised account, billing trouble, an unusual list import, policy violations, or deliverability risk. Do not create a new account and upload the same list before you understand the cause.

Your subscriber list is not enough by itself. A safe migration also needs consent status, unsubscribes, suppression records, templates, sending-domain configuration, and recent campaign history.

Warning signs

• You cannot sign in or send.
• The provider asks for a compliance, identity, billing, or security review.
• A campaign is stopped after unusual complaints or bounces.
• Subscribers report spam you did not send.
• API keys, integrations, owners, or sending domains changed unexpectedly.

Recover now

First 15 minutes

1. Read the provider notice carefully. Record the case number, stated reason, deadline, affected audience, and requested evidence.
2. Secure the primary email and provider account. Reset access from a trusted device, enable 2FA, remove unknown users, and revoke old API keys.
3. Pause connected automations. Stop forms, webhooks, scheduled sends, imports, and integrations that may keep creating the problem.
4. Open one factual appeal. Explain how contacts joined, what changed recently, and what you have already contained.
5. Do not email the list elsewhere yet. An incomplete export can omit unsubscribes or consent evidence.

Today

1. Export every available audience, consent field, subscription status, suppression list, template, campaign, automation, and report.
2. Compare recent imports and sends with signup records. Remove contacts without a clear permission trail.
3. Inspect the account for unauthorized campaigns, API use, users, integrations, and domain changes.
4. Prepare a plain status update on your website or social account if a promised send is delayed.
5. If the provider restores access, send a small monitored campaign before resuming normal volume.
6. If migration is required, import subscribed contacts and suppression data separately. Configure SPF, DKIM, DMARC, unsubscribe handling, and a gradual warm-up before a large send.

Verify recovery

• The provider confirms the account and sending function are active.
• Unknown users, API keys, campaigns, and integrations are gone.
• Subscribed, unsubscribed, cleaned, and suppressed contacts remain correctly separated.
• A small test reaches major mailbox providers without unusual complaints or bounces.
• Signup forms, consent records, unsubscribe links, and sending-domain authentication work.

Prepare now

Portability

• Audience data is exported regularly with consent and subscription status.
• Templates and essential campaign copy are stored outside the provider.
• Suppression and unsubscribe records can be migrated safely.
• Signup source, time, and permission evidence are retained.

Access and reputation

• Owners use named accounts, strong 2FA, and reviewed API keys.
• SPF, DKIM, and DMARC are documented and monitored.
• Imports require a clear source and permission check.
• Complaint, bounce, and abuse alerts go to a monitored address.

Practice

• A recent export can be opened and explains which contacts may legally receive email.

Common mistakes

• Uploading only active email addresses to a new provider. Missing suppressions can cause illegal or unwanted mail.
• Sending the full list immediately. A cold domain and sudden volume can damage deliverability.
• Blaming the provider before checking compromise. An attacker may have sent the abusive campaign.
• Keeping templates only inside the tool. You lose both audience and production assets together.
• Importing an old list without consent evidence. Age is not permission.

Sources

• Mailchimp: Export and back up account data
• Mailchimp: View or export contacts
• Mailchimp: Compromised accounts