Of course, inclusion of settings in the GUI is something that will need to be done (I have some thoughts on that, but for later.) We should also roll up some of the INI only settings that seem to be fairly stable as well. After reception is known to be working sending should be implemented. Off the cuff calculation of usage at the work front shows about 90% of the non-spam traffic is STARTTLS enabled. Rolaids0 wrote:I'll compile it up to run with STARTTLS on 25 to test. Interesting solutions & similar to how we suggest people use ASSP in front of hmailserver as it can essentially do the same thing but giving STARTTLS support & passing the traffic on to hmail.
Thomas89 wrote:Since a lot of people seem to need this overrated feature and it's popping up on google on top, I want to share the solution for this problem: nginx
#DEFAULT PORT FOR SURGEMAIL INSTALL#
One word of warning: while nginx works on windows it's very strict when it comes to the config => Highly recommend to install in a directory like C:\nignx and avoid any spaces -and pay special attention to \ / The Mail-Module is afaik not a finished product so far, but it can already do a lot of nice stuff, such as load-balancing.įor further information please refer to: and scroll to the bottom for the mail-config. This requires significantly less resources and NGINX in front of hmailserver can probably tweaked to additionally increase security (for example by specifying Ciphers, TLS/SSL-Versions.). net I would rather suggest to officially support NGINX as proxy in front of hmailserver and probably maintain a "default-config" on the hmailservers wiki. I've not set this up myself yet since I don't require StartTLS as it doesn't provide real security.Īnyway, instead of putting a lot of resources into developing StartTLS into hmailserver due to limitations in.
0 kommentar(er)
