Heralding vs Mailoney
Heralding
github.comMailoney
github.comSide by side
| Figure | Heralding | Mailoney |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| Linux | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Honeypot Software | 7.5 (#12) | 6.9 (#18) |
| License | GitHub identifies the project as GPL-3.0 licensed. | The repository identifies Mailoney as MIT-licensed. |
| Purpose | Heralding is a simple honeypot that collects credentials. | Mailoney is a low-interaction SMTP honeypot that simulates a vulnerable mail server to detect and log unauthorized access attempts, credential harvesting, and other SMTP-based attacks. |
Plans
In their own words
Heralding
Heralding is a free, self-hosted network honeypot that collects credentials. It runs on Linux and supports FTP, Telnet, SSH, HTTP, HTTPS, POP3, POP3S, IMAP, IMAPS, SMTP, VNC, PostgreSQL and SOCKS5. When a protocol makes them available, its authentication log records usernames and plaintext passwords. It also writes authentication attempts, session summaries and full session data to CSV and JSON Lines files. Session details can include timestamps, duration, source and destination IP addresses and ports, protocol, authentication attempts and protocol-specific auxiliary data. Session log entries are written after sessions end; authentication entries appear once a password has been transmitted. The README describes pip installation on Debian-based systems and Docker deployment using port mapping. Python 3.7.0 or higher is required. For separate packet captures per session, the README points to Curisoum and says it must be enabled in Heralding.yml. GitHub identifies the project as GPL-3.0 licensed.
Mailoney
Mailoney is a self-hosted SMTP honeypot for recording attempts to access a simulated vulnerable mail server. It listens on port 25 and captures authentication attempts and credentials. Session data can be stored in SQLite, PostgreSQL, or MySQL/MariaDB, or the database can be disabled for event-only logging; PostgreSQL is recommended for production. By default, captured email bodies are discarded. Setting MAILONEY_MAIL_DIR enables writing them to disk. Events can be emitted as JSON Lines for forwarding to log shippers and security tools, including SIEM, ELK Stack, or Loki. An optional Prometheus endpoint reports connection, session, credential, command, and duration metrics. STARTTLS is available when a certificate and matching private key are configured, with TLS 1.2 as the minimum. Deployment options include Docker, Docker Compose, or local Python installation. It supports Linux and Windows and is distributed under the MIT License. The project advises controlled deployment, limited privileges, and firewall configuration; its unauthenticated metrics endpoint should not be exposed to the internet.