2.8 KiB
2.8 KiB
created, modified, type, client, project, status, priority, tags, aliases, id
| created | modified | type | client | project | status | priority | tags | aliases | id | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2026-08-28 | 2026-08-28 | plan | sam | web-host-migration | pending | 2 |
|
|
1848129020-P2 |
Phase 2 — Email (inbound mailboxes + transactional outbound)
Part of Migration Plan — InMotion to Local + AWS Offsite. Blocked-by: none (can run parallel to Phase 1). Depends-on decision D3/D5/D6.
Goal
Deliver working email: real inbound mailboxes (webmail/IMAP) + transactional outbound per site — with deliverability credibility (reputation isolation, SPF/DKIM/DMARC).
Decisions (from main plan)
- Inbound: managed provider — Zoho Mail (free ≤5 users). Chosen for
audasmedia.com.au+where-woof.comfirst; more domains later. - Outbound: Amazon SES (~0.10/1000, effectively free at low volume).
- Both on separate reputation islands (don't send transactional from mailbox provider).
DNS dependency (IMPORTANT — 2026-08-28)
Both domains are authoritative on InMotion nameservers (ns1/ns2.inmotionhosting.com), so MX/SPF/DKIM/DMARC records must be added there today. User chose to HOLD OFF on moving DNS to Cloudflare until InMotion infra is fully retired (defer; avoid outage risk).
audasmedia.com.auA →173.231.229.92(still InMotion VPS)where-woof.comA →144.6.86.11(static IP, already local)- Not blocked by DNS: Amazon SES domain verification + outbound config can proceed now (verification tokens/CNAME are added later with records).
Sub-steps
2.1 Inbound mailboxes (user + config)
- Pick provider (Zoho / MXroute).
- Register custom domain mailbox(es) e.g.
hello@where-woof.com+ site addresses. - Set MX records on each domain → provider.
- Add
TXTSPF (include provider + SES),DKIM(provider + SES),DMARC. - Connect responders: Zoho webmail + Thunderbird/Gmail app via IMAP (993)/SMTP (465) if paid IMAP tier.
2.2 Outbound transactional (SES)
- Verify sending domains/emails in SES (
samuelrolfe@gmail.com, site domains). - Configure SPF/DKIM; exit SES sandbox (ticket/limit increase).
- Optionally use FLoci (localhost:4566) to develop/test the SES API integration offline first.
2.3 Site integration (later, with CMS migration project)
- Point site forms / password reset / notifications → SES SMTP or API.
- (CMS code changes are the separate migration project — only wire-up decisions here.)
2.4 Monitor
- Check bounces/complaints/deliverability dashboard.
Acceptance criteria
- Can receive into a real mailbox and read via webmail/IMAP.
- Can send a test transactional email through SES successfully (not sandbox-blocked).
- DNS passes SPF/DKIM/DMARC checks (use MXToolbox).