Skip to main content

Overview

Forwarding mode accepts mail for your domain and re-sends each message out to a destination address you choose, like a Gmail or company inbox. There’s no SMTP relay to run and no webhook to host, just rules that map [email protected] to wherever you actually read mail. This is the right delivery type when you want your domain to look professional in the From line but you don’t want to operate a mail server. Use SMTP if you have a destination mail server, or Webhook if you want to receive mail in your application.

How it works

1

Add the domain in forwarding mode

In the Dashboard, go to Inbound → Add Domain and choose Forward as the delivery type.
2

Publish four DNS records

Forwarding requires MX, DKIM, SPF, and DMARC records on your domain. We show the exact values on the Settings tab and verify them with a single click. See DNS Records.
3

Add forwarding rules

Map specific addresses (e.g. [email protected][email protected]) or set a catch-all that captures every unmatched address. See Forwarding Rules.
4

Verify each destination

The first time you forward to a new destination, the destination owner gets a confirmation email and has to click the link before mail starts flowing. See Destination Verification.

Workflow at a glance

sender → MX (smtp.jetsmtp.net) → JetEmail filters → forwarding rule → your inbox
When mail arrives:
  1. Our edge looks up the recipient’s localpart in your domain’s rules.
  2. If a rule matches and the destination is verified, the message is rewritten and re-sent to that destination.
  3. If no rule matches and there’s no catch-all, mail is rejected with 550.

Before you go live

Mail won’t be delivered until all four DNS records verify and the destination has been confirmed. The dashboard surfaces both gates as orange banners on the Forwarding tab so you can tell exactly what’s blocking delivery.