CopilotKit / CopilotKit/outpost
Email go-live: configure Postmark DNS for support.copilotkit.ai
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7
- Forks
- 3
- Avg merge
- 7d 16h
- Merged PRs (30d)
- 15
Description
Inbound email is built — the Postmark webhook route, the EmailPostmarkAdapter, the transport, and the templates are all on main — but the DNS for support.copilotkit.ai is not configured, so no mail reaches it.
Checklist
- MX records pointed at Postmark's inbound servers
- SPF
- DKIM
- DMARC
- Verify the domain in the Postmark dashboard
- Send a live test email and confirm a ticket is created
- Confirm the reply path (outbound) reaches the sender
The DNS records need whoever holds access to the domain — worth coordinating before starting.
Do not enable this publicly before #189 (an inbound email quoting any ticket's display ID can append to and reopen that ticket) is fixed. That is the one hard ordering constraint here.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Postmark webhook route, EmailPostmarkAdapter, transport, and templates on main, then coordinate access to configure support.copilotkit.ai. Done means the domain is verified in Postmark, inbound and outbound live email tests pass, and ticket creation is confirmed; wait for #189 to be fixed before public enablement.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100