diff --git a/mailcow/src/mailcow-dockerized/.github/FUNDING.yml b/mailcow/src/mailcow-dockerized/.github/FUNDING.yml
new file mode 100644
index 0000000..befe7db
--- /dev/null
+++ b/mailcow/src/mailcow-dockerized/.github/FUNDING.yml
@@ -0,0 +1 @@
+custom: https://mailcow.github.io/mailcow-dockerized-docs/#help-mailcow
diff --git a/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/Bug_report.md b/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/Bug_report.md
new file mode 100644
index 0000000..6e39c4c
--- /dev/null
+++ b/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/Bug_report.md
@@ -0,0 +1,60 @@
+---
+name: 🐞 Bug Report
+about: Report a reproducible bug for mailcow. (NOT to be used for support questions.)
+labels: bug
+---
+
+<!--
+  Please DO NOT delete this template or use it for support questions.
+  You are welcome to visit us on our community channels listed at https://mailcow.github.io/mailcow-dockerized-docs/#community-support
+  For official support, please check https://mailcow.github.io/mailcow-dockerized-docs/#commercial-support
+-->
+
+**Prior to placing the issue, please check following:** *(fill out each checkbox with an `X` once done)*
+- [ ] I understand that not following or deleting the below instructions will result in immediate closure and/or deletion of my issue.
+- [ ] I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
+- [ ] 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](https://github.com/mailcow/mailcow-dockerized/issues).
+
+## Summary
+<!--
+  This should be a clear and concise description of what the bug is. What EXACTLY does happen?
+  If applicable, add screenshots to help explain your problem. Very useful for bugs in mailcow UI.
+  Write your detailed description below.
+
+  Also mention on which commit/date your mailcow instance was last updated.
+-->
+
+## Logs
+<!--
+  Please take a look at the [official documentation](https://mailcow.github.io/mailcow-dockerized-docs/debug-logs/) and post the last
+  few lines of logs, when the error occurs. For example, docker container logs of affected containers.
+-->
+
+## Reproduction
+<!--
+  It is really helpful to know how exactly you are able to reproduce the reported issue.
+  Have you tried to fix the issue? What did you try?
+  What are the exact steps to get the above described behavior?
+  Screenshots can be added, if helpful. Add the text below.
+-->
+
+## System information
+<!--
+  In this stage we would kindly ask you to attach general system information about your setup.
+  Please carefully read the questions and instructions below.
+-->
+
+| 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 - **LXC and OpenVZ are not supported** | 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 |
+
+- 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`.
+- DNS problems? Please run `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 post the output.
diff --git a/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/Feature_request.md b/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/Feature_request.md
new file mode 100644
index 0000000..64ff9d3
--- /dev/null
+++ b/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/Feature_request.md
@@ -0,0 +1,29 @@
+---
+name: 💡 Feature Request
+about: Suggest an idea for mailcow.
+labels: enhancement
+---
+
+<!--
+  Please note that the mailcow team and its contributors do have finite
+  resources and that we can not work on all filed feature requests.
+
+  However making us aware about certain ideas can help us improving
+  mailcow together.
+  
+  We're also happy to help you getting a specific  feature implemented.
+-->
+
+## Summary
+
+A clear and concise description of what the problem is.
+For example: I'm always frustrated when [...]
+
+## Motivation
+
+What are you about to solve or improve with this idea?
+What would be the benefit for most users?
+
+## Additional context
+
+Add any other context or screenshots about the feature request.
diff --git a/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/config.yml b/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 0000000..51d0370
--- /dev/null
+++ b/mailcow/src/mailcow-dockerized/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: ❓ Community-driven support
+    url: https://mailcow.github.io/mailcow-dockerized-docs/#get-support
+    about: Please use the community forum for questions or assistance
+  - name: 🚨 Report a security vulnerability
+    url: https://www.servercow.de/anfrage?lang=en
+    about: Please give us appropriate time to verify, respond and fix before disclosure.
diff --git a/mailcow/src/mailcow-dockerized/.github/stale.yml b/mailcow/src/mailcow-dockerized/.github/stale.yml
new file mode 100644
index 0000000..24db8c0
--- /dev/null
+++ b/mailcow/src/mailcow-dockerized/.github/stale.yml
@@ -0,0 +1,18 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 60
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+# Issues with these labels will never be considered stale
+exemptLabels:
+  - pinned
+  - security
+  - enhancement
+# Label to use when marking an issue as stale
+staleLabel: dunno
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false