Skip to content

OpenSMTPD stack documentation

No delivery guarantee

If you're using a server from a public cloud there's a good chance that its IP is already compromised and blacklisted by major mail services, hence your emails will not be delivered or will land in the spam folder. We strongly recommend using OpenSMTPD in pair with a third-party SMTP services.

OpenSMTPD can be configured with the following environment variables

Sending test emails from CLI

  1. Access OpenSMTPD container
  2. Run sendmail -v -f verified-sender@verified-domain.com to@example.com
  3. Enter email subject and body in the input:
    Subject: test subject
    
    test body
    
  4. Enter Ctrl + D

Integration with third-party SMTP services

  • SendGrid
  • AWS SES
  • OpenSMTPD can be configured with any SMTP server. Just provide the following environment variables:
    RELAY_HOST
    RELAY_USER
    RELAY_PASSWORD
    
    By default it utilizes TLS schema with port 587 that can be changed via RELAY_PORT.

Changelog

This changelog is for OpenSMTPD stack on Wodby, to see image changes see tags description on repository page.

1.1.1

OpenSMTPD patch update to 6.0.3

1.1.0

  • Improved health check now runs smtp command
  • Messages queue is now persistent
  • Default memory request set to 4m

1.0.3

  • Allow relay auth without password
  • Use netcat instead of telnet in health checks
  • Health check timeout increased to 30 seconds

1.0.2

  • Bugfix: health probes caused warning in logs

1.0.1

  • Support for relay without authentication

1.0.0

Initial release