From bd4a1e23c78ac87607b0259163c6fce3b376bceb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Andr=C3=A9=20Peters?= <andre.peters@debinux.de>
Date: Tue, 16 Feb 2021 15:00:39 +0100
Subject: [PATCH] Update u_e-xmpp-enable.md

---
 docs/u_e-xmpp-enable.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/u_e-xmpp-enable.md b/docs/u_e-xmpp-enable.md
index 1cc73ed78..3d4dc0adf 100644
--- a/docs/u_e-xmpp-enable.md
+++ b/docs/u_e-xmpp-enable.md
@@ -76,6 +76,18 @@ If your reverse proxy is configured to point to a site like `webmail.domain.tld`
 
 That's because mailcow does not know it should respond to `webmail.domain.tld` with mailcow UI.
 
+### Method 1
+
+A more simple approach is defining `ADDITIONAL_SERVER_NAMES` in `mailcow.conf`:
+
+```
+ADDITIONAL_SERVER_NAMES=webmail.domain.tld
+```
+
+Run `docker-compose up -d` to apply.
+
+### Method 2
+
 In your reverse proxy configuration, make sure you set a "Host" header that mailcow actually services, similar to this (Nginx example):
 
 ```