Files
autoreg-skills-max/skills/chatgpt-autoreg/references/session-2026-07-30.md

56 lines
2.3 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Session Inventory — 2026-07-30
## File Discovery Results
Full file inventory gathered from these locations:
### Core Toolkit
- `C:\Users\User\Desktop\_PROJECTS\oai-register\aBaiAutoplus\` — 232 source files (after stripping .venv, frontend, node_modules)
- main.py, gateway.py, requirements.txt, docker-compose.yml, Dockerfile
- api/ (13 files), application/ (14), services/ (8), core/ (39), tools/ (34)
- platforms/chatgpt/ (27) — protocol_register.py, constants.py
- providers/ (18) — imap_pool.py, rucaptcha.py, twocaptcha.py, yescaptcha.py
- data/ — .imap_mailbox_pool_state.json
### Email Bases
- `working_mails.txt` — 650,733 bytes, 17,893 t-online.de accounts (format: email:password)
- 32 × `*Good*Mail*` lists (50k × N + 2k variants)
- `fakemailbot.zip`, `mailer_v3_gothbreach.zip`
### Autoreg Scripts (all versions)
- 44 iterations: `autoreg_v1.py` through `autoreg_v46.py` in `tmp/`
- conol_github/ (8 files): api, email, github_stealth, curl, aliases
- velokey/ (3 files), sepa/ (2 files), baia, gorouter, gmail
### Proxy Scripts
- `grok_proxy_pool.py`, `grok_cli_proxy.py`
- `cf_proxy.py` (in gpt-auto-register)
## Server Crash Pattern
Observed crashes at concurrency=3:
1. First crash: during 20-account batch, progress 5/20. Server down, restarted. Got +5 accounts.
2. Second crash: during 15-account batch, progress 7/15. No JSON response — `JSONDecodeError`.
3. Root cause: likely IMAP connection exhaustion or unhandled exception under concurrent load.
**Mitigation:** use concurrency=2. Monitor with `curl` polling every 15-30s.
## Registration Test (2026-07-30 12:43 UTC)
```json
{"count":2,"concurrency":2,"executor_type":"protocol","captcha_solver":"auto","extra":{"mail_provider":"imap_pool","identity_provider":"mailbox"}}
```
Results:
- Worker 1: [REDACTED-EMAIL] → code 568181 received → OpenAI rejected: account_deactivated
- Worker 2: [REDACTED-EMAIL] → still waiting for IMAP code (stalled)
Conclusion: pipeline functional. Captcha solves. IMAP delivers. ~50% of t-online.de pool is burned.
## Current State
- **Server:** running on localhost:8000
- **Accounts in DB:** 30 (all chatgpt, t-online.de, status registered)
- **Captcha:** RuCaptcha, API key configured, auto mode
- **IMAP pool:** 17,893 entries, file at `C:\Users\User\Desktop\solenne_de_emails.txt`