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.2. ActiveSync Special Licensing Notes

The ActiveSync features are activated individually per-account, but also the setting can be enabled globally on an entire domain. As a consequence, situations in which the number of allowed accounts is different from the number of ActiveSync accounts can be encountered.

If more than the allowed number of users inherits the ActiveSync option, the conflict is solved by allowing the connection to the use of the feature on a first users’ basis, up to the maximum limit allowed by the license, and explicitly disabling the option for all of the other accounts that try to connect afterwards.

Here is a practical example in which the ActiveSync option is inherited from the domain level and the account number is greater than the ActiveSync license limitation. If you have 500 accounts in the respective account and only 200 ActiveSync mailboxes, the following will apply:
  • Any accounts in the domain will be able to use ActiveSync.
  • Once 200 unique accounts have connected at least once the account list is retained by Axigen.
  • The 200 unique users will continue to have access to the ActiveSync feature unless otherwise specified by an administrator.
  • The 300 accounts that did not login before the ActiveSync capping will have their ActiveSync option disabled and the inheritance method set to “explicitly defined”.
  • To change (enable) the ActiveSync option for another user account you will have to disable one of the already active ones from before.