From 80f67992837c23d47b5bca26c117e24ef0d87454 Mon Sep 17 00:00:00 2001
From: netdatabot <43409846+netdatabot@users.noreply.github.com>
Date: Wed, 8 Jan 2025 12:11:15 +0000
Subject: [PATCH] Ingest new documentation

---
 .../agent-dispatched-notifications/email.mdx          | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/email.mdx b/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/email.mdx
index 2c203591e8..bed22ab816 100644
--- a/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/email.mdx
+++ b/docs/alerts-&-notifications/notifications/agent-dispatched-notifications/email.mdx
@@ -29,6 +29,17 @@ Send notifications via Email using Netdata's Agent alert notification feature, w
 
 - A working sendmail command is required for email alerts to work. Almost all MTAs provide a sendmail interface. Netdata sends all emails as user netdata, so make sure your sendmail works for local users.
 - Access to the terminal where Netdata Agent is running
+- When running Netdata with Docker Compose the emails are sent with `msmtp`, and you need a basic configuration for it to work. 
+  
+  - Add a [msmtprc](https://marlam.de/msmtp/msmtprc.txt) config file on your Docker root folder, and edit it according to your needs.
+  - Link it into your Netdata container with this:
+  
+    ```yaml
+        volumes:
+          - /path/to/netdata-docker/msmtprc:/etc/msmtprc:ro
+    ```
+  
+  - Update your container with `docker compose up -d`.