NetSendo v2.12.3: Broadcast Mailbox for Gmail-Default Lists
Gmail is a reasonable default mailbox for a lot of lists. It works well for autoresponders, system emails and one-to-one messages. It doesn't work for campaigns. Google limits what a personal account can send, and NetSendo can't process bounces from a Gmail mailbox. Starting in 2.12.2, NetSendo refused campaigns that would go out from Gmail, which protected your sender reputation. It also meant that a list with a Gmail default mailbox had no way to send a campaign at all.
NetSendo v2.12.3 fixes this with a second mailbox setting on each list. The list's default mailbox keeps handling its day-to-day email, and a separate broadcast mailbox sends its campaigns.
broadcast_mailbox_id in the API and MCP. When a campaign's mailbox can't send campaigns (for example, Gmail), the campaign goes out from the broadcast mailbox instead. The campaign editor now shows the actual sender or the reason a campaign can't be sent, and send_campaign and schedule_campaign return the real sender in sender.
🚀 What's New in v2.12.3
Broadcast Mailbox per List
A separate mailbox that only sends this list's campaigns.
Sender Visibility
The campaign editor shows which mailbox will send the campaign, or why it can't be sent.
API & MCP Support
broadcast_mailbox_id is available in the API and in update_contact_list.
Predictable Refusals
No more silent fallback to a random mailbox when a campaign inherits Gmail.
Two Mailboxes, Two Jobs
Each list now has two mailbox roles. The default mailbox sends autoresponders, system emails and individual emails (including send_email). The broadcast mailbox steps in only for campaigns whose mailbox can't send campaigns.
You'll find the new field in List → Settings → Sending. It only appears when the list's default mailbox can't send campaigns, so lists that already work don't get any extra settings.
How the Sender Is Resolved
When you send a campaign, NetSendo checks its mailbox: either the one set on the campaign or the default of its list. If that mailbox can't send campaigns, the campaign goes out from the broadcast mailbox of the first list that has one, in the order the campaign's lists are listed.
The broadcast mailbox must belong to your account and must allow One-time (Broadcast) messages. Gmail mailboxes therefore can't be chosen as a broadcast mailbox.
// Illustrative MCP call: set a broadcast mailbox on a list
{
"tool": "update_contact_list",
"arguments": {
"id": 42,
"broadcast_mailbox_id": 7
}
}
ℹ️ Note: The example above is illustrative. Check the API and MCP documentation for the exact parameter names your installation expects.
Behavior Change: Inherited Gmail Is Now Refused
Before this release, a campaign that inherited a Gmail mailbox from its list quietly went out from the first mailbox allowed to send broadcasts. That could be a mailbox you never intended to use. Now, if the list has no broadcast mailbox, the campaign is refused, the same way a campaign with its own Gmail mailbox is.
The 422 Mailbox Not Allowed response lists the campaign's lists and points you to broadcast_mailbox_id, so you know exactly what to fix. These cases still fall back as before:
- A campaign with no mailbox set anywhere
- A mailbox that has reached its limit
- Autoresponders
Smaller Improvements
- Sender in API responses:
send_campaignandschedule_campaignreturn the mailbox that will actually send the campaign in thesenderfield. - Editor clarity: The campaign editor shows the resolved sender or the reason the campaign is blocked, with a link to the list settings.
- Fix: A campaign whose mailbox was the account default used to show Automatic in the mailbox field. The campaign always kept that mailbox. Only the label was wrong, and now it's correct.
💼 Benefits & Use Cases
E-commerce: Personal Touch + Promotions
A store owner sends order follow-ups and abandoned-cart reminders from a personal Gmail address because customers reply to it. With v2.12.3 they can:
- Keep Gmail for post-purchase autoresponders
- Set an SMTP or provider mailbox as the broadcast mailbox for weekly promotions
- Get bounce handling on campaigns without changing any existing automations
SaaS: Founder Onboarding, Product Newsletters
Onboarding emails "from the founder" go out from Gmail. Product updates and churn-prevention campaigns go out from a dedicated broadcast mailbox on the same list, so you don't need to duplicate lists or split your audience.
Agencies: Safe Multi-Client Setups
Since inherited Gmail mailboxes no longer fall back to just any broadcast-capable mailbox, a campaign can't go out from the wrong client's sender. Each list either uses its own broadcast mailbox or gets refused with a clear error.
🛠️ Step-by-Step Guide
- Update NetSendo
Pull the latest image and restart your stack.
docker compose pull docker compose up -d - Check your mailboxes
Make sure you have at least one non-Gmail mailbox that allows One-time (Broadcast) messages.
- Open the list settings
Go to List → Settings → Sending. If the default mailbox can't send campaigns, you'll see the Broadcast mailbox (campaigns) field.
- Choose the broadcast mailbox
Select a mailbox and save. Only mailboxes from your account that can send broadcasts appear in the list.
- Check the campaign editor
Open a campaign for that list. The editor should now show the broadcast mailbox as the sender.
- Update automation scripts
If you send campaigns through the API or MCP, read the
senderfield fromsend_campaignandschedule_campaignto log or verify the actual sender.
⚠️ Common pitfall: After upgrading, campaigns to lists with a Gmail default and no broadcast mailbox will return 422 Mailbox Not Allowed where they used to fall back silently. Before your next scheduled send, check your lists and set a broadcast mailbox on each one that needs it.
🎯 Expert Tips
For campaigns sent to several lists, the broadcast mailbox comes from the first list that has one. Put the list whose sender identity you want first.
Catch 422 Mailbox Not Allowed in n8n or your own scripts. The response names the affected lists, so you can turn it into an alert that tells you which list needs a broadcast mailbox.
Store the sender value returned by send_campaign. It makes deliverability audits much easier.
Set up SPF, DKIM and DMARC for the domain of your broadcast mailbox. Bounce handling only helps if your mail reaches inboxes in the first place.
✅ Conclusion
- Lists with a Gmail default mailbox can send campaigns again
- Autoresponders and system emails keep using the default mailbox
- The editor and API show the actual sender
- No more silent fallback to a mailbox you didn't choose
Because NetSendo is self-hosted, you decide which mailbox sends what, and you aren't locked into one provider's sending rules.
Upgrade to v2.12.3
Set up broadcast mailboxes on your lists today, and see our integrations for more ways to automate.
Like NetSendo? Star us on GitHub ⭐


