One domain is identified during the installation process and additional domains can be easily added to the Zimbra system from the administration console.
A domain can be renamed and all account, distribution list, alias and resource addresses are changed to the new domain name. The CLI utility is used to changing the domain name. See
Renaming a Domain.
|
•
|
Active. Active is the normal status for domains. Accounts can be created and mail can be delivered. Note: If an account has a different status setting than the domain setting, the account status overrides the domain status.
|
|
•
|
Closed. When a domain status is marked as closed, Login for accounts on the domain is disabled and messages are bounced. The closed status overrides an individual account’s status setting.
|
|
•
|
Locked. When a domain status is marked as locked, users cannot log in to check their email, but email is still delivered to the accounts. If an account’s status setting is marked as maintenance or closed, the account’s status overrides the domain status setting.
|
|
•
|
Maintenance. When the domain status is marked as maintenance, users cannot log in and their email is queued at the MTA. If an account’ status setting is marked as closed, the account’s status overrides the domain status setting.
|
|
•
|
Suspended. When the domain status is marked as suspended, users cannot log in, their email is queued at the MTA, and accounts and distribution lists cannot be created, deleted, or modified. If an account’s status setting is marked as closed, the account’s status overrides the domain status setting.
|
You can configure each domain with the public service host name to be used for REST URLs. This is the URL that is used when sharing Documents Notebooks, email folders and Briefcase folders, as well as sharing task lists, address books, and calendars.
When users share a ZCS folder, the default is to create the URL with the Zimbra server hostname and the Zimbra service host name. This is displayed as
http://server.domain.com/service/home/username/sharedfolder. The attributes are generated as follows:
When you configure a public service host name, this name is used instead of the server/service name, as
http://publicservicename.domain.com/home/username/sharedfolder. The attributes to be used are:
|
•
|
Internal. The Zimbra LDAP server is used for directory lookups.
|
|
•
|
External. External directory servers are used for GAL lookups. You can configure multiple external LDAP hosts for GAL. All other directory services use the Zimbra LDAP service (configuration, mail routing, etc.). When you configure the external GAL mode, you can configure GAL search and GAL sync separately.
|
|
•
|
Both. Internal and external directory servers are used for GAL lookups.
|
When you configure and internal or external GAL, you create a GAL sync account with an address book where the LDAP contact data can be syncd. Syncing the LDAP to this account gives users faster access to the GAL data and makes it easier for them to search the GAL.
If Both is selected, a GAL sync account with an address book is created for each LDAP data source. These accounts display in the administration console’s Accounts list.
You enter the GAL datasource for each account. When a datasource is configured on an account, the GAL configuration on the domain is overridden.
The internal GAL polling interval for the GAL sync determines how often the GALsync account syncs with the LDAP server. The sync intervals can be in x days, hours, minutes, or seconds.
When the GAL sync account syncs to the LDAP, all GAL contacts from the LDAP are added to the GAL address book. During the sync, the GAL sync account is updated with new contact, modified contact and deleted contact information. You should not modify the GAL sync account address book directly. When the LDAP syncs the GAL to the account, changes you make to the address book are deleted.
See Appendix A Command-Line Utilities, the CLI
zmgsautil for information about the GALsync CLI command.
When you configure an external GAL, you can configure different search settings and sync settings. You may want to configure different search settings if your LDAP environment is set up to optimize LDAP searching by setting up an LDAP cache server, but users also will need to be able to sync to the GAL.
Authentication is the process of identifying a user or a server to the directory server and granting access to legitimate users based on user name and password information provided when users log in. Zimbra Collaboration Suite offers the following three authentication mechanisms:
|
•
|
Internal. The Internal authentication uses the Zimbra directory server for authentication on the domain. When you select Internal, no other configuration is required.
|
|
•
|
External LDAP. The user name and password is the authentication information supplied in the bind operation to the directory server. You must configure the LDAP URL, LDAP filter, and to use DN password to bind to the external server.
|
|
•
|
External Active Directory. The user name and password is the authentication information supplied to the Active Directory server. You identify the Active Directory domain name and URL.
|
Virtual hosting allows you to host more than one domain name on a server. The general domain configuration does not change. When you create a virtual host, this becomes the default domain for a user login. Zimbra Web Client users can log in without having to specify the domain name as part of their user name.
Virtual hosts are entered on the Domains>Virtual Hosts tab on the administrator’s console. The virtual host requires a valid DNS configuration with an A record. Not required for Virtual Hosts.
When the Zimbra login screen displays, users enter only their user name and password. The authentication request searches for a domain with that virtual host name. When the virtual host is found, the authentication is completed against that domain.
Zimbra Documents is a document sharing and collaboration application. Users can create, organize, and share web documents. Images, spreadsheets, and other rich web content objects can be embedded into Documents via the AJAX Linking and Embedding (ALE) specification.
The Documents application consists of a global Documents account that includes the Document templates and the global notebook, one optional Documents account per domain, and individual accounts’ Documents notebooks. The global Documents account is automatically created when ZCS is installed. The domain Documents account is not automatically created.
One Documents account can be created per domain. You can easily add the account from the administration console when you create a domain. When you create the account, you configure who can access this Documents account and what access rights these users can have.
Except for Public, which is view-only, you can select the access privileges these users can have: view, edit, remove, and add pages to the Documents notebook. You can view and change these access permissions from the administration console.
The Zimbra Free/Busy Module to connect with Microsoft Exchange pulls the free/busy schedule of users on Exchange and also pushes the free/busy schedule of ZCS users to the Exchange server. You complete the Interop tab for the domain to enable this feature for the domain. For more information see
Zimbra Free/Busy Interoperability.
Zimbra Collaboration Suite includes pre configured Zimlets, see Working with Zimlets. These Zimlets are enabled in the default COS. Additional Zimlets can be added and enabled by COS or by account. All Zimlets that are deployed are displayed in the
Domain>Zimlets tab. If you do not want all the deployed Zimlets made available for users on the domain, select from the list the Zimlets that are available for the domain. This overrides the Zimlet settings in the COS or for an account.
When you rename a domain you are actually creating a new domain, moving all accounts to the new domain and deleting the old domain. All account, alias, distribution list, and resource addresses are changed to the new domain name. The LDAP is updated to reflect the changes.
Copyright © 2009 Zimbra Inc.
