Hi Rainer, Thank you for this quick answer. So my idea to declare a server for port 25 and an other for ports 465 and 587 is probably good. You pitch about Haraka lead me to investigate about it. Maybe it will solve my need to route emails as I need to do.by dethegeek - Nginx Mailing List - English
Hi Still building a nginx reverse proxy for my mail servers. Thanks to the community, I now have a secure connection between nginx and my backend mail server. POP and IMAP are working well, from a MUA to my server. I'm wondering how nginx can manage SMTP coonnections as it is used by both MUA and MTA. A MUA must authenticate before sending mails; and my http_auth backend is able to auby dethegeek - Nginx Mailing List - English
Hi As I understood the example given in the documentation, it is for a TLS session between a client and nginx. This is the next step in my roadmap. Right now, I'm focusing on the secure connection between nginx and the backend servers. It still would be interesting to implement whad I need directly in nginx; As I understand how nginx works with pop3 / imap / smtp protocols I guess this woby dethegeek - Nginx Mailing List - English
Hi Steve, thank you for your reply. I already read the page you mentionned, and as I understand it, either this feature is missing, either it is not documented. Andrew said TLS is not implemented, so I'll follow his advice to properly workaround this limitation.by dethegeek - Nginx Mailing List - English
Hi Thank you Andrew, You confirmed what I'm afraid of. I hope this feature will be implemented soon.by dethegeek - Nginx Mailing List - English
Hi I'm setting up nginx as a reverse proxy for a postfix / dovecot setup. My imap server requires STARTTLS usage. Nginx seems to not issue STARTTLS command before forwarding users credentials. Here is the error I found in /var/log/nginx/error.log 928#0: *20 upstream sent invalid response: "* BAD Plaintext authentication not allowed without SSL/TLS, but your client did it anywayby dethegeek - Nginx Mailing List - English