Add SimploMail Domain Connect email template

[simplyi]

Description

Update the SimploMail Domain Connect template for email sending to use the synchronous flow.

This template configures:

• Amazon SES Easy DKIM using 3 CNAME records
• SPF using SPFM
• DMARC with p=none
• Custom MAIL FROM using SES MX + SPF

This update changes the template from async-only behavior to synchronous behavior by:

• setting syncBlock to false
• adding syncPubKeyDomain
• adding syncRedirectDomain

This update also removes the rua email address from the DMARC record, so the DMARC value is now simply v=DMARC1; p=none;.

Type of change

• 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?

• Template functionality checked using Online Editor

• Template file name follows the pattern <providerId>.<serviceId>.json

• resource URL provided with logoUrl is actually served by a webserver

• simplomail.com.email apex

• simplomail.com.email host

Checklist of common problems

• syncPubKeyDomain is set
• warnPhishing is not set alongside syncPubKeyDomain
• syncRedirectDomain is set whenever the template uses redirect_uri in the synchronous flow
• no TXT record contains SPF content ("v=spf1 ...") — use the SPFM record type instead
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (e.g. DMARC)
• no variable is used as a bare full record value (e.g. @ TXT "%foo%") unless necessary
• no bare variable is used as the full host label — the non-variable parts are fixed to limit misuse
• no variable is used in the host field to create a subdomain — use the host parameter or multiInstance instead
• %host% does not appear explicitly in any host attribute
• essential is set to OnApply on records the end user may need to modify or remove without breaking the template (e.g. DMARC)

Online Editor test results

Editor test link(s):

• simplomail.com.email apex

• simplomail.com.email host

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

simplomail.com.email.json

Level	Code	Note

[simplyi]

All checks are passing now. This PR is ready for review.

[pawel-kow]

are you super sure about syncBlock?
Are you in contact with DNS providers which will onboard the template for async flow?

[simplyi]

No. I am not very sure about the syncBlock. The reason I chose to go with it is because it sounded simpler to start. Since it is my first time doing this, I wanted to start small with an easy integration. And then, expand. syncBlock sounded much easier to go with. I am not in touch with DNS providers yet because it is my understanding that the first step is to prepare the template, and only then contact providers to onboard it. I trust you have much more experience with this than I do. If you think that going with async will be more problematic than going with sync, then I will go with the sync approach and will update this template.

[pawel-kow]

No. I am not very sure about the syncBlock. The reason I chose to go with it is because it sounded simpler to start. Since it is my first time doing this, I wanted to start small with an easy integration.

syncBlock = you are left with async flow. This one is way more complex than sync.

And then, expand. syncBlock sounded much easier to go with. I am not in touch with DNS providers yet because it is my understanding that the first step is to prepare the template, and only then contact providers to onboard it. I trust you have much more experience with this than I do. If you think that going with async will be more problematic than going with sync, then I will go with the sync approach and will update this template.

Yes, you will be better off with sync. Use signature though.

[simplyi]

Alright, thank you 👍🏻. I will update it to use the sync flow instead.

[github-actions]

PR Description Check Passed

All required sections are filled in correctly.

Details

  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked
  OK  Online Editor test results: 2 link(s) found
  OK  Template coverage: all 1 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED