Skip to content

Add ventorie email template#1390

Merged
pawel-kow merged 3 commits into
Domain-Connect:masterfrom
ventorie:add-ventorie-email-template
Jul 14, 2026
Merged

Add ventorie email template#1390
pawel-kow merged 3 commits into
Domain-Connect:masterfrom
ventorie:add-ventorie-email-template

Conversation

@ventorie

@ventorie ventorie commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Description

New Domain Connect template for Ventorie (https://ventorie.com), a supply-chain
platform for eCommerce brands. The template configures verified-domain email via
Resend in one apply: outbound sending (SPFM + feedback MX on vsend, DKIM on
resend._domainkey) and a reply subdomain for inbound routing (reply MX plus its
own SPFM/feedback-MX/DKIM under vsend.reply / resend._domainkey.reply).
The vendor-prefixed vsend host is deliberate: our customers are Shopify brands
where send.{domain} is commonly NS-delegated to Klaviyo for its dedicated
sending domains, so a conventional send host would collide with or be shadowed
by existing setups.

No records are written on the domain apex, so existing mailbox routing
(Google Workspace, Microsoft 365) is never touched. All records are DNS-only
(MX/TXT/SPFM) and must not be proxied. Sync flow only.

Bare-variable justification (per the checklist): %dkim% and %replydkim%
are the full TXT values on the two resend._domainkey hosts by necessity — a
DKIM record's entire value is the key material (p=…) issued per-domain by the
email provider; it cannot carry a fixed prefix. The hosts are fixed labels.

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
  • 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)

Online Editor test results

Editor test link(s):
Test ventorie.com/email example.com/@
Test ventorie.com/email example.com/shop

@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

ventorie.com.email.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 Jul 14, 2026
github-actions[bot]
github-actions Bot previously approved these changes Jul 14, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linter passed all checks — approving for auto-merge.

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

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Linter passed all checks — approving for auto-merge.

@github-actions github-actions Bot removed the Test links missing No test links from Online Editor provided label Jul 14, 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

@pawel-kow
pawel-kow added this pull request to the merge queue Jul 14, 2026
Merged via the queue into Domain-Connect:master with commit 968eac6 Jul 14, 2026
7 of 8 checks passed
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants