Skip to content

Add DeepCurrent Mailgun outreach template#1127

Open
ulmoai wants to merge 1 commit into
Domain-Connect:masterfrom
ulmoai:deepcurrent-mailgun-outreach
Open

Add DeepCurrent Mailgun outreach template#1127
ulmoai wants to merge 1 commit into
Domain-Connect:masterfrom
ulmoai:deepcurrent-mailgun-outreach

Conversation

@ulmoai
Copy link
Copy Markdown

@ulmoai ulmoai commented May 20, 2026

Description

Adds the DeepCurrent managed email Domain Connect template.

This template configures a selected sending subdomain for outbound email through DeepCurrent's managed Mailgun/Smartlead infrastructure.

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

  • Template functionality attempted using Online Editor; editor redirected to provisioned OIDC login and returned a server error, so no signed editor token link is available yet
  • 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 TXT records requiring unique conflict matching are included
  • 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); no such end-user-modified records are included

Online Editor test results

Editor test link(s):

No signed Online Editor token link is available yet.

The editor redirected to provisioned OIDC login and returned a server error from this validation session. No forged editor link is included.

Template

  • Provider ID: deepcurrent.app
  • Service ID: mailgun-outreach
  • File: deepcurrent.app.mailgun-outreach.json

DNS Records

  • SPFM for Mailgun sending
  • Mailgun Automatic Sender Security PDK CNAME records
  • Mailgun tracking CNAME
  • Mailgun MX records scoped to the selected sending subdomain

The template uses the standard Domain Connect host apply parameter for selected sending subdomains. It does not use a custom host variable.

Signing

  • syncPubKeyDomain: domainconnect.deepcurrent.app
  • Key label for testing: _dcpubkeyv1

Validation

  • Online Editor signed token result: unavailable due provisioned editor login / server error
  • dc-template-linter -cloudflare -logos: passed

Linter note: DCTL5003 syncRedirectDomain is not supported. Cloudflare documents this as ignored for its implementation.

Live DNS / Mailgun Test

The template values were manually applied to an isolated test domain, outreach-test.deepcurrent.app, without touching existing production outreach domains or Smartlead campaigns.

Mailgun verification result:

  • Domain state: active
  • SPF: valid
  • PDK1 CNAME: valid
  • PDK2 CNAME: valid
  • Tracking CNAME: valid
  • MX records: valid

Notes

Human replies are handled by the configured reply-to mailbox in DeepCurrent/Smartlead. The Mailgun MX records are scoped to the sending subdomain and match the current production Mailgun setup pattern.

@github-actions github-actions Bot added Checklist of common problems not complete See PR template and mark *all* checkboxes, even if not applicable. Explain any discrepancies. PR description incomplete The PR description template was not filled in at all, altered or filled in improperly. labels May 20, 2026
@github-actions
Copy link
Copy Markdown

JSON Filename Check Passed

@github-actions github-actions Bot added the Test links missing No test links from Online Editor provided label May 20, 2026
@github-actions
Copy link
Copy Markdown

JSON Schema Validation Passed

@github-actions github-actions Bot added the automerge-possible Label indicating, that restrictive linter checks all pass. For now it's PoC. label May 20, 2026
@github-actions
Copy link
Copy Markdown

Linter OK

deepcurrent.app.mailgun-outreach.json

Level Code Note

@github-actions github-actions Bot removed Checklist of common problems not complete See PR template and mark *all* checkboxes, even if not applicable. Explain any discrepancies. PR description incomplete The PR description template was not filled in at all, altered or filled in improperly. labels May 21, 2026
@github-actions
Copy link
Copy Markdown

PR Description Check Failed

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

Details
  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 11/11 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: deepcurrent.app.mailgun-outreach.json: no editor test link found (expected template id 'deepcurrent.app.mailgun-outreach')

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. Test links missing No test links from Online Editor provided

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant