Skip to content

MailerSend and SendGrid decommission plan

Updated November 3, 2026.

This is the authoritative migration checklist for retiring MailerSend and SendGrid without silently breaking church notifications. The 2025 Goodbye, SendGrid page explains why MailerSend was introduced; it is historical context, not evidence that every listed consumer is still active.

Current decision

Cole has set December 1, 2026 as the soft deadline and January 1, 2027 as the hard deadline for MailerSend and SendGrid to be completely retired. Nothing should send through SendGrid now. Any SendGrid traffic or active delivery path is an immediate migration blocker to investigate, rather than a path to keep using during observation.

Target the reversible provider-access pause by about November 10, 2026. The planned observation window runs from the actual pause date through December 1. December 1 to January 1 is buffer for slips. Record the actual pause date and escalate delays or missed consumers promptly so the owner can agree recovery and any revised observation within that buffer, with complete retirement no later than January 1, 2027. MailerSend remains available for rollback and unverified SMTP consumers until the approved pause. Do not cancel accounts, remove DNS records, revoke credentials, or delete protected variables before the staged gates and owner approvals below are satisfied. Portal, the primary rocc-db-local Node-RED mail flows, Q-SYS, and the Cloudflare gateway are migrated. The Fiery, Ricoh, Bitwarden, Jamf, Cloudron, WordPress, and BillionMail relays remain unverified. Each external path must move independently and pass a real delivery and failure-path test before provider retirement.

No credential values belong in Git, documentation, tickets, job output, or test email bodies. Repository code may name the protected variables MAILERSEND_API_KEY, MAILERSEND_FROM_EMAIL, and MAILERSEND_FROM_NAME; the values remain in the approved runtime boundary.

Migration status snapshot

This snapshot records the migration state reviewed on November 3, 2026. Historical test evidence below is identified by its original date; this review did not send email or perform new consumer acceptance tests. It distinguishes current default-branch code from historical documentation and old feature branches.

Consumer or control Status Evidence / remaining gate
Cloudflare email gateway Migrated The production application transport uses the signed Cloudflare gateway. Preserve its delivery, retry, volume-limit, and operational ownership evidence through closeout.
Portal application mail Migrated Current Portal code permits only the Cloudflare gateway. A production test email was received. Final-delivery analytics and a normal-cycle observation window remain required.
Expense workflow Migrated; PDF attachments restored Portal !899, merged September 29, attaches the expense-request form and stored bill/receipt PDFs to accounting approval and resend emails. The handoff fails if a receipt is missing, invalid, oversized, or rejected by the gateway. The former review-link-only limitation is resolved.
Q-SYS alerts Migrated The managed Q-SYS boundary uses Cloudflare. Infrastructure runtime audits verified the Q-SYS process contract and zero legacy MailerSend names; whole-host legacy-name closeout remains separate.
rocc-db-local Node-RED mail Migrated The primary tracked flow uses the Cloudflare gateway only, and the August 21 live drift check passed.
MPR and MDF Node-RED Tracked cleanup merged; live rollout pending Verified November 3: MDF has no SendGrid references in its flows; MPR's only SendGrid node is disabled on the disabled MP tab. Infrastructure !266 merged November 3, removing the unused packages, disabled node, and its four inbound wire references, and adding regression checks. No live Node-RED rollout was performed; that remains a separate approved manual release.
Tasks application Acceptance evidence still required for closeout The current code inventory uses the gateway. Retain a successful production acceptance result and final-delivery evidence in the closeout ledger; this review did not rerun a mail smoke test.
Copy Room Fiery and Ricoh Unverified Verify each device's current SMTP relay independently. Obtain a dedicated device credential from Portal SMTP Credentials, then record a scan attachment acceptance test and rollback evidence. Direct SMTP bypasses gateway caps.
Bitwarden, Jamf, and Cloudron Unverified Historical documentation identifies MailerSend SMTP consumers; current relay settings for all three still need verification. Verify their current live settings without recording credential values, then migrate or explicitly retire each sender.
BillionMail Unverified / unreachable Historical address 10.141.74.109 did not answer HTTP or HTTPS during the August 22 audit. Confirm whether the VM/service still exists and whether any live caller remains.
WordPress website Unverified runtime SMTP relay The canonical website repository contains no MailerSend or SendGrid reference. Runtime plugin configuration on 10.141.74.111 still needs a credential-safe WordPress/SMTP plugin inventory and a replacement delivery test.
Delivery observability Closeout evidence required The gateway supports aggregated Cloudflare final-event counts without recipient, subject, or body data. Verify the current analytics job and retain reports for the owner-approved observation window. This review does not establish current delivery volume or analytics credential readiness.

The August 22 canonical default-branch repository audit found no active MailerSend or SendGrid implementation in Portal, Tasks, the Cloudflare applications, the website repository, Portal API, church/mobile apps, or current supporting services. Legacy names remain in tests, historical ledgers, rollback helpers, and documentation; those references are not proof of a live delivery path.

Replacement SMTP credentials

Use Portal Tech > SMTP Credentials to obtain a separate credential for each device or service. Portal !1103 uses the saved management token and account ID in the protected Portal boundary; operators no longer paste them for each action. Issued SMTP passwords are shown once and are not saved by the page. A lane without its management configuration displays a setup notice and cannot issue tokens. Portal !1105 adds token status, creation date, and expiry metadata. Both merged November 3; merge evidence does not establish that every lane can issue a live token. Verify readiness without copying the saved management token into a device.

Repository consumer inventory

Workflow Evidence Migration acceptance
Sermon-slide pastor and production notifications Portal scripts/sermon-slide-notification-worker.py and its focused worker tests Both distinct recipient emails deliver through the replacement; success, attention, retry, and cost/runtime content remain correct.
Support intake and staff notifications Portal dashboard/v2/support/submit.php, dashboard/v2/support/support.php, and support smoke scripts A synthetic ticket reaches the intended staff route; user confirmation and provider-failure behavior are verified without creating duplicate tickets.
Key-fob reminders, digests, approvals, and resends Portal key-fob scripts and dashboard/v2/keys/ handlers Reminder, digest, approval, and resend paths deliver once to reviewed recipients and preserve existing audit state.
Q-SYS and file-storage monitoring alerts Portal Q-SYS watch/listen helpers and scripts/files-storage-watch.php A controlled warning and recovery notification are received; deduplication and cooldown behavior are preserved.
Expense reports Portal v1.1/v2 expense common code and the retained 2026 form handler A non-production request proves submitter and reviewer delivery, attachment/link handling, and provider-error visibility. Retire obsolete form code separately rather than assuming it is inactive.
Node-RED email flows Infrastructure nodered/instances/rocc-db-local/flows.json Inventory the live flow by stable node identifier, migrate one flow at a time, and verify the real caller plus Node-RED error path. Do not copy flow credentials into the migration ledger.

The code inventory is a lower bound. Runtime jobs, rollback releases, and external SMTP devices can remain consumers even when the current repository no longer references them.

External SMTP inventory to re-verify

The historical inventory and current closeout review identify these SMTP consumers and caller groups to verify:

  • Bitwarden;
  • the Copy Room Fiery and Ricoh scan-to-email workflows;
  • Jamf and Cloudron;
  • WordPress SMTP plugins;
  • BillionMail and the Node-RED workflows that call it;
  • Wi-Fi administrator messages;
  • Planning Center weekly Wi-Fi access messages;
  • key-fob confirmations.

For each system, record only owner, hostname/service name, sender domain, replacement status, test date, and reviewer. Confirm the live configuration without displaying usernames, passwords, tokens, message contents, or a full environment file. An unverified historical row is not permission to remove it.

Required replacement capabilities

The selected replacement must support:

  • the current sender identities and distinct pastor/staff recipient routing;
  • authenticated API delivery for application emails and authenticated SMTP for devices that cannot use an API;
  • TLS certificate validation and protected, least-privilege credentials;
  • bounded retries with idempotency or application-side deduplication;
  • bounce, suppression, complaint, and provider-failure visibility;
  • SPF, DKIM, and DMARC alignment for every active sender domain;
  • content-safe operational logging with timestamps, provider request IDs, latency, result class, and cost when applicable;
  • a documented monthly owner and spending/volume limit.

Cloudflare is the selected replacement. Gateway and direct SMTP consumers need separate acceptance evidence because direct SMTP does not inherit the gateway's queue, idempotency, or volume controls.

Staged closeout

Retire both MailerSend and SendGrid by the December 1, 2026 soft deadline, with January 1, 2027 as the hard deadline. The interval from December 1 to January 1 is buffer for slips. SendGrid must carry no traffic now; do not wait for the pause target to stop using it. Each stage needs recorded evidence and owner review before the next stage. This plan does not authorize credential pauses, retirement, DNS changes, or subscription cancellation by itself.

  1. Migrate and accept consumers. Assign an owner and replacement transport to every repository and external inventory row. Unknown consumers block closeout. Obtain device/service SMTP credentials from Portal, stage changes in the appropriate protected boundary, and move one consumer at a time. Use reviewed test recipients to verify sender, reply-to, links, PDF/scan attachments, retries, deduplication, failure handling, and final delivery. Retain MailerSend as a sealed rollback path until the approved pause; do not dual-send normal mail or activate any SendGrid path.
  2. Pause legacy access as a reversible test. After consumer acceptance, obtain approval to pause MailerSend and SendGrid API tokens and SMTP logins without deleting or revoking them. Target the pause by about November 10, 2026, and record the actual pause date. The observation window is planned from that pause date through December 1, 2026. Record how the owner can restore MailerSend access promptly if an overlooked consumer fails; restoring SendGrid delivery would conflict with the no-traffic requirement and needs Cole's decision. Observe replacement delivery/failure metrics, both legacy providers' activity and rejected-authentication attempts, scheduled jobs, and device error reports throughout the window. Investigate every unexpected attempt. Escalate any failed consumer, temporary restoration, or delayed pause to Cole immediately for a recovery and observation decision. Use the December 1–January 1 buffer for any slips while preserving complete retirement by the January 1 hard deadline.
  3. Retire legacy names and credentials. Only after the reversible test passes, inventory current source, protected variable names, OpenBao metadata, systemd/cron definitions, Node-RED metadata, process environments, rollback copies, and PM2 persistence without displaying values. Retire obsolete names through separately reviewed host/controller changes. Cover both providers' GitLab/OpenBao/host names, protected rollback copies, packages, disabled nodes, and remaining API/SMTP credentials. Reconcile stale PM2 recovery inputs as a separate host maintenance action; never treat a 2023 dump as live runtime evidence or run pm2 save merely to silence an audit. Verify old authentication is rejected and remove retained credentials according to the approved recovery policy. Review legacy DNS records separately, preserve replacement SPF/DKIM/DMARC alignment, and remove provider records only with explicit authorization.
  4. Obtain owner-approved cancellation. Present the consumer acceptance, pause/observation, runtime/persistence audit, credential retirement, DNS, and operational ownership evidence to the account owner. Cancel the MailerSend and SendGrid subscriptions/accounts only after explicit owner approval, and record both providers' approval and completion dates. Complete credential and legacy DNS retirement and owner-approved cancellation by the December 1, 2026 soft deadline, using the December 1–January 1 buffer for slips only, and finish no later than the January 1, 2027 hard deadline.

Completion evidence

MailerSend and SendGrid are decommissioned only when all of the following are true: target December 1, 2026 and complete by the January 1, 2027 hard deadline.

  • [ ] Every repository row has a replacement, test owner, production cutover, and failure-path result.
  • [ ] Every historically documented SMTP consumer is verified migrated or explicitly retired.
  • [ ] Nothing sends through SendGrid now; any discovered path or traffic has been investigated and migrated.
  • [ ] Current source and runtime metadata contain no active MailerSend or SendGrid consumer.
  • [ ] Both providers' API tokens and SMTP logins are paused with owner approval; the actual pause date is recorded against the approximately November 10 target.
  • [ ] The planned pause-date-to-December-1 observation completes with no unexplained legacy activity or authentication attempts and healthy replacement delivery; any recovery or schedule slip has been escalated to Cole and any revised observation fits within the December 1–January 1 buffer.
  • [ ] Replacement SPF, DKIM, DMARC, bounce, suppression, alerting, and cost ownership are verified.
  • [ ] Old credentials are rejected and removed from active GitLab/OpenBao/host boundaries without exposing their values.
  • [ ] Rollback and incident runbooks name the replacement transport.
  • [ ] The account owner approves cancellation of both providers and records completion against the December 1, 2026 soft deadline and January 1, 2027 hard deadline.

Until every box is complete, the correct task status is in progress, not decommissioned.