Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

darkzwarmer

github.com

  • Free plan
  • Windows
  • macOS
  • Linux
  • Self-hosted
7.4 Club score Visit github.com

What darkzwarmer is

darkzwarmer is a self-hosted email warmup tool that creates inboxes across domains you provide, then exchanges messages among those inboxes. Each inbox starts at five messages per day and ramps to 35 over 28 days before holding at the configured steady-state volume. Traffic only crosses between different domains; inboxes on the same domain are not paired. The network replies to its own messages after a random delay of 30 minutes to four hours and ignores mail from outside it.

Sending uses configurable SMTP, with Amazon SES, SMTP.com, Postmark, Mailgun, Brevo, and SendGrid listed as examples. Mail can arrive through IMAP or Resend; the latter setup uses a Vercel webhook and Upstash Redis queue. Sends are randomized across a default 07:00–19:00 local window, with 2–8 minutes of jitter between consecutive sends, and weekends paused. The Python 3.11-or-later runtime stores state in SQLite and is designed to resume after crashes or reboots. It requires an always-on machine, two or more domains you control, an outbound SMTP provider, and a way to receive mail. The project is free and MIT-licensed.

Who it suits

It suits users who control multiple domains and want to run a warmup network on their own always-on machine or VPS. It is aimed at people comfortable configuring Python, SMTP, and inbound mail.

Good to know, and what to watch

  • Free and MIT-licensed.
  • Supports Linux, macOS, and Windows.
  • Configurable sending windows, delays, and volume ceiling.
  • Can resume after crashes or reboots.
  • Supports SMTP sending and IMAP or Resend inbound mail.
  • Requires Python 3.11 or later.
  • Needs at least two user-owned domains.
  • Requires an always-on machine and mail providers.
  • Provided as-is without warranty.

The verdict

darkzwarmer provides configurable cross-domain warmup and delayed replies in a self-hosted setup. It requires domains, mail services, and an always-on host that you manage.

What the maker publishes

Controls
Configuration includes inbox counts, sending windows, send delays, reply delays, steady-state volume, and an optional per-inbox daily send ceiling. source
Cross-domain sending
Inboxes send to inboxes on other configured domains; same-domain pairs are not used. source
Cross-domain traffic
Each inbox sends only to inboxes on other domains, and the tool does not use same-domain pairs. source
Expansion
Optional wave cohorts can add inboxes automatically on a configured schedule, with new inboxes starting at Day 1. source
Inbound integrations
Inbound mail can be received through IMAP or Resend; the Resend setup uses a Vercel webhook and an Upstash Redis queue. source
License and warranty
The project is MIT-licensed and provided as-is without warranty. source
Operating systems
The README describes unattended operation on Windows and running under process managers on Linux and macOS. source
Operating system support
The README provides unattended-operation scripts for Windows and says Linux and macOS users can run the process under a service manager or terminal session. source
Purpose
darkzwarmer generates inboxes across user-provided domains, sends warmup email between those inboxes, and replies after human-like delays. source
Replies
The network waits a random 30 minutes to 4 hours before replying in-thread to its own messages, and ignores outsider mail. source
Reply behavior
The tool replies to its own network’s messages after a random 30-minute to 4-hour delay and ignores outsider mail. source
Requirements
It requires Python 3.11 or later, at least two user-owned domains for cross-domain traffic, an outbound SMTP provider, and a way to receive mail. source
Responsible use
The maker says the tool only emails its own network and is intended for domains and mailboxes the user owns and controls. source
Runtime
The project requires Python 3.11 or later and an always-on machine, and stores state in SQLite. source
Scheduling
Sends are randomized across a default 07:00–19:00 local window, with 2–8 minutes of jitter between an inbox’s consecutive sends; weekends are paused. source
Security and credentials
The README says secrets are supplied through environment variables, and identifies .env, catch-all credentials, and the SQLite database as git-ignored files. source
Security practices
The Resend webhook verifies request signatures, while SMTP, Resend, Upstash, and IMAP credentials are configured locally and credential files are gitignored. source
Self-hosting
The project describes itself as a Python runtime backed by SQLite that users run on an always-on machine or VPS. source
Sending integrations
Outbound delivery uses configurable SMTP and the README lists Amazon SES, SMTP.com, Postmark, Mailgun, Brevo, and SendGrid as examples. source
SMTP integrations
Outbound sending uses configurable SMTP; listed providers include Amazon SES, SMTP.com, Postmark, Mailgun, Brevo, and SendGrid. source
State and recovery
SQLite stores runtime state, and the README says the tool resumes after crashes or reboots and prevents duplicate replies with a unique index. source
Usage limits
A per-inbox daily send ceiling can be configured, and the README notes that provider rate or quota limits can cause send failures. source
Warmup ramp
Per-inbox volume increases from 5 to 35 messages per day over 28 days, then stays at the steady-state level. source
Warmup schedule
Per-inbox sending volume ramps from 5 to 35 messages per day over 28 days, then stays at the steady-state volume. source

Checked against the maker's pages on 7 Oct 2026.