cybercinch/docker-smtp
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improve README

Browse Source
This commit is contained in:
Jamie Nguyen
2018-07-11 15:35:58 +01:00
parent 6509375f1d
commit 414a898235
1 changed files with 20 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
README.md
View File

@@ -27,9 +27,6 @@ Via Docker Compose:
restart: always restart: always
``` ```
Optionally, set `MAILNAME` environment variable. (By default, Exim will use the
hostname of the container.)
### SMTP smart host ### SMTP smart host
In this example, linked containers can connect to hostname `mail` and port `25` In this example, linked containers can connect to hostname `mail` and port `25`
@@ -57,5 +54,23 @@ Via Docker Compose:
RELAY_PASSWORD: secretpassword RELAY_PASSWORD: secretpassword
``` ```
Optionally, set `MAILNAME` environment variable. (By default, Exim will use the ### Environment variables
hostname of the container.)
All environment variables are optional. But if you specify a `RELAY_HOST`, then
you'll want to also specify the port, username and password otherwise it's
unlikely to work!
* **`MAILNAME`**: Sets Exim's `primary_hostname`, which defaults to the
hostname of the server.
* **`RELAY_HOST`**: The remote SMTP server address to use.
* **`RELAY_PORT`**: The remote SMTP server port to use.
* **`RELAY_USERNAME`**: The username to authenticate with the remote SMTP
server.
* **`RELAY_PASSWORD`**: The password to authenticate with the remote SMTP
server.
* **`RELAY_NETS`**: Declare which networks can use the smart host, separated by
semi-colons. By default, this is set to
`10.0.0.0/8;172.16.0.0/12;192.168.0.0/16`, which provides a thin layer of
protection in case port 25 is accidentally exposed to the public internet
(which would make your SMTP container an open relay).