Skip to content
Documentation

Your EMCP guide

Answers from our docs

YOUR CHAT, YOUR CHOICE

Before we chat

MSR Builds processes your question and up to four recent messages on our server to answer from the EMCP docs. AI is optional and needs your separate permission.

The chat is kept in this page's memory, not saved as a conversation in our database or browser storage. Our hosting and security services process connection information, such as your IP address, to prevent abuse.

Cloudflare Turnstile checks your browser and connection to prevent automated abuse when you send a question. No login is required.

Please leave out personal, sensitive or confidential information, passwords and API keys.

You can withdraw consent and clear this page's chat at any time. This cannot undo a request already sent or erase provider/security records.

Chat privacy, retention & your rights ↗ · Privacy contact

Starting chat consents to this processing. You can browse our docs without using the chat.

WP Mail SMTP

New in 3.21.1 (free), and in EMCP Lite 1.0.5 on WordPress.org. Two dispatcher tools work with WP Mail SMTP 4.10.3:

ToolDefaultPurpose
wp-mail-smtp-readOnThe active mailer and your test receipts (2 operations)
wp-mail-smtp-writeOffSend one test email (1 operation)

Enable the write tool under Tools > Plugins > WP Mail SMTP.

Requirements

Section titled “Requirements”
  • WP Mail SMTP 4.10.3 exactly, on a single site. Another version answers unsupported_version; multisite answers unsupported_environment.
  • An administrator (manage_options) with WP Mail SMTP’s own manage capability.
  • FluentSMTP must not be active. Two SMTP plugins compete for WordPress mail, so a test, dry run included, answers competing_mailer.

Operations

Section titled “Operations”
OperationToolWhat it does
statusreadWP Mail SMTP version, the mailer, whether SMTP sign-in is on (SMTP only)
test-statusreadThe stored receipt for a request_id you sent
send-testwriteOne plain-text test to recipient, with a new request_id and confirm: true

request_id is a UUID version 4 your AI generates. recipient is one email address.

How a test is sent

Section titled “How a test is sent”
  1. EMCP stores a receipt for the request ID and records the attempt in History. If History cannot be saved, nothing is sent (history_failed).
  2. WP Mail SMTP’s own test email is sent once, as plain text.
  3. The receipt is updated and read back.

Repeating a request ID returns the stored receipt and never sends again, even when the first outcome was unknown. The same ID with a different recipient or user answers request_conflict. Only one test runs at a time (send_busy).

Receipt states

Section titled “Receipt states”
StateMeaning
acceptedThe mail transport accepted the message. It does not prove inbox delivery.
failedWP Mail SMTP reported a failure.
interceptedAnother plugin stopped WordPress mail before it reached WP Mail SMTP.
unknownThe outcome could not be confirmed or saved. The request is never resent.
not_sentThe History record failed, so nothing was sent.

Receipts are kept per user: test-status only returns your own.

Limits

Section titled “Limits”
  • No passwords, API keys, tokens, message bodies or raw settings are ever returned.
  • No settings changes, email logs or resends.
  • Sending cannot be undone; History records each attempt as irreversible.