Zimbra Collaboration Administrator Guide

Add to My manuals
402 Pages

advertisement

Zimbra Collaboration Administrator Guide | Manualzz

Zimbra LDAP Service

Flushing LDAP Cache

When you modify the following type of entries in the Zimbra LDAP server, you might need to flush the LDAP cache to make the change available on the server.

Themes

Locales

Account

Groups

COS

Domains

Global configuration

Server

Zimlet configuration

Flush the Cache for Themes and Locales

When you add or change theme (skin) property files and locale resource files for ZCS on a server, you must flush the cache to make the new content available.

CLI:

To flush skins: zmprov flushCache skin

CLI:

To flush locales: zmprov flushCache locale

Flush Accounts, Groups, COS, Domains, and Servers

When you modify the account, COS, groups, domain, and server attributes, the change is effective immediately on the server to which the modification is done. On the other servers, the LDAP entries are automatically updated after a period of time if the attributes are cached.

The default ZCS setting to update the server is 15 minutes. The caching period is configured on local config key.

CLI:

To change the setting: zmlocalconfig ldap_cache_<object>_maxage

CLI:

To enable changes immediately: zmprov flushCache [account|cos|domain|group|server] [name|id]

If you do not specify a name or ID along with the type, all entries in cache for that type are flushed and the cache is reloaded.

Zimbra Collaboration Network Edition 51

Administrator Guide

Note: Some server attributes require a server restart even after the cache is flushed. For example, settings like bind port or number of processing threads.

Flush Global Attributes

When you modify global config attributes, the changes are effective immediately on the server to which the modification is done. On other mailbox servers, you must flush the cache to make the changes available or restart the server. LDAP entries for global config attributes do not expire.

Some global config attributes are computed into internal representations only once per server restart. For efficiency reasons, changes to those attributes are not effective until after a server restart, even after the cache is flushed. Also, some global configuration settings and server settings that are inherited from global config are only read once at server startup, for example port or number of processing threads. Modifying these types of attributes requires a server restart.

CLI:

To flush the cache for global config changes on all servers:

1.

Modify the setting on the local server zmprov mcf zimbraImapClearTextLoginEnabled TRUE

The change is only effective on the server

zimbra_zmprov_default_soap_server, port zimbra_admin-service_port

.

2.

Flush the global config cache on all other servers,

zmprov flushCache

must be issued on all servers, one at a time. For example: zmprov –s server-2 flushcache config zmprov –s server-3 flushcache config

3.

To determine if the action requires a restart zmprov desc -a <attributename>

.

The requiresRestart value is added to the output if a restart is required.

52 Network Edition Zimbra Collaboration

6 Zimbra Mail Transfer Agent

The Zimbra MTA (Mail Transfer Agent) receives mail via SMTP and routes each message using Local Mail Transfer Protocol (LMTP) to the appropriate

Zimbra mailbox server.

Note: You can set MTA parameters with the Admin Console and the CLI.

However, it is highly recommended that you use the CLI for MTA configuration to ensure the best results.

Topics in this chapter:

Zimbra MTA Deployment , next.

SMTP Authentication, on page 55

.

Anti-Virus and Anti-Spam Protection, on page 56

.

Receiving and Sending Mail, on page 70 .

The Zimbra MTA server includes the following programs:

MTA Server Programs Purpose/Description

Postfix MTA

Clam AntiVirus

Mail routing, mail relay, and attachment blocking

Scanning email messages and attachments in email messages for viruses

Spam Assassin

Amavisd-New

Identify unsolicited commercial email (spam)

Interface between Postfix and ClamAV / SpamAssassin

Zimbra Milter Server Enforce restrictions on which addresses can send to distribution lists and adds Reply-To and X-Zimbra-DL headers to messages sent from distribution lists

Zimbra policy server Aid in protecting Alias Domains from Backscatter Spam

Cluebringer Policy daemon/cbpolicyd used to enforce actions, such as rate limiting.

For more information, see https://wiki.zimbra.com/wiki/Postfix_Policyd

Opendkim Sign outgoing email if it has been configured to do so.

For more information, see https://wiki.zimbra.com/wiki/Configuring_for_DKIM_Signing

Zimbra Collaboration Network Edition 53

advertisement

advertisement

Table of contents