Skip to main content

Validation policies and lists

The result verdict is the same for every customer. Two tools, set in the dashboard, adapt it to your rules: the validation policy, which produces finalDecision, and the allowlist and blocklist, which settle the matter for specific addresses or domains.

Validation policies​

A policy (Validation rules in the dashboard) lists what you reject. It applies to every call and feeds two fields of the response:

"finalDecision": "rejected",
"policy": {
"decision": "rejected",
"reasons": ["reject_disposable", "reject_role_account"],
"rejectedByClientConfig": true
}
RuleCode in policy.reasonsRejects when
Reject disposable addressesreject_disposablefeatures.disposable flags a disposable address
Reject malicious domainsreject_malicious_domainfeatures.maliciousDomains flags the domain
Reject trap domainsreject_typosquatfeatures.typosquat flags the domain
Reject generic accountsreject_role_accountcontact@, info@, support@… (noreply@ included)
Reject noreply addressesreject_no_replynoreply@, mailer-daemon@… only: contact@ is still accepted
Reject accept-all domainsreject_catch_allThe domain accepts any address
Reject consumer providersreject_free_providerGmail, Outlook, Orange… (B2B forms)
Reject inconclusive resultsreject_unknownresult is unknown
Reject offensive termsreject_on_profanityfeatures.profanity flags a term
Reject random local partsreject_on_random_detectionfeatures.randomDetection flags it
Minimum scorereject_low_quality_scorescore below the chosen minimum
Minimum domain healthreject_low_domain_healthDomain health below the chosen level (excellent → critical)
Reject VPN and Torreject_vpn_or_torThe call comes from an anonymising network
Reject hosting providersreject_datacenter_ipThe call comes from a hosting provider
finalDecision does not replace result

The policy evaluates only its own rules. An invalid address that no rule targets comes out with finalDecision: "accepted". Without a policy, finalDecision is always accepted. So decide on both: reject if result is invalid or if finalDecision is rejected.

Network rules and server calls

The reject_vpn_or_tor and reject_datacenter_ip rules look at the IP that calls the API. On a server key, that is your own server, hosted in a data centre: reject_datacenter_ip would then reject every address. Keep these rules for widget policies.

Which policy applies​

  1. The policy linked to the API key, if the key has one.
  2. Otherwise, the policy marked as default in the organisation.
  3. Otherwise, none: everything is accepted.

Create one policy per use (B2C form, B2B form, newsletter widget…) and link it to the matching key.

Allowlist and blocklist​

Exception lists in the dashboard. Each entry targets a specific address or a whole domain.

ListEffect on verification
AllowlistSMTP does not run (no credit). The score is at least 95. The verdict follows syntax and DNS.
BlocklistSMTP does not run (no credit). The verdict is invalid, with features.listCheck.details.isBlacklisted: true.

The same value cannot be on both lists: adding it is refused with the code LIST_CONFLICT and the dashboard offers to move the entry.

The lists also apply to batches and to the widget. A key can ignore them by disabling its whitelist or blacklist checks.