Add reply.cv.email template

[feelthefusion]

Description

Adds the reply.cv email service template (providerId reply.cv, serviceId email). One apply sets up sending and receiving on a domain: DKIM (CNAME), inbound MX (apex), custom MAIL FROM (MX + SPF via SPFM merge on the mail host), and DMARC. Signed template (syncPubKeyDomain: reply.cv; public key published at _dcpubkeyv1.reply.cv).

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

• 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

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 ...") — the SPF policy uses the SPFM record type
• txtConflictMatchingMode is set on every TXT record that must be unique per label or content prefix (DMARC uses Prefix / v=DMARC1)
• no variable is used as a bare full record value — the only bare variables are pointsTo targets on CNAME/MX records (%dkimtarget%, %mxtarget%, %mailfrommx%), which are inherently full provider-supplied hostnames; there is no fixed prefix to add for these record types
• no bare variable is used as the full host label (all hosts are fixed: reply._domainkey, @, mail, _dmarc)
• no variable is used in the host field to create a subdomain
• %host% does not appear explicitly in any host attribute
• essential is set to OnApply on the DMARC record

Online Editor test results

Editor test link(s):
Test reply.cv/email example.com/@
Test reply.cv/email example.com/sub

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

reply.cv.email.json

Level	Code	Note

[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