Update prerequisite-system.md

Dieser Commit ist enthalten in:
André Peters 2019-02-19 10:21:36 +01:00 committet von GitHub
Ursprung b3cd97f7d4
Commit a6d6794ed1
Es konnte kein GPG-SchlĂĽssel zu dieser Signatur gefunden werden
GPG-SchlĂĽssel-ID: 4AEE18F83AFDEB23

Datei anzeigen

@ -30,11 +30,17 @@ Please check if any of mailcow's standard ports are open and not in use by other
# netstat -tulpn | grep -E -w '25|80|110|143|443|465|587|993|995' # netstat -tulpn | grep -E -w '25|80|110|143|443|465|587|993|995'
``` ```
!!! warning
There are several problems with running mailcow on a firewalld/ufw enabled system. You should disable it (if possible) and move your ruleset to the DOCKER-USER chain, which is not cleared by a Docker service restart, instead. See [this blog post](https://blog.donnex.net/docker-and-iptables-filtering/) for information about how to use iptables-persistent with the DOCKER-USER chain.
As mailcow runs dockerized, INPUT rules have no effect on restricting access to mailcow. Use the FORWARD chain instead.
**
If this command returns any results please remove or stop the application running on that port. You may also adjust mailcows ports via the `mailcow.conf` configuration file. If this command returns any results please remove or stop the application running on that port. You may also adjust mailcows ports via the `mailcow.conf` configuration file.
### Default Ports ### Default Ports
If you have a firewall already up and running please make sure that these ports are open for incoming connections: If you have a firewall in front of mailcow, please make sure that these ports are open for incoming connections:
| Service | Protocol | Port | Container | Variable | | Service | Protocol | Port | Container | Variable |
| --------------------|:--------:|:-------|:----------------|----------------------------------| | --------------------|:--------:|:-------|:----------------|----------------------------------|