5 solution docs
Mailgun solution docs
The veteran sending API. EU data residency and suppression lists kept server-side.
Pick Mailgun and all 5 land in docs/solutions/mailgun/, next to the rules and skills that reference them.
Every Mailgun doc in the registry
Tags: api · authorized-recipients · batch · bounces · complaints · deliverability · email · eu · gdpr · handlebars · mailgun · onboarding · phishing · privacy · react-email · recipient-variables · regions · sandbox · suppressions · templates · tracking · unsubscribe
Mailgun returns 401 and your API key is fine: the EU/US region trap
A Mailgun domain lives in the region it was created in. Calling the wrong regional host returns 401 Unauthorized, which reads exactly like a bad API key.
mailgun · email · regions · eu
Mailgun says the message was queued and nobody receives it: sandbox domain limits
The sandbox domain accepts every send and delivers only to five addresses you authorised. Recognise it, use it deliberately, and know when to stop.
mailgun · email · sandbox · authorized-recipients
Suppression lists in Mailgun: stop maintaining your own bounce table
Mailgun stores bounces, complaints and unsubscribes per domain and refuses to send to them. Read that list instead of building a table you have to keep in sync.
mailgun · email · suppressions · bounces
Mailgun templates and recipient variables versus rendering HTML in your app
Mailgun stores Handlebars templates in its dashboard and substitutes variables at send time. Rendering in your app instead keeps email in code review: here is when each one wins.
mailgun · email · templates · handlebars
Open tracking, click tracking and why they are off by default
Mailgun's tracking adds a pixel and rewrites every link. Both are personal data under GDPR, both cost deliverability, and neither belongs on a magic link.
mailgun · email · tracking · privacy