內容簡介
Lean SMTP 是一款 WordPress 外掛，能透過真實郵件服務發送郵件，提升郵件送達率。此外掛設計簡潔，無需付費，並提供多種傳輸方式及設置，確保用戶隱私。
【主要功能】
• 支援多種郵件傳輸方式
• 內建郵件發送日誌功能
• 提供失敗警報通知
• 支援 WP-CLI 操作
• 離線模式可記錄郵件
• 無需創建帳戶或付費功能
外掛標籤
開發者團隊
原文外掛簡介
Lean SMTP makes WordPress send its mail through a real mail service instead of the host’s default PHP mail, which improves deliverability. It is deliberately small: a handful of transports and a handful of settings.
Everything is free. There is no pro version, no paid add-ons, no locked features, no account to create, and no upsell banners in the admin. Every mailer, the send log, the failure alerts, WP-CLI, offline mode and encrypted credential storage are all in this plugin, for everyone. Nothing phones home. The plugin sends no telemetry or usage data anywhere, and it makes no network requests other than delivering your mail to the provider you configured.
Website: https://leansmtp.com
Every provider below also offers plain SMTP, so the SMTP transport alone covers all of them. The API transports exist for hosts that block outbound mail ports (25/465/587), which is common on shared hosting and some managed platforms.
SMTP: any host/port with TLS, SSL, or no encryption, optional username/password.
Amazon SES (API): the SES v2 API, signed with a hand-rolled AWS Signature V4 signer, so no AWS SDK is bundled.
Mailgun (API): US or EU region, sending the message as MIME so attachments and formatting survive untouched.
Resend (API): a single API key, nothing else to configure.
Gmail / Google Workspace (API): for Workspace domains, with two ways to authenticate. A service account with domain-wide delegation (a short-lived JWT signed in-plugin, no consent screen and no refresh tokens), or OAuth2 where you authorize a single mailbox in the browser instead of needing a Super Admin to set up delegation. Either way the plugin sends through the Gmail API with no bundled Google SDK. (Consumer @gmail.com accounts are not supported; use SMTP with an App Password for those.)
Offline: record every message and send nothing, for staging sites that must never mail real customers. wp_mail() still reports success, so plugins behave exactly as they would in production.
From identity: set the From name and address, and optionally force them over anything another plugin sets.
Reply-To: a site-wide default for replies, useful when the From address is a no-reply. A Reply-To the message set itself is always kept.
wp-config.php overrides: pin any setting in code instead of the database, so credentials can live in environment variables and never diverge between environments.
Failure alerts: an admin notice when mail stops going out, so a broken mailer isn’t discovered via missed password resets. It clears itself once mail works again.
WP-CLI: wp lean-smtp test and wp lean-smtp status.
Test email: a button on the settings page to confirm your configuration works.
Send log: optional. Records each send (recipient, subject, result) on an Email Log screen with paging, a status filter, search, and per-row or bulk delete. Stored in your own database and never sent anywhere. The message headers, attachment filenames and body can each be recorded too, behind their own settings and off by default.
Encrypted secrets: stored passwords and API keys are AES-256 encrypted, keyed to your site salts.
Deliberately not included: consumer-Gmail and Microsoft 365 OAuth. Using the gmail.send scope with a consumer (external) app would require Google’s app-verification / security-assessment process, or it hands out refresh tokens that expire after a week — more machinery than the rest of this plugin combined. The Workspace OAuth that does ship sidesteps that because it uses an Internal consent screen, which needs no verification and issues lasting refresh tokens. For a consumer @gmail.com account, use SMTP with an app password.
Configuring in wp-config.php
Any setting can be defined as a constant instead of saved in the database. The constant name is the option name in upper case, and it always wins. The settings page shows the field as read-only and names the constant, so what you see is always what is in force. Removing the constant restores whatever was saved before.
define( 'LEAN_SMTP_MAILER', 'ses' );
define( 'LEAN_SMTP_FROM_EMAIL', '[email protected]' );
define( 'LEAN_SMTP_SES_REGION', 'us-east-1' );
define( 'LEAN_SMTP_SES_ACCESS_KEY', 'AKIA…' );
define( 'LEAN_SMTP_SES_SECRET_KEY', getenv( 'SES_SECRET_KEY' ) );
Secrets defined this way are used as-is and are never written to the database. Run wp lean-smtp status to see every setting and where it came from.
External services
Lean SMTP sends email through whichever mail service you configure. The plugin connects to a provider’s HTTPS API only when you have selected an API transport and your site sends mail. It then transmits the message being sent (recipients, subject, body, headers, and any attachments) along with the credentials you entered, so the provider can authenticate the request and deliver the message. Nothing is sent until you configure and select a transport, and the plugin contacts no other services: there is no telemetry, tracking, or analytics.
The provider you choose is the data controller for the mail you route through it. Review its terms and privacy policy:
Amazon SES: sends to email.{region}.amazonaws.com. Terms: https://aws.amazon.com/service-terms/ · Privacy: https://aws.amazon.com/privacy/
Mailgun: sends to api.mailgun.net or api.eu.mailgun.net. Terms: https://www.mailgun.com/legal/terms/ · Privacy: https://www.mailgun.com/legal/privacy-policy/
Resend: sends to api.resend.com. Terms: https://resend.com/legal/terms-of-service · Privacy: https://resend.com/legal/privacy-policy
Gmail / Google Workspace: authenticates at oauth2.googleapis.com and sends to gmail.googleapis.com. Terms: https://workspace.google.com/terms/premier_terms/ · Privacy: https://policies.google.com/privacy
The SMTP transport connects only to the host you configure and bundles no third-party service. The Offline mailer connects to nothing at all: messages are written to the local send log and never leave your server.
