Skip to content

fix(email): resolve live staging acceptance failures - #332

Merged
Brooooooklyn merged 1 commit into
mainfrom
codex/email-live-acceptance
Sep 20, 2026
Merged

Brooooooklyn merged 1 commit into
mainfrom
codex/email-live-acceptance

Conversation

@Brooooooklyn

Copy link
Copy Markdown
Member

Live staging acceptance exposed failures in first-time native setup, hosted recipient confirmation, admission timing, and forwarding from nested plus-tag addresses. This makes those paths work through the current email design and removes the retired internal verification transport.

  • Preserve an exact owned native routing plan while new subdomain MX records propagate; stop before build/upload instead of losing the plan or failing after upload.
  • Send recipient confirmations through the native email binding and serve confirmation links through the public gateway. Align hosted identities, account-token verification, and installer permissions.
  • Batch admission queries, use one bounded direct-send deadline with finalization time reserved, and place the hosted API beside its PostgreSQL origins. Preserve idempotency, quota accounting, and unknown-outcome handling.
  • Accept nested plus tags consistently while retaining project ownership checks. Update the existing design and affected guidance; remove obsolete handlers, helpers, exports, and tests.

Validation: complete vp run test:all passed (551 files; 10,429 tests passed, 20 skipped), plus focused PostgreSQL admission checks and repeated GPT-5.6-sol xhigh reviews ending with no actionable findings. Real staging/native mail covered To/CC/BCC, consent, retries, conflicts, quotas, policy modes, replies, forwarding, sender isolation, and sibling-domain preservation. The final forward passed SPF/DKIM/DMARC/ARC and its ledger recorded provider acceptance. The reproduced hosted send improved from a 10-second timeout to a confirmed result in 4.9 seconds.

Only staging and disposable fixtures were deployed. The previous staging credential and recipient policy were restored. Standalone customer-account relay rotation still needs its separate live acceptance run; three intentionally interrupted sends remain under the existing 24-hour recovery guard. Production configuration was reviewed but not deployed.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-19T17:19:39.008237Z a0044dc PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Brooooooklyn
Brooooooklyn merged commit c114a6e into main Sep 20, 2026
19 checks passed
@Brooooooklyn
Brooooooklyn deleted the codex/email-live-acceptance branch September 20, 2026 03:44
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