Mailhog

Testing a password-reset or order-confirmation email should not require sending it to a real customer. MailHog acts as a mail server that captures messages from a development application and displays them in a browser or through an API. Developers can inspect the contents, attachments and formatting while testing the surrounding workflow. It can also release captured mail to a real server, so that outbound-delivery option needs an intentional boundary.

Current guidance

MailHog’s primary repository describes an SMTP capture server, web interface and JSON API, with in-memory storage by default and optional persistent backends. It also supports releasing captured messages through a real SMTP server. It is an email-testing tool rather than a production mailbox or general mail-transfer service.

Use test addresses and control outbound delivery so password resets, order confirmations or other captured messages cannot reach real recipients accidentally. Protect the UI and API because message bodies may contain credentials or personal data. The documented HTTP basic authentication is a configuration choice, not evidence that every historical chart enabled it.

Choose whether messages should survive pod replacement and set a retention policy appropriate to the test environment. Exercise multipart messages, attachments and the application’s retry behavior without relying on a public SMTP destination. This review verifies the original project and features but does not establish an ongoing support commitment or a current security assessment of the old image. Do not infer retirement solely from the age of examples.