Skip to content
nofeb

What is Custom MAIL FROM domain?

Also called return-path or envelope sender domain

A custom MAIL FROM domain is a subdomain you own, such as bounce.example.com, used as the SMTP envelope sender instead of the sending service's own domain. With its own MX and SPF records, SPF then passes for your domain and aligns with your From: address, which DMARC requires.

Checked against the engine on .

How does Custom MAIL FROM domain work?

Every message has two senders: the envelope sender used during the SMTP conversation (where bounces go) and the From: header a person reads. Without a custom MAIL FROM, the envelope sender is the provider's domain, so SPF passes for the provider rather than for you, and DMARC can only align through DKIM.

Publishing a dedicated subdomain keeps two alignments available (SPF and DKIM), so one failing does not fail DMARC. Because only the subdomain's records change, the root domain's SPF and MX stay as they are.

How does nofeb use Custom MAIL FROM domain?

  • nofeb configures a custom MAIL FROM on bounce. for every domain you add and returns its MX and SPF records with the DKIM and DMARC records, so mail from your inboxes aligns on both SPF and DKIM.

Frequently asked questions

Does a custom MAIL FROM change where replies go?

No. Replies go to the From: or Reply-To address. The MAIL FROM domain only receives bounces and delivery reports.

Why use a subdomain?

So the records nofeb needs never collide with the SPF or MX records your root domain already has.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Custom domains Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Shipped
DNS setup made easy nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. Shipped