Sendmux for MailWizz
Connect MailWizz to Sendmux through the Sendmux Sending API. MailWizz manages lists, campaigns and autoresponders, while Sendmux routes accepted messages through the active sending accounts and limits configured for your team.
接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
Connect MailWizz to Sendmux through the Sendmux Sending API. MailWizz manages lists, campaigns and autoresponders, while Sendmux routes accepted messages through the active sending accounts and limits configured for your team.
MailWizz delivery server extension for Sendmux — route emails through multiple SMTP providers (Gmail, Outlook, custom SMTP) with smart rate limiting, automatic failover, and bounce/complaint webhook handling.
An API response with queued status means Sendmux accepted the message for processing. It does not guarantee final delivery or inbox placement.
graph LR
A[MailWizz] -->|Sending API| B[Sendmux]
B --> C[Sending account 1]
B --> D[Sending account 2]
B --> E[Sending account 3]
C --> F[Recipients]
D --> F
E --> F
B -->|Signed feedback| A
smx_mbx_.smx_mbx_.smx_mbx_ value into Sending Key and complete the required sender fields.https://your-mailwizz-domain.example/dswh/sendmux-api/{server_id}.message.bounced and message.complained.whsec_. It is shown once.Existing version 0.2 installations must complete this webhook-secret step before feedback processing will resume. Unsigned requests are rejected.
Create and schedule a regular campaign in MailWizz as usual, selecting the Sendmux delivery server where required by your setup. MailWizz autoresponder campaigns use the same delivery path, so follow-up messages can be triggered by the timing and subscriber actions available in MailWizz.
Sendmux accepts either a fixed cap or a minimum-to-maximum range for supported time windows. For example, a range can vary the active cap periodically within the configured bounds. Messages above the current cap wait in the queue until capacity is available.
A range changes the active throughput cap. It is not a random delay applied independently to every message, and it does not by itself improve inbox placement. Start with limits suitable for each sending account and follow the account provider's policies.
The extension verifies X-Sendmux-Signature against the exact request body before reading the event. Feedback is applied only when the campaign, subscriber and webhook delivery server match a current or archived MailWizz delivery record. For the same campaign and subscriber, a stronger bounce classification replaces an earlier one; matching or weaker duplicates are ignored. Feedback without MailWizz campaign and subscriber identifiers cannot be applied to a campaign record.
The MailWizz extension is one way to use Sendmux. Developers and AI agents can also use these available tools:
https://mcp.sendmux.ai/mcp or the sendmux-mcp package.@sendmux/cli or Snap.Not for campaign feedback handled by this integration. The signed webhook writes correlated bounces and complaints into MailWizz. Keep the webhook active and monitor failed webhook deliveries in Sendmux.
Yes. Add the accounts to Sendmux and configure their individual sender details and limits. Sendmux chooses among eligible active accounts according to your routing configuration.
Use a separate MailWizz campaign for each intended follow-up. The retry key identifies one logical send by campaign and subscriber, so deliberately re-entering the same subscriber into the same autoresponder during Sendmux's idempotency window is unsupported.
The initial record stays inactive until a webhook secret is saved. MailWizz also deactivates a server after a credential change so you can test it before sending campaigns.
Use a send-capable mailbox key beginning with smx_mbx_ in Sending Key. Use the reveal-once whsec_ value from the Sendmux webhook in Webhook signing secret. Leave the secret field blank on later edits to keep the stored value.
FSL-2.0 (Functional Source License 2.0)
MailWizz delivery server extension for Sendmux — route emails through multiple SMTP providers (Gmail, Outlook, custom SMTP) with smart rate limiting, automatic failover, and bounce/complaint webhook
總覽
MailWizz delivery server extension for Sendmux — route emails through multiple SMTP providers (Gmail, Outlook, custom SMTP) with smart rate limiting, automatic failover, and bounce/complaint webhook handling.
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Mailwizz Smtp Proxy 透過 stdio 在本機執行。
上次檢查時間:2026-10-28。 MailWizz delivery server extension for Sendmux — route emails through multiple SMTP providers (Gmail, Outlook, custom SMTP) with smart rate limiting, automatic failover, and bounce/complaint webhook handling.