1.7 KiB
Codex onboarding ClawEmail random suffix policy — 2026-05-08
BOSS corrected the mailbox policy during a Codex OAuth registration test:
- Use only 8 lowercase English random letters as the ClawEmail create prefix.
- Do not prepend
cod,codex, or another business marker unless explicitly requested. - Desired visible mailbox shape:
chickliu.<8 lowercase random letters>@claw.163.com
Example created successfully in-session:
chickliu.ktqcxzux@claw.163.com
Why not codex + 8 letters?
The live ClawEmail Open API rejected create prefixes of length 12+ with OPEN_API_1003 prefix format is invalid, despite public docs/help saying 1-64 characters. The real accepted maximum observed was 11 characters. Since codex + 8 letters is 13 characters, it fails.
A temporary cod + 8-letter scheme created chickliu.coddwrkviby@claw.163.com, but BOSS clarified they want the dot-suffix itself to be only the 8 random letters. That temporary mailbox was deleted and replaced.
Env policy
For this workflow, use:
CLAWEMAIL_PREFIX=
CLAWEMAIL_RANDOM_SUFFIX_LENGTH=8
CLAWEMAIL_RANDOM_SUFFIX_CHARSET=abcdefghijklmnopqrstuvwxyz
CLAWEMAIL_PREFIX_WITH_RANDOM_SUFFIX=true
If helper scripts do not support these fields, generate the prefix directly in the runner:
import random, string
prefix = ''.join(random.choice(string.ascii_lowercase) for _ in range(8))
Then call:
mail-cli clawemail create --prefix "$prefix" --type sub --display-name "Codex OAuth $prefix" --json
Record created mailboxes in the configured CLAWEMAIL_RECORD_FILE, mark them pending, and update to deleted_replaced, success, or failed as the run proceeds.