| 开发者 | TigrouMeow |
|---|---|
| 更新时间 | 2026年8月13日 22:20 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wp-config.php instead of the database.meow-mailer folder to /wp-content/plugins/, or install it from the Plugins screen.Not for routing, no, and that's on purpose. One active provider keeps configuration simple and predictable, and you can switch any time in Settings. What you can do is name a second one as a fallback: it never touches your email until the main provider refuses one, so nothing is lost to a bad afternoon.
If you have a second provider account, use that. If you don't, pick WordPress: it hands the email to your own server, which is nobody's idea of good deliverability, but it is always there and it needs no setup at all. Delivered imperfectly beats not delivered when it's a password reset. If you do use a second provider, publish its SPF and DKIM records for your domain, exactly like your main one. Otherwise the rescued email is accepted, delivered, and quietly filed as spam, which is harder to notice than a plain failure. Test it with the Test Fallback button rather than waiting to find out during an outage.
Yes. Set a Return Path in Settings and non-delivery reports go there instead of to your From address, which is left exactly as recipients see it. Leave it empty and bounces follow the From address, as they always have.
This is the SMTP envelope sender, so it applies to Generic SMTP. The API providers put their own envelope around your message and handle bounces on their own side, so the field does nothing there. If you need a different bounce address per email, filter mwmail_return_path, which receives the address and the message it belongs to.
For SMTP and API providers, credentials are stored in the WordPress database. You can instead define them as PHP constants in wp-config.php (e.g. MWMAIL_SMTP_PASSWORD) to keep them out of the database. Gmail, Microsoft 365 and Zoho Mail use OAuth 2.0, so no password is ever stored.
When enabled, no email is sent. Every message WordPress tries to send is recorded in the log instead. Ideal for staging sites where you don't want real emails going out.
Yes, and you can set it up once for the whole network. Activate it as usual (network activate works too), then on the main site turn on Shared Settings: every site of the network will send through the same provider, configured once from the main site. Subsites see that section as managed elsewhere and cannot change it, so nobody can reconfigure the network by accident. You decide how far the sharing goes. The provider is always shared once the option is on. The sender details (From address, name, Reply-To) and the delivery options (background send, logging, retention) are each optional, so you can share the mail account but let every site keep its own From address, which is usually what you want since each site has its own domain. Email logs are never shared. Each site keeps its own log and only ever sees its own emails. Leave Shared Settings off and nothing changes: every site configures itself, exactly like a standalone install.
Yes. Meow Mailer intercepts WordPress's standard wp_mail(), which is what those plugins use.
When enabled, the page is returned to your visitor immediately and the email is sent a moment later in the background, so a slow mail server never slows down your site. The email shows as "Pending" in the log, then updates to Sent or Failed.
Both use OAuth 2.0, so no password is stored. Create an OAuth app (Google Cloud Console for Gmail, Azure Portal for Microsoft 365), paste the Client ID and Secret into the provider settings, add the shown redirect URI to your OAuth app, then click Connect.
mwmail_return_path filter.