mirror of
https://github.com/adferrand/docker-backuppc.git
synced 2023-11-05 04:40:26 +01:00
Update changelog and documentation
This commit is contained in:
parent
d79dfd142d
commit
37824a69b0
@ -3,7 +3,7 @@
|
||||
## master - CURRENT
|
||||
### Added
|
||||
* The system configuration file `/etc/msmtprc` for `msmtprc` is not overwritten
|
||||
if it already exists at container initialization.
|
||||
if it already exists at container initialization. Update documentation on that matter.
|
||||
|
||||
## 4.4.0-3 - 06/11/2020
|
||||
### Modified
|
||||
|
@ -223,7 +223,7 @@ docker run \
|
||||
|
||||
### Advanced SMTP configuration
|
||||
|
||||
In more complex scenarios, like sending notifications through a TLS-secured SMTP server with authentication (eg. Google SMTP), you can use any advanced configuration supported by MSMTP. To do so, mount or copy a user-wide SMTP configuration file `.msmtprc` in the volume `/home/backuppc`. This configuration will be used for any email sended by BackupPC.
|
||||
In more complex scenarios, like sending notifications through a TLS-secured SMTP server with authentication (eg. Google SMTP), you can use any advanced configuration supported by MSMTP. To do so, mount your custom `msmtprc` configuration file on the Docker path `/etc/msmtprc`. This configuration will be used for any email sent by BackupPC.
|
||||
|
||||
See [MSMTP documentation](http://msmtp.sourceforge.net/doc/msmtp.html), in particular its [configuration examples](http://msmtp.sourceforge.net/doc/msmtp.html#Examples), to see how to build the configuration which suits your needs.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user