diff --git a/docs/debug.md b/docs/debug.md index 5cfba7c4b..b45debb89 100644 --- a/docs/debug.md +++ b/docs/debug.md @@ -4,7 +4,6 @@ When a problem occurs, then always for a reason! What you want to do in such a c 2. Follow the leads given to you in your logfiles and start investigating. 3. Restarting the troubled service or the whole stack to see if the problem persists. 4. Read the documentation of the troubled service and search it's bugtracker for your problem. -5. Search our [issues](https://github.com/mailcow/mailcow-dockerized/issues) and [forum](https://forum.mailcow.email/) for topics related to your problem. +5. Search our [issues](https://github.com/mailcow/mailcow-dockerized/issues) for your problem. 6. [Create an issue](https://github.com/mailcow/mailcow-dockerized/issues) over at our GitHub repository if you think your problem might be a bug or a missing feature you badly need. But please make sure, that you include **all the logs** and a full description to your problem. -7. If you need help with a problem on a configuration or a setup, or got a question please head over to our [forum](https://forum.mailcow.email/) and open a thread. 8. Connect to IRC ([chat.freenode.net](https://webchat.freenode.net/)) and join our IRC channel [#mailcow](irc://chat.freenode.net:6667/mailcow). diff --git a/docs/index.md b/docs/index.md index dadf351d3..b6770e712 100644 --- a/docs/index.md +++ b/docs/index.md @@ -17,7 +17,6 @@ For commercial support contact [info@servercow.de](mailto:info@servercow.de). ### Community support - IRC @ [Freenode, #mailcow](irc://irc.freenode.org:6667/mailcow) -- Forum @ [forum.mailcow.email](forum.mailcow.email) - GitHub @ [mailcow/mailcow-dockerized](https://github.com/mailcow/mailcow-dockerized) ## Screenshots diff --git a/docs/mc14_migrate.md b/docs/mc14_migrate.md index 73b95059d..74d007f9a 100644 --- a/docs/mc14_migrate.md +++ b/docs/mc14_migrate.md @@ -1,5 +1,5 @@ !!! warning - Please be adviced that this guide is a first draft. Mailcow: dockerized changed quite a lot on its DB configuration. It now uses the InnoDB file format `Barracuda` and the `utf8mb4` character set. There is also some change to the DB / TABLE structure. + Please be adviced that this guide is a first draft. mailcow: dockerized changed quite a lot on its DB configuration. It now uses the InnoDB file format `Barracuda` and the `utf8mb4` character set. There is also some change to the DB / TABLE structure. !!! info Also note that this guide doesn't touch on the users settings like *Spamlevels*, *TLS Settings*, etc. nor the export / import of your roundcube or SOGo settings. diff --git a/docs/requirements.md b/docs/requirements.md index 5a3a0b4af..74efcbca2 100644 --- a/docs/requirements.md +++ b/docs/requirements.md @@ -1,10 +1,10 @@ Before you run **mailcow: dockerized**, there are a few requirements that you should check: !!! warning - When you want to run the dockerized version on your Debian 8 (Jessie) box you should [switch to the kernel 4.9 from jessie backports](https://packages.debian.org/jessie-backports/linux-image-amd64) because there is a bug (kernel panic) with the kernel 3.16 when running docker containers with *healthchecks*! For more details read: [github.com/docker/docker/issues/30402](https://github.com/docker/docker/issues/30402) and [forum.mailcow.email/t/solved-mailcow-docker-causes-kernel-panic-edit/448](https://forum.mailcow.email/t/solved-mailcow-docker-causes-kernel-panic-edit/448) + When running mailcow: dockerized on a Debian 8 (Jessie) box, you should [switch to kernel 4.9 from Jessie backports](https://packages.debian.org/jessie-backports/linux-image-amd64) to avoid a bug when running Docker containers with *healthchecks*! For more details read: [github.com/docker/docker/issues/30402](https://github.com/docker/docker/issues/30402) !!! info - - Mailcow: dockerized requires [some ports](#default-ports) to be open for incomming connections, so make sure that your firewall is not bloking these. Also make sure that no other application is interferring with mailcow's configuration. + - mailcow: dockerized requires [some ports](#default-ports) to be open for incomming connections, so make sure that your firewall is not bloking these. Also make sure that no other application is interferring with mailcow's configuration. - A correct DNS setup is crucial to every good mailserver setup, so please make sure you got at least the [basics](dns/#the-minimal-dns-configuration) covered bevore you begin! - Make sure that your system has a correct date and [time setup](#date-and-time). This is crucial for stuff like two factor TOTP authentication. diff --git a/docs/reset_pw.md b/docs/reset_pw.md index 0e1cfe705..e455fa01a 100644 --- a/docs/reset_pw.md +++ b/docs/reset_pw.md @@ -1,4 +1,4 @@ -## Mailcow Admin Account +## mailcow Admin Account Reset mailcow admin to `admin:moohoo`: