Create one disposable mailbox without giving personal data to the provider. DispMail drives the system Chrome through a provider signup flow, stops before the submit button by default, and stores the result locally.
Documentation: https://konscanner.github.io/dispmail/
The site covers install, usage, providers, egress, account data and the exit codes. The
design record lives in docs/, with the recon evidence in
docs/recon/.
| Provider | Plan | State |
|---|---|---|
| Tuta | Free | Dry run verified against the live site. A live run needs a clean egress. |
| Interia | Darmowe | Fill flow verified to the submit gate. This IP was challenged after repeated attempts. Live is assisted: it ends in an image CAPTCHA and SMS/mail verification. |
Tuta asks you to affirm that you own no other free Tuta account, and Interia has a
similar term. The tool cannot verify this. It enforces a configurable limit of 4
accounts per provider in a rolling 7 days (--weekly-limit, DISPMAIL_WEEKLY_LIMIT).
You are responsible for the provider terms.
- Python 3.14.8 or newer (
.python-version) uv- Google Chrome (patchright uses the system browser)
- Linux or macOS (the run lock uses
fcntl)
uv sync --all-groups
uv run dispmail doctor# Dry run: fill the form, stop before submit, create nothing.
uv run dispmail tuta --state-dir ./.dispmail-state
# Live Tuta: one free account, unattended.
uv run dispmail tuta --submit --accept-attestation \
--state-dir ./.dispmail-state --headed
# Live Interia: solve the CAPTCHA and the SMS/mail step in the window.
uv run dispmail interia --submit --assisted --headed --state-dir ./.dispmail-state
uv run dispmail list # providers, plans, live requirements
uv run dispmail doctor # Python, patchright, Chrome, paths, egressuv run dispmail <provider> --help lists --domain, --consents, --timeout,
--assist-timeout, --seed, --json, --egress-*, --proxy-* and --home-ip.
All account data is under one gitignored data/ directory:
data/sqlite.db email, password, recovery, platform, egress
data/recovery_<email>_<platform>.txt recovery kit, as given by the provider
data/ is mode 0700, the database and the recovery files are 0600. Set another
location with DISPMAIL_DATA_DIR or --data-dir.
Read the data with dispmail read or the make targets. Passwords and recovery keys
are masked unless --show-passwords is given.
uv run dispmail read
uv run dispmail read --platform tuta
uv run dispmail read --recovery yes
uv run dispmail read --email-regex '^alpha' --json
uv run dispmail read --show-passwords
make read-tuta
make read-interia
make read-recovery
make read-email RE='@tutamail.com$'
make read-json
make read-secretsA run refuses to open a provider page for writing unless the browser exit matches the
declared egress. The check runs inside the browser, uses two endpoints, and fails
closed on a country/ASN mismatch, on divergent endpoints, or when the exit is
DISPMAIL_HOME_IP.
Two modes:
- System VPN or phone hotspot. No secrets in this repository.
mullvad relay set location pl && mullvad connect uv run dispmail tuta --egress-country PL ...
- HTTP/SOCKS proxy, configured only in
.env(copy.env.example).
Exit codes: 0 ok, 1 flow error, 2 usage, 3 egress mismatch, 4 challenge, 5 budget or cooldown or lock, 6 provider changed, 7 rejected, 8 account already recorded.
- Up to 4 accounts per provider in a rolling 7 days. The database and the ledger both
count;
--replace-accountbypasses the limit for a lost account. - One run at a time. A challenge sets a 24 hour cooldown, then 7 days.
- CAPTCHAs are never solved automatically. A headed assisted run waits for a human; a headless run stops with exit code 4.
- Passwords never enter logs or the ledger. Artifacts are a screenshot and a DOM with
value=attributes blanked, textareas emptied, and the run secrets redacted. --jsonmasks the password and the recovery key unless--show-passwordsis given.
make check # ruff format --check, ruff check, ty check, pytest
uvx prek installLayout: src/dispmail/ (engine, browser port, providers), tests/unit/,
tests/contract/ (locator checks against the recon snapshots), docs/.
There is no CI. Rings 2 and 3 need a specific egress and, for Interia, a human.
The documentation site is built by GitHub Pages from docs/ with Jekyll and the
just-the-docs theme. It has no analytics, no cookies and no third-party requests.
Run make check before you push; the site needs no local toolchain.