Live Chat
773 598 5800
Search Results
  • Search Results

Table of Contents

3. Mail Server Architecture

3.1. Generic Server Configuration

3.1.1. Running Services

3.1.2. Other Generic Server Parameters

3.1.3. DNR Settings

3.2. Services and Modules

3.2.1. SMTP Receiving

3.2.2. Processing

3.2.3. SMTP Sending

3.2.4. POP3

3.2.5. IMAP

3.2.6. Logging

3.2.7. Reporting

3.2.7.1. Reporting Parameters

3.2.8. WebMail

3.2.9. Storage

3.2.10. FTP Backup Service

3.2.11. RPOP Service

3.3. Connectivity and Threading

3.3.1. Listeners

3.3.2. Rules

3.3.3. Threads

3.4. Clustering Support

3.4.1. Cluster Overview

3.4.1.1. LDAP Introduction

3.4.1.1.1. Basic Directory Setup

3.4.1.1.2. LDAP Entry Structure

3.4.1.1.3. LDAP Authentication

3.4.1.2. LDAP Synchronization

3.4.1.2.1. Minimum requirements

3.4.1.2.2. Feature Design & Data Flow

3.4.1.2.2.1. LDAP Integration Design

3.4.1.2.2.2. Active Directory Integration Design

3.4.1.2.2.3. Synchronization options

3.4.1.2.2.4. Categories of synced data

3.4.1.2.3. Integration Processes

3.4.1.2.3.1. Important Notices

3.4.1.2.3.2. Axigen LDAP Connector Configuration

3.4.1.2.3.3. Active Directory Integration

3.4.1.2.3.4. OpenLDAP Integration

3.4.1.3. AXIGEN Mapping System

3.4.1.4. AXIGEN Authentication System

3.4.1.5. AXIGEN Front-End Services Setup

3.4.1.5.1. The SMTP Proxy

3.4.1.5.2. The IMAP and POP3 Proxies

3.4.1.5.3. The WebMail Proxy

3.4.1.5.4. Mapping Setup

3.4.1.6. AXIGEN Back-End Services Setup

3.4.2. LDAP Routing

3.4.2.1. Configuring Mapping Parameters

3.4.2.2. POP3 Proxy Service

3.4.2.3. IMAP Proxy Service

3.4.2.4. Webmail Proxy Service

3.4.3. AXIGEN LDAP Authentication

3.4.4. Integrating Active Directory into a cluster environment

3.4.5. Exotic Cluster Setups

3.5. Groupware and collaboration

3.5.1. Personal Organizer & AXIGEN Outlook Connector

3.5.2. Folders and permissions

3.5.3. iCalendar Functionality

3.5.3.1. Minimum requirements

3.5.3.2. Feature Design

3.5.3.3. Axigen Configuration

3.6. ActiveSync

3.6.1. Minimum requirements

3.6.2. ActiveSync Configuration

3.6.2.1. ActiveSync Provisioning

3.6.2.2. ActiveSync Special Licensing Notes

3.6.2.1. ActiveSync Provisioning

The ActiveSync option is enabled on a per-account basis and can be inherited, as any other regular option is, from either the domain level or through the means of an Account Class object. Thus, the other inheritance state (explicitly set) is also supported and can be used if a limited number of accounts are set to use this feature. The number of accounts that have access to this feature is limited through the licensing information. The trial and office editions of the product do not offer this feature and, in this instance, it cannot be activated.

In order to enable the ActiveSync option at the account level, an administrative account, which has sufficient privileges to change this setting, must log into the web administration interface and access the “Quotas and Restrictions” page for that account. On this page, in the “Webmail Restrictions” section, the following options are available:


ActiveSync Options


The “Enable ActiveSync” check box activates the availability of this feature. The other sub-options specify which functionalities of the feature are accessible to the respective account.
  • Email. Specifies access to email pushing through the ActiveSync protocol. This functionality enables the handset to synchronize the local mailbox contents with the server-side mailbox and maintain their consistency.
  • Contact. Specifies access to the contact address book stored on the server and the possibility to synchronize the contacts stored on the handset with the ones stored on the server.
  • PIM. Specifies access to the contact calendar and task information stored on the server. Using this functionality, the user can update appointment and task completion levels (as well as create and delete objects) using the mobile device.