Phoenix Eve Aspacio
GitHub
Commit
51481a46d0
4 geänderte Dateien mit 20 neuen und 15 gelöschten Zeilen
|
|
@ -27,14 +27,19 @@ docker-compose exec redis-mailcow redis-cli
|
||||||
|
|
||||||
Here is a brief overview of what container / service does what:
|
Here is a brief overview of what container / service does what:
|
||||||
|
|
||||||
| Service Name | Service Descriptions |
|
| Service Name | Service Descriptions |
|
||||||
| --------------- | ------------------------------------------------------------------------- |
|
| ----------------- | ------------------------------------------------------------------------- |
|
||||||
| unbound-mailcow | Local (DNSSEC) DNS Resolver |
|
| unbound-mailcow | Local (DNSSEC) DNS Resolver |
|
||||||
| mysql-mailcow | Stores SOGo's and most of mailcow's settings |
|
| mysql-mailcow | Stores SOGo's and most of mailcow's settings |
|
||||||
| postfix-mailcow | Receives and sends mails |
|
| postfix-mailcow | Receives and sends mails |
|
||||||
| dovecot-mailcow | User logins and sieve filter |
|
| dovecot-mailcow | User logins and sieve filter |
|
||||||
| redis-mailcow | Storage back-end for DKIM keys and Rspamd |
|
| redis-mailcow | Storage back-end for DKIM keys and Rspamd |
|
||||||
| rspamd-mailcow | Mail filtering system. Used for av handling, dkim signing, spam handling |
|
| rspamd-mailcow | Mail filtering system. Used for av handling, dkim signing, spam handling |
|
||||||
| clamd-mailcow | Scans attachments for viruses |
|
| clamd-mailcow | Scans attachments for viruses |
|
||||||
| sogo-mailcow | Webmail client that handles Microsoft ActiveSync and Cal- / CardDav |
|
| sogo-mailcow | Webmail client that handles Microsoft ActiveSync and Cal- / CardDav |
|
||||||
| nginx-mailcow | Nginx remote proxy that handles all mailcow related HTTP / HTTPS requests |
|
| 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 |
|
||||||
|
|
|
||||||
|
|
@ -1,5 +1,5 @@
|
||||||
!!! warning
|
!!! 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.
|
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.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -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.
|
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.
|
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
|
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.).
|
Redis keys will only hold logs from applications and filter out system messages (think of cron etc.).
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -57,7 +57,7 @@ Each container represents a single application.
|
||||||
- Nginx
|
- Nginx
|
||||||
- Rspamd
|
- Rspamd
|
||||||
- SOGo
|
- SOGo
|
||||||
- Fail2ban-like integration by @mkuron
|
- Netfilter (Fail2ban-like integration by @mkuron)
|
||||||
|
|
||||||
**6 volumes** to keep dynamic data - take care of them!
|
**6 volumes** to keep dynamic data - take care of them!
|
||||||
|
|
||||||
|
|
|
||||||
Laden …
In neuem Issue referenzieren