add Hikyak, Hikyak Email DNS#1380
Merged
Merged
Conversation
# Description Adds Hikyak's signed Domain Connect template for outbound AWS SES authentication and optional inbound routing. ## Type of change - [x] New template # How Has This Been Tested? - [x] Online Editor apex and subdomain tests - [x] JSON parsing and merged-candidate comparison ## Online Editor test results The exact generated test links are included in the pull request description. Co-Authored-By: Codex <noreply@openai.com>
|
✅ JSON Filename Check Passed |
|
✅ JSON Schema Validation Passed |
PR Description Check PassedAll required sections are filled in correctly. Details |
Linter OK
|
| Level | Code | Note |
|---|
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
Adds Hikyak's signed Domain Connect email template for outbound AWS SES authentication and optional inbound routing. The template exposes separate outbound, inbound, and root wildcard groups so the application can request sending, receiving, or both.
Type of change
How Has This Been Tested?
<providerId>.<serviceId>.jsonlogoUrlis actually served by a webserver (not applicable; this template does not includelogoUrl)Checklist of common problems
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 (not applicable; the template has no TXT records)hostlabelhostfield to create a subdomain — the standardhostparameter is used%host%does not appear explicitly in anyhostattributeessentialis set toOnApplyon records the end user may need to modify independently (not applicable; no independently editable policy record is included)Online Editor test results