- Edited
Hello there.
I’m trying Mailcow self hosted at home in France for testing purposes (at least for now).
I’m also using this as a base to see if we can replace our Exchange 365 solution by a hosted one that is easy to manage, safe and reliable, but that’s a story for another time since if my tests are successfull, I will make sure my compagny gets enterprise support since it’s fairly reasonably priced.
I managed to set everything and working pretty good for now but I’m trying to see if I can reach PCI DSS / HIPAA / NIST level at as I’m able to with our Exchange Online solution.
I read all the doc I could read, searched this community forum and git repository for solutions but I did not find one that seems to be working for these elements for which immuniweb does not seem to be happy about :
- SMTP AUTHENTICATION : Plain authentication without TLS available
- ${FQDN}:25 (SMTP) SSL Security Test : The server has TLS 1.0 enabled. It is non-compliant with NIST since SP 800-52 REV. 2 and non-compliant with PCI DSS since the 30th of June 2018.
- ${FQDN}:25 (SMTP) SSL Security Test => SERVER DOES NOT SUPPORT OCSP STAPLING : The server is not configured to support OCSP stapling for its RSA certificate that allows better verification of the certificate validation status. Reconfigure or upgrade your web server to enable OCSP stapling.
- ${FQDN}:25 (SMTP) SSL Security Test => Non compliant cipher suites : Example : TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA or TLS_DHE_RSA_WITH_CAMELLIA_128_CBC_SHA
I searched every place in data/config and Mailcow UI to find where I could change these parameters but I can’t find a way to disable these warnings on immuniweb analysis.
Does someone have some hints as to where I could change this ?
Greetings.