SMTP relay with header support
320
Contains:
Processes are managed by supervisord, including cronjobs
The container provides a simple proxy relay for environments like Amazon VPC where you may have private servers with no Internet connection and therefore with no access to external mail relays (e.g. Amazon SES, SendGrid and others). You need to supply the container with your external mail relay address and credentials. The configuration is tested with Amazon SES.
25RELAY_HOST_NAME=relay.example.com: A DNS name for this relay container (usually the same as the Docker's hostname)ACCEPTED_NETWORKS=192.168.0.0/16 172.16.0.0/12 10.0.0.0/8: A network (or a list of networks) to accept mail fromEXT_RELAY_HOST=email-smtp.us-east-1.amazonaws.com: External relay DNS nameEXT_RELAY_PORT=587: External relay TCP port, default: 587SMTP_LOGIN=: Login to connect to the external relay (required, otherwise the container fails to start)SMTP_PASSWORD=: Password to connect to the external relay (required, otherwise the container fails to start)USE_TLS=: Remote require tls. Might be "yes" or "no". Default: no.TLS_VERIFY=: Trust level for checking the remote side cert. (none, may, encrypt, dane, dane-only, fingerprint, verify, secure). Default: may.HEADERS=: Create custom_header file as a header_checks to add content for headers, default: /^From:/i PREPEND X-SES-MESSAGE-TAGS: Origin=relayLaunch Postfix container:
$ docker run -d -h relay.example.com --name="mailrelay" -e SMTP_LOGIN=myLogin -e SMTP_PASSWORD=myPassword -p 25:25 -p 465:465 -p 587:587 narfman0/docker-mail-relay
Content type
Image
Digest
Size
22.1 MB
Last updated
almost 8 years ago
docker pull narfman0/docker-mail-relay