Skip to content

Add meeng.dev.sending template - #3272

Open
paulorlima9 wants to merge 1 commit into
Domain-Connect:masterfrom
meeng-dev:add-meeng.dev-sending
Open

paulorlima9 wants to merge 1 commit into
Domain-Connect:masterfrom
meeng-dev:add-meeng.dev-sending

Conversation

@paulorlima9

@paulorlima9 paulorlima9 commented Nov 21, 2026 •

Copy link
Copy Markdown

Description

New template meeng.dev.sending for Meeng.dev (https://meeng.dev), an e-mail sending platform. It makes a customer's domain ready to send through Meeng.dev:

  • group sending: the return-path CNAME mail -> return.meeng.dev (the SPF record and the MX of the return path live at that host, so nothing else is published on the customer's zone) and the DKIM key at meeng._domainkey (p=%dkim%, txtConflictMatchingMode set to All: the selector label must hold exactly one TXT record);
  • group tracking (optional, applied only when the customer enables link and open tracking): the CNAME links -> track.meeng.dev.

The service signs every apply request (RSA-SHA256, query without key and sig, sig last) with the key whose public part is published as TXT at _dck1.meeng.dev (syncPubKeyDomain is meeng.dev). DMARC is deliberately not part of the template: it belongs to the customer's apex and the service never touches it.

Contact for questions about this template: ajuda@meeng.dev

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 — not checked yet, see the note at the end of this description
  • 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) — not applicable: every record is required for sending, and there is no DMARC record

Local checks: dc-template-linter -cloudflare -tolerate warn meeng.dev.sending.json exits 0 (two informational findings, DCTL5003 and DCTL5008, both about Cloudflare ignoring syncRedirectDomain and TXT conflict matching), dc-template-linter -merge-or-fail exits 0, and dc-template-linter -logos exits 0.

Online Editor test results

Editor test link(s): none yet. The sharable "Copy Markdown" link needs a signed-in session in the Online Editor, and we have not produced one, so we cannot claim an editor run here. What was checked is the local linter run above. If the maintainers want the signed-in editor links before the review, we will add them to this description as soon as we have them. Suggested test inputs: variable dkim (any base64 text), apex domain example.com with an empty host, and a subdomain test with host send; groups sending and sending,tracking.

@github-actions

Copy link
Copy Markdown

✅ JSON Filename Check Passed

@github-actions

Copy link
Copy Markdown

✅ JSON Schema Validation Passed

@github-actions github-actions Bot added PR description incomplete The PR description template was not filled in at all, altered or filled in improperly. Test links missing No test links from Online Editor provided labels Nov 21, 2026
@github-actions

Copy link
Copy Markdown

Linter OK

meeng.dev.sending.json

Level Code Note

@github-actions github-actions Bot added the automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. label Nov 21, 2026
@github-actions

Copy link
Copy Markdown

PR Description Check Failed

The PR description is missing required elements. Please update it according to the PR template.

Details
  OK  Type of change: 1/4 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked

Labels to add: PR description incomplete, Test links missing
Labels to remove: Checklist of common problems not complete, Forged editor links

PR description check FAILED:
  FAIL  'How Has This Been Tested?': 1/3 checkboxes are not ticked
  FAIL  'Online Editor test results': no valid editor test link found
  FAIL  Template coverage: meeng.dev.sending.json: no editor test link found (expected template id 'meeng.dev.sending')

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. PR description incomplete The PR description template was not filled in at all, altered or filled in improperly. Test links missing No test links from Online Editor provided

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant