Updated FAQ (markdown)

This commit is contained in:
Thomas VIAL 2016-02-10 09:39:41 +01:00
parent b6b9b2b5c7
commit 220681f469
1 changed files with 30 additions and 1 deletions

View File

@ -7,6 +7,35 @@ You'll probably want to `push` your config updates to your server and restart th
Mails are stored in `/var/mail/${domain}/${username}`. Mails are stored in `/var/mail/${domain}/${username}`.
You should use a [data volume container](https://medium.com/@ramangupta/why-docker-data-containers-are-good-589b3c6c749e#.uxyrp7xpu) for `/var/mail` for data persistence. Otherwise, your data may be lost. You should use a [data volume container](https://medium.com/@ramangupta/why-docker-data-containers-are-good-589b3c6c749e#.uxyrp7xpu) for `/var/mail` for data persistence. Otherwise, your data may be lost.
### How can I use data volume container as proposed above?
Here is a `docker-compose.yml` example which use a data volume container for email storage named `maildata`.
maildata:
image: ubuntu
volumes:
- /var/mail
command: /bin/true
mail:
image: "tvial/docker-mailserver"
hostname: "mail"
domainname: "domain.com"
volumes_from:
- maildata
ports:
- "25:25"
- "143:143"
- "587:587"
- "993:993"
volumes:
- ./spamassassin:/tmp/spamassassin/
- ./postfix:/tmp/postfix/
- ./opendkim/keys:/etc/opendkim/keys
- ./letsencrypt/etc:/etc/letsencrypt
environment:
- DMS_SSL=letsencrypt
### What about backups? ### What about backups?
Assuming that you use `docker-compose` and a data volume container named `maildata`, you can backup your user mails like this: Assuming that you use `docker-compose` and a data volume container named `maildata`, you can backup your user mails like this:
@ -39,4 +68,4 @@ Antispam rules are managed in `spamassassin/rules.cf`.
### What kind of SSL certificates can I use? ### What kind of SSL certificates can I use?
You can use the same certificates you use with another mail server. You can use the same certificates you use with another mail server.
The only thing is that we provide a `self-signed` certificate tool and a `letsencrypt` certificate loader. The only thing is that we provide a `self-signed` certificate tool and a `letsencrypt` certificate loader.