Skip to content

Add peloran.com.email template - #1663

Open
ersanyus wants to merge 1 commit into
Domain-Connect:masterfrom
ersanyus:add-peloran-email-template
Open

Add peloran.com.email template#1663
ersanyus wants to merge 1 commit into
Domain-Connect:masterfrom
ersanyus:add-peloran-email-template

Conversation

@ersanyus

Copy link
Copy Markdown

Description

Adds the Domain Connect template for Peloran (providerId: peloran.com, serviceId: email).

Peloran (https://www.peloran.com) is a marketing and email automation platform for e-commerce merchants. Merchants connect their own sending domain so transactional and journey email (bulk campaigns, automations) can be verified with SPF, DKIM, MX, and optional click-tracking CNAME. Record values are provisioned per merchant through Resend and passed as signed template variables. Apply URLs use RS256 signing; the public key is published at _dcpubkeyv1.peloran.com (key=_dcpubkeyv1).

This template follows the same record shape as the merged resend.com.mail.json (SES outbound + Resend DKIM + click-tracking CNAME).

Type of change

  • 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

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 — peloran.com; public key TXT at _dcpubkeyv1.peloran.com (key id _dcpubkeyv1)
  • warnPhishing is not set alongside syncPubKeyDomain
  • syncRedirectDomain is set — app.peloran.com (synchronous flow uses redirect_uri)
  • no TXT record contains SPF content — uses SPFM with include:amazonses.com
  • txtConflictMatchingMode — not required: DKIM lives on fixed selector resend._domainkey; SPFM/MX use dedicated send subdomain %spfDomain% (no shared apex TXT conflict)
  • no variable is used as a bare full record value without justification — see justification below (p=%domainKey% carries provider-issued DKIM public key)
  • no bare variable is used as the full host label — see justification below (%spfDomain% and %clickTrackingSubdomain% are provider-issued labels on dedicated subdomains, same pattern as resend.com.mail.json)
  • no variable is used in the host field to create a subdomain — %spfDomain% / %clickTrackingSubdomain% are record labels on subdomains already scoped by the host parameter, not subdomain-creation variables
  • %host% does not appear explicitly in any host attribute
  • essential — all records are required for email sending; none are user-tunable optional extras (same as resend.com.mail.json)

Justifications (per-merchant provider-issued records):

Resend issues each merchant their exact DKIM public key (domainKey), send subdomain (spfDomain), SES region, and click-tracking CNAME target. Values are passed only inside RS256-signed apply URLs (syncPubKeyDomain: peloran.com), so they cannot be repurposed by third parties. This matches the established resend.com.mail.json template already in this repository.

Online Editor test results

Editor test link(s):

@github-actions github-actions Bot added the Test links missing No test links from Online Editor provided label Aug 25, 2026
@github-actions

Copy link
Copy Markdown

JSON Filename Check Passed

@github-actions

Copy link
Copy Markdown

JSON Schema Validation Passed

@github-actions

Copy link
Copy Markdown

Linter OK

peloran.com.email.json

Level Code Note

@ersanyus
ersanyus force-pushed the add-peloran-email-template branch from 3f699db to 58fc632 Compare August 25, 2026 17:01
@ersanyus
ersanyus force-pushed the add-peloran-email-template branch from 58fc632 to a2ef82c Compare August 25, 2026 17:10
@github-actions github-actions Bot removed the Test links missing No test links from Online Editor provided label Aug 25, 2026
@github-actions

Copy link
Copy Markdown

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: 2 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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant