| 开发者 | rahul1099 |
|---|---|
| 更新时间 | 2026年9月23日 17:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
mail() function by default, which many hosts throttle or block outright — so the message never arrives and nothing on the site says so.
This plugin replaces that transport and then keeps working after the swap, which is the part most setups leave out:
cybexsoft-smtp folder to /wp-content/plugins/, or install the zip via Plugins → Add New → Upload Plugin.PHP 7.4 through the latest stable release.
Not on any normal host. Passwords, API keys and OAuth tokens are encrypted before they are written to the database (XSalsa20-Poly1305 via PHP's sodium extension), so a leaked database backup or an SQL injection in some other plugin does not expose working mail credentials. The key is derived from your site's WordPress salts; if you rotate your salts on a schedule, define CYBEX_SMTP_ENCRYPTION_KEY in wp-config.php first so stored credentials survive the rotation.
Sodium has been compiled into PHP by default since 7.2, so it is present on every version this plugin supports. The one exception is a host that has deliberately built PHP without it — there is then nothing to encrypt with, and credentials are stored as you typed them. If that matters to you, ask your host whether sodium is enabled, or look for it in a phpinfo report.
Either way, you can keep a credential out of the database entirely by defining it in wp-config.php — CYBEX_SMTP_PASSWORD, CYBEX_SMTP_SES_PASSWORD, CYBEX_SMTP_SENDGRID_API_KEY, CYBEX_SMTP_MAILGUN_API_KEY, CYBEX_SMTP_BREVO_API_KEY or CYBEX_SMTP_SMTP2GO_API_KEY. A defined constant overrides whatever is stored, and is never written back to the database.
If sodium is missing and a credential is stored anyway, the plugin now says so in the admin rather than leaving you to find out from this page.
Click Get Pro for Free in the plugin header (or next to Settings on the Plugins screen), fill in the short form, and we will email you the Pro download along with your license key. The download is a separate plugin, Cybexsoft SMTP Pro, which you install alongside this one: Plugins → Add New → Upload Plugin, then activate. Keep Cybexsoft SMTP active — Pro extends it and will say so if it is missing. Your settings and email log stay exactly where they are, and everything Pro adds appears on the same settings screen, so there is still only one place to configure anything.
No. They are two separate plugins, so an update to this one cannot touch the other. Update either from the Plugins screen whenever you like. It used to be a real risk, and this is why the two were separated. Pro was once shipped as this same plugin with the extra code included, which meant an update from WordPress.org replaced the whole directory and took the Pro code with it — leaving the license behind and the features gone. Nothing to watch out for now.
The License tab in Cybexsoft SMTP. Paste the key we emailed you there. With the Pro plugin not yet installed the key is saved but shown as unverified, because nothing on this side can check one — activating Cybexsoft SMTP Pro verifies it.
The form sends its request through the very mailer this plugin configures, so a site that has not finished setting one up cannot email us either. When that happens the form offers a link that opens the same request in your own email app instead — nothing is lost.
A message that was deliberately not sent, rather than one that failed. It appears when your block list stops a message before it reaches your mailer — the row records who it was for and which rule matched. Blocked rows are counted separately from failures and left out of your delivery rate, because nothing was ever handed to a mail server.
One small row is written per message, on the request that sends it. The log is indexed on the columns the screens filter by, and Pro adds a retention window that prunes old rows nightly if you would rather not keep them forever.