From 37824a69b077756fd90ed29eb2d55608ea60b6a0 Mon Sep 17 00:00:00 2001 From: Adrien Ferrand Date: Fri, 13 Nov 2020 18:56:09 +0100 Subject: [PATCH] Update changelog and documentation --- CHANGELOG.md | 2 +- README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 67daddd..797b4d2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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 diff --git a/README.md b/README.md index fe2ed4c..31ff117 100644 --- a/README.md +++ b/README.md @@ -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.