Files
codex-oauth-plus-onboarding…/skill/codex-oauth-plus-onboarding/references/mail2925-openai-resend-cadence-attempts-2026-05-11.md
T

1.7 KiB

2925 OpenAI signup attempts with resend cadence — 2026-05-11

BOSS requested: use 1085 proxy, 2925 email pool, Luban SMS UK. Luban was not used because email verification never passed.

Resend cadence adopted

For each current alias:

  1. Refresh 2925 收件箱 and 垃圾箱.
  2. Wait ~15s.
  3. Repeat 3 refresh rounds.
  4. If no current-alias code, click OpenAI 重新发送电子邮件.
  5. Repeat.

Attempts

  • chickliu2027@2925.com -> chickliu20274ynsem@2925.com
    • explicit refresh + poll found no current-alias OpenAI mail.
  • chickliu2028@2925.com -> chickliu2028t95bip@2925.com
    • 3-refresh-then-resend cadence executed.
    • OpenAI resend clicked 3 times.
    • Inbox/Junk showed correct account but no current-alias mail/code.
  • chickliu2029@2925.com -> chickliu2029ssejc6@2925.com
    • fresh 2925 profile was required; old 2925 session remained logged into 2028 until profile restart.
    • 3-refresh-then-resend cadence executed.
    • OpenAI resend clicked 3 times.
    • Inbox/Junk showed correct account but no current-alias mail/code.

Findings

  • 2925 top-account gate is mandatory. When switching accounts, clear cookies or use a fresh profile; otherwise UI may remain logged into the previous account.
  • OpenAI email-verification pages showed delivery to the generated alias, but 2925 Inbox/Junk did not receive current-alias messages for the tested accounts.
  • Older OpenAI mail can exist in Junk/Deleted for older aliases; candidate code must match current alias/local-part.
  • Stop before SMS purchase if email verification is not complete.

Safety

No Luban UK number was purchased. No OpenAI/Codex tokens or phone numbers were generated in this blocked run.