Every email a WordPress site sends — password resets, order confirmations, form notifications — goes through one mailer configuration. When mail stops arriving, this is the first thing worth reading.
email/get-delivery-settings returns which mailer is in use, the address and name the site sends as, and whether those are forced over what individual plugins request.
At a glance
| Ability | email/get-delivery-settings |
| Toolset | Email Delivery — toolset/wp-mail-smtp |
| Group | Email Delivery › Delivery |
| Requires | WP Mail SMTP, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
No password, API key or token is ever returned. Each credential is reported only as set or not set — which is the fact you actually need when diagnosing, and is safe to put in a chat transcript.
Everything withheld is listed explicitly under withheld, so you can tell an empty setting from a hidden one. That distinction matters: a missing API key and a redacted API key look identical otherwise, and only one of them is a bug.
The forcing flags are worth attention. With from_email_force on, a plugin that carefully sets its own sender is overridden — which is usually what you want for deliverability, and occasionally the reason a transactional email looks wrong.
Input
This ability takes no input.
What comes back
| Name | Type | What it is |
|---|---|---|
mailer | string | Which mailer the site sends through. |
from_email | string | The address the site sends from. |
from_name | string | The name the site sends as. |
from_email_force | boolean | Whether that address overrides what plugins ask for. |
from_name_force | boolean | Whether that name overrides what plugins ask for. |
return_path | boolean | Whether the return path is set to match the from address. |
credentials_set | object | Per-credential set / not set, with no values. |
withheld | array | Which settings were deliberately not returned. |
configured_groups | array | Which mailer configuration groups hold settings. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
What address does this site send email from, and is it forcing it?
It resolves to one call:
{
"ability": "email/get-delivery-settings",
"parameters": {}
}Worth knowing
- Safe to run and safe to quote — no secret leaves the site.
- This reads configuration. It cannot tell you whether mail actually arrives;
email/send-test-emailis the only thing that can. - If mail is failing,
email/get-delivery-statusis the better first call — it reads the same settings and adds the last recorded failure.
Related abilities
- Diagnose Email Delivery — the same settings plus what is wrong
- Update Email Delivery Settings — change the sender
- Send a Test Email — prove delivery end to end
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category