Add SendCanary DKIM CNAME templates (dkim-1, dkim-2, dkim-3)#945
Open
jotra7 wants to merge 2 commits intoDomain-Connect:masterfrom
Open
Add SendCanary DKIM CNAME templates (dkim-1, dkim-2, dkim-3)#945jotra7 wants to merge 2 commits intoDomain-Connect:masterfrom
jotra7 wants to merge 2 commits intoDomain-Connect:masterfrom
Conversation
Three templates for pushing DKIM CNAME records to enable email signing. Provider-agnostic: works for any email provider (Google Workspace, Microsoft 365, Resend, SendGrid, Mailchimp, etc.) - dkim-1: 1 CNAME record (e.g. Google Workspace) - dkim-2: 2 CNAME records (e.g. Microsoft 365) - dkim-3: 3 CNAME records (e.g. Resend, SendGrid, Mailchimp) Variables use fully-parameterized host and pointsTo fields so the same templates work for any email provider's DKIM selectors and targets.
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
Linter OK
|
| Level | Code | Note |
|---|---|---|
| info | DCTL1031 | all record groupId values are the same |
sendcanary.com.dkim-2.json
| Level | Code | Note |
|---|
sendcanary.com.dkim-3.json
| Level | Code | Note |
|---|
pawel-kow
requested changes
Apr 6, 2026
sendcanary.com.dkim-1.json
Outdated
| { | ||
| "groupId": "dkim1", | ||
| "type": "CNAME", | ||
| "host": "%host1%", |
Member
There was a problem hiding this comment.
This can be done better.
See Rule 7 in README.
Applies to all templates.
Rename bare %host1% to %selector1%._domainkey so the ._domainkey suffix is fixed and only the selector varies. Addresses review feedback from pawel-kow.
PR Description Check FailedThe PR description is missing required elements. Please update it according to the PR template. Details |
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
Three new templates for SendCanary to push DKIM CNAME records for email signing setup. Provider-agnostic -- works for any email provider (Google Workspace, Microsoft 365, Resend, SendGrid, Mailchimp, etc.).
Host variables use scoped
%selector%._domainkeypattern per Rule 7 -- the._domainkeysuffix is fixed, only the selector name varies.Type of change
How Has This Been Tested?
Checklist of common problems
Online Editor test results
sendcanary.com.dkim-1.json (1 CNAME - Google Workspace):
sendcanary.com.dkim-2.json (2 CNAMEs - Microsoft 365):
sendcanary.com.dkim-3.json (3 CNAMEs - Resend/SendGrid/Mailchimp):
Existing Templates
SendCanary already has 3 templates in the registry: