mailcow-dockerized/.github/ISSUE_TEMPLATE/Bug_report.md

name	about
Bug report	Report a bug for this project

Please try to answer all questions. If you cannot, don't just delete it. If you completely ignore or remove the whole template, your issue is either closed or ignored, too. :( This is (not only) because we are evil. Many awesome mailcow supporters don't bother to reply to an issue, when crucial information is missing. Especially when it could have been answered by using this issue template. We need as much information as possible. Please post all logs, do not copy that one line you think may be interesting. Copy the whole bunch and remove sensible information. :) Thank you!

Prior to placing the issue, please check following: (fill out each checkbox with a X once done)

• I understand that not following below instructions might result in immediate closing and deletion of my issue.
• I have understood that answers are voluntary and community-driven, and not commercial support.
• I have verified that my issue has not been already answered in the past. I also checked previous issues.

---

Description of the bug: What kind of issue have you exactly come across?

My issue is...

Reproduction of said bug: How exactly do you reproduce the bug?

1. I go to...
2. And then to...
3. But once I do...

I have tried or I do... (fill out each checkbox with a X if applicable)

• In case of WebUI issue, I have tried clearing the browser cache and the issue persists.
• I do run mailcow on a Synology, QNAP or any other sort of NAS.

System information

Further information (where applicable):

Question	Answer
My operating system	I_DO_REPLY_HERE
Is Apparmor, SELinux or similar active?	I_DO_REPLY_HERE
Virtualization technlogy (KVM, VMware, Xen, etc)	I_DO_REPLY_HERE
Server/VM specifications (Memory, CPU Cores)	I_DO_REPLY_HERE
Docker Version (docker version)	I_DO_REPLY_HERE
Docker-Compose Version (docker-compose version)	I_DO_REPLY_HERE
Reverse proxy (custom solution)	I_DO_REPLY_HERE

Further notes:

• Output of git diff origin/master, any other changes to the code? If so, please post them.
• All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you: iptables -L -vn, ip6tables -L -vn, iptables -L -vn -t nat and ip6tables -L -vn -t nat
• Check docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254 (set the IP accordingly, if you changed the internal mailcow network) and docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @1.1.1.1 - output? Timeout?

General logs:

• Please take a look at the official documentation.