Changrid Email Delivery
| 开发者 | tuanpm094 |
|---|---|
| 更新时间 | 2026年10月31日 01:06 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
wp_mail() calls to a Changrid workspace through the dedicated, API-key-protected WordPress endpoint.
The plugin is free, and you can start sending with Changrid's Free plan. Upgrade only when you need more sending capacity, routing, retention, workspace capacity, or provider options.
Features:
- Uses workspace access and secret keys; no WordPress user password is shared.
- Start sending with the Changrid Free plan; no separate plugin license is required.
- Routes normal WordPress mail, including HTML and plain-text messages.
- Supports To, Cc, Bcc, and Reply-To addresses.
- Keeps the From identity protected by Changrid provider configuration while allowing an optional site-wide Reply-To address.
- Optional open, click, and unsubscribe tracking.
- Optional fallback to native
wp_mail()after a Changrid request error. - Sends one explicit test message from the settings screen.
- Checks credentials and send permission without sending an email.
- Keeps automatic workspace routing as the recommended default, with an advanced fixed-provider option for strict route control.
- Keeps a small local diagnostic log without recipient addresses, subjects, or message bodies.
- Supports constants in
wp-config.phpso production secrets do not need to be stored in the WordPress database.
wp_mail().
安装:
- Upload the plugin ZIP in Plugins > Add New > Upload Plugin, or copy the
changrid-email-deliverydirectory into/wp-content/plugins/. - Activate the plugin.
- Open Settings > Changrid Email.
- Create a workspace access key with
communications:sendpermission in Changrid. - Enter the access key and secret key, then save the settings.
- Optionally set a default Reply-To address for replies to website email.
- Press Check connection. This does not send an email.
- Keep Automatic workspace routing (recommended), or choose a fixed active provider under Advanced delivery routing and save again.
- Send one test to an address you control.
- Verify the accepted execution and final delivery state in Changrid before enabling production routing.
wp-config.php:
define( 'CHANGRID_ACCESS_KEY', 'your-access-key' );
define( 'CHANGRID_SECRET_KEY', 'your-secret-key' );
The optional CHANGRID_API_BASE_URL constant overrides the API base URL.屏幕截图:
常见问题:
Does this replace SMTP?
It short-circuits wp_mail() and submits the message to Changrid over HTTPS. The actual provider path is selected and operated in the Changrid workspace.
Do I need to configure an API base URL?
No. The plugin automatically uses Changrid's secure production API. The CHANGRID_API_BASE_URL constant is only for advanced or self-hosted installations and is not required for normal setup.
Does accepted mean delivered?
No. HTTP 202 means Changrid persisted or accepted the request. Delivery depends on routing, provider state, sender identity, suppression checks, and the recipient system.
What happens when Changrid is unavailable?
If native-mail fallback is enabled, the plugin lets WordPress continue with its normal wp_mail() transport after a request error. It does not retry a response that Changrid reported as accepted.
A network timeout is ambiguous: Changrid may have accepted the request even though WordPress did not receive the response. Native fallback in that situation can deliver a duplicate. Disable fallback for duplicate-sensitive messages and review the Changrid execution before manually retrying an uncertain send.
Are attachments supported?
Not in this release. Messages with attachments use native wp_mail() when fallback is enabled, or fail if strict Changrid-only behavior is selected.
Are Cc and Bcc headers preserved?
All To, Cc, and Bcc destinations are submitted as individual Changrid recipients. They do not receive a visible shared recipient header, which keeps Bcc destinations private.
Can I change the From address in WordPress?
No. The From email and name come from the active provider route in Changrid. This prevents WordPress from requesting an unverified identity that would fail provider, SPF, DKIM, or DMARC checks. Use the plugin links to manage providers or verify a sending domain in Changrid. WordPress can set a per-message Reply-To header, and the plugin also supports an optional site-wide default Reply-To address.
Can I choose a specific email provider?
Yes. Automatic workspace routing is the recommended default because Changrid can apply route priority, health, capacity, and failover rules. After pressing Check connection, open Advanced delivery routing to choose an active provider. A fixed provider controls the sender route but disables automatic failover for those WordPress requests.
更新日志:
- Added a guided provider selector populated by the deliberate no-send connection check.
- Kept automatic workspace routing as the recommended default and moved fixed routing into an advanced section.
- Shows managed-versus-own-provider and sender details without exposing or manually entering provider IDs.
- Sends
providerAccountIdonly when a valid fixed provider is saved.
- Added a sender-identity section with direct links to Changrid provider and sending-domain settings.
- Added an optional site-wide Reply-To address while preserving per-message Reply-To precedence.
- Clarified that From identities are selected from verified Changrid provider routes and cannot be overridden by WordPress.
- Added a no-send connection and permission check.
- Added clear plans, billing, setup, integration, and troubleshooting guidance.
- Clarified that the plugin is free and works with Changrid's Free plan.
- Improved WordPress.org external-service disclosure and release documentation.
- Initial release.
- Dedicated Changrid WordPress API delivery for
wp_mail(). - Test-send flow, privacy-conscious local diagnostics, tracking controls, and native-mail fallback.