Почтовый сервер zimbra на windows

Important Notice About Single Server Installations

Zimbra Collaboration is designed to be the only application suite installed
on the server. As part of the installation process, Zimbra Collaboration
bundles and installs various other third party and open source
software, including Eclipse Jetty,
Postfix, and OpenLDAP®. The
versions installed have been tested and configured to work with Zimbra
software. See the Zimbra Collaboration Administrator Guide for a complete
list of software.

A Zimbra license is required in order to create accounts on
servers running Zimbra Collaboration Network Edition.
You cannot install Zimbra Collaboration Network Edition without a license.

The following table shows the default port settings when Zimbra Collaboration is installed.

Zimbra Port Mapping

Important: You cannot have any other web server, database, LDAP,
or MTA server running, when you install Zimbra Collaboration. If you have
installed any of those applications before you install Zimbra
software, disable them. During Zimbra Collaboration installation,
Zimbra makes global system changes that may break
applications that are on your server.

System Requirements

For the Zimbra Collaboration system requirements see
System Requirements for Zimbra Collaboration at the end of
this guide.

Modifying Operating System Configurations

Zimbra Collaboration runs on one of several operating systems, including
Ubuntu® LTS, Red Hat® Enterprise Linux, and SUSE® Linux Enterprise.

A full default installation of the Linux distribution that you select is
required.

Configuring High-Fidelity Document Preview (Network Edition Only)

The high-fidelity document preview feature requires the installation of
LibreOffice or the LibreOffice-headless package, depending on the
operating system you are running.

If LibreOffice is installed, the system is automatically configured
to use high-fidelity document preview. If LibreOffice is not
installed, the preview engine from prior Zimbra Collaboration releases
is used.

This can be accomplished with the appropriate Linux distribution’s
package management systems:

yum install libreoffice
yum install libreoffice-headless

apt-get install libreoffice

apt-get install libreoffice-l10n-*
apt-get install ttf-vlgothic

apt-get install libreoffice-l10n-*
apt-get install fonts-vlgothic

yum install libreoffice-langpack-xx

DNS Configuration Requirement

When you create a domain during the installation process, Zimbra Collaboration checks
to see if you have an MX record correctly configured for that domain.
If it is not, an error is displayed suggesting that the domain name have
an MX record configured in DNS.

In order to send and receive email, the Zimbra MTA must be configured in
DNS with both A and MX records. For sending mail, the MTA uses DNS to
resolve hostnames and email-routing information. To receive mail, the MX
record must be configured correctly to route the message to the mail
server.

During the installation process, Zimbra Collaboration checks to see if
you have an MX record correctly configured. If it is not, an error is
displayed suggesting that the domain name have an MX record configured
in DNS.

You must configure a relay host if you do not enable DNS. After Zimbra Collaboration is installed, go to the administration console‘s
Global Settings>MTA tab and:

Zimbra Application Packages

Zimbra architecture includes open-source integrations using industry
standard protocols. The third-party software has been tested and
configured to work with the Zimbra software.

The following describes the Zimbra Collaboration application packages that are
installed.

The Zimbra server configuration is menu driven. The installation menu
shows you the default configuration values. The menu displays the
logical host name and email domain name [mailhost.example.com] as
configured on the computer. You can change any of the values. For single
server installs, you must define the administrator’s password, which you
use to log on to the administration console, and you specify the
location of the Zimbra license xml file.

• Accounts limit. The maximum number of accounts you can create and
  the number of accounts created are shown.

• Mobile accounts limit. The maximum number of accounts that can have
  the native mail mobile feature enabled.

• Touch Client accounts limit. The maximum number of accounts that
  can have the touch client mobile feature enabled.

• MAPI accounts limit. The maximum number of accounts that can use
  Zimbra Connector for Microsoft Outlook (ZCO).

• Exchange Web Services (EWS) accounts limit. The maximum number of
  accounts that can use EWS for connecting to an Exchange server.
  EWS is a separately licensed add-on feature.

• High-Fidelity Document Preview: The maximum number of accounts that
  can use the High-Fidelity document preview facility. LibreOffice must be
  installed.

• Archiving Accounts limit. The maximum number of archive accounts
  that can be created. The archive feature must be installed.

Zimbra License Requirements

A Zimbra license is required in order to create accounts in
the Network Edition of Zimbra Collaboration.

Several types of licenses are available:

License Usage by Zimbra Collaboration Account Type

A mailbox license is required for an account assigned to a person,
including accounts created for archiving. Distribution lists, aliases,
locations and resources do not count against the license.

Below is a description of types of Zimbra Collaboration accounts and if they
impact your license limit.

License Activation

All Network Edition installations require license activation. New
installations have a 10 day grace period from the license issue date
before requiring activation. Your license can be activated from the
administration console by selecting
Configure>Global Settings>License
then clicking Activate License in the toolbar. You can also
activate your license from the command line interface.

Automatic License Activation

Licenses are automatically activated if the Zimbra Collaboration server
has a connection to the Internet and can communicate with the Zimbra
License server. If you are unable to automatically activate your
license, see the next section on
Manual License Activation

Manual License Activation

For systems that do not have external access to the Zimbra License
server, you can use the Zimbra Support Portal to manually activate your
license. Go to the Zimbra website at https://www.zimbra.com and click on the
Support page to display the Zimbra Technical Support page. Click on the
Support Portal Login button to display the Zimbra Support Portal page.
Enter your email and password to log in.

If you have problems accessing the Support Portal, contact Zimbra Sales
at sales@zimbra.com or by calling 1-972-407-0688.

License Not Installed or Activated

If you fail to install or activate your Zimbra Collaboration server
license, the following scenarios describe how your Zimbra Collaboration
server will be impacted.

Obtaining a License

Go to Zimbra’s Website https://www.zimbra.com to obtain a trial license
from the Network Downloads area. Contact Zimbra sales regarding a trial
extended license, or to purchase a subscription license or perpetual
license, by emailing sales@zimbra.com or calling 1-972-407-0688.

The subscription and perpetual license can only be installed on the
Zimbra Collaboration system for which it is purchased. Only one Zimbra
license is required for your Zimbra Collaboration environment. This
license sets the number of accounts that can be created.

Current license information, including the number of accounts purchased,
the number of accounts used, and the expiration date, can be viewed from
the administration console’s Configure>Global Settings>License page.

The default configuration installs Zimbra-LDAP, Zimbra-MTA with
anti-virus and anti-spam protection, the Zimbra mailbox server, SNMP
monitoring tools (optional), Zimbra-spell (optional), the logger tool
(optional), and the Zimbra proxy on one server.

The menu driven installation displays the components and their existing
default values. You can modify the information during the installation
process. The table below describes the menu options.

• (Network Edition Only) Store your license in a directory folder on
  your server as it is needed to complete your installation of Zimbra Collaboration

• Confirm you have the latest system requirements and prerequisites for
  installing Zimbra Collaboration.

1. Log in as root to the Zimbra server and cd to the directory where
   the Zimbra Collaboration archive tar file is saved (cd /var/<tmp>). Type
   the following commands:

   • Unpack the file: tar xvzf [zcsfullfilename.tgz]

   • Change to the correct directory: cd [zcsfullfilename]

   • Begin the installation: ./install.sh

     root@mailhost:/tmp# tar xzvf zcs.tgz
     zcs-NETWORK-8.7.6_GA_1776.UBUNTU16_64.20170326144124/
     zcs-NETWORK-8.7.6_GA_1776.UBUNTU16_64.20170326144124/packages/
     .
     .
     .
     zcs-NETWORK-8.7.6_GA_1776.UBUNTU16_64.20170326144124/install.sh
     zcs-NETWORK-8.7.6_GA_1776.UBUNTU16_64.20170326144124/README.txt

2. The install.sh script reviews the installation software to verify that the
   Zimbra packages are available.
   The installation process checks to see whether any of the applications
   Sendmail, Postfix, MySQL or MariaDB are running.
   If any of these applications are running,
   you are asked to disable them. Disabling MySQL and MariaDB is optional
   but highly recommended.
   Sendmail and Postfix must be disabled for Zimbra Collaboration to start correctly.

   root@zimbraiop:/tmp/# cd zcs-NETWORK-8.7.6_GA_1776.UBUNTU16_64.20170326144124/
   root@zimbraiop:/tmp/zcs-NETWORK-8.7.6_GA_1776.UBUNTU16_64.20170326144124# ./install.sh
   
   Operations logged to /tmp/install.log.y1YeCSI5
   
   Checking for existing installation...
       zimbra-chat...NOT FOUND
       zimbra-drive...NOT FOUND
       zimbra-ldap...NOT FOUND
       zimbra-logger...NOT FOUND
       zimbra-mta...NOT FOUND
       zimbra-dnscache...NOT FOUND
       zimbra-snmp...NOT FOUND
       zimbra-store...NOT FOUND
       zimbra-apache...NOT FOUND
       zimbra-spell...NOT FOUND
       zimbra-convertd...NOT FOUND
       zimbra-memcached...NOT FOUND
       zimbra-proxy...NOT FOUND
       zimbra-archiving...NOT FOUND
       zimbra-core...NOT FOUND

3. The Zimbra software agreement displays. Read the agreement and when
   Do you agree with the terms of the software license agreement? [N]
   displays, enter Y to continue.
   Important: The license agreement displays in multiple sections,
   and you must accept each section of the license agreement.

4. Use Zimbra’s package repository [Y]
   displays, press enter to continue. Your system will be configured to add
   the Zimbra packaging repository for yum or apt-get as appropriate
   so it can install the Zimbra 3rd party packages.

   Checking for installable packages
   
   Found zimbra-core (local)
   Found zimbra-ldap (local)
   Found zimbra-logger (local)
   Found zimbra-mta (local)
   Found zimbra-dnscache (local)
   Found zimbra-snmp (local)
   Found zimbra-store (local)
   Found zimbra-apache (local)
   Found zimbra-spell (local)
   Found zimbra-convertd (local)
   Found zimbra-memcached (repo)
   Found zimbra-proxy (local)
   Found zimbra-archiving (local)
   Found zimbra-chat (repo)
   Found zimbra-drive (repo)
   
   
   Use Zimbra's package repository [Y] y
   
   Use internal development repo [N] n
   Configuring package repository
   
   Select the packages to install
   
   Install zimbra-ldap [Y] Y
   
   Install zimbra-logger [Y] N
   
   Install zimbra-mta [Y] N
   
   Install zimbra-dnscache [Y] N
   
   Install zimbra-snmp [Y] N
   
   Install zimbra-store [Y] N
   
   Install zimbra-apache [Y] N
   
   Install zimbra-spell [Y] N
   
   Install zimbra-convertd [Y] N
   
   Install zimbra-memcached [Y] N
   
   Install zimbra-proxy [Y] N
   
   Install zimbra-archiving [N] N
   
   Install zimbra-chat [Y] N
   
   Install zimbra-drive [Y] N
   
   .
   .
   
   Checking required space for zimbra-core
   Checking space for zimbra-store
   Checking required packages for zimbra-store
        MISSING: libreoffice
        MISSING: libreoffice-headless
   
   ###WARNING###
   
   One or more suggested packages for zimbra-store are missing.
   Some features may be disabled due to the missing package(s).
   
   
   Installing:
       zimbra-core
       zimbra-ldap
       zimbra-logger
       zimbra-memcached
       zimbra-mta
       zimbra-dnscache
       zimbra-snmp
       zimbra-store
      .
      .
   
   
   The system will be modified.  Continue? [N] y

   Also select the services to be installed on this server. To install
   Zimbra Collaboration on a single server, enter Y for the ldap, logger,
   mta, snmp, store, and spell packages. If you use IMAP/POP Proxy, enter
   Y for the Zimbra proxy package and the Zimbra Memcached package.

   Note: Ensure that the zimbra-memcached package is installed on at least one of the nodes in the system
   if the Proxy is installed.

   Note: For the cross mailbox search feature, install the Zimbra Archive
   package. To use the archiving and discovery feature, contact Zimbra
   sales.

   The installer verifies that there is enough room to install Zimbra.

5. Next, type Y and press Enter to modify the system.

   • Selected packages are installed on the server.

   • Checks to see if MX record is configured in DNS. The installer checks
     to see if the hostname is resolvable via DNS. If there is an error, the
     installer asks if you would like to change the hostname. We recommend
     that the domain name have an MX record configured in DNS.

   • Checks for port conflict.

6. At this point, the Main menu displays showing the default entries
   for the Zimbra components you are installing. To expand the menu to see
   the configuration values, type X and press Enter. The Main menu
   expands to display configuration details for the packages being
   installed. Values that require further configuration are marked with
   asterisks (******) to their left. To navigate the Main menu, select the
   menu item to change. You can modify any of the defaults. For a quick
   installation, accepting all the defaults, you only need to do the
   following:

7. To set the appropriate time zone, enter 1 to select Common Configuration and then enter 7 for TimeZone.
   Set the correct time zone.

   Main menu
   
      1) Common Configuration:
      2) zimbra-ldap:                             Enabled
      3) zimbra-logger:                           Enabled
      4) zimbra-mta:                              Enabled
      5) zimbra-dnscache:                         Enabled
      6) zimbra-snmp:                             Enabled
      7) zimbra-store:                            Enabled
           +Create Admin User:                    yes
           +Admin user to create:                 admin@zmail.example.com
   ******* +Admin Password                        UNSET
           +Anti-virus quarantine user:           virus-quarantine.ws91yggvp@zmail.example.com
           +Enable automated spam training:       yes
           +Spam training user:                   spam.seewcbk6@zmail.example.com
           +Non-spam(Ham) training user:          ham.h8qmkwft@zmail.example.com
           +SMTP host:                            zmail.example.com
           +Web server HTTP port:                 8080
           +Web server HTTPS port:                8443
           +Web server mode:                      https
           +IMAP server port:                     7143
           +IMAP server SSL port:                 7993
           +POP server port:                      7110
           +POP server SSL port:                  7995
           +Use spell check server:               yes
           +Spell server URL:                     http://zmail.example.com:7780/aspell.php
           +Enable version update checks:         TRUE
           +Enable version update notifications:  TRUE
           +Version update notification email:    admin@zmail.example.com
           +Version update source email:          admin@zmail.example.com
           +Install mailstore (service webapp):   yes
           +Install UI (zimbra,zimbraAdmin webapps): yes
   ******* +License filename:                     UNSET
   
      8) zimbra-spell:                            Enabled
      9) zimbra-convertd:                         Enabled
     10) zimbra-proxy:                            Enabled
     11) Default Class of Service Configuration:
     12) Enable default backup schedule:          yes
      s) Save config to file
      x) Expand menu
      q) Quit
   
   Address unconfigured (**) items  (? - help)

8. Type r to return to the Main menu.

9. Enter 5 to select zimbra-dnscache from the Main menu.

   • Select 1 to disable.

   • Select 2 to configure the master DNS IP address(es).

10. Type r to return to the Main menu.

11. Enter 7 to select zimbra-store from the Main menu. The store
    configuration menu displays.

12. Select the following from the store configuration menu:

    • Type 4 to set the Admin Password. The password must be six or more characters.
      Press Enter.

    • (Network Edition only) Type 33 for License filename and type the
      directory and file name for the Zimbra license.
      For example, if you saved to the /tmp directory, you
      would type /tmp/ZimbraLicense.xml. If you do not have the license, you
      cannot proceed. See the section on
      Zimbra License Requirements

    • Enable version update checks and Enable version update notifications.
      If these are set to TRUE. Zimbra Collaboration automatically checks for the
      latest Zimbra Collaboration software updates and notifies the account
      that is configured in Version update notification email. You can modify
      this later from the administration console.

13. Type r to return to the Main menu.

14. If you want to change the default Class of Service settings for new
    features that are listed here, type 11 for Default Class of Service
    Configuration.
    Then type the appropriate number for the feature to be enabled or disabled.
    Changes you make here are reflected in the default COS configuration.

15. If no other defaults need to be changed, type a to apply the
    configuration changes. Press Enter

    *** CONFIGURATION COMPLETE - press 'a' to apply
    Select from menu, or press 'a' to apply config (? - help) a

16. When Save Configuration data to file appears, type Yes and press Enter.

    Save configuration data to a file? [Yes]

17. The next request asks where to save the files. To accept the
    default, press Enter. To save the files to another directory, enter the
    directory and then press Enter

    Save config in file: [/opt/zimbra/config.16039]
    Saving config in /opt/zimbra/config.16039...done.

18. When The system will be modified - continue? appears, type Yes and
    press Enter.

    The server is modified. Installing all the components and configuring
    the server can take several minutes. Components that are installed
    include spam training and documents, (wiki) accounts, time zone
    preferences, backup schedules, licenses, as well as common Zimlets.

    The system will be modified - continue? [No] y
    Operations logged to /tmp/zmsetup.20160711-234517.log
    Setting local config values...done.
    Initializing core config...Setting up CA...done.
    Deploying CA to /opt/zimbra/conf/ca ...done.
    Creating SSL zimbra-store certificate...done.
    Creating new zimbra-ldap SSL certificate...done.
    Creating new zimbra-mta SSL certificate...done.
    Creating new zimbra-proxy SSL certificate...done.
    Installing mailboxd SSL certificates...done.
    Installing MTA SSL certificates...done.
    Installing LDAP SSL certificate...done.
    Installing Proxy SSL certificate...done.
    Initializing ldap...done.
    .
    .
    Checking current setting of zimbraReverseProxyAvailableLookupTargets
    Querying LDAP for other mailstores
    Searching LDAP for reverseProxyLookupTargets...done.
    Adding zmail.example.com to zimbraReverseProxyAvailableLookupTargets
    Setting convertd URL...done.
    .
    .
    Granting group zimbraDomainAdmins@zmail.example.com domain right +domainAdminConsoleRights on zmail.example.com...done.
    Granting group zimbraDomainAdmins@zmail.example.com global right +domainAdminZimletRights...done.
    Setting up global distribution list admin UI components..done.
    Granting group zimbraDLAdmins@zmail.example.com global right +adminConsoleDLRights...done.
    .
    .
    Setting default backup schedule...Done
    Looking for valid license to install...license installed.
    Starting servers...done.
    Installing common zimlets...
            com_zimbra_attachmail...done.
            com_zimbra_phone...done.
            com_zimbra_proxy_config...done.
              .
              .
            com_zimbra_ymemoticons...done.
            com_zimbra_date...done.
    Finished installing common zimlets.
    Installing network zimlets...
            com_zimbra_mobilesync...done.
             .
             .
            com_zimbra_license...done.
    Finished installing network zimlets.
    Restarting mailboxd...done.
    Creating galsync account for default domain...done.
    Setting up zimbra crontab...done.
    
    
    Moving /tmp/zmsetup.20160711-234517.log to /opt/zimbra/log
    
    
    Configuration complete - press return to exit

Access to the ‘zimbra’ user

Zimbra Collaboration ships a default zimbra user with a disabled
password.
Zimbra Collaboration requires access to this account via
ssh public key authentication.
On most operating systems this combination is okay, but if you have
modified pam rules to disallow any ssh access to disabled accounts
then you must define a password for the zimbra UNIX account.
This will allow ssh key authentication for checking remote
queues. See the Zimbra wiki article,
Mail Queue Monitoring.

Set up the ssh keys. To populate the ssh keys

sudo -u zimbra -i # if not already logged in as the zimbra user
zmupdateauthkeys

The key is updated on /opt/zimbra/.ssh/authorized_keys

Enabling Server Statistics Display. In order for the server statistics
to display on the administration console, the syslog configuration files
must be modified.

• zimbraAuthTokens

• zimbraCsrfTokenData

• zimbraLastLogonTimestamp

zmprov mcf zimbraAttachmentsScanURL clam://localhost:3310/
zmprov mcf zimbraAttachmentsScanEnabled TRUE

https://[mailhost.example.com]:7071

Activate the Zimbra Collaboration license (Network Edition Only)

Go to:

Home > Configure > Global Settings > License

click Activate License on the toolbar then Click OK to continue.

Provision accounts

You can configure one account at a time with the New Account Wizard or
you can create many accounts at once using the Account Migration Wizard.

Configuring One Account

To configure aliases, forwarding addresses, and specific features for
this account, proceed through the dialog before you click Finish.

When the accounts are provisioned, you can send and receive emails.

Importing Content from User Mailboxes

Zimbra developed different applications to facilitate moving a user’s
email messages, calendars, and contacts from their old email servers to
their accounts on the Zimbra server. When the user’s files are imported,
the folder hierarchy is maintained. Use one of the Zimbra Collaboration
utilities to move user mail to Zimbra Collaboration to guarantee that
all information is imported correctly.

The following applications can be accessed from the administration
console Download page, and instruction guides are available from the
Help Desk page or from the Zimbra Website, Documentation page.

Administrator Account

Initial administrative tasks when you log on for the first time may
include setting up the admin mailbox to include features, aliases, and
forwarding addresses needed for the administrator’s working environment.

Two aliases for the admin account are created during install:

If you entered a notification address for AV alerts when you configured
the MTA, that is different from the default, you need to create that
account in the administration console. If you didn’t change the default
during installation, the anti-virus notification is sent directly to the
admin account.

1. cd to the original install directory for the Zimbra Collaboration files.

2. Type sudo ./install.sh -u

3. When Completely remove existing installation? is displayed, type
   Yes.
   The Zimbra servers are stopped, the existing packages, webapp
   directories, and most of the contents of the /opt/zimbra directory
   are removed.

4. Type rm -rf [zcsfullfilename] to delete the Zimbra Collaboration directory.

5. Delete the zcs.tgz file.

Zimbra Connector for Outlook (Network Edition Only)

Zimbra Mobile (Network Edition Only)

Network Edition Mobile (MobileSync) provides mobile data access to email,
calendar, and contacts for users of selected mobile operating systems,
including:

Smartphone Operating Systems:

Zimbra Touch Client (Network Edition Only)

Supported devices for the Zimbra Touch Client include:

Zimbra Connector for BlackBerry Enterprise Server (Network Edition Only)

Zimbra Connector for BlackBerry Enterprise Server (ZCB) provides seamless,
real-time synchronization of Zimbra user mailbox data to BlackBerry devices.

Available Languages

This section includes information about available languages, including
End User Translations and
Administrator Translations.

Switching to Backup NG

Switching to the new Backup NG is a simple process that will initialize the
new backup system on a dedicated path.
Until the initialization is completed, the old backup engine will be active.
Old backup files will not be removed and the old backup and restore tools are
still available via the usual CLI commands.

Switching to Mobile NG

Switching to the new Mobile NG is a simple process that will activate the new
mobile handlers, deactivate the old ones and switch the synchronization control
over to Mobile NG from the legacy Zimbra Mobile.
Until the initialization is completed, the old mobile engine will be active.

Switching to HSM NG

The HSM NG module will become active as soon as the upgrade to Zimbra 8.8 is
completed, and does not require any interaction.

Any old HSM policy, volume and volume configuration will be maintained.

Switching to Admin NG

Switching to the new Admin NG module is a simple process that will migrate any
relevant ACL information to the module’s own configuration manager, clearing
existing ACLs and ACEs from the system.

The Admin NG module is significantly different than the old Delegated Administration engine.
Please make sure to read the product’s documentation and to only migrate to Admin NG if its feature set
meets your needs.

Critical Security Fix
This patch contains a critical security fix that affects previous Zimbra 8.8.15 «Joule» patches: Patch-26, Patch-25, Patch-24, Patch-23.
We strongly advise that our Partners and Customers immediately upgrade to the latest patch: Zimbra 8.8.15 Patch-27.
To keep your systems secure, Zimbra encourages our Partners and Customers to always keep current with patches.
Zimbra releases patch information directly to Partners and Customers via our regular newsletters, website, blog, and social posts, in addition to this wiki.Release Notes

Release Notes

3rd Party Open Source Licenses

Windows Open Source Licenses