Send a test email through the configured SMTP relay
POST /admin/system/smtp/test
Renders the admin_test template + sends it via the currently
configured Sender (SMTP / capture / disabled per the boot
mode). The recipient defaults to the calling admin’s own
email; an explicit to overrides for diagnosing relay-side
routing issues.
Synchronous — the response carries the outcome (sent + delivery mode) so the operator sees the failure immediately instead of digging in the job queue.
Gated on system.config.write (same gate as the SMTP
config-write surface).
Authorizations
Section titled “Authorizations ”Request Body
Section titled “Request Body ”object
Recipient override. When omitted, the server uses the calling admin’s email on file. Useful for diagnosing relay-side routing (e.g. send to an external Gmail account to verify deliverability).
Responses
Section titled “ Responses ”Test email accepted by the configured Sender.
object
True when the Sender accepted the message.
The boot-time Sender mode (informational).
The email the test was sent to.
Human-readable summary (e.g. “captured locally; not delivered”).
Malformed request
object
Human-readable error summary
Example
the request could not be completedAuthentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completedSMTP not configured (relay host empty).
object
Human-readable error summary
Example
the request could not be completed