Repository navigation
Add meeng.dev.sending template - #3272
Open
paulorlima9 wants to merge 1 commit into
Open
paulorlima9 wants to merge 1 commit into
paulorlima9 wants to merge 1 commit into
Conversation
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|
PR Description Check FailedThe PR description is missing required elements. Please update it according to the PR template. Details |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
New template
meeng.dev.sendingfor Meeng.dev (https://meeng.dev), an e-mail sending platform. It makes a customer's domain ready to send through Meeng.dev:sending: the return-path CNAMEmail->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 atmeeng._domainkey(p=%dkim%,txtConflictMatchingModeset toAll: the selector label must hold exactly one TXT record);tracking(optional, applied only when the customer enables link and open tracking): the CNAMElinks->track.meeng.dev.The service signs every apply request (RSA-SHA256, query without
keyandsig,siglast) with the key whose public part is published as TXT at_dck1.meeng.dev(syncPubKeyDomainismeeng.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.
How Has This Been Tested?
Please mark the following checks done
<providerId>.<serviceId>.jsonlogoUrlis actually served by a webserverChecklist 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.
syncPubKeyDomainis set — this is mandatory; omitting it requires explicit justification in the PR description or the PR will be rejectedwarnPhishingis not set alongsidesyncPubKeyDomain— the two must not appear togethersyncRedirectDomainis set whenever the template usesredirect_uriin the synchronous flow"v=spf1 ...") — use theSPFMrecord type insteadtxtConflictMatchingModeis set on every TXT record that must be unique per label or content prefix (e.g. DMARC)@ TXT "%foo%") unless necessary — prefer@ TXT "service-foo=%foo%"; if bare, justify in the PR descriptionhostlabel — the non-variable parts are fixed to limit misuse (e.g.%dkimkey%._domainkey, not%dkimhost%); if bare, justify in the PR descriptionhostfield to create a subdomain — use thehostparameter ormultiInstanceinstead%host%does not appear explicitly in anyhostattributeessentialis set toOnApplyon 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 recordLocal checks:
dc-template-linter -cloudflare -tolerate warn meeng.dev.sending.jsonexits 0 (two informational findings, DCTL5003 and DCTL5008, both about Cloudflare ignoringsyncRedirectDomainand TXT conflict matching),dc-template-linter -merge-or-failexits 0, anddc-template-linter -logosexits 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 domainexample.comwith an empty host, and a subdomain test with hostsend; groupssendingandsending,tracking.