Mailgun forward email: forwarding routes vs a real inbox
Forwarding incoming Mailgun mail to Gmail is the most common workaround for Mailgun having no inbox. Here is how to set it up, where it breaks, and when a dedicated inbox is the better choice.
How to forward incoming mail with a Mailgun route
- Make sure your domain's MX records point to Mailgun (see how Mailgun receives email)
- Open Receiving / Routes in the Mailgun control panel and create a route
- Filter:
match_recipient("hello@example.com"), orcatch_all()to forward everything - Action:
forward("you@gmail.com"). You can add several destinations, separated by commas - Save, then send a test email to the address
Reply from your own domain in Gmail
Forwarding only covers incoming mail. To reply as hello@example.com, add it in Gmail under Settings → Accounts → Send mail as, using Mailgun's SMTP server and your domain's SMTP credentials. Every person who needs the address has to repeat this setup.
Where Mailgun forwarding breaks down
- Deliverability: forwarded messages can fail SPF or DMARC checks and land in spam
- Spam is forwarded too: everything that reaches the route goes to your personal inbox
- Mixed inboxes: business mail from support@ and hello@ ends up mixed with personal mail
- No delivery insight: Gmail does not show Mailgun delivery events for your replies
- Hard to share: a team cannot work from one support@ mailbox
Forwarding to Gmail vs a Mailgun inbox
| Forward to Gmail | Inboxes | |
|---|---|---|
| Receive mail for your domain | Yes | Yes |
| Reply from your domain | Needs SMTP send-as setup | Built in |
| Separate inbox per address | No, mixed with personal mail | Yes, one per mailbox |
| Mailgun delivery status | No | Yes, on every message |
| Setup | Routes + Gmail settings | API key; routes and webhooks are created for you |
| Cost | Free | $5 / month |
Forwarding is fine for one personal alias. If you run hello@, support@, and more on a Mailgun domain, a Mailgun webmail inbox keeps them organized and replies on-brand.
Frequently asked questions
Point your MX records to Mailgun, then create a route with a filter such as match_recipient("hello@example.com") and the action forward("you@gmail.com").
Only if you also set up "Send mail as" in Gmail with Mailgun SMTP credentials. Without that, replies come from your personal Gmail address.
Forwarding re-sends the message from Mailgun servers, so the original sender SPF check can fail, and strict DMARC policies may mark it as suspicious. Spam sent to your domain is forwarded too.
Mailgun is sending and receiving infrastructure. Gmail is an inbox. If you only need an inbox for your Mailgun domain, a Mailgun email client like Inboxes replaces the forwarding setup.