Skip to content

Add Unbox Domain Connect Template#773

Merged
kerolasa merged 2 commits intoDomain-Connect:masterfrom
adityasahas:master
Feb 16, 2026
Merged

Add Unbox Domain Connect Template#773
kerolasa merged 2 commits intoDomain-Connect:masterfrom
adityasahas:master

Conversation

@adityasahas
Copy link
Contributor

Description

New Domain Connect template for Unbox email service configuration. This template automates DNS setup for AWS SES-based email sending and receiving, including DKIM authentication, SPF via SPFM merging, MX records for both sending (MAIL FROM) and receiving, and DMARC policy.

Type of change

Please mark options that are relevant.

  • New template
  • Bug fix (non-breaking change which fixes an issue in the template)
  • New feature (non-breaking change which adds functionality to the template)
  • Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

Please mark the following checks done

  • Schema validated using JSON Schema template.schema
  • Template functionality checked using Online Editor
  • Template is checked using template linter
  • Template file name follows the pattern <providerId>.<serviceId>.json
  • resource URL provided with logoUrl is actually served by a webserver

Checklist of common problems

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.

  • digital signatures are used and syncPubKeyDomain specified (yes, warnPhishing is an option, but some providers reject such templates by policy, so signing shall be a default)
  • syncRedirectDomain is specified when intended to use redirect_uri parameter in the synchronous flow
  • no TXT record with SPF content (i.e. "v=spf1 ...") instead of using SPFM record type on APEX
  • txtConflictMatchingMode is set on TXT records which shall be unique on a label (like DMARC)
  • variables are set to the smallest scope needed (i.e. limit possibility to be misused to set any arbitrary record and conflict with other template). Too broad scope example: @ TXT "%verification%". Better usage: @ TXT "foo-verification=%verification%".
  • no variables as a host name to apply template on subdomain instead of standard host parameter
  • no explicit usage of %host% variable in host attribute
  • essential setting is used on records, which the user shall be able to change or remove manually later without dropping the whole template (like DMARC)

Example variable values

 "testData": {
    "domainconnecttest": {
      "variables": {
        "domain": "example.com",
        "dkimToken1": "abc123xyz",
        "dkimToken2": "def456uvw",
        "dkimToken3": "ghi789rst",
        "verificationToken": "jkl012opq",
        "sesRegion": "us-east-2"
      },
      "results": [
        {
          "type": "CNAME",
          "name": "abc123xyz._domainkey",
          "ttl": 3600,
          "data": "abc123xyz.dkim.amazonses.com"
        },
        {
          "type": "CNAME",
          "name": "def456uvw._domainkey",
          "ttl": 3600,
          "data": "def456uvw.dkim.amazonses.com"
        },
        {
          "type": "CNAME",
          "name": "ghi789rst._domainkey",
          "ttl": 3600,
          "data": "ghi789rst.dkim.amazonses.com"
        },
        {
          "type": "TXT",
          "name": "_amazonses",
          "ttl": 3600,
          "data": "\"jkl012opq\""
        },
        {
          "type": "MX",
          "name": "unbox",
          "ttl": 3600,
          "data": "10 feedback-smtp.us-east-2.amazonses.com"
        },
        {
          "type": "TXT",
          "name": "unbox",
          "ttl": 6000,
          "data": "\"v=spf1 include:amazonses.com ~all\""
        },
        {
          "type": "MX",
          "name": "@",
          "ttl": 3600,
          "data": "10 inbound-smtp.us-east-2.amazonaws.com"
        },
        {
          "type": "TXT",
          "name": "_dmarc",
          "ttl": 3600,
          "data": "\"v=DMARC1; p=none; rua=mailto:dmarc@unbox.so\""
        }
      ]
    }
  }

@github-actions
Copy link

Linter OK:

Linter result for unbox.so.email-setup.json

Copy link
Member

@pawel-kow pawel-kow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@kerolasa kerolasa self-requested a review February 16, 2026 09:36
Copy link
Collaborator

@kerolasa kerolasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I am not sure why the pull request is marked as draft. I would have merged had this been ready.

@adityasahas adityasahas marked this pull request as ready for review February 16, 2026 13:56
@adityasahas
Copy link
Contributor Author

Looks good to me. I am not sure why the pull request is marked as draft. I would have merged had this been ready.

Sorry about that, must’ve been an accident on my end, just marked it as ready

@kerolasa kerolasa added this pull request to the merge queue Feb 16, 2026
Merged via the queue into Domain-Connect:master with commit 958a7a0 Feb 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants