Sending from a custom domain

Once a domain is verified, any address on it can be used as a From.

Add a send address

Settings → Domains → [domain] → Send addresses → Add. You’ll specify:

• Local part (the part before the @): hello, you, blake, etc.
• Display name: Blake Stacks, Acme Inc., etc.
• Signature (optional; can also be set globally).

The address is available in the compose From picker immediately. Send attribution is logged per message - look at the “Sent from” footer in the reader to see which profile was used.

The send flow

1. You compose a message with blake@yourdomain.com as From.
2. SuperMail hands the message to SES for delivery.
3. SES signs it with your DKIM key, adds our Return-Path for bounce handling, and delivers it.
4. A copy is stored in your Sent folder for that domain.
5. Bounces, complaints, and delivery confirmations come back through SES → our queue → your inbox (as a bounce notification).

Reply behavior

When you reply to a message that was sent to blake@yourdomain.com, the compose From defaults to blake@yourdomain.com. You can override with the From picker.

SuperMail remembers the From you actually used on each thread and offers it on subsequent replies.

Deliverability tips

1. Warm up gradually. If your domain is brand new, start with lower-volume sends to personal contacts before blasting a newsletter.
2. Set DMARC to p=none for the first 1-2 weeks, review aggregate reports, then tighten to p=quarantine.
3. Don’t send from no-reply@ if you want replies - recipients’ mail clients hide no-reply senders.
4. Use DMARC reports to confirm every legitimate sender (SuperMail, mailing-list tools, etc.) is aligned before tightening to p=reject.

What you can’t do

• Newsletter-scale sends. SuperMail is a personal/small-business client, not a marketing platform. Our SES quota is tuned for human mail volume (low thousands per day). For newsletters, use a dedicated ESP.
• Spoof a domain you don’t own. The From address must be on a domain you’ve verified.