bunny-lab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update deployments/services/email/mailcow.md
Automatic Documentation Deployment / Sync Docs to https://kb.bunny-lab.io (push) Successful in 6s
Details

Browse Source
This commit is contained in:
Nicole Rappe
2026-06-19 15:46:12 -06:00
parent a46f7a3e54
commit 61f7f574c8
1 changed files with 6 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
deployments/services/email/mailcow.md
+3 -15
View File
@@ -1,10 +1,9 @@
--- ---
tags: tags:
- Mailcow
* Mailcow - Email
* Email - Docker
* Docker
--- ---
@@ -12,14 +11,12 @@ tags:
The deployment of Mailcow is mostly correct here. Mail protocol ports should be forwarded directly to the Mailcow server from the firewall. Traefik should only sit in front of Mailcow for web traffic, and it should pass HTTPS through transparently so Mailcow can manage and serve its own certificates. The deployment of Mailcow is mostly correct here. Mail protocol ports should be forwarded directly to the Mailcow server from the firewall. Traefik should only sit in front of Mailcow for web traffic, and it should pass HTTPS through transparently so Mailcow can manage and serve its own certificates.
## Purpose ## Purpose
The purpose of this document is to illustrate how to deploy Mailcow in a dockerized format. The purpose of this document is to illustrate how to deploy Mailcow in a dockerized format.
!!! note "Assumptions" !!! note "Assumptions"
It is assumed that you are deploying Mailcow into an existing Ubuntu Server environment. If you are using a different operating system, refer to the [official documentation](https://docs.mailcow.email/getstarted/install/). It is assumed that you are deploying Mailcow into an existing Ubuntu Server environment. If you are using a different operating system, refer to the [official documentation](https://docs.mailcow.email/getstarted/install/).
### Setting Up Docker ### Setting Up Docker
Go ahead and set up docker and docker-compose with the following commands: Go ahead and set up docker and docker-compose with the following commands:
```bash ```bash
@@ -35,7 +32,6 @@ systemctl enable --now docker # (4)
4. Make docker run automatically when the server is booted. 4. Make docker run automatically when the server is booted.
### Download and Deploy Mailcow ### Download and Deploy Mailcow
Run the following commands to pull down the mailcow deployment files and install them with docker. Go get a cup of coffee as the `docker compose pull` command may take a while to run. Run the following commands to pull down the mailcow deployment files and install them with docker. Go get a cup of coffee as the `docker compose pull` command may take a while to run.
!!! note "Potential `Docker Compose` Issues" !!! note "Potential `Docker Compose` Issues"
@@ -60,7 +56,6 @@ docker-compose up -d
``` ```
### Firewall / NAT Configuration ### Firewall / NAT Configuration
Forward Mailcow service ports as follows: Forward Mailcow service ports as follows:
```text ```text
@@ -80,7 +75,6 @@ WAN :4190 -> Mailcow :4190
Mail protocol ports should be sent directly to the Mailcow server. Traefik should not terminate or proxy the SMTP, SMTPS, Submission, IMAP, IMAPS, POP3, POP3S, or ManageSieve ports. Mail protocol ports should be sent directly to the Mailcow server. Traefik should not terminate or proxy the SMTP, SMTPS, Submission, IMAP, IMAPS, POP3, POP3S, or ManageSieve ports.
### Reverse-Proxy Configuration ### Reverse-Proxy Configuration
For the purposes of this document, it will be assumed that you are deploying Mailcow behind Traefik for web traffic only. Traefik should pass HTTPS through transparently, allowing Mailcow to manage and serve its own certificates. For the purposes of this document, it will be assumed that you are deploying Mailcow behind Traefik for web traffic only. Traefik should pass HTTPS through transparently, allowing Mailcow to manage and serve its own certificates.
You can use the following dynamic configuration file to achieve this: You can use the following dynamic configuration file to achieve this:
@@ -129,7 +123,6 @@ tcp:
``` ```
### Traefik-Specific Configuration ### Traefik-Specific Configuration
Traefik only needs the standard HTTP and HTTPS entrypoints for Mailcow web traffic. Mail protocol ports should not be exposed through Traefik if the firewall is forwarding those ports directly to Mailcow. Traefik only needs the standard HTTP and HTTPS entrypoints for Mailcow web traffic. Mail protocol ports should not be exposed through Traefik if the firewall is forwarding those ports directly to Mailcow.
```yaml ```yaml
@@ -145,9 +138,7 @@ Traefik only needs the standard HTTP and HTTPS entrypoints for Mailcow web traff
Do not add Mailcow mail protocol entrypoints or port bindings to Traefik unless you intentionally want Traefik to proxy those ports. Do not add Mailcow mail protocol entrypoints or port bindings to Traefik unless you intentionally want Traefik to proxy those ports.
### Certificate Validation ### Certificate Validation
Mailcow should manage and serve the certificate for `mail.bunny-lab.io`. Mailcow should manage and serve the certificate for `mail.bunny-lab.io`.
To verify the active Mailcow certificate on disk, run the following on the Mailcow server: To verify the active Mailcow certificate on disk, run the following on the Mailcow server:
```bash ```bash
@@ -166,16 +157,13 @@ docker compose restart postfix-mailcow dovecot-mailcow nginx-mailcow
``` ```
### Login to Mailcow ### Login to Mailcow
At this point, the Mailcow server has been deployed so you can log into it. At this point, the Mailcow server has been deployed so you can log into it.
* **Administrators**: `https://${MAILCOW_HOSTNAME}/admin` (Username: `admin` | Password: `moohoo`) * **Administrators**: `https://${MAILCOW_HOSTNAME}/admin` (Username: `admin` | Password: `moohoo`)
* **Regular Mailbox Users**: `https://${MAILCOW_HOSTNAME}` (*FQDN only*) * **Regular Mailbox Users**: `https://${MAILCOW_HOSTNAME}` (*FQDN only*)
### Mail-Client Considerations ### Mail-Client Considerations
You need to ensure that you generate an app password if you have MFA enabled within Mailcow. (MFA is non-functional in Roundcube/SoGo, you set it up via Mailcow itself). You can access it via the Mailcow configuration page: https://mail.bunny-lab.io/user, then look for the "**App Passwords**" tab. You need to ensure that you generate an app password if you have MFA enabled within Mailcow. (MFA is non-functional in Roundcube/SoGo, you set it up via Mailcow itself). You can access it via the Mailcow configuration page: https://mail.bunny-lab.io/user, then look for the "**App Passwords**" tab.
### Running Updates ### Running Updates
If you want to run updates, just SSH into the server, and navigate to `/opt/mailcow-dockerized` and run `./update.sh`. I recommend avoiding the IPv6 implementation section. Be patient, and the upgrade will be fully-automated. If you want to run updates, just SSH into the server, and navigate to `/opt/mailcow-dockerized` and run `./update.sh`. I recommend avoiding the IPv6 implementation section. Be patient, and the upgrade will be fully-automated.