Skip to content

Receiving email ​

SendGrail can receive mail for your domains. Someone writes to support@inbound.example.com, and the message lands in your team's Inbox in the dashboard — and, if you want, reaches your own app through a webhook and the API.

How it works ​

Mail for your receiving host is accepted by Amazon SES, scanned for spam and viruses, stored, and filed into the mailbox it was addressed to. There is no mail server for you to run: you add one MX record.

Turn on receiving for a domain ​

  1. Open a verified domain under Domains and choose Receive emails.

  2. Pick where mail arrives:

    • A subdomain such as inbound.example.com — the safe choice. Mail you already receive on example.com is not affected.
    • The root domain — only if example.com doesn't receive mail anywhere else. If it already has MX records, SendGrail asks you to confirm first, because switching takes that mail over.
  3. Add the MX record SendGrail shows at your DNS provider, for example:

    TypeNameValuePriority
    MXinboundinbound-smtp.ap-south-1.amazonaws.com10
  4. Click I've added the record — or just wait. SendGrail checks every few minutes and turns receiving on by itself once the record is visible.

SendGrail must be the only MX

Receiving is verified only when SendGrail's record is the host's only MX record. Any other MX — preferred or fallback — can take mail that never reaches you.

Mailboxes ​

Turning receiving on creates a catch-all, which receives every address on the host. Add mailboxes such as support@ and sales@ under Inbox › Mailboxes:

  • Mail goes to the exact address first, then to the address without a +tag (support+billing@ reaches support@), then to the catch-all.
  • Mail to an address with no mailbox, when there is no catch-all, is discarded.
  • Everyone on your team can read and manage every mailbox, as with the rest of the dashboard.
  • New mailbox lists only domains that receive mail. Domains that don't yet are named under the picker, each with what it still needs — verifying, or turning receiving on — and a link to it. Receiving is turned on per domain, from that domain's page.

Giving a mailbox to a person ​

A new mailbox belongs to the whole team: every member can open it, like every other team resource. Hand it to someone and that changes.

Open Inbox › Mailbox settings and add a person under People with access:

  • Only they and team admins can open it from then on. Other members stop seeing it in their mailbox list, its mail disappears from their inbox, and they cannot send from it.
  • Several people can share one mailbox — add each of them.
  • Remove everybody and the mailbox goes back to the whole team.

Only a team admin decides who holds a mailbox.

To give one person several mailboxes at once, start from the person instead: open Settings › Team, click ⋮ on their row and choose Mailbox access. Tick every mailbox they should hold and save; untick one to take it back. A mailbox the whole team still shares becomes private to them when you tick it, and the dialog says so before you save.

An account that only has mail ​

Invite someone as a Mailbox member (Settings › Team › Members, then tick the mailboxes to give them — one or several). They sign in and land in the mail app, see only the mailboxes granted to them, and reach nothing else — no domains, no sending, no API keys, no team settings.

This is the right role for someone who needs sumon@yourdomain.com and no part of the rest.

The role applies inside your team only. Someone who also has their own team — a developer you've given a mailbox, say — keeps it: they switch between your mailbox and their own dashboard from the team switcher in the mail app.

Reading and replying ​

The Inbox has Inbox, Sent, Spam, Archive and Trash folders, search, and conversations: a reply joins the thread it answers.

Reply, Reply all, Forward and Compose send from a mailbox's own address — the catch-all can only receive — through SendGrail's normal sending, so your suppression list and sending limits apply. Messages are sent as plain text. Forwarding includes the original's attachments.

Safety ​

  • Messages the spam scan flags go to Spam. A message that fails the virus scan is kept, but its attachments are not.
  • A message's HTML is shown with scripts and forms disabled, and remote images stay blocked until you click Show images — loading them tells the sender you opened the message.
  • Received mail is stored in the AWS region used for receiving (Asia Pacific — Mumbai).

In your app ​

  • Subscribe a webhook to email.received to hear about each message as it arrives. The event carries the sender, recipients, subject and attachment names — never the content.
  • Fetch the full message, and its attachments, with the inbound email API.

Turning receiving off ​

Choose Turn off on the domain. Mailboxes and mail already received are kept; new mail for the host is discarded — so remove the MX record at your DNS provider too.

Transactional email on your own domain.