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.5.3.2. Feature Design

The use of built in support for ICS/iCalendar is only available for a selected number of clients because the HTTP based protocol is by no means standardized throughout the industry. In this sense any other client except the ones mentioned in the “Requirements” page, are not supported.

iCalendar is a computer file format which allows users to send meeting requests and tasks and appointments to other users, via email, or sharing files with an ICS extension. Recipients of the iCalendar data file can respond to the sender easily or counter-propose another meeting date/time. The iCalendar data is usually sent by traditional email and shared using the HTTP protocol.

For this feature to work, the Axigen Webmail HTTP Service includes an extension to provide ICS/IFB-based access to users' calendars and tasks. Thus, by using a specific URL, an external client can retrieve and save calendar information stored normally by Axigen. Additionally, free/busy information is available at a different URL with similar properties.

Once the support for iCalendar is enabled by the administrator, the users can access their task and calendar information by configuring a couple of standard HTTP addresses within the client and then authenticating with their respective credentials (same as for the email account). The complete list of addresses can be found below:

Note: These are the address endings only. The first section of the webmail link will be identical to the one used for Webmail access. So if the base address for the webmail is “http://webmail.company.com”, the final ICS connection link will be “http://webmail.company.com/ical/main.ics”.

  • Standard – “/ical/main.ics”. This address will allow individual users to access their own account information (tasks and calendar).
  • Custom Folder – “/ical/folder/<path_to_folder>.ics”. This address changes according to the folder name created for tasks or calendar content management. This should only be used if you have created additional calendars in addition to the default.
  • Shared Calendars – “/ical/~<username>/main.ics”. By using this type of address ending, the user can access other users’ calendar and task related information (Warning: To be able to accomplish this task, the user accessing the address must have full read and write access to the calendar itself).
  • Shared Calendar in custom folder – “/ical/~<username>/folder/<path_to_folder>.ics”. An example combination of the two previous situations.
  • Public Folders – “/ical/pf/<path_to_folder>.ics”. Using this type of address one can see calendar and task information stored in a public folder
    Note: The “pf” particle is always the same, regardless of the public folder root configured in Axigen
  • Free/Busy – “/ical/~<username>/freebusy.ifb”. This address allows access to the Free/Busy status.

Warning: The free/busy status address also includes the user’s credentials so it can be a potential security breach. Unfortunately this cannot be avoided due to the technology design. This information is stored on the client computer for that account and is not dependant upon the Outlook profile being used.