Add DMARCeye Domain Connect template

[bart-el]

Description

Adds a new Domain Connect template for DMARCeye setup. Template configures SPF, DMARC, BIMI, MTA-STS and TLSRPT records using provider-supplied variables; DMARC record marked as essential. Signed sync flow enabled with syncPubKeyDomain=app.dmarceye.com and redirect domain whitelist.

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

<-- to make review process easier please provide the whole testData object from the Online Editor after testing and using "Add as test" button. Hint: test also with "host" variable set. -->

{
  "testData": {
    "test-dmarceye": {
      "variables": {
        "domain": "example.com",
        "group": [
          "spf",
          "dmarc",
          "bimi",
          "mta-sts",
          "tlsrpt"
        ],
        "spfDomain": "@",
        "spfRules": "include:_spf.google.com",
        "dmarctxt": "v=DMARC1; p=none; rua=mailto:dmarc@dmarceye.com",
        "bimitxt": "v=BIMI1; l=https://dmarceye.com/logo.svg; a=https://dmarceye.com/cert.pem",
        "mta_sts_txt": "v=STSv1; id=2026021101",
        "tlsrpt": "v=TLSRPTv1; rua=mailto:tlsrpt@dmarceye.com"
      },
      "results": [
        {
          "type": "TXT",
          "name": "@",
          "ttl": 3600,
          "data": "\"v=spf1 include:_spf.google.com ~all\""
        },
        {
          "type": "TXT",
          "name": "_dmarc",
          "ttl": 3600,
          "data": "\"v=DMARC1; p=none; rua=mailto:dmarc@dmarceye.com\""
        },
        {
          "type": "TXT",
          "name": "default._bimi",
          "ttl": 3600,
          "data": "\"v=BIMI1; l=https://dmarceye.com/logo.svg; a=https://dmarceye.com/cert.pem\""
        },
        {
          "type": "TXT",
          "name": "_mta-sts",
          "ttl": 600,
          "data": "\"v=STSv1; id=2026021101\""
        },
        {
          "type": "TXT",
          "name": "_smtp._tls",
          "ttl": 3600,
          "data": "\"v=TLSRPTv1; rua=mailto:tlsrpt@dmarceye.com\""
        }
      ]
    }
  }
}

[github-actions]

Linter OK:

Linter result for dmarceye.com.dmarceye-setup.json

[pawel-kow]

lgtm