Quote:
Originally Posted by bjquinn  Well good, that's a first step. 
Anyone have a solution to the recipient authentication issue in this instance? Since Zimbra can authenticate with AD, can't Zimbra accept or deny a recipient address against AD, and then if it is accepted recognize that the account must exist (according to AD) but isn't local, and therefore redirect it to a specified mail host? |
Not sure what you want here so I will stay out of it. I plan to implement relay_recipients ( a check to see that there is a valid recipient in the exchange server) before I send the mail on to the Exchange server but as far as authentication goes that is all done in Exchange.
Quote:
Originally Posted by bjquinn dlochart - What were the Outlook connector and mobile sync problems? If you were only using Zimbra as an email gateway, why would you even be using the Outlook connector and mobile sync? Wouldn't you just leave that to Exchange, since Zimbra is only the gateway and doesn't even store any messages? |
We moved this client from Exchange into Zimbra. Bad Move. They were used to OutLook and Exchange. No one used the web interface (except to get around Calendaring issues). The Outlook connector has lots of issues. So much so they decided to go back to Exchange. We still want to use the Zimbra MTA as a gateway for this client only. Our other clients (web users) are very happy.
Microsoft products do not play well with non M$ products ... plain and simple.