|
Version 6.3 |
|
| ||||||||||||||||||||||
Configuring the AirSync ModuleThe AirSync protocol works over the HTTP protocol, using the HTTP User Module. Open the HTTP User Module settings, and find the Sub-Protocols panel: Use the AIRSYNC Log Level setting to specify the type of information the AirSync module should put in the Server Log.
The Access setting specifies who can access the AirSync service. Note: Many AirSync clients are designed to access only the standard HTTP ports (port 80 for clear-text connections and port 443 for secure connections), make sure your HTTP User module is properly configured to accept connections on these ports. Restricting AccessServer and Domain administrators may want to restrict AirSync access to to certain devices only:
Managing AirSync DevicesServer and Domain administrators can monitor and manage AirSync devices employed by the Account user.
Open the Account Settings WebAdmin Interface page, open the Mail section, and follow the Mobile link. Find the AirSync Devices panel:
The table elements show the device type and unique ID for each device the Account user has used, as well as the time of the last AirSync operation with that device. Devices can be protected with a PIN (password) that needs to be entered every time the device is switched on, or after a period of inactivity. You can remotely enable or disable this function: select the device element and click the Enable PIN-lock or Disable PIN-lock button. To remove all information from the device (if it has been lost or stolen), select the device element and click the Wipe Out button.
To cancel the Wipe Out operation (if the device has been recovered before it tried to access the Server), select the device element and click the Cancel button. Some devices may fail to deal with all user Mailboxes - either because the user Account has too many Mailboxes, or because some Mailbox has too many items in it. A user can "hide" certain Mailboxes from the AirSync client by disabling the Visible to Mobile Devices Mailbox option. Compatibility NotesThe AirSync protocol was designed to work in a proprietary, non-standard environment. CommuniGate Pro AirSync module makes its best effort to convert AirSync data to the standard formats (such as iCalendar and vCard). Replying to Event RequestsWhen an AirSync client accepts or declines an Event, it generates an E-mail message to be sent to the Event organizer.
This message contains Microsoft proprietary data not suitable for any standard-based application.
Sub-MailboxesAirSync clients do not support sub-mailboxes of the Sent and Trash Mailboxes,
and older clients do not support sub-mailboxes of the INBOX Mailbox either.
|