
Set up MailWizz with Qubrics
Install the extension and connect Qubrics

Upload the Qubrics extension ZIP in MailWizz.
smx_mbx_.In MailWizz, open Delivery servers → Create new, select Qubrics
Web API, paste the key into Sending Key and complete the sender
fields. Save the server. It remains inactive until you connect signed
feedback.Reopen the server and select Info to copy its webhook URL. In Qubrics,
open Webhooks → Create webhook, use that URL and subscribe to
message.bounced and message.complained. Copy the reveal-once whsec_
secret back into Webhook signing secret in MailWizz. Save, test and
activate the delivery server.Add sending accounts and set limits

Choose the connection type for each Qubrics sending account.

Set fixed or ranged quotas for each sending window.
5–10 lets Qubrics periodically select an active cap inside those
boundaries. Messages above the current cap wait until capacity is
available.Start the campaign and follow-ups

Use MailWizz's campaign actions to schedule or save your work.
How MailWizz and Qubrics divide the work
MailWizz owns the campaign workflow. Qubrics decides which eligible account can send and enforces that account’s current limits. This keeps lists and automations in MailWizz without recreating every sending account as a separate delivery server.Choose fixed limits or ranges
Use a fixed cap when you want one predictable ceiling. Use a range when the active ceiling may move within approved boundaries. Qubrics selects a value when account information refreshes and keeps that cap until the next refresh. A range varies the sending ceiling. It does not add a random delay to each message or guarantee inbox placement. Good targeting, authenticated sender domains, relevant content and a healthy account history still matter.How feedback returns to MailWizz
The extension includes MailWizz campaign and subscriber identifiers with campaign sends. When Qubrics reports a bounce or complaint, MailWizz verifies the signed event and matches it to the campaign, subscriber and delivery server that recorded the send before changing subscriber state.What queued means
queued means Qubrics accepted the message for processing. It does not mean the recipient system accepted it or that it reached the inbox. Final delivery still depends on the selected account, the recipient system, message quality and sender reputation.
Check before your first campaign
- Test and activate the Qubrics delivery server in MailWizz.
- Confirm at least one eligible sending account is active.
- Review From, Reply-To and sending limits for every account.
- Confirm the feedback webhook has its saved
whsec_secret. - Check prospect sourcing, suppression and opt-out handling.
- Read the original campaign and every follow-up from start to finish.
Common questions
Do I need a separate MailWizz bounce server?
Do I need a separate MailWizz bounce server?
Can Qubrics use multiple sending accounts?
Can Qubrics use multiple sending accounts?
Why is the delivery server inactive?
Why is the delivery server inactive?
Can I reuse one autoresponder for repeated sends?
Can I reuse one autoresponder for repeated sends?