ByteBite Docs
Infrastructure

Mail

Mail VM, DNS, Stalwart + SES architecture, and current status.

Mail

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

BYTEBITE-MAIL-01

AttributeValue
VMBYTEBITE-MAIL-01
Public IPv488.99.0.97
vMAC00:50:56:00:05:51
SSHReachable
OS / specsUnknown

DNS (configured)

RecordValue
mail.getbytebite.co A88.99.0.97
getbytebite.co MX (pri 10)mail.getbytebite.co

Architectural direction

Mail typePlanned providerVM
Ordinary mailbox / mail-serverStalwartBYTEBITE-MAIL-01
Transactional application mailAWS SESCloud (not on MAIL VM)
SMS (transactional)TwilioCloud (planned)

Status

Implemented

  • MAIL VM provisioned with network access
  • Mail DNS records (A + MX) created in Cloudflare

Planned

  • Stalwart installation and configuration on BYTEBITE-MAIL-01
  • AWS SES production setup 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
  • Application integration with SES (placeholders in .env.example only)

Responsibility split

ConcernOwner
Operator/admin email (mailboxes)Stalwart on MAIL VM
Order confirmations, password resets, etc.AWS SES (application)
SMS notificationsTwilio (planned, ADR-008)

Do not document provider credentials. See Secrets.

Database

PostgreSQL staging service, migrations, seeds, and tenant-domain schema.

Object Storage

MinIO local development, planned Backblaze B2 production storage.

On this page

MailBYTEBITE-MAIL-01DNS (configured)Architectural directionStatusImplementedPlannedOpenResponsibility splitRelated