#7 · stacks/paweldregan

Context

Need a real hello@paweldregan.com mailbox so the contact form (separate issue) and any direct correspondence have a destination.

Hard constraint: must live on the same EC2 server / same sender IP as our existing mail. We're building IP reputation on a single sender IP rather than splitting across multiple — every new domain or mailbox extends the same server, never a fresh one.

The existing mail server runs github.com/mail-os/mail on EC2.

Scope

DNS for paweldregan.com (Porkbun):
- MX → existing mail server hostname (matching the same name our other domains use)
- SPF (TXT @ → v=spf1 ip4:<server-ip> -all or whatever our other domains use)
- DKIM (publish the public key for whatever selector mail-os uses)
- DMARC (TXT _dmarc → v=DMARC1; p=quarantine; rua=… matching existing policy)
mail-os configuration: add paweldregan.com as a hosted domain and hello@paweldregan.com as a mailbox (whatever the mail-os equivalent of accounts add is).
Mail server may need to be upgraded to comfortably host another domain (RAM / disk / spool config). Note any limit hit.
Send + receive smoke test: SMTP outbound from hello@paweldregan.com, IMAP/POP inbound, confirm delivery to a Gmail and an iCloud test account isn't bouncing or going to spam.
Verify SPF/DKIM/DMARC pass via mail-tester.com — target 10/10.

Risks / open questions

Adding a new domain to a shared sender IP is generally safe but first emails from a "new" domain are spam-suspicious even on a warm IP. May want to throttle initial volume.
If mail-os doesn't already support multi-domain trivially, that's a feature gap to call out separately (don't sidestep with a second server).

Out of scope

Setting up a webmail UI for hello@. Forwarding to a personal account if needed is fine for now.
Migrating any other mail off-server.