eoinbox is not open yet. This site describes the service we are building; items marked "Later" arrive after launch.
All docs

Set up DNS at Amazon Route 53

Add the eoinbox DNS records to a public hosted zone in Amazon Route 53.

Menus change. Amazon Route 53 updates its dashboard from time to time, so button and menu names may differ slightly from this guide. Look for the DNS settings of your domain; the records you need are always the same. Your eoinbox dashboard shows the exact values and checks them for you.

Find the hosted zone

  1. Sign in to the AWS Management Console and open Route 53.
  2. Choose Hosted zones and select the public hosted zone for your domain.
  3. Click Create record for each record set. In the wizard, switch to the quick create view if you see a choice.

Make sure the domain actually uses this hosted zone: the NS records of the zone must match the nameservers set at your registrar. If you created a zone more than once, only one of them is live.

TypeName / hostValue / targetPriorityStatus
TXT@eoinbox-verify=<your token>Proves you own the domainRequired
MX@mx1.eoinbox.comReceiving mail10Required
MX@mx2.eoinbox.comReceiving mail (backup)20Required
TXT@v=spf1 include:spf.eoinbox.com ~allSPF, allows us to send for youRequired
CNAMEeo1._domainkeyeo1._domainkey.<id>.dkim.eoinbox.comDKIM signing key 1Required
CNAMEeo2._domainkeyeo2._domainkey.<id>.dkim.eoinbox.comDKIM signing key 2Required
CNAMEeo3._domainkeyeo3._domainkey.<id>.dkim.eoinbox.comDKIM signing key 3Required
TXT_dmarcv=DMARC1; p=none; rua=mailto:<id>@dmarc.eoinbox.comDMARC policy and reportsRecommended
CNAMEmta-stsmta-sts.eoinbox.comMTA-STS policy hostRecommended
TXT_mta-stsv=STSv1; id=<policy id>MTA-STS, enforces TLS for incoming mailRecommended
TXT_smtp._tlsv=TLSRPTv1; rua=mailto:<id>@tlsrpt.eoinbox.comTLS reportingRecommended
CNAMEautoconfigautoconfig.eoinbox.comAutomatic setup in mail appsOptional
CNAMEautodiscoverautoconfig.eoinbox.comAutomatic setup in OutlookOptional
SRV_imaps._tcp0 1 993 mail.eoinbox.comIMAP discoveryOptional
SRV_submissions._tcp0 1 465 mail.eoinbox.comSMTP discoveryOptional
SRV_jmap._tcp0 1 443 mail.eoinbox.comJMAP discoveryOptional

Route 53 specifics

Route 53 works with record sets: one name and type, with one or more values, each on its own line. That changes how a few records are entered.

  • Record name: leave empty for the domain itself. Otherwise type the name from the table, such as _dmarc or eo1._domainkey.
  • MX: create one MX record set at the domain with two lines:
    10 mx1.eoinbox.com
    20 mx2.eoinbox.com
  • TXT at the domain itself: the verification record and SPF both live at the domain, so they go into one TXT record set, each value on its own line and in double quotes:
    "eoinbox-verify=<your token>"
    "v=spf1 include:spf.eoinbox.com ~all"
    If a TXT record set already exists there (for example with Google verification), edit it and add the lines instead of creating a new one.
  • Other TXT records: also in double quotes, for example "v=DMARC1; p=none; rua=mailto:<id>@dmarc.eoinbox.com".
  • CNAME: value is the target, for example eo1._domainkey.<id>.dkim.eoinbox.com.
  • SRV: value in the form priority weight port target, for example 0 1 993 mail.eoinbox.com.
  • TTL: 300 seconds is a good choice while you set things up.

Remove old mail records

If the domain received mail elsewhere (for example Amazon WorkMail or Google Workspace), edit the existing MX record set and replace its values with ours when you are ready to switch. Merge the SPF value into the existing one rather than adding a second v=spf1 line.