MailHog was the go-to fake SMTP server for years. It's simple, free, and gets the job done locally. But if you've tried to use it in a modern CI pipeline, you've probably hit the same wall: it requires a running Docker container, adds startup overhead, and is effectively unmaintained.

If you're testing email flows in 2026 — password resets, magic links, verification codes — here's what your options actually look like.

Why people are moving away from MailHog

MailHog's last commit was years ago. It works, but:

• Requires Docker in your CI environment
• Adds a services: block to every GitHub Actions workflow
• Needs health checks and port mappings before tests can run
• Can cause flaky tests when the container is slow to start
• No SDK — you poll a custom HTTP API and parse the response yourself

None of these are dealbreakers locally. In CI, they add up.

The alternatives

1. Mailpit

Best self-hosted replacement for MailHog

Mailpit is the modern, maintained successor to MailHog. Single static binary, faster startup, cleaner API, actively developed. If you're already running Docker in CI and just want something better than MailHog, Mailpit is the answer.

# docker-compose.yml
mailpit:
  image: axllent/mailpit
  ports:
    - "1025:1025"   # SMTP
    - "8025:8025"   # HTTP API

// Poll the Mailpit API
const res = await fetch('http://localhost:8025/api/v1/messages');
const data = await res.json();
const message = data.messages?.find(m => m.To?.[0]?.Address === testEmail);

Pros: Maintained, fast, drop-in MailHog replacement, better UI
Cons: Still requires Docker in CI, still no SDK

2. Mailtrap

Best for teams who want a managed sandbox

Mailtrap is a hosted email sandbox — no Docker required, but you need an account and API key. Works well for staging environments where you want a persistent inbox.

Pros: No infrastructure to run, good UI, team features
Cons: Paid for most CI use cases, account required, rate limits on free tier

3. smtp4dev

Lightweight alternative if you're on .NET or Windows

smtp4dev is a simple fake SMTP server that works well in Windows environments. Less common in modern Node/TypeScript stacks.

Pros: Lightweight, works without Docker on Windows
Cons: Less active community, not ideal for cloud CI

4. MailCrab

Rust-based, fast, minimal

MailCrab is a newer fake SMTP server written in Rust. Faster startup than MailHog, Docker image is small. Still requires a container in CI.

Pros: Fast, small image, modern codebase
Cons: Smaller community, still Docker-dependent

5. ZeroDrop

Best for zero-infrastructure CI testing

ZeroDrop takes a different approach entirely — instead of running a fake SMTP server, it catches real emails at the edge using Cloudflare Workers and stores them in Redis with a 30-minute TTL.

No Docker. No container. No CI config changes. Just an npm package.

npm install zerodrop-client

import { ZeroDrop } from 'zerodrop-client';

const mail = new ZeroDrop();
const inbox = mail.generateInbox();

// Sign up with the disposable inbox
await page.fill('[name="email"]', inbox);
await page.click('[type="submit"]');

// Wait for the real verification email
const email = await mail.waitForLatest(inbox, { timeout: 10000 });
const link = email.body.match(/https?:\/\/\S+verify\S+/)?.[0];
await page.goto(link);

There's also a GitHub Action that generates the inbox as a CI step:

- name: Generate test inbox
  id: inbox
  uses: zerodrop-dev/create-inbox@v1

- name: Run tests
  run: npx playwright test
  env:
    TEST_INBOX: ${{ steps.inbox.outputs.inbox }}

Pros: No Docker, no SMTP config, works in any CI environment, SDK with built-in polling, GitHub Action available
Cons: Emails go through the real internet (by design), free tier uses shared domain

Free tier: shared domain, AI spam filtering, 30-min TTL, no signup required.
→ zerodrop.dev

Comparison

Which should you use?

Already running Docker Compose in CI → Mailpit. It's the best self-hosted option and a straight MailHog replacement.

Staging environment, team inbox → Mailtrap. Managed, no infrastructure to maintain.

No Docker in CI, want zero setup → ZeroDrop. Drop in the SDK and your tests work anywhere.

Still on MailHog → Migrate. It's unmaintained and Mailpit does everything it does better.

GitHub Actions example (no Docker)

The biggest practical difference between the Docker-based tools and ZeroDrop shows up in your CI workflow.

With Mailpit (Docker required):

services:
  mailpit:
    image: axllent/mailpit
    ports:
      - 1025:1025
      - 8025:8025
    options: >-
      --health-cmd "wget -qO- http://localhost:8025/api/v1/info"
      --health-interval 5s
      --health-timeout 3s
      --health-retries 5

steps:
  - name: Run tests
    run: npx playwright test
    env:
      SMTP_HOST: localhost
      SMTP_PORT: 1025
      MAILPIT_URL: http://localhost:8025

With ZeroDrop (no Docker):

steps:
  - name: Generate test inbox
    id: inbox
    uses: zerodrop-dev/create-inbox@v1

  - name: Run tests
    run: npx playwright test
    env:
      TEST_INBOX: ${{ steps.inbox.outputs.inbox }}

No services: block. No health checks. No port mappings. The inbox is ready in milliseconds.

Working example

A complete Playwright example with email verification and password reset flows, using ZeroDrop with a green CI badge:

→ github.com/zerodrop-dev/zerodrop-playwright-example