Files
obsidian-vault/200 projects/220 Web Host Migration/Phase 2 — Email.md

59 lines
2.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
created: 2026-08-28
modified: 2026-08-28
type: plan
client: sam
project: web-host-migration
status: pending
priority: 2
tags:
- migration
- email
- ses
- zoho
- mxroute
aliases:
- phase-2-email
id: 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) or **MXroute** (~30–45/yr). Pick one: _default = Zoho free tier_ for cost; MXroute for unlimited domains.
- **Outbound:** **Amazon SES** (~0.10/1000, effectively free at low volume).
- Both on separate reputation islands (don't send transactional from mailbox provider).
## 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 `TXT` SPF (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).
---
*See [[Migration Plan — InMotion to Local + AWS Offsite]] §6.*