Mail

ByteBite mail infrastructure spans a dedicated VM for mailbox services and a planned cloud provider for transactional application email.

BYTEBITE-MAIL-01

DNS (configured)

Architectural direction

Status

Implemented

• MAIL VM provisioned with network access
• Mail DNS records (A + MX) created in Cloudflare
• Application SES + Twilio clients (packages/notifications): optional env, documented no-op without credentials. sendSms is invoked from Accept / Reject / Timeout / Ready. Checkout does not send. sendEmail is unused (no customer_email on orders).
• Optional POST /webhooks/twilio/status stub (signature check only; no order writes)

Planned

• Stalwart installation and configuration on BYTEBITE-MAIL-01
• AWS SES production setup (domain verification, DKIM) for application transactional email
• PTR record: mail.getbytebite.co → 88.99.0.97
• SPF, DKIM, DMARC records
• Hetzner outbound port 25 restriction resolution (may be required)

Open

• Whether Hetzner port 25 is currently blocked for 88.99.0.97 (not verified)
• SES sending domain verification (production)
• Application e-mail on order events (orders has no customer_email)

Responsibility split

Do not document provider credentials. See Secrets.

Stalwart / BYTEBITE-MAIL-01 is not this application slice. Transactional application mail is SES only.

Related

• Compute — MAIL VM details
• DNS — mail DNS records
• ADR-008 Transactional SMS
• Transactional notifications
• Known gaps