mirror of
https://github.com/tomav/docker-mailserver.git
synced 2024-07-19 22:28:36 +02:00
a0ee472501
"Brief" summary/overview of changes. See the PR discussion or individual commits from the PR for more details.
---
Only applies to the `docs/content/**` content (_and `setup` command_). `target/` and `test/` can be normalized at a later date.
* Normalize to `example.com`
- Domains normalized to `example.com`: `mywebserver.com`, `myserver.tld`, `domain.com`, `domain.tld`, `mydomain.net`, `my-domain.tld`, `my-domain.com`, `example.org`, `whoami.com`.
- Alternative domains normalized to `not-example.com`: `otherdomain.com`, `otherdomain.tld`, `domain2.tld`, `mybackupmx.com`, `whoareyou.org`.
- Email addresses normalized to `admin@example.com` (in `ssl.md`): `foo@bar.com`, `yourcurrentemail@gmail.com`, `email@email.com`, `admin@domain.tld`.
- Email addresses normalized to `external-account@gmail.com`: `bill@gates321boom.com`, `external@gmail.com`, `myemail@gmail.com`, `real-email-address@external-domain.com`.
- **`faq.md`:** A FAQ entry title with `sample.domain.com` changed to `subdomain.example.com`.
- **`mail-fetchmail.md`:** Config examples with FQDNs for `imap`/`pop3` used `example.com` domain for a third-party, changed to `gmail.com` as more familiar third-party/external MTA.
* Normalize config volume path
- Normalizing local config path references to `./docker-data/dms/config/`: `./config/`, `config/`, \``config`\`, `/etc/` (_volume mount src path prefix_).
- Normalize DMS volume paths to `docker-data/dms/mail-{data,state,log}`: `./mail`, `./mail-state` `./data/mail`, `./data/state`, `./data/logs`, `./data/maildata`, `./data/mailstate`, `./data/maillogs`, (_dropped/converted data volumes: `maildata`, `mailstate`_).
- Other docker images also adopt the `docker-data/{service name}/` prefix.
* `ssl.md` - Use `dms/custom-certs` where appropriate.
* Apply normalizations to README and example `docker-compose.yml`
---
Common terms, sometimes interchangeably used or now invalid depending on context: `mail`, `mail container`, `mail server`, `mail-server`, `mailserver`,`docker-mailserver`, `Docker Mailserver`.
Rough transformations applied to most matches (_conditionally, depending on context_):
- 'Docker Mailserver' => '`docker-mailserver`'
- 'mail container' => '`docker-mailserver`' (_optionally retaining ' container'_)
- 'mail server' => 'mail-server' / '`docker-mailserver`'
- 'mail-server' => '`docker-mailserver`'
- 'mailserver' => 'mail-server' / '`docker-mailserver`'
Additionally I checked `docker run` (_plus `exec`, `logs`, etc, sub-commands_) and `docker-compose` commands. Often finding usage of `mail` instead of the expected `mailserver`
Additionally changes `mailserver` hostname in k8s to `mail` to align with other non-k8s examples.
---
* drive-by revisions
Mostly minor revisions or improvements to docs that aren't related to normalization effort.
66 lines
2.6 KiB
Markdown
66 lines
2.6 KiB
Markdown
---
|
|
title: 'Troubleshooting | Debugging'
|
|
---
|
|
|
|
!!! info "Contributions Welcome!"
|
|
Please contribute your solutions to help the community :heart:
|
|
|
|
## Enable Verbose Debugging Output
|
|
|
|
You may find it useful to enable the [`DMS_DEBUG`][docs-environment-dmsdebug] environment variable.
|
|
|
|
## Invalid Username or Password
|
|
|
|
1. Shell into the container:
|
|
|
|
```sh
|
|
docker exec -it <my-container> bash
|
|
```
|
|
|
|
2. Check log files in `/var/log/mail` could not find any mention of incorrect logins here neither in the dovecot logs.
|
|
|
|
3. Check the supervisors logs in `/var/log/supervisor`. You can find the logs for startup of fetchmail, postfix and others here - they might indicate problems during startup.
|
|
|
|
4. Make sure you set your hostname to `mail` or whatever you specified in your `docker-compose.yml` file or else your FQDN will be wrong.
|
|
|
|
## Installation Errors
|
|
|
|
During setup, if you get errors trying to edit files inside of the container, you likely need to install `vi`:
|
|
|
|
```sh
|
|
sudo su
|
|
docker exec -it <my-container> apt-get install -y vim
|
|
```
|
|
|
|
## Testing Connection
|
|
|
|
I spent HOURS trying to debug "Connection Refused" and "Connection closed by foreign host" errors when trying to use telnet to troubleshoot my connection. I was also trying to connect from my email client (macOS mail) around the same time. Telnet had also worked earlier, so I was extremely confused as to why it suddenly stopped working. I stumbled upon `fail2ban.log` in my container. In short, when trying to get my macOS client working, I exceeded the number of failed login attempts and fail2ban put dovecot and postfix in jail! I got around it by whitelisting my ipaddresses (my ec2 instance and my local computer)
|
|
|
|
```sh
|
|
sudo su
|
|
docker exec -it mailserver bash
|
|
cd /var/log
|
|
cat fail2ban.log | grep dovecot
|
|
|
|
# Whitelist IP addresses:
|
|
fail2ban-client set dovecot addignoreip <server ip> # Server
|
|
fail2ban-client set postfix addignoreip <server ip>
|
|
fail2ban-client set dovecot addignoreip <client ip> # Client
|
|
fail2ban-client set postfix addignoreip <client ip>
|
|
|
|
# This will delete the jails entirely - nuclear option
|
|
fail2ban-client stop dovecot
|
|
fail2ban-client stop postfix
|
|
```
|
|
|
|
## Sent email is never received
|
|
|
|
Some hosting provides have a stealth block on port 25. Make sure to check with your hosting provider that traffic on port 25 is allowed
|
|
|
|
Common hosting providers known to have this issue:
|
|
|
|
- [Azure](https://docs.microsoft.com/en-us/azure/virtual-network/troubleshoot-outbound-smtp-connectivity)
|
|
- [AWS EC2](https://aws.amazon.com/premiumsupport/knowledge-center/ec2-port-25-throttle/)
|
|
|
|
[docs-environment-dmsdebug]: ../environment.md#dms_debug
|