Files
codex-oauth-plus-onboarding…/skill/codex-oauth-plus-onboarding/references/mail2925-openai-live-test-2026-05-11.md
T

1.7 KiB

2925 + OpenAI live signup test notes — 2026-05-11

Scope: BOSS requested one OpenAI/Codex registration test using 2925 account pool, Luban SMS UK, and 1085 proxy.

Result

Stopped before SMS purchase. Email verification did not pass, so Luban was not used.

Verified gates

  • Proxy: 1085 Chrome/CDP worked for OpenAI pages.
  • CPA OAuth URL generation: worked via /v0/management/codex-auth-url?is_webui=true.
  • 2925 account pool binding: worked.
    • chickliu2025@2925.com -> generated alias with chickliu2025 prefix.
    • chickliu2026@2925.com -> generated alias with chickliu2026 prefix.
  • 2925 displayed top/current mailbox matched the selected account before polling.
  • Inbox pre-clear/check worked.

Findings

  1. OpenAI email-verification page displayed that it sent mail to the generated 2925 alias.
  2. 2925 Inbox did not receive OpenAI mail during the polling window.
  3. 2925 Junk (垃圾箱) contained OpenAI/ChatGPT mail and 6-digit codes, but many were stale messages for older aliases.
  4. Submitting a visible stale code from Junk returned OpenAI error 代码不正确.
  5. Resend did not produce a new code matching the current generated alias within the tested polling window.
  6. 已删除 also contained many stale OpenAI codes and must not be used without current-alias matching.

Required rule update

  • Poll both Inbox and Junk.
  • Never accept a 6-digit code unless the candidate message matches the current generated alias/local-part or an unambiguous current-run time window.
  • Maintain rejected codes and never resubmit them.
  • If no current-alias code appears, stop before SMS purchase.

Safety

No Luban number was purchased because email verification did not pass. No passwords/API keys/codes are included in this note.