Skip to content

feat(skills): move Mandrill sends to PostHog - #467

Draft
Silthus wants to merge 693 commits into
mainfrom
feat/migrate-email-mandrill
Draft

Silthus wants to merge 693 commits into
mainfrom
feat/migrate-email-mandrill

Conversation

@Silthus

@Silthus Silthus commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Parked until after 2026-11-25. Michael chose SendGrid as the first migrate-email provider on 2026-11-14; this PR stays a draft and resumes after that date, with the slim pass from research/2026-11-14-review-bloat-retro before its next review round.

Problem

A person who sends with Mailchimp Transactional, formerly Mandrill, and asks to move those sends to PostHog gets no help: migrate-email has no Mailchimp Transactional variant.

With this PR, migrate-email-mandrill moves Mailchimp Transactional sends to PostHog's email send in each language where PostHog has one, whether the app uses the official SDKs, the older mandrill clients, a community client or the HTTP API, and wizard migrate mandrill runs it.

Important

Stacked on #472, the core migrate-email skill. The base stays feat/migrate-email-all-sdks until #472 merges. Each provider PR adds its own provider and lands in any order. The lists they all touch, config.yaml, AGENTS.md and the skill test, conflict in one line each as they land.
It adds one provider folder, one config variant, one AGENTS.md row and the provider in the bundle test. The shared steps it uses come from #472.
It waits for the PostHog SDK releases with the code-form email send: nothing in this stack merges until code sends are live and usable for customers.

Impact

Sends that arrive with migratedFrom: 'mandrill' show whether people use this skill to move off Mailchimp Transactional. Read it 14 days after the Wizard runs migrate as a family.

Merge risk

Caution

🔴 Merge risk: high · two-way door until the next context-mill release ships the skill; one-way once agents run it, because a migration's changes persist in each app's code and PostHog account

  • Once merged, the skill ships with the next context-mill release, and a person who runs wizard migrate mandrill gets an agent that rewrites their Mailchimp Transactional send code, where the base offers no such migration. A wrong instruction silently changes how the agent rewrites sends: a refused recipient that used to pass quietly now fails the send, a site moves that Mailchimp Transactional sent differently, or a denylisted address gets mail. The account-level branches have no run either: a Sending Defaults setting the person names or can't tell, such as the BCC address that copies every send without its own bcc_address, open tracking, or inline CSS, and the account's rules. A wrong answer there moves a site that then silently loses its BCC copy or its tracking. That row has no live run (gap below), so its residual risk is silent harm once the person deploys the rewrite.
  • Two changes are by design, not by a wrong instruction, and the report tells the person of both. A moved send reaches an address on the Rejection Denylist for a spam complaint, since PostHog blocks a moved send only to an address that hard-bounced, as feat(migrate-email): move Resend sends in every PostHog SDK's language #472's Step 5 says for every provider. And an imported hard bounce stays blocked in PostHog until someone removes it, where Mailchimp Transactional sent to the address again after seven days. Step 3 keeps the sites that rely on the denylist's custom and unsubscribe entries.
  • Everyone else is unchanged: the shadow diff of the built bundles against feat(migrate-email): move Resend sends in every PostHog SDK's language #472 changes only the Mailchimp Transactional bundles and the manifest, and the bundle test shows the other variants build without the Mailchimp Transactional folder.
  • Once agents run it, a migration's changes stay in that app's code and PostHog account: the rewritten sends, the senders, the imported suppression entries, the key, and templates the person moved. A revert of the skill doesn't undo them.
  • Switch-off: none: a revert only stops new runs. Fix forward by changing the variant's text, or drop the mandrill variant from config.yaml to stop new runs.
  • Tier: critical (b: the grade is high; c: one-way once agents run it)

Rollout

Summary

references/mandrill/ holds the three files each variant has:

  • sdk-reference.md: the official packages in Node.js, Python, Ruby and PHP, the older mandrill clients, community clients in Go, .NET and Elixir, the HTTP API, SMTP and framework mailers. It covers how each reports an error: the Node.js and PHP SDKs answer the error in place of the list, the others raise, and a PHP connection error follows the Guzzle version in composer.lock (answered with Guzzle 6, thrown with Guzzle 7). Every SDK answers a refused recipient as rejected or invalid in a successful answer. It also covers the send fields, stored templates and merge languages, status reads, signed webhooks, and the APIs that are not sends.
  • mapping.md:
    • Fields. Each field maps to PostHog's or names what keeps a site on Mailchimp Transactional: more than one to entry or none, cc and bcc entries, bcc_address, headers other than Reply-To, tags, metadata, attachments, images, subaccount, send_at, ip_pool, custom signing and return-path domains, important, send-raw, SMTP and framework mailers. inline_css keeps a site only when its HTML has a <style> element, or the code doesn't show that it has none. A tracking_domain is dropped, and the plan row notes that PostHog counts no clicks. A send through the older PHP client mandrill/mandrill, or a copy of it kept in the app's code under other names, stays: its source is no longer published, so how it failed can't be read.
    • Sending Defaults and rules. A field the site leaves out takes the account's default for tracking, inline CSS, HTML and plain-text generation and merge language, and the site is classified with that value. The person gives the defaults and the account's rules, since the API can't read them. A setting the person can't tell keeps the sites it could change, each with its own reason: account tracking not checked, account inline CSS not checked, account HTML part not checked, plain-text part not checked, merge language not checked, or sending rule not checked. Since feat(migrate-email): move Resend sends in every PostHog SDK's language #472, PostHog makes a text part whenever a send has none, so an HTML send that Mailchimp Transactional sent with no text part, with auto_text: false or the plain-text box off, stays: turns the plain-text part off.
    • Tracking. Opens and clicks are worked out per site from the send's fields, the Sending Defaults and the rules. Tracking never maps to captureEngagement: PostHog adds its open pixel to every email and counts no clicks for a send in the code form, as Step 7 says. Opens untracked, from track_opens: false, the Sending Defaults or a rule, or in a send with no html and auto_html off, which had no HTML part for the pixel, go to Step 3's "Opens the provider didn't track", which moves them only with the person's yes; opens nobody can tell stay (open tracking not checked). Opens tracked moves, and the plan row notes that PostHog counts no clicks when Mailchimp Transactional tracked them and the site moves in the code form.
    • Templates. A stored template, a send-mc-template template, and merge tags in a send's own content move by bringing the email into the code, as the core's template-to-code.md says: the code renders the Mailchimp merge language or Handlebars, fills mc:edit regions from template_content, and sends the rendered subject, HTML, text and from, read from a Mailchimp template's own subject and sender fields for send-mc-template. Tags and helpers whose output the docs don't define, such as *|UNSUB:…|*, title, partials, or a {{#with}} over a value that can be missing, keep the site. A template in PostHog is made only when the person asks for one, with the Liquid conversions the mapping lists.
    • Errors. Never widen a catch; a catch of every error stays as it is. A refused recipient and an API error stay two branches: a branch on a rejected recipient runs only for recipient_suppressed, handled the way the site handled it, and a branch on one reject_reason moves only when the site treats hard-bounce, spam and custom the same. A branch on ValidationError reads validation_error, after recipient_suppressed; a branch on an invalid recipient alone, or a site that went on for one, becomes a check of the address before the send. Python and Ruby raise network_error again, which the old catch never saw. A caller or retry policy that took the HTTP library's base network error also takes network_error; one that took only some network failures, or that the app doesn't own, keeps the site. A try that also holds a Mailchimp Transactional call that stays keeps the provider's handler and gets PostHog's next to it. A mandrill-api call without onError keeps the site: the old client threw its errors outside the call, where no catch saw them, and a moved send's error reaches the code around it. A replaced onerror keeps the site too.
    • Webhooks. Each event maps to a $workflows_email_* event. A click maps only for a template made in PostHog that is not marked sensitive: a send in the code form counts no clicks. A handler that matches events by the send's _id, a site that sets metadata, a click handler on a site that doesn't move to such a template, or a handler of a message event with no PostHog event, such as soft_bounce, deferral, unsub or reject, keeps its sites on Mailchimp Transactional.
    • HTTP and deadlines. A request to the send endpoints becomes the SDK's send. The part names the deadlines that count as the site's own, from the official SDKs' timeout setters to HTTP and community clients' timeouts, and leaves what to do with them to Step 7's shared rule. A send the code can cancel moves only where the PostHog send takes the same cancellation.
    • Suppression writes. rejects.add, rejects.delete and allowlists.add on the main account stay on Mailchimp Transactional, and Step 3 and Step 5 say what to do with each. Step 3's question names the Rejection Denylist and asks about its custom and unsubscribe entries, which PostHog doesn't block for a moved send; a site that relies on them stays (relies on Mailchimp Transactional's suppression list). The bounces that sites still on Mailchimp Transactional add come in through the report's weekly re-import, as Step 5's "Re-import only" says.
  • account.md: Mailchimp Transactional's DKIM, verification and DMARC records next to PostHog's, a read-only key limited to templates/info, templates/list, mctemplates/info and rejects/list, the Sending Defaults and rules to ask for, and a template's published version. An account that adds an unsubscribe footer, or can't tell, keeps every site, since PostHog's send adds none. The BCC address in the Sending Defaults keeps every site that sets no bcc_address. sdk-reference.md has Step 6 ask which places set a Mailchimp Transactional test key, which delivered nothing, so the report warns that a PostHog key there delivers real email. The suppression import takes the main account's unexpired hard bounces, spam complaints and custom entries from the Rejection Denylist, with PostHog's reason bounce, complaint and manual, and the report tells the person that PostHog keeps an imported hard bounce until removed, where Mailchimp Transactional let it expire after seven days. It leaves out subaccount entries (their sends stay), soft bounces, expired entries and unsubscribes, with the reason why.
  • SMTP sends through smtp.mandrillapp.com stay: PostHog has no SMTP relay, as Resend's row says on this base.

Evidence

  • Lane gate on 6a28c92, after main merged feat(migrate-email): move Resend sends in every PostHog SDK's language #472: vitest run scripts passes 344 tests in 30 files, and node scripts/build.js builds every skill, migrate-email-mandrill included, with a clean tree after.
  • Owed proofs, fleet proof gate on 6a28c92:
    • shadow-diff: the built bundles at 6a28c92 against main at 8cd7381: only the Mailchimp Transactional bundle and its manifest and skill-menu entries change.
    • live-run: gap. An agent run of this provider's migration on a real app needs the released email SDKs and the production send API. The planned trial on generated codebases runs it after both land.
    • CI: now that the base is main, build.yml runs, and build passes on 6a28c92, with every other check. The CI gap recorded before feat(migrate-email): move Resend sends in every PostHog SDK's language #472 merged no longer applies.
    • Prod-shape: gap. The inputs are customer-written send code and config and each person's Mailchimp Transactional account content; there is no store of real customer codebases to sample. Michael's planned trial on generated codebases covers it after the SDKs land.
  • Test seams (migrate-email-skill.test.js): the Mailchimp Transactional bundle resolves every reference, holds its three files and the eight rewrite files and no other provider's folder, never maps open or click tracking onto engagement capture, brings its templates into the code with a template in PostHog only on request, and is a migrate subcommand.
  • Earlier dry runs, now stale. Headless dry runs of the built skill on a fixture app with eleven sends in TypeScript, Python and Ruby ran up to f8bc637 (2026-11-05), and a prod-shape survey of real codebases' send shapes shaped the rules at 733e0e3. They predate bringing templates into the code (32f01fce), the tracking rules (0709579, ac1ef09) and this round's Sending Defaults, rules, inline CSS, merge-language and deadline rules, so they prove none of those.
  • Gaps:
    • No run applies the rewrite, typechecks or sends.
    • No run at this head. The paths with no run at all: a template brought into the code (Mailchimp merge language with mc:edit, and Handlebars), send-mc-template, merge tags in a send's own content, unknown Sending Defaults (open tracking, inline CSS, HTML part, merge language), the account's rules, PHP, Go, .NET, Elixir, HTTP calls, the older Node.js mandrill-api callbacks, community clients, a branch on ValidationError, one reject_reason or a 429 retry, subaccount sends, request deadlines and cancellable sends, network-error handlers outside the send, a try shared with a call that stays, a replaced mandrill-api onerror, text-only sends without an HTML part, the account's BCC address and unsubscribe footer, test keys, rejects.add and rejects.delete, the Guzzle 6 and 7 split, and the suppression import.
    • No run with the PostHog MCP connected, and none inside the Wizard.

Decisions

Question Answer Who Where
When this merges Not before code sends are live and usable for customers, for #451 and every PR on it 👤 Human this PR
Who lands the provider PRs We land them ourselves, after every ReviewHog finding is addressed and the full QA swarm ran 👤 Human this PR
Which providers Mailgun, Loops, SendGrid, Postmark and SMTP, plus the providers the Wizard detects that a real codebase sends transactional email from 👤 Human Silthus/posthog#461
Mailchimp Transactional tracking Work out opens and clicks from the send's fields, the Sending Defaults and the rules. Tracking never maps to captureEngagement: opens untracked follow Step 3's "Opens the provider didn't track", moving only with the person's yes; opens nobody can tell stay (open tracking not checked); opens tracked moves, with a plan-row note that PostHog counts no clicks when clicks were tracked. Replaced moving neither tracked with captureEngagement: false and keeping mixed, then keeping every untracked site 👤 Human this PR
Stack shape One PR per provider on top of #472, each landing in any order 🤖 Agent #472
Stored templates and inline merge tags Brought into the code by default, as template-to-code.md says; a template in PostHog only on request. Replaced keeping inline merge tags and moving templates only to a PostHog template 🤖 Agent this PR
Account settings the person can't tell Keep each site the setting could change, with its own reason: open tracking, inline CSS, HTML part, merge language, rules. Replaced guessing the merge language from the tags 🤖 Agent this PR
inline_css Keeps a site only when its HTML has a <style> element or the code can't show it has none. Replaced keeping every inline_css site 🤖 Agent this PR
A recipient answered as rejected Counts as an error of the send: it becomes recipient_suppressed, handled the way the site handled the rejected recipient. A branch on it runs only for recipient_suppressed, never for API or network errors 🤖 Agent this PR
A recipient answered as invalid A site that branched on it, or went on for it, checks the address before the send and logs and skips 🤖 Agent this PR
A branch on one reject_reason Moves only when the site treats hard-bounce, spam and custom the same, since PostHog answers all three as recipient_suppressed 🤖 Agent this PR
A narrow catch on one Mailchimp Transactional error ValidationError becomes a check of PostHog's validation_error, a status such as 429 a check of PostHog's status code, other error names keep the site, never a wider catch 🤖 Agent this PR
Network errors Python and Ruby raise network_error again, which their old catch never saw; PHP follows the Guzzle version; a catch of every error stays as it is. A caller's handler of the HTTP library's network error follows Step 7's rule on network failures; one in code the app doesn't own keeps the site 🤖 Agent this PR
Webhook events with no PostHog event A site whose emails a handler acts on for soft_bounce, deferral, unsub or reject stays (its <event> events feed a webhook handler), as Resend's mapping does on #472 🤖 Agent this PR
The older PHP client mandrill/mandrill Its sites stay, including copies kept in the app's code: its source is no longer published 🤖 Agent this PR
Which denylist entries move The main account's unexpired hard bounces, spam complaints and custom entries, kept in PostHog until removed; the report says they no longer expire 🤖 Agent this PR
cc, bcc, attachments, tags, metadata Stay on Mailchimp Transactional in every language, since no PostHog SDK takes them yet 🤖 Agent this PR
The account's unsubscribe footer On or unknown keeps every site (account adds an unsubscribe footer, account unsubscribe footer not checked): PostHog's send adds none, and recipients would lose their way to stop these emails, as with *|UNSUB:…|*. Replaces the earlier note in the report 🤖 Agent this PR
Mailchimp Transactional test keys Step 6 asks which places set a test key; the report says those sends delivered nothing and a PostHog key there delivers real email, so the person sets one only where that is fine. The rewrite can't keep a non-delivering mode: PostHog has no test key 🤖 Agent this PR
A try that also holds a call that stays Keeps the provider's handler for that call and adds PostHog's next to it, since the Python and Ruby clients raise one error class from every call 🤖 Agent this PR
A replaced mandrill-api onerror Keeps the site (the client's onerror handler takes its errors) 🤖 Agent this PR
A mandrill-api call without onError Keeps the site (the old client threw its errors outside the call): the default onerror threw outside the call, where no catch saw it, and a moved send's error reaches the code around it; replaces "moves, since both throw", after the proof gate's quality judge 🤖 Agent this PR
A text-only send with auto_html off Counts as untracked opens, whatever track_opens says: Mailchimp Transactional's pixel needs an HTML part 🤖 Agent this PR
The account's BCC address account.md asks for the Sending Defaults' BCC address. A site that sets no bcc_address takes it and stays, as a site that sets one does; when the person can't tell, it stays with account BCC address not checked 🤖 Agent this PR
SMTP row Says only that PostHog has no SMTP relay, as Resend's row does on this base; the pointer to migrate-email-smtp follows once that skill lands 🤖 Agent this PR
A request with its own deadline Follows Step 7's shared rule; this folder only names Mailchimp Transactional's timeout options. Replaced the folder's own client recipe 🤖 Agent this PR
rejects.add on an allowlisted address Mirrors to PostHog only when the answer says added, so an allowlisted address stays off both lists 🤖 Agent this PR
allowlists.add Also takes the address off PostHog's list where Step 5 allows it, since Mailchimp Transactional clears its denylist entry 🤖 Agent this PR
Bounces and complaints added after the import Follow #472's Step 5 "Re-import only": the report asks a weekly re-import while any site sends through Mailchimp Transactional, and a final one when the last site moves. This folder only names the Rejection Denylist calls and points there 🤖 Agent this PR
Tests of mapping wording Dropped the one this PR added: a wording test breaks the outside-in rule, and the live run is the proof of the rules 🤖 Agent this PR
Merge risk High: a wrong instruction silently changes rewrites, it ships with the next release, and the live run is a gap. Two-way door until that release ships the skill; one-way once agents run it, because a migration's changes persist in each app's code and PostHog account. No switch-off: a revert only stops new runs 👤 Human this PR
An HTML send Mailchimp Transactional sent with no text part Stays (turns the plain-text part off), or plain-text part not checked when the person can't tell the Sending Defaults' plain-text box, matching #472's rule that PostHog always makes a text part 🤖 Agent this PR

Involvement: qa-swarm on 2026-11-12, 2 panel rounds (round 1: fresh-eyes, correctness, risk, design, anti-overengineering, sweep and the author's ReviewHog perspective; round 2 on the fixes: the same without sweep) and 17 final reads, the last at 339ea45; reads 7 to 17 ran past the cap of six under Michael's standing review rule, to read the ReviewHog fixes and the reconciles after the second, third and fourth core merges. Read 12 read the fifth core merge and its reconcile at 0e14a82 clean; the proof judge then found the account's BCC address missing, fixed in c01ddcc, which read 13 read clean. ReviewHog then raised five findings over four runs (a try shared with a call that stays, text-only open tracking, a replaced mandrill-api onerror, test keys, and the account's unsubscribe footer), fixed in add7a56, 5eb68e7, e997aea and 339ea45; reads 14 to 16 were clean, and read 17's one finding, an outside-in trial of the last two rules, was rejected as the accepted live-run gap. Earlier swarms on this PR ran before the forward merges. ReviewHog: 9 runs, which raised 10 should-fix findings and 1 must-fix, all fixed; the last run, on 339ea45, found nothing. After #472 merged, main was merged in (9f3dcff) and the bundle adapted to #472's shared steps in 93bba69: Rejection Denylist entries map to PostHog's reason, Step 3's suppression question names the Rejection Denylist, and an HTML send Mailchimp Transactional sent with no text part stays. Read 18 raised two findings: the Step 3 note's claim about which entries reach a moved send, fixed in db750a6 with complaints left to the report as #472 decides, and a behavioural test, rejected as the accepted live-run gap; read 19 was clean. The proof gate on db750a6 then failed two judges: the merge-risk callout left out the two changes by design (complaint addresses and the hard bounces kept past seven days), now named in it, and a mandrill-api call without onError moved although its errors had thrown outside the call, fixed in 6a28c92. Read 20 on 6a28c92 was clean. Proof captured: shadow diff at 6a28c92 against main (only the Mailchimp Transactional bundle and its manifest and menu entries change), CI green on main's workflows; live run and prod-shape recorded as gaps.

🤖 Agent context

Agent: Claude Code, Claude Opus 5.5 (claude-opus-5-5, high), as the migration-skills slice of Silthus/posthog#461. Reviews on GPT-6.1 Sol (high), the fresh-eyes lens on Opus 5.5; fixes on Opus 5.5 (high).

🤖 Generated with Claude Code

@github-actions

github-actions Bot commented Nov 4, 2026

Copy link
Copy Markdown

🧙 Wizard CI

Run the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands:

Test all apps:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci ai-observability
  • /wizard-ci basic-integration
  • /wizard-ci feature-flags
  • /wizard-ci mcp-analytics
  • /wizard-ci replay-vision
  • /wizard-ci revenue
  • /wizard-ci self-driving
  • /wizard-ci warehouse
  • /wizard-ci warehouse-seeded

Test an individual app:

  • /wizard-ci ai-observability/anthropic
  • /wizard-ci ai-observability/google-adk
  • /wizard-ci ai-observability/groq
Show more apps
  • /wizard-ci ai-observability/manual-capture
  • /wizard-ci ai-observability/openai
  • /wizard-ci ai-observability/openai-agents
  • /wizard-ci ai-observability/opentelemetry
  • /wizard-ci ai-observability/vercel-ai
  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/flutter
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci feature-flags/django
  • /wizard-ci feature-flags/next-js
  • /wizard-ci mcp-analytics/custom-dispatcher
  • /wizard-ci mcp-analytics/typescript-sdk
  • /wizard-ci replay-vision/javascript-node
  • /wizard-ci replay-vision/next-js
  • /wizard-ci replay-vision/react-vite
  • /wizard-ci revenue/stripe
  • /wizard-ci self-driving/astro
  • /wizard-ci self-driving/fastapi
  • /wizard-ci self-driving/nuxt
  • /wizard-ci self-driving/react-router
  • /wizard-ci self-driving/sveltekit
  • /wizard-ci warehouse/monorepo-env
  • /wizard-ci warehouse/multi-source-next
  • /wizard-ci warehouse/stripe-node
  • /wizard-ci warehouse/zero-source
  • /wizard-ci warehouse-seeded/next-stripe
  • /wizard-ci warehouse-seeded/next-stripe-declined

Test against a wizard branch:

  • /wizard-ci all wizard:my-branch

Add wizard:<branch> to any command above to pin the wizard branch. It defaults to main.

Results will be posted here when complete.

Silthus and others added 28 commits November 5, 2026 09:01
Brings #472's Elixir fix (fall back past a nil :posthog host) and each lower provider's move to the rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…iljet

Brings #472's Elixir fix (fall back past a nil :posthog host) and each lower provider's move to the rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ndrill

Brings #472's Elixir fix (fall back past a nil :posthog host) and each lower provider's move to the rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The rewrite files pointed at a coarse-name list that only the Resend
mapping has. Step 7 now lists the ten names, and each rewrite file
points there. Each rewrite file now says whether reply-to takes one
address, a list, or both, as the SDK heads do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o feat/migrate-email-sendgrid

No conflicts. The Resend mapping keeps its own list of the coarse names in its stay row, which is a stay rule, not the definition.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's single list of error names in Step 7 and the reply-to rule in each rewrite file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A client with the secret key loads flag definitions from its host with
it: Go and Ruby when they start, Python and .NET when the app
evaluates a flag. Reusing the app's client behind a reverse proxy
handed the key to the proxy. Step 7 now gives email its own client on
PostHog's host behind a proxy, for every SDK, in place of the Go and
Ruby special cases.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…feat/migrate-email-sendgrid

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's Step 7 rule: behind a reverse proxy, email gets its own client on PostHog's host.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The step 7 proxy test matched only the separate-client wording, so
dropping "leave the secret key off the app's existing client" still
passed. Assert that clause too; it fails without it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… key) into feat/migrate-email-sendgrid

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's added assertion in the Step 7 proxy test. No skill text changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's added assertion in the Step 7 proxy test. No skill text changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Brings #472's added assertion in the Step 7 proxy test. No skill text changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Silthus and others added 21 commits November 13, 2026 14:37
Resend's answers carry response headers: headers in Node.js,
http_headers in Python, headers and rate-limit fields on Ruby, Go,
.NET and Rust errors. PostHog's answer carries none, and its error
carries only the retry delay. A site that reads any other header value
now stays on Resend, and a read of the retry delay moves to the PostHog
error's, with each SDK's name and unit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each PostHog SDK's error shape lives in its rewrite file under "The
answer", so the retry delay's name and unit move there, and Resend's
mapping keeps only where Resend carries the value. A site that keeps its
own deadline sends with no retries, so its own wait and retry stay.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Resend sends no text part when text is an empty string, on a send or a
template, and makes one from the HTML when text is left out. PostHog
makes the text part from the HTML whenever a send has none, so a send or
template with an empty text now stays on Resend, and one without text
moves as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…plate rule per provider

Resend also drops the text part for an empty text next to react, and for
a text the code builds that can be empty. The shared template rule now
keeps any template whose provider sent its emails with no text part, as
that provider's mapping says.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pty Text as left out

Step 3 reads only the Check part of the template file, so the rule that
keeps a template whose provider sent no text part moves there. Resend's
Go SDK leaves an empty Text out of the request, so Resend made that text
part from the HTML, and such a site moves.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ain text off

A dashboard copy shows no plain text both for a template without one and
for one whose plain text is an empty string. Ask which, or read the
template from the API; when nobody can tell, the site stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…tion and keep the answer

A dashboard copy has no key to read the template from the API, so the
question offers to make one. The answer goes into the template's plan
note, so a copy made again in Step 7 asks nothing new.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nly in Step 3

The template's note records its plain text however the template was
read, so Step 7 never asks again, and the key is offered only in Step 3,
before Step 5 asks the person to delete it. A site stays whenever
neither the answer nor the API read settles it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PostHog's bulk add takes only bounce, complaint or manual, and writes its own
reason text, such as "Imported (bounced)". The removal guard now keys on that
prefix, and the import maps each Resend origin to the reason value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…them

PostHog's list records no source an app could check before a removal, a bulk
add skips an address removed earlier, and an app can't call the import tool.
PostHog blocks a transactional send only to an address that hard-bounced, and
records that itself. So each such call becomes a "Before cutover" item.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PostHog blocks a transactional send only to an address that hard-bounced, so
the weekly re-import limits mail to bounced addresses, not complaints. A call
that removes an address becomes an "After cutover" item the person acts on
when a moved send fails with recipient_suppressed. A call that adds one names
the action before the deploy.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Re-import only now names bounces alone, and an app call that adds an address
also records it where the moved sends can skip it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A moved send reaches every address an app's add call put on the provider's
list, and an app-side flag misses past adds and survives a reactivation. So
Step 3 asks once which sites rely on the call, and keeps them on the provider.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Step 3 asks which sites rely on the provider's list for addresses added by
hand or by the app, and a non-answer keeps every site when the app adds
addresses itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the list

The suppression-list question gets its own Step 3 section, asks only about
sites that would move otherwise, keeps them on a non-answer, and says what
would let them move.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e work

The question now comes right after the field checks, so a site it keeps
needs no template copy or PostHog template, and the plan note carries what
would let the site move.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
posthog-rs's async email send waits between retries with tokio::time::sleep
and sends through reqwest, so a site on async-std or smol stays on Resend.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
main equals #451's merged head a090b5b, which this branch already contains, so the tree is unchanged from f98eb3b.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Silthus
Silthus changed the base branch from feat/migrate-email-all-sdks to main November 13, 2026 16:26
Silthus and others added 5 commits November 13, 2026 16:27
…t rules

Map each Rejection Denylist entry to PostHog's reason, drop the "which
adds count" text Step 5 no longer reads, and name the Rejection Denylist
and its custom and unsubscribe entries for Step 3's new question. PostHog
now makes a text part whenever a send has none, so an HTML send that
Mailchimp Transactional sent with no text part stays, and the Sending
Defaults' plain-text box joins the account questions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…the core does

Step 3's Mandrill note said its two entry kinds were the ones a moved send
would reach; spam complaints reach it too. Name custom and unsubscribe
entries as the ones someone adds, and say complaints go to the report, as
Step 5 and Step 9 say for every provider.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Without onError, mandrill-api passed every error to its onerror method,
which throws outside the call. A moved send's error reaches the code
around it instead, so the site stays.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@posthog posthog Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

PostHog Review · Standard · reviewed 6a28c92: no findings.

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