MME-Mail to SMTP
| 开发者 | mmeprowp |
|---|---|
| 更新时间 | 2026年10月7日 16:48 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
WordPress sends its email with
wp_mail(), which hands the message to the web server's own mail function. On most hosts that means it lands in spam, or does not arrive at all - and nothing on the site says so, because almost no WordPress code checks what wp_mail() returned. Sites routinely go weeks before somebody notices the receipts stopped arriving.
This plugin does two things about that. It routes your mail through a real mail service, and it makes failure visible.
Why this one and not one of the others
There are a great many SMTP plugins. Four things here are deliberate choices the others mostly do not make.
- No email log, on purpose. A table of every message this site has sent - recipients, subjects, often the body - is a standing liability sitting in your database waiting for the next breach, and it is the first thing most mailer plugins turn on. This one keeps no copy of what it sent. It tells you instead whether sending is working right now, what the last error was, and what is queued.
- A retry queue, in the free plugin. A message lost to a five-minute network fault is lost for good in most free mailers, because a failed send is simply a failed send. Here it is persisted and retried over the following hours, and a failure no retry can fix - an oversized attachment, a rejected recipient - is reported straight away rather than queued behind hope.
- Errors that name the misconfiguration. "The service account is not authorized to impersonate this mailbox, so authorize its client ID in Google Workspace Admin" - not "HTTP 401". Every provider's responses are mapped to the thing you actually have to go and change.
- Nothing is sent to the plugin's author. No registration, no activation check-in, no usage statistics, no telemetry of any kind, no account to create. The only servers contacted are the mail service you configured. The list is in External services below, and it is the whole list.
- Google Workspace, with a service account and domain-wide delegation. No consent screen, no refresh token, nothing that expires: the site signs a short-lived assertion whenever it needs a token.
- Gmail, with a standard OAuth sign-in, for an account that is not on a Workspace domain.
- SendGrid, Mailgun, Brevo, Postmark, Resend and SMTP2GO, with an API key.
- Any SMTP server, including services not named above.
wp_mail()returns an accurate result, andwp_mail_failedfires with a real error rather than a barefalse.- Once sends fail repeatedly - you choose how many in a row count as an outage - an admin notice appears and the Email delivery check under Tools, Site Health turns red and names the last error. One success clears both.
- Error messages name the actual misconfiguration. "The service account is not authorized to impersonate this mailbox", not "HTTP 401".
- A persistent retry queue holds a message that a transient fault would otherwise have lost, and retries it over the following hours. Failures no retry can help, such as an oversized attachment, are reported immediately instead of being queued behind hope.
- Hooks for your own monitoring:
mmoa_send_attemptedon every attempt,mmoa_send_failedon each failure,mmoa_send_failingonce an outage starts, andmmoa_send_recoveredwhen it ends.
- One MIME pipeline. Every connection here accepts a complete RFC 822 message, so what PHPMailer already built is what gets sent. Attachments, inline images, Reply-To, Cc, Bcc and custom headers are handled by WordPress core code rather than reassembled by hand.
- Credentials belong in
wp-config.php, and the plugin marks a field as pinned when a constant is set. Anything stored in the database instead is encrypted with libsodium. - A setup wizard that connects a mailbox, checks the credentials against the provider, and sends one real message - in that order, so you find out it works before you rely on it.
- Answers privacy requests through WordPress's own Tools, Export and Erase Personal Data.
- The plugin sends nothing to its author. No registration, no check-in, no usage figures, no telemetry of any kind.
安装:
- Install and activate the plugin.
- Go to MME-Mail to SMTP in the admin menu. The setup wizard opens on first run.
- Choose a mail service and enter its credentials, or sign in to Google.
- Send the test message the wizard offers. If it arrives, you are done.
wp-config.php instead of the database - for example define( 'MMOA_GOOGLE_SA_PRIVATE_KEY', '...' );. The plugin shows a field as pinned when a constant is set for it.屏幕截图:
常见问题:
Do I need a Google Workspace account?
For the service account connection, yes - domain-wide delegation is a Workspace feature. A plain @gmail.com account uses the Gmail OAuth connection instead, which works but keeps a refresh token.
My Gmail connection stops working every week.
Your Google Cloud consent screen is still in Testing status, which expires refresh tokens every seven days. Publish it to In production and reconnect.
Why does the service account connection say it cannot impersonate the mailbox?
Its client ID has not been authorized in Google Workspace Admin under Security, API Controls, Domain-wide Delegation, with the https://www.googleapis.com/auth/gmail.send scope. The error message names this too.
How large can attachments be?
About 2 MB. The API caps a single request at 4-5 MB, and a message on this path is base64-encoded twice, so the usable payload is roughly half the nominal limit. Oversized messages are rejected before sending, with a message saying so, rather than failing on the wire.
Where did my mail go? Is there a log?
Not in this plugin. It records no copy of what it sent - a mail log holding recipients and subjects is a standing liability, and this one deliberately does not keep one. What it does tell you is whether sending is currently working, what the last error was, and what is waiting in the retry queue.
Can another mailer plugin be active at the same time?
No. WordPress lets exactly one plugin take over sending, so one of the two would be configured and doing nothing - and which one wins depends on load order rather than on anything you chose. The plugin detects the common ones and says so on screen.
更新日志:
0.17.4
- Microsoft 365, Zoho Mail and Google one-click now appear in the connection picker, marked Pro. They come with MME-Mail to SMTP Pro, which is a separate plugin; choosing one explains where it comes from, or - when Pro is already installed - what is left to do: switch Pro on, or enter its licence. Nothing of those connections is inside this plugin.
- Add-ons can now contribute a way of connecting to an existing service - a new mode on a tile such as Google - and the sign-in block that goes with it, shown on the connection screen and in the setup wizard alike.
- Add-ons can add their own state to the connection screen, and are told before a connection is wiped so they can withdraw any access they granted elsewhere.
- Add-on screens can now use this plugin's own data-fetching hooks. Without them an add-on had to bundle a second copy of the same library, which cannot see the cache this app sets up and fails as soon as the screen renders.
- Fixed: a screen contributed by an add-on never appeared. The data this plugin passes to its admin app was being assigned over the top of the object the add-on had just registered into, wiping it a moment before the app read it - so the tab row looked exactly as it does with no add-on installed. The data is merged in now instead of replacing what is there.
- Fixed: disconnecting a connection could leave an add-on's sign-in credentials behind. The screen said every credential for the connection had been deleted, while a refresh token stored by an add-on's own sign-in flow stayed in the database. Add-ons can now have their credentials cleared with the rest. Nothing stored by this plugin itself was ever affected.
- Add-ons can now contribute their own screens to the admin app. A screen registered this way gets a tab of its own in the row, between Connections and Settings, and a route to match.
- An add-on's screen can be built from the same panels, buttons and form fields as the screens either side of it, so the page reads as one piece of software rather than two.
- Nothing changes on a site with no add-on installed. The tab row, the screens and every setting are exactly as they were.
- First public release.