Add jmjbillings.com ar-sending template (Postmark AR email)

[JMJBILLINGS]

Description

New template for JMJ Billings (providerId jmjbillings.com, serviceId ar-sending). Configures Postmark email sending for a customer's dedicated subdomain (standard host parameter, e.g. mail.example.com): DKIM TXT, Return-Path CNAME (pm-bounces -> pm.mtasv.net), and inbound MX (inbound.postmarkapp.com, priority 10). Requests are signed; public key published at _dck1.jmjbillings.com.

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

• syncPubKeyDomain is set
• warnPhishing is not set alongside syncPubKeyDomain
• syncRedirectDomain is set (the synchronous flow uses redirect_uri)
• no TXT record contains SPF content
• txtConflictMatchingMode — n/a: the DKIM TXT host embeds a per-instance Postmark selector (%dkimSelector%._domainkey), so no per-label conflict is possible
• no variable is used as a bare full record value — EXCEPTION with justification: %dkimValue% is a DKIM public key record (k=rsa;p=...) whose full value is prescribed by the DKIM standard and cannot carry a service prefix; the host is constrained to %dkimSelector%._domainkey
• no bare variable is used as the full host label (%dkimSelector%._domainkey — fixed ._domainkey suffix)
• no variable is used in the host field to create a subdomain — the sending subdomain is supplied via the standard host apply parameter (hostRequired: true)
• %host% does not appear explicitly in any host attribute
• essential — all three records are integral to the service; none are independently user-modifiable records (no DMARC record in this template)

Online Editor test results

Editor test link(s):
Test jmjbillings.com/ar-sending example.com/mail

Note: single subdomain-rooted test (host mail) — apex test not applicable since hostRequired: true.

[JMJBILLINGS]

Note on the failing checks: all of them die at the checkout step — the Actions runner now refuses fork-PR checkout in pull_request_target workflows without allow-unsafe-pr-checkout: true on the actions/checkout step (see the run annotations). It looks like this affects every fork PR currently, not just this one.

Meanwhile the template has been reworked to follow the Template Quality Guidelines (host-parameter pattern, signed requests, no warnPhishing), the PR description now follows the PR template, and the Online Editor test link is included above. Happy to adjust further on review.

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

jmjbillings.com.ar-sending.json

Level	Code	Note
info	DCTL1037	hostRequired template should be combined with NS or CNAME record that uses host @ or empty

[github-actions]

PR Description Check Failed

The PR description is missing required elements. Please update it according to the PR template.

Details

  WARNING: could not decode token: CRC check failed
  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

Labels to add: Test links missing
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete

PR description check FAILED:
  FAIL  'Online Editor test results': no valid editor test link found
  FAIL  Template coverage: jmjbillings.com.ar-sending.json: no editor test link found (expected template id 'jmjbillings.com.ar-sending')