Does Mailgun have an inbox?

No. Mailgun receives email through routes that forward or store messages for your app, but it has no mailbox for people to read and answer. HelloBox connects to Mailgun and gives your team a shared inbox.

Which Mailgun keys does HelloBox need?

An API key, which can manage routes and read stored messages, and the HTTP webhook signing key, which proves notifications come from Mailgun. Both are under Settings, API Security.

Does HelloBox work with Mailgun's EU region?

Yes. HelloBox detects whether your domains are in the US or EU region, and asks you to pick when it can't tell.

How long does Mailgun keep received email?

Messages stored by a route are kept for up to 3 days. HelloBox saves its own copy as soon as Mailgun notifies it, so mail stays in your inbox after Mailgun's copy expires.

Is there an inbox for Mailgun?

Updated November 11, 2026

Short answer

Mailgun can receive email, but only through routes that forward each message to a URL or email address, or store it for 3 days for your app to fetch. There's no inbox for people. To get one, connect Mailgun to HelloBox with your API key and HTTP webhook signing key: it adds a route for each domain that receives, verifies every notification, saves each email, and gives your team a shared inbox. It's free for one person.

How Mailgun handles incoming mail

Point a domain's MX records at mxa.mailgun.org and mxb.mailgun.org, and Mailgun accepts its mail. What happens next is up to your routes: rules like match_recipient(".*@yourdomain.com") with actions such as forward(), store() and stop().

store(notify=...) keeps the message for up to 3 days and posts a signed notification with a link to fetch it. Routes are account-wide, and accounts live in a US or EU region that keeps its domains, routes and webhooks apart.

Connect Mailgun to HelloBox

In Mailgun, open Settings then API Security. Copy an API key (a domain sending key can only send, so it isn't enough) and the HTTP webhook signing key.
In HelloBox, choose Connect a provider, then Mailgun, and paste both. HelloBox finds your region from where your domains are, and asks only if it can't tell.
Turn receiving on for a domain. HelloBox adds a route that stores its mail and notifies HelloBox, and shows the MX records, or adds them if your DNS is on Cloudflare.

Each notification is checked against your signing key and refused if it's more than 15 minutes old. HelloBox then fetches the original message and saves it before answering Mailgun, and it reads Mailgun's logs for anything stored in the last 3 days that a notification missed.

What stays the same

Your app's keys, SMTP credentials and other routes keep working. HelloBox's routes don't stop the ones you already have.
Mailgun bills you for email volume at its own prices. HelloBox plans limit people, domains, storage and contacts, not how much you send.
Both keys are encrypted before HelloBox stores them. Disconnecting removes the routes and webhook it added; your domains stay in Mailgun.

HelloBox is an independent product and isn't affiliated with Mailgun.

Frequently asked questions

Does Mailgun have an inbox?: No. Mailgun receives email through routes that forward or store messages for your app, but it has no mailbox for people to read and answer. HelloBox connects to Mailgun and gives your team a shared inbox.
Which Mailgun keys does HelloBox need?: An API key, which can manage routes and read stored messages, and the HTTP webhook signing key, which proves notifications come from Mailgun. Both are under Settings, API Security.
Does HelloBox work with Mailgun's EU region?: Yes. HelloBox detects whether your domains are in the US or EU region, and asks you to pick when it can't tell.
How long does Mailgun keep received email?: Messages stored by a route are kept for up to 3 days. HelloBox saves its own copy as soon as Mailgun notifies it, so mail stays in your inbox after Mailgun's copy expires.