Keep Email Address Validation Separate From Permission

In Migma, an address can be technically valid and still be ineligible for marketing. Keep validation results separate from subscription permission, and never let an improved validation result silently restore a person’s marketing status.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 13, 2026.

We recommend using Migma’s documented subscription and validation filters together because they describe different properties of a contact. The product’s sending rules require permission-based marketing and exclude bought, scraped, and similar address sources. Technical address validation cannot supply that missing relationship.

Two questions, two records#

The validation record asks what is currently known about the address. The permission record asks what kind of communication the person chose and whether that permission remains active. A suppression adds another exclusion that must be respected rather than folded into a convenient “good contact” score.

Imagine a former subscriber who unsubscribed last month. A new validation check says the mailbox remains valid. That result updates the technical record; it does not undo the person’s choice. Equally, an opted-in subscriber whose address becomes unknown has not withdrawn permission merely because a validation provider cannot give a conclusive answer.

Treat these as different state changes with different evidence and owners.

Build a two-axis admission matrix#

This is an original, deliberately conservative campaign-planning matrix. It is not a description of automatic Migma enforcement for every row.

“Current valid” still does not guarantee inbox placement or human engagement. The matrix simply prevents one technical field from answering every eligibility question.

Migma documents an optional risky-address exclusion and a daily revalidation process for subscribed contacts with old checks. The sweep is capped, so a daily job does not prove every stale contact has been refreshed by the next campaign. Inspect the actual status and observation time needed for your audience decision.

Test transitions rather than only the final count#

Use synthetic records in a non-sending review process. Give one record withdrawn permission with a new valid result, another active permission with an invalid result, and a third active permission with a stale valid result. Apply the proposed admission logic and inspect the reason each record is included or held.

Then change only the validation field. The withdrawn record must remain excluded. Change only the permission evidence on a different record and confirm that technical risks remain visible. These exercises expose an implementation or import mapping that mistakenly treats either status as a universal “sendable” switch.

Keep the matrix and expected results with the import or segmentation specification. A final audience count can look reasonable while one forbidden transition is hidden inside it.

Preserve meaning during imports and corrections#

When a source file arrives, document which field owns subscription status and which owns validation. Do not use a supplier’s single “verified” column as both. Ask what was verified, when, and by whom before mapping it to a campaign decision.

If a contact corrects an address, keep evidence of the correction and the existing permission scope. Avoid automatic assumptions about whether a different address belongs to the same person. Resolve identity and permission through the organization’s approved process.

Use skipped-recipient reconciliation after a campaign to understand actual exclusions. This article defines the meaning of states before admission; it does not report a live enforcement test. The next step is to review the field mapping for one upcoming import and explicitly forbid validation-driven resubscription.