GnuTLS: avoid hang in older library, in selfsigned-cert creation
[exim.git] / .github / ISSUE_TEMPLATE.md
CommitLineData
b988b061
PP
1# The Exim Project does not use GitHub Issues
2
3Hey, we want your input, but we want to make sure that we actually see it and
4that your help is not wasted, so please read this.
5
6The GitHub repo exists for convenience for some folks, and to host our Wiki.
7The Git repo is an automated clone of our real repo over at
8<https://git.exim.org/exim.git>.
9
10Sometimes a maintainer will take a look at GitHub issues, just because we care
11about the software and want to know about issues, but expect long delays.
12It's not a really supported workflow.
13
14If you need help with configuration, or _think_ you've found a bug, then the
15Exim Users mailing-list is the place to start. Many experienced postmasters
16hang out there: <https://lists.exim.org/mailman/listinfo/exim-users>
17
18Our documentation is _very_ extensive and if the behavior does not match the
19documentation, then that's a bug to be reported.
20<https://www.exim.org/docs.html>
21In addition, if using Debian or a derivative (such as *Ubuntu*), then you
22should read: <https://pkg-exim4.alioth.debian.org/README/README.Debian.html>
23
24If you're absolutely sure it's a bug, and it's not a security problem, then
25our Bugzilla is the main place to go: <https://bugs.exim.org/>
26
27If you've found a security bug, then please email <security@exim.org>.
28All Exim Maintainers can and do use PGP.
29Keyring: <https://ftp.exim.org/pub/exim/Exim-Maintainers-Keyring.asc>
30We don't have a re-encrypting mailer, just encrypt to all of them please.
31
32
33## If you MUST file an issue on GitHub
34
35Read "How to Report Bugs Effectively":
36<https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
37
38Please include the OS details, output of `exim -d -bV 2>/dev/null`
39and as much information as you think is relevant.
40
41Thanks.