When are custom thresholds worth it for Physical address included?
When are custom thresholds warranted?
Set `senderPostalAddress` when you want the strong form of the check: with your real address supplied, a footer carrying somebody else's address, or a stale address from a previous office, fails instead of passing. Set `expectedAddressCountries` when you send from or to Canada, so CASL's anchors run alongside or instead of the US ones. Extend `recipientAddressLabels` if your templates label recipient addresses in wording the defaults do not cover, or in a language other than English.
When should you stay on Standard?
Stay with presence-only detection while your address is genuinely in flux — mid-move, mid-restructure — because a check configured to an address you are about to leave will fail correct mail. Keep the default country list if you send only to US recipients, since adding anchors for regimes you are not subject to only widens what counts as a pass. If your mail is transactional, the right answer is not a narrower configuration but leaving the check out.
What do you trade away?
Supplying `senderPostalAddress` is the strictest and therefore the most maintenance-sensitive setting: the moment your registered address changes, correct mail starts failing until someone updates the value, and the temptation is to clear it rather than correct it. Adding countries widens the set of formats that satisfy the check, which can let an address that is valid somewhere pass where you needed one valid locally. Extending recipient labels reduces false positives but each addition is also a phrase the check will now decline to count, so an over-broad label list can hide a genuinely missing sender address.
Community Standard vs org Custom
The Standard configuration transcribes what the statute and postal standards require rather than what any organisation prefers, which is why presence-only is the default and country anchors are explicit. A Custom configuration — especially your own postal address — is legal information and should come from whoever owns the entity's registered details, not from a marketing template. Because this check's output is the kind of thing that ends up in a compliance file, record when the address value was last confirmed.
Worked override examples
A US company sets `senderPostalAddress` to its registered office address, upgrading the check from "an address is present" to "our address is present" and catching footers still showing a previous office. A sender with Canadian subscribers sets `expectedAddressCountries` to `["US", "CA"]` so CASL anchors run and Canadian-format addresses are recognised properly. An ecommerce brand whose confirmation templates print delivery details adds its own wording to `recipientAddressLabels`, so the buyer's address is never mistaken for the sender's when the footer block is missing.
How does an agent call it with parameters?
{
"type": "email",
"validations": [
{
"id": "email-physical-address-present",
"parameters": {
"expectedAddressCountries": [
"US"
],
"senderPostalAddress": "",
"recipientAddressLabels": [
"ship to",
"shipping address",
"deliver to",
"delivery address",
"bill to",
"billing address",
"sold to",
"your address"
]
}
}
]
}