SpeedyMessaging
| 开发者 | hthub247 |
|---|---|
| 更新时间 | 2026年8月25日 06:03 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
This is the official WordPress client for SpeedyMessaging, a paid transactional email service. It is not a general SMTP configuration plugin: it does not connect to arbitrary mail hosts, and it has no server/port/encryption fields. It speaks one service's API, and it exists to make sending from that account correct rather than merely possible.
Routes
wp_mail() through the SpeedyMessaging API so every email your site sends — WooCommerce receipts, Contact Form 7 submissions, password resets — goes out through your own mailbox, without changing any of those plugins.
What this does that a mail-configuration plugin does not
Sending here costs money per message, and the account can run out. That makes the hard problems different from "which host do I point at", and it is where this plugin does its work:
- You are never charged twice. Every paid call carries an
Idempotency-Key, so a plugin that fireswp_mail()twice, or two overlapping cron runs, produce one delivery and one charge — not two. Retrying a paid send is normally the thing you cannot safely do; here it is safe by construction. - Attachments arrive openable, or not at all. Every file is uploaded first and sent by reference. Testing against the live API showed that passing a file inline is accepted and then never stored — the recipient gets a message claiming an attachment nobody can open. This plugin never sends that way, and if a file cannot be uploaded it hands the message to your normal mail rather than delivering it gutted.
- Running out of credit holds mail, it does not lose it. Queued messages wait, an admin notice appears, and they send once the account is topped up. Nothing is discarded.
- Consent is tracked and enforced. A do-not-contact list is checked on every send, with signed one-click unsubscribe links that cannot be edited to suppress somebody else. Privacy exporters and erasers are registered, so a GDPR request covers what the plugin stores.
- It stays out of your way. The plugin's screen lives under Settings. The only notices raised elsewhere mean mail is not being delivered right now — they are dismissible, and they never appear while you are writing a post.
POST /v1/email/messages— preferred: idempotent retries, uploads for attachments, mailbox-bound scope checksPOST /business-email/send— fallbackPOST /messages— last resort- This site's normal
wp_mail()/ SMTP
- A durable queue with claiming, exponential backoff and a per-minute rate budget
- An SMS helper for theme and plugin code,
speedy_send_sms( $to, $body ), for sites whose account also has SMS enabled — a secondary convenience in this release, not its focus - A do-not-contact list, checked on every send, with signed one-click unsubscribe links
- Privacy exporters and erasers, so a data request covers what this plugin stores
- Optional HMAC request signing
- A delivery log with recipients masked at write time
安装:
- Upload the plugin and activate it. Activation creates two database tables, for the send queue and the delivery log.
- Create an API key in the SpeedyMessaging dashboard under Developer → API keys, scoped
business_emailand bound to your mailbox (addmessaging:smsfor SMS). Start with ansk_test_key, which never debits credits. - Enter your credentials under Settings → SpeedyMessaging, or — preferred — define them in
wp-config.phpso they stay out of the database:
define( 'SPEEDY_API_KEY', 'sk_live_…' );
define( 'SPEEDY_MAILBOX_EMAIL', 'noreply@yourdomain.com' );
define( 'SPEEDY_MAILBOX_APP_PASSWORD', '…' );
- Check the status badges and use Send a test to confirm delivery. Then swap the test key for a live one.
- If your site sends in volume, disable traffic-driven cron so the queue drains on time:
define( 'DISABLE_WP_CRON', true );
and add a system cron entry running wp cron event run --due-now every minute.屏幕截图:
常见问题:
Do I need a SpeedyMessaging account?
Yes. This plugin is a client for that service and does nothing without credentials for it. See the "External service" section above for exactly what is transmitted.
I already use an SMTP plugin. What happens?
Whichever plugin hooks wp_mail() first handles a given message. The settings screen names any other mail plugin it detects and tells you which one is in charge. Running one at a time makes delivery predictable.
Why did some emails not go through SpeedyMessaging?
The settings screen counts them by reason. Messages with CC/BCC or a Reply-To header, and messages whose attachment fails the size or type check, are handed to your site's normal mail. They are still delivered — just not by this plugin.
What happens when the account runs out of credit?
Queued messages are held, not failed, and an admin notice appears. They send once the account is topped up. Nothing is discarded.
Does the plugin slow down my site?
Front-end page views do no work at all. Sending happens when WordPress sends mail, and bulk sending happens on cron.
Is any customer data stored?
The queue stores recipients and message bodies until delivery, then drops the bodies after 30 days. The delivery log masks recipients at write time and never stores message content. Privacy exporters and erasers are registered so a data request covers all of it.
更新日志:
1.0.0
- Initial release.
- Email transport ladder with fallback to the site's normal mail.
wp_mail()takeover, including attachments.- SMS with E.164 normalisation and GSM-7 segment counting.
- Durable queue with claiming, backoff, rate budget and idempotency.
- Do-not-contact list, one-click unsubscribe, privacy exporters and erasers.
- Optional HMAC request signing; delivery-receipt webhook endpoint.