smtp4dev

AWS Azure Streaming & Messaging 2 variations

smtp4dev, a fake SMTP server that catches outbound mail from your applications and shows every message in a web UI inbox, ready from first boot.

Base
Hardened build
minimal ports, security patches applied at build time
Access
Unique credentials
generated on first boot, readable only by root
Verified
Boots working
services pass a health gate before release
Support
24/7, 365 days
by email and live chat, 24 hour response SLA

Variations

Choose the operating system, cloud and version you need. Every variation is the same hardened smtp4dev image, built and supported by cloudimg.

ProductCloudOperating systemVersion
smtp4dev - Fake SMTP Server & Email Testing UI AWS Standard View · Guide
smtp4dev on Ubuntu 24.04 Azure Ubuntu 24.04 Standard View · Guide

Overview

smtp4dev is a fake SMTP server for development and testing. It accepts the mail your applications send, stores it locally, and shows every captured message in a modern web UI inbox instead of delivering it to real recipients, so you can safely point a development, test or staging environment at it and inspect exactly what your application would have sent: rendered HTML, plain text and raw source, attachments, every header, and an HTML client-compatibility analysis. It also speaks IMAP, so captured mail can be browsed from any standard mail client.

Why the cloudimg image

The cloudimg image delivers smtp4dev already installed and running behind an nginx reverse proxy, with the .NET runtime installed from the distribution archive so it stays patched. A unique web password is generated and proven on first boot, refusing unauthenticated and wrong-password requests before it records the new one, and the captured-mail SQLite store lives on its own dedicated data volume. Paired with a step by step deploy guide and backed by 24/7 cloudimg support.

Common uses

  • Inspect the mail your application sends from development and staging without any risk of it reaching real recipients
  • Debug transactional email templates, HTML rendering, attachments and headers before they go out
  • Wire the REST API into automated integration tests that assert a message was sent