Restore MySQL dump with docker instead of compose

docs/u_and_e.md

@@ -209,10 +209,13 @@ docker-compose exec mysql-mailcow mysqldump --default-character-set=utf8mb4 -u${
 ```
 
 ### Restore
+
+You should redirect the sql dump without Docker-Compose to prevent parsing errors.
+
 ```
 cd /path/to/mailcow-dockerized
 source mailcow.conf
-docker-compose exec mysql-mailcow mysql -u${DBUSER} -p${DBPASS} ${DBNAME} < backup_file.sql
+docker exec -i $(docker-compose ps -q mysql-mailcow) mysql -u${DBUSER} -p${DBPASS} ${DBNAME} < backup_file.sql
 ```
 
 ### Reset MySQL passwords
@@ -274,9 +277,9 @@ Limit the output by calling logs with `--tail=300` like `docker-compose logs --t
 
 Since February the 28th 2017 mailcow does come with port 80 and 443 enabled.
 
-Open `mailcow.conf` and set `HTTP_BIND=0.0.0.0`.
+Open `mailcow.conf` and set `HTTP_BIND=0.0.0.0` - if not already set.
 
-Open `data/conf/nginx/site.conf` and add a new "catch-all" site at the top of that file:
+Open `data/conf/nginx/site.conf` and add a new site at the top of that file:
 
 ```
 server {
@@ -286,9 +289,19 @@ server {
 }
 ```
 
-Restart the stack, changed containers will be updated:
+In case you changed the HTTP_BIND parameter, recreate the container:
+
+```
+docker-compose up -d
+```
+
+Otherwise restart Nginx:
+
+```
+docker-compose restart nginx-mailcow
+```
+
 
-`docker-compose up -d`
 
 ## Redis