| 开发者 | everpress |
|---|---|
| 更新时间 | 2026年10月15日 19:10 |
This plugin requires Mailster 4.0 or newer and a SparkPost account with a Master API key and a verified sending domain. When SparkPost is the active delivery method, outgoing email content and delivery metadata are sent to SparkPost (US or EU API, depending on your endpoint setting).Why send Mailster newsletters with SparkPost?
api.eu.sparkpost.com / smtp.eu.sparkpostmail.com).mailster-sparkpost folder to the /wp-content/plugins/ directory, or install from the WordPress plugins screen.No. This is a delivery addon for the Mailster Newsletter Plugin and requires Mailster 4.0 or newer.
Yes. You need a SparkPost account, a verified sending domain (or verified From address), and a Master API key. SparkPost is a paid email delivery service; see SparkPost for current plans.
WEB API (recommended) sends through SparkPost’s Transmissions API and usually returns clearer errors. SMTP API relays via smtp.sparkpostmail.com (or the EU host) on port 587 or 2525 with TLS. Both are available in the SparkPost delivery settings.
Mailster needs Account read access (and related permissions) to verify the key, list sending domains and subaccounts, read message events for bounces, and send transmissions. A restricted key without those permissions will not work fully.
Yes. Choose the EU endpoint in the SparkPost delivery settings to use the EU API and SMTP hosts.
When SparkPost is the active delivery method, bounce handling is driven by SparkPost message events synced into Mailster. Mailster’s own bounce mailbox settings are ignored for this delivery method.
Yes. When this delivery method is active, Mailster sends email content and related delivery metadata to SparkPost so messages can be delivered. Bounce and engagement events are read back from SparkPost’s APIs.
For Mailster and this addon, see mailster.co and the SparkPost setup guide. For SparkPost account, billing, and API questions, use SparkPost documentation.