List verification runs

Mailcheck validates an uploaded or connected mailing list and returns a status for each address. A Beam agent starts a run when a new list arrives, reads the per-address results, and applies your approved rule for each outcome. Valid addresses are written back as clean, invalid ones are marked for removal, and uncertain ones are tagged for a second look. It records the run summary where you keep your lists. A run with an unusually high failure rate, which often means a bad import rather than bad data, is handed to a person before anything is deleted.

Risk scoring per address

Beyond a pass or fail, Mailcheck rates how risky an address looks. A Beam agent reads that score for each record, compares it against the threshold you set, and files the address into the bucket your rule names, for example clean, review, or drop. It writes the score and the decision onto the contact so later sends can respect it. Addresses that sit right at your threshold, or that flip between runs, are set aside for a person, because a borderline score is a judgment call rather than a clear reject.

Disposable and role address filtering

Mailcheck flags disposable inboxes and role addresses such as generic team mailboxes. A Beam agent reads those flags, applies your policy for each type, and either suppresses the address or tags it for a lighter sending rule. It notes why each address was filtered so the choice is auditable. When a role address belongs to a known contact you still want to reach, or a domain you rely on starts returning disposable flags, the agent routes the case to a person instead of removing addresses that may matter to you.