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.

FluentSMTP

New in 3.21.1 (Pro). Two dispatcher tools work with FluentSMTP 2.4.1:

ToolDefaultPurpose
fluentsmtp-readOnStatus, connections, routing, health, delivery logs and test receipts (7 operations)
fluentsmtp-writeOffSend one test email through a connection (1 operation)

Enable the write tool under Tools > Plugins > FluentSMTP.

Requirements

Section titled “Requirements”
  • An active EMCP Pro licence.
  • FluentSMTP 2.4.1 exactly, on a single site. Another version answers unsupported_version; multisite answers unsupported_environment.
  • An administrator (manage_options) who can manage FluentSMTP.
  • WP Mail SMTP must not be active: a test answers competing_mailer.

Read operations

Section titled “Read operations”
OperationWhat it does
statusVersion, number of connections, whether simulation and logging are on
list-connectionsEach connection’s ID, provider and sender address
routingThe default and fallback connections and the sender mappings
healthFluentSMTP’s stored health report per connection; no live probe is made
list-logsDelivery log entries, newest first, filtered by status (sent, failed, pending), paged
get-logOne log entry by id
test-statusThe stored receipt for a request_id you sent

Log entries return ID, status, created and updated dates, retries and resend count. Recipients, subjects, headers and bodies are never returned, and neither are connection credentials.

Sending a test

Section titled “Sending a test”

send-test needs connection_id (from list-connections), recipient (one address), a new request_id (UUID version 4) and confirm: true.

  • The connection must have a sender address mapped to it in FluentSMTP’s routing, or the answer is connection_unavailable.
  • EMCP stores the receipt and records the attempt in History before sending; if History fails, nothing is sent.
  • FluentSMTP’s own test sender sends one plain-text email from the connection’s sender address.
  • Repeating a request ID returns the stored receipt and never sends again; the same ID with different input answers request_conflict.
StateMeaning
acceptedThe connection accepted the message. It does not prove inbox delivery.
simulatedFluentSMTP’s email simulation is on, so the message was logged, not sent.
failedFluentSMTP reported a failure.
interceptedAnother plugin stopped WordPress mail first.
unknownThe outcome could not be confirmed or saved. It is never resent.

The receipt also lists log_ids, the FluentSMTP log rows this send created.

Limits

Section titled “Limits”

No resends, routing or connection changes, log deletion or settings. Sends cannot be undone; History records each attempt as irreversible.