Merge pull request #85 from mailcow/draft

Some Updates

docs/debug-attach_service.md

@@ -28,7 +28,7 @@ docker-compose exec redis-mailcow redis-cli
 Here is a brief overview of what container / service does what:
 
 | Service Name      | Service Descriptions                                                      |
-| --------------- | ------------------------------------------------------------------------- |
+| ----------------- | ------------------------------------------------------------------------- |
 | unbound-mailcow   | Local (DNSSEC) DNS Resolver                                               |
 | mysql-mailcow     | Stores SOGo's and most of mailcow's settings                              |
 | postfix-mailcow   | Receives and sends mails                                                  |
@@ -38,3 +38,8 @@ Here is a brief overview of what container / service does what:
 | clamd-mailcow     | Scans attachments for viruses                                             |
 | sogo-mailcow      | Webmail client that handles Microsoft ActiveSync and Cal- / CardDav       |
 | nginx-mailcow     | Nginx remote proxy that handles all mailcow related HTTP / HTTPS requests |
+| acme-mailcow      | Automates HTTPS (SSL/TLS) certificate deployment                          |
+| memcached-mailcow | Internal caching system for mailcow services                              |
+| watchdog-mailcow  | Allows the monitoring of docker containers / services                     |
+| php-fpm-mailcow   | Powers the mailcow web UI                                                 |
+| netfilter-mailcow | Fail2Ban like integration                                                 |

docs/debug-logs.md

@@ -1,5 +1,5 @@
 !!! warning
-    This section only applies for Dockers default logging driver (Json).
+    This section only applies for Dockers default logging driver (JSON).
 
 To view the logs of all mailcow: dockerized related containers, you can use `docker-compose logs` inside your mailcow-dockerized folder that contains your `mailcow.conf`. This is usually a bit much, but you could trim the output with `--tail=100` to the last 100 lines per container, or add a `-f` to follow the live output of all your services.
 

docs/firststeps-logging.md

@@ -14,12 +14,12 @@ The **default logging driver is "json"**.
 
 Some logs are filtered and written to Redis keys but also streamed to a Redis channel.
 
-The Redis channel is used to stream logs with failed authentication attempts to be read by fail2ban-mailcow.
+The Redis channel is used to stream logs with failed authentication attempts to be read by netfilter-mailcow.
 
 The Redis keys are persistent and will keep 10000 lines of logs for the web UI.
 
 This mechanism makes it possible to use whatever Docker logging driver you want to, without losing 
-the ability to read logs from the UI or ban suspicious clients with fail2ban-mailcow.
+the ability to read logs from the UI or ban suspicious clients with netfilter-mailcow.
 
 Redis keys will only hold logs from applications and filter out system messages (think of cron etc.).
 

docs/index.md

@@ -57,7 +57,7 @@ Each container represents a single application.
 - Nginx
 - Rspamd
 - SOGo
-- Fail2ban-like integration by @mkuron
+- Netfilter (Fail2ban-like integration by @mkuron)
 
 **6 volumes** to keep dynamic data - take care of them!