Login with @domain.com for 2nd MTA

[hodd]

So a little background. We added a second MTA with mailboxes for another location. We've been using AD authentication on our main server for 8 months now and users have only had to login using their username that's found in Zimbra and AD. One the secondary server that's been installed if you want to login to it, you have to use username@2nd.server.name.com.

Has anyone else had this problem with their "alternate" server?


Would it be that we have 2 domains? Maybe I configured the setup of the second server wrong?

[mmorse]

Would it be that we have 2 domains?

What your noticing is that the single domain specified in zimbraDefaultDomainName doesn't need to type @domain.com for login.

If you have two domains what you can do is set a virtual host so by visiting mail.domainB.com they'd just type the username part.

zmprov md domainB.com zimbraVirtualHostname mail.domainB.com

(Where mail.domainB.com points to 2nd.server.name.com when resolved via DNS both internally and externally.)



Also, the server uses zimbraPublicServiceHostname to generate REST URLs, ie: briefcase, document, calendar sharing etc.

Say it's generating URL's like http:// 2nd.server.name.com and you'd rather have it http:// mail.domainB.com:

zmprov md domainB.com zimbraPublicServiceHostname mail.domainB.com

In 5.0.9+ REST URL's can now be composed of 3 attributes: zimbraPublicService[Protocol + Hostname + Port] to avoid dependency on zimbraServer objects.

To minimize browser warnings on SSL connections, use either a different cert per mailstore, subjectAltNames, or wildcards: Administration Console and CLI Certificate Tools - Zimbra :: Wiki