Outside users (users travelling) should be able to access their email
through NGINX and it should redirect the connection to my Internal Exchange
server for authentication and access:
2. Outlook Anyway
My environment info:
Client email access through External Proxy server is mail.example.com, IP
External DNS A record for mail.example.com point to IP 184.108.40.206
Internal Exchange server is EX-01.example.com with internal IP 10.10.10.11
Internal DNS A record for mail.example.com point to 10.10.10.11
So, if you noticed, all the outside user's email client will look for
mail.example.com with external IP 220.127.116.11.
From outside my office, i used my laptop to test.
On Mon, Oct 08, 2018 at 11:58:38PM -0400, alisampras wrote:
I have not tried putting anything to do with Exchange behind nginx, so I do not
have any tested-config for you.
> Business Objective
> Outside users (users travelling) should be able to access their email
> through NGINX and it should redirect the connection to my Internal Exchange
> server for authentication and access:
> 1. OWA
> 2. Outlook Anyway
> 3. ActiveSync
When I do a Google search for "nginx owa", among the first few results I get are
The general impression I get from reading those is that, for this to work,
it depends significantly on the versions of Exchange and friends, and
on the configuration of Exchange and friends.
Generally: RPC is bad; NTLM authentication is bad; many other things
It does appear that there are some versions and configurations of Exchange
and friends that stock-nginx will not successfully reverse-proxy; if you
must use some of those, then you may be much happier using a different
product to do the reverse-proxying.
Both "haproxy" and "nginx plus" appear to have some reports of being
made to work.