## TL;DR
Omnivore scans imported lists for abuse signals like role addresses, disposable domains, and spam traps. Remove those segments, verify the remaining addresses with a proper validation service, and re-import; do not just re-upload the same file.

```text
mailchimp omnivore warning triggered list import
```

## Use this when
- Omnivore flags a CSV import with a warning or per-address charge.
- An import is stuck in the Omnivore review state.
- You bought or scraped the list and the warning rate is high.

## Not for this skill when
- Full account suspension for abuse, that needs Mailchimp compliance not a cleaner list.
- High bounce rate on an already-live audience.
- Double opt-in configuration questions.

## Steps
1. Read the Omnivore report and note which categories it flagged (abuse, spam traps, role-based). Verify: you can list the flagged categories, not just the total.
2. Delete the flagged segment from the file instead of arguing with it. Verify: the cleaned file has zero role or disposable addresses in a spot check.
3. Run the remaining addresses through an email validation service and drop anything invalid. Verify: the validation report shows deliverable status for every row.
4. Re-import the cleaned file into a fresh audience. Verify: Omnivore passes the import with no warning.
5. Turn on confirmed opt-in for future collection so the list never needs importing again. Verify: new signups confirm before they land in the audience.

## Variant phrasings
### omnivore warning mailchimp import blocked
Common phrasing of the block.
### mailchimp omnivore charge per email
The cost-angle search.
### how to get past omnivore warning
The remediation phrasing.

Compatibility: Mailchimp Standard and above; Omnivore runs on every list import regardless of plan.

## Why it happens
Omnivore protects Mailchimp's sending reputation by scoring every imported list. Lists that were scraped, bought, or collected without consent are full of spam traps and dead addresses, so the check flags them before a single campaign goes out.

## Edge cases / pitfalls
- Omnivore charges per cleaned email; a huge dirty list is expensive before it is useful.
- Splitting one dirty list into small imports to dodge the check is exactly the abuse it hunts.
- An import that passes Omnivore can still bounce hard; validation and Omnivore are two different gates.
- Scraped lists almost always fail Omnivore; buy validation, not excuses.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qBEKrztdspdWAwcrMD5FWw