Hi,

Thanks for the quick response. I've done what you suggested with the following results:

>A
>simple way to do this would be to just throw away all funny
>regexp locations you wrote in your config, and start with a simple

>location / {
>proxy_pass http://backend;
>}

Absolutely happy to.

Now I'm seeing slightly different behaviour. No more 405 errors, the Outlook client just hangs now, eventually reporting 'Server not Available'

In the debug log, I'm now seeing the following:

2013/02/28 13:56:55 [info] 3150#0: *1 client prematurely closed connection, client: 10.110.2.15, server: , request: "RPC_IN_DATA /rpc/rpcproxy.dll?EX-SERVER-2008.servers.null.org:6002 HTTP/1.1", host: "webmail.null.com"
2013/02/28 13:56:55 [info] 3150#0: *2 client prematurely closed connection, so upstream connection is closed too (104: Connection reset by peer) while reading upstream, client: 10.110.2.15, server: , request: "RPC_OUT_DATA /rpc/rpcproxy.dll?EX-SERVER-2008.servers.null.org:6002 HTTP/1.1", upstream: "http://10.1.1.2:80/rpc/rpcproxy.dll?EX-MBX-2008.servers.aeltc.org:6002", host: "webmail.null.com"

Which is me eventually cancelling the Outlook connection. This is evident from tailing the debug log - Nothing during the connection; but these events which the connection attempt is cancelled.

So...

Good news, Error 405 doesn't seem to be the cause of my issues, it would appear that my location directives were wrong in some way.

Bad news, Outlook Anywhere still isn't working.

If anyone has any other suggestions, please let me know.

Thanks,

Graham.