Temp Mail

Temp Mail is a simple tool that lets you create a temporary email address to receive messages instantly.

  • Communication
  • Development
  • Tools & Utilities
Temp Mail is a simple tool that lets you create a temporary email address to receive messages instantly. It is perfect for protecting your privacy and keeping your personal inbox free from spam when signing up for websites or testing online services.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
72last commit 24 days ago
Popular
45182 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
85512 MB minimum RAM
Security check
75no serious findings
GitHub stars
182
Open issues
2
Last commit
2026-10-28
Latest release
v2.0.0
Activity
rising

Checked 2 days ago - source: GitHub (mehmetkahya0/temp-mail)

Resources & Compatibility

Minimum requirements: 512 MB RAM, 1 CPU core(s), 10 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create the worker config file In the `worker` folder (the backend service), run `pnpm install` (a package-install command) to download its packages, then copy `wrangler.toml.template` to `wrangler.toml`. This file tells Cloudflare where to deploy the backend, so without it the deploy step fails or sends things to the wrong place. source
  • Point frontend at your worker Copy the sample settings file `.env.example` to `.env.prod` in the `frontend` folder, and set `VITE_API_BASE` (the address the website sends requests to) to your worker URL. Then in the `pages` folder, confirm `wrangler.toml` uses your actual worker name if it isn't `cloudflare_temp_email`, or the site may deploy but still can't reach the backend. source
  • Set SMTP proxy address and port If you use the SMTP (email sending) proxy, set `proxy_url` in its settings file to your worker address, and set `port` to the port your email client will use. If you're using Docker, that file is `docker-compose.yaml`; wrong values make email sending or fetching fail. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What backend file must be prepared before deploying the worker to Cloudflare?

Copy wrangler.toml.template to wrangler.toml in the worker folder after installing its packages. This file tells Cloudflare where to deploy the backend, and without it the deploy can fail or send the backend to the wrong place.

How do I make the frontend use my deployed worker?

Copy .env.example to .env.prod in the frontend folder and set VITE_API_BASE to the worker URL. Also confirm the Pages wrangler file uses the actual worker name if it is not the default name, or the site may deploy but not reach the backend.

How should the SMTP proxy be configured in Docker?

Set proxy_url to the worker address and set port to the port your email client will use. In Docker these settings are in docker-compose.yaml, and wrong values can make email sending or fetching fail.

Can I use my own domain to avoid blocks on sign-up sites?

The self-hosted tempmail project lets you host your own disposable email service with whatever domain you choose. It is described as a response to sites that block well-known disposable email services.

What licensing restriction does the README emphasize?

The README says all code for the website is copyrighted and cannot be used to open another website in the same way. It also states that the code is tracked and a DMCA violation will be sent if it is opened elsewhere.

Answers sourced from github.com, github.com, temp-mail-docs.awsl.uk, temp-mail-docs.awsl.uk, temp-mail-docs.awsl.uk

Community

Collected 48 days ago - public community threads