add OSV-1, Email sending and receiving

[ankrstak]

Description

New template for OSV-1 (osv-1.com), service email: the DNS records an organization needs to send and receive its email through OSV-1 (Resend / Amazon SES underneath) on the hostname it chooses — typically a subdomain such as notify.example.com, apex allowed.

• sending: DKIM TXT at resend._domainkey (p=%dkim%), bounce-path MX at send (feedback-smtp.%region%.amazonses.com), SPFM at send (include:amazonses.com), and the sending-host CNAME rsend → send.forge.rmta.net that the email provider now requires for new domains and checks directly (fixed target, as in update SendBeam, SendBeam sending domain (version 2) #1827)
• receiving: MX at the host itself (inbound-smtp.%region%.amazonaws.com) — requested only for domains that receive mail
• dmarc: fixed v=DMARC1; p=none; with Prefix matching, essential: OnApply

Variables are scoped narrowly: region only varies the SES region inside fixed hostnames; dkim is the key material after a fixed p= prefix. Synchronous flow with signed requests (syncPubKeyDomain osv-1.com, key published at _dck1.osv-1.com); syncRedirectDomain osv-1.com (redirect_uri lives on app.osv-1.com).

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

Mark all the checkboxes after conducting the check. Comment on any point which is not fulfilled.
See Template Quality Guidelines for details and rationale on each rule.

• syncPubKeyDomain is set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejected
• warnPhishing is not set alongside syncPubKeyDomain — the two must not appear together
• 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 — prefer @ TXT "service-foo=%foo%"; if bare, justify in the PR description
• no bare variable is used as the full host label — the non-variable parts are fixed to limit misuse (e.g. %dkimkey%._domainkey, not %dkimhost%); if bare, justify in the PR description
• 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):

• Subdomain, all groups: Test osv-1.com/email example.com/notify
• Apex, all groups: Test osv-1.com/email example.com/@
• Subdomain, groups sending + dmarc only (no receiving MX): Test osv-1.com/email example.com/notify

🤖 Generated with Claude Code

[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: 3 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

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

osv-1.com.email.json

Level	Code	Note

[github-actions]

Linter passed all checks — approving for auto-merge.

[github-actions]

Linter passed all checks — approving for auto-merge.

[github-actions]

Thanks @ankrstak for contributing to the template. 🎉

This template has been reviewed and merged by @pawel-kow. 🙌

This template repository and its review process are maintained by independent individuals in their spare time, not as part of a paid role. If you or your company benefit from this protocol and its tools, please show your appreciation by buying a beer for @pawel-kow: https://github.com/sponsors/pawel-kow