Quote:
Originally Posted by gaspode  Okay, if it replies with a 403 the problem lies in Zimbra not proxying then and not on our servers.
Can you run a zmprov gc default and a zmprov gc <whichever COS your user is in> and check that send.arunalabs.com and storage.arunalabs.com is in the zimbraProxyAllowedDomains? |
They were listed for the default COS, but not for the one my test user is in. I updated user's COS via zmprov and still no-go. Do I need to restart Tomcat for this change to be picked-up? Shouldn't zimbraProxyAllowedDomains be updated when zimlet is enabled for a COS?
I've recently upgraded this customer to ZCS 4.5.10. It's one of our managed hosting customers.
Artur