2017-05-13 18:16:08 +00:00
..todo.. - Please contribute more to help others debug this package
2019-03-08 20:54:33 +00:00
## Enable verbose debugging output
2019-03-08 20:55:05 +00:00
You may find it useful to enable the [DMS_DEBUG ](https://github.com/tomav/docker-mailserver#dms_debug ) environment variable.
2019-03-08 20:54:33 +00:00
2017-01-04 00:41:59 +00:00
## Invalid username or Password
2017-05-13 18:16:08 +00:00
2017-01-04 00:46:39 +00:00
1. Login Container
2017-05-13 19:56:06 +00:00
```bash
2017-01-04 00:46:39 +00:00
docker exec -it < mycontainer > bash
2017-05-13 19:56:06 +00:00
```
2017-01-04 00:46:39 +00:00
2. Check log files
2017-05-13 19:56:06 +00:00
`/var/log/mail`
2017-01-04 00:46:39 +00:00
could not find any mention of incorrect logins here
neither in the dovecot logs
2017-01-04 00:58:12 +00:00
2018-11-10 10:46:58 +00:00
3. Check the supervisors logfiles
`/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
2018-01-01 17:27:15 +00:00
2018-01-01 17:30:55 +00:00
## Installation Errors
2018-01-01 17:29:12 +00:00
2018-01-01 17:30:39 +00:00
1. During setup, if you get errors trying to edit files inside of the container, you likely need to install vi:
2018-01-01 17:29:12 +00:00
2018-01-01 17:33:39 +00:00
``` bash
sudo su
docker exec -it < mycontainer > apt-get install -y vim
```
2018-01-01 21:20:58 +00:00
## 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)
```bash
sudo su
docker exec -ti mail bash
cd /var/log
cat fail2ban.log | grep dovecot
# Whitelist ip addresses:
2018-01-09 07:39:54 +00:00
fail2ban-client set dovecot addignoreip < server ip > # Server
2018-01-01 21:23:27 +00:00
fail2ban-client set postfix addignoreip < server ip >
2018-01-09 07:39:54 +00:00
fail2ban-client set dovecot addignoreip < client ip > # Client
2018-01-01 21:23:27 +00:00
fail2ban-client set postfix addignoreip < client ip >
2018-01-01 21:20:58 +00:00
2018-01-01 21:23:27 +00:00
# this will delete the jails entirely - nuclear option
2018-01-01 21:20:58 +00:00
fail2ban-client stop dovecot
fail2ban-client stop postfix
2020-07-15 06:32:38 +00:00
```
## Send 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/ )
