corestack_ email_ get
Read a site's email sending.
When to use it
Read how a row sends email: whether a sending domain is set up and verified, the DNS records it needs and which are found, the sender, and whether a test email can be sent.
The top level is the default sending domain. domains[] lists every sending domain of the row, the default first: its state, the From domain it carries (from_domain), whether the site sends through it yet (active), its records and Cloudflare zone, its last test, its newest email change (operation_id: follow it with corestack_site_operation_get), and what can be done with it (can_test, can_rotate, can_make_default, can_remove, each with its reason when it cannot). add says whether another sending domain can be added (corestack_email_domain_add) and why not. On a Magento 2 row, store_mapping lists each store, the From addresses it sends as, and the sending domain each goes through (via: own, pending until the new domain verifies, or default; warn: no_domain when no sending domain matches its From domain, capitals when the address has capitals in its domain); it is read from Magento in the background and is null until the first read answers.
On a preview row (a staging or development environment, or a site with no domain attached yet) mailpit says where its mail is caught: url, catches and note. catches is all, or php_mail on a WordPress site whose platform plugins are turned off: then only email sent with PHP mail is caught, an SMTP plugin with its own live credentials can send real email, and note says so in the person's words (corestack_site_platform_plugins_get shows the setting). On a staging or development environment role_held is the sentence corestack_email_enable is refused with there.
Ask for it
Using the Corefinity MCP server, call corestack_email_get with site_id 4211. (Read a site's email sending.) Tell me what it returned.Inputs
At least 1.
Example call
{
"name": "corestack_email_get",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
deleted | The site is deleted (in its grace period); restore it with corestack_site_restore_deleted first. |
provisioning | The site is still being created; wait for corestack_site_provisioning_get to finish. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |