otinstaller · Email

Install MailAccess on Linux in one command

MailAccess checks an email address against a large set of platforms for registration, groups the hits into likely identities, and flags addresses seen in breach data. It is a newer alternative to Holehe with broader coverage.

MailAccess in three lines

pipx install otinstaller
ot install mailaccess
ot run mailaccess -- e:jane@example.com

Runs KatrielMoses/MailAccess (unknown, ★ 1.4k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

What MailAccess is for

Broad registration checks on one address.
A second opinion next to Holehe.

Typed inputs for MailAccess

otinstaller translates these prefixes into MailAccess's own flags. Anything else after -- is passed through unchanged, so every original flag still works.

e:: email · ot run mailaccess -- e:jane@example.com

Run every installed tool that takes the same input at once: ot run --all e:jane@example.com

Where the results go

Every run lands under ./results/mailaccess/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff mailaccess <target>, and pull indicators out with ot extract.

Before you run it

Newer project; verify surprising hits by hand.

Update, remove, inspect

ot info mailaccess      # inputs, flags, keys
ot example mailaccess   # sample output
ot update mailaccess    # move to the next tested version
ot remove mailaccess    # delete its virtualenv

Full reference for this tool: docs for mailaccess.

Pairs with

Holehe

Holehe asks about 120 services whether an email address is registered, using their password-reset and sign-up checks without sending anything to the address.

h8mail

h8mail checks an email address against breach sources and, with API keys, pulls the matching records.

GHunt

GHunt looks up a Google account by its Gmail address and returns the public parts of it: profile name and photo, Google ID, reviews, and sometimes a calendar or Maps contributions.

When open-source isn't enough

MailAccess flags that an address appears in breaches. SearchIn's leak providers return the rows.

Breach intelligence

People & identity

Breach intelligence

FAQ

MailAccess with otinstaller, answered

How do I install MailAccess on Kali or Ubuntu?

Install otinstaller once with pipx install otinstaller, run ot init, then ot install mailaccess. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.

Which inputs does MailAccess take through otinstaller?

e: (email). otinstaller maps each prefix to MailAccess's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.

Where does otinstaller save MailAccess results?

Under ./results/mailaccess/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot diff mailaccess <target> to compare the last two.

Does MailAccess need an API key or a login?

No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.

Can I run MailAccess together with other tools?

Yes. ot run --all e:jane@example.com runs every installed tool that accepts email input, in parallel, including MailAccess. Save the combination as a playbook to repeat it.