Project email address

How you get an address

There's nothing to set up: creating a project provisions the address immediately. On the free plan the slug before the @ is auto-generated; on Pro you pick your own, so the address can match your project's name. Every address lives on the mailcontact.app domain.

No DNS, no mail server

Because the address is on mailcontact.app, there's nothing to configure on your side: no MX records, no SPF or DKIM, no mail server to run, no forwarding rules in another provider. That makes it useful when:

• the project doesn't have a domain yet (or ever: a demo, a beta, a weekend build),
• the site is on a static host and you don't want to touch DNS just for mail,
• you want a public contact address that isn't your personal inbox and can be retired with the project.

Where inbound mail lands

Mail sent to the address lands in the project's inbox: the same one your form endpoint feeds. Each message is tagged with its source, so you can tell an email from a form submission at a glance while still reading everything in one place. Notification channels fire the same way for both sources: a new email pings Discord or your inbox on the free plan, Slack or a webhook on Pro.

Free plan vs Pro

• Free: one email address per project with an auto-generated slug, up to 2 projects.
• Pro: an address of your choice, more addresses and projects, and higher volume. Priced at launch; details on the pricing page.

Custom domains

Not supported yet: addresses are @mailcontact.app only for now. If you need inbound mail on your own domain today, mailcontact isn't that tool (yet). The form endpoint is domain-independent, though: it works from any site you point at it.

Test it

Send an email to your project's address from your normal account. It shows up in the project inbox tagged as an email, and your notification channel pings. Getting started walks the whole setup in about a minute.