The Messaging Settings are settings that pertain to or affect the message flow in the NotifyLink Enterprise System.
|
|
Location: Select Server Administration, then click the Messaging Settings button |
|
|
|
Default Check Intervals
Email Check Interval is the frequency at which the NotifyLink Messaging Component queries your mail server for email. For example, if set to 5 minutes, each user’s mailbox on the Enterprise Server will be checked every 5 minutes for new email.
This interval should be set according to the number of users on the Enterprise Server. By default the number of mailbox threads is 5 and the gleaner interval is 3 seconds.
The following formula will help you determine the optimum setting for your system.
The Email Check Interval must be greater than or equal to:
(Number of Enterprise Server Users / Number of Mailbox Threads) x (Gleaner Interval in Minutes)
For example, if you have 100 users:
(100/5) x .05 = 1 minute Email Check Interval should be set to 1 minute or more.
You can change the values for the Number of Threads and the Gleaner Interval within the system registry.
1. Open the Registry by entering regedit in the Run prompt.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Notify Technology Corporation\NLES Gleaner Controller.
3. The names of the keys are: MaximumGleanerThreads and Interval.
PIM Poll Interval is the interval at which the NotifyLink Messaging Component initiates a new query for new, changed, or deleted calendar events, contacts, and tasks (PIM). It is essentially a minimum time, however, since actual PIM processing time can be affected by the number of users, volume of PIM data, and number of PIM processing threads available.
For example, if the interval is set to 5 minutes, begins at 3:00, and processes all users in 5 minutes or less, the next query will begin at 3:05. This is the best case scenario. If number of users or data volume causes the processing to go beyond 5 minutes, however, a new query will not begin until the next PIM processing thread becomes available.
Enable Multi-PIM Processing The default setting for PIM processing threads is one (1). To increase speed and maximize the efficiency of PIM processing, administrators can enable Multi-PIM Processing by increasing the number of MaxThreads in the registry’s NLES PIMService. This allows multiple PIM threads to run simultaneously.
1. Open the Registry by entering regedit in the Run prompt.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Notify Technology Corporation\NLES PIMService.
3. Open the MaxThreads option and change the number of threads to 3. This allows 3 PIM processing threads to run simultaneously.
4. Once you make this change you will need to restart the NLES PimService and NLES MonitorService in Windows Services.
Email Settings
Admin Email Address contains the email address of the server administrator (entered during the NotifyLink Messaging component installation). The address can be edited if necessary. The administrator will receive Emails regarding:
• System monitoring errors
• Warnings (for example, if the leasing service goes into a grace period)
• Notices of new installer or software updates (Hotfixes)
Admin SMTP Server – Select the SMTP Server that will handle system messages such as monitoring job reports, ‘Notify All’ messages, etc.)
Default SMTP Server – Select the SMTP Server that will be assigned by default to unclassified users. SMTP server may also be defined by class and by individual user.
Server Time Zone is the time zone of the server on which the NotifyLink Messaging Component resides. Change it to fit your server location.
Max ActiveSync Message Availability This setting affects all users synchronizing with the NotifyLink Enterprise Server via an ActiveSync account. An ActiveSync user has the capability of setting a message availability range on the device. The server setting places a limit on this device setting, thereby providing a way for an administrator to control the size of the NotifyLink Enterprise Server database.
The Max ActiveSync Message Availability is a default setting for unclassified users. A similar setting may be defined by user class, through Manage User Classes. The default setting is Sync All (180 Days), but may be changed to One Day, Three Days, One Week, Two Weeks, One Month. The administrator may also choose not to set a limit by selecting, Never Delete. In this case, the setting on the device will determine when messages get deleted from the device and the database.
When a Max ActiveSync Message Availability is set, behavior on the device will vary.
When the device setting is less than
this server setting.
Messages are deleted from
the device during the next folder synchronization
(see note below*) after the device
message availability date. Messages are deleted from the database
according to the Max ActiveSync Message Availability setting.
Example: Device
= One Week, Max ActiveSync Message Availability = Two Weeks
Messages are
deleted from the device at 7-14 days if the folder syncs prior to 14 days, which
is when the database delete occurs. If folder sync does not occur in this
time frame, the messages remain on the device.
When the device setting is equal to
this server setting.
Messages are deleted from the device during the next folder synchronization
(see note below*) after the device message
availability date. Messages are deleted from the database 7 days after the
Max ActiveSync Message Availability setting.
Example: Device = Two Weeks, Max ActiveSync Message Availability = Two Weeks
Messages are deleted from the device at 14-21 days if the folder syncs prior to 21 days, which is when the database delete occurs. If folder sync does not occur in this time frame, the messages remain on the device.
When the device setting is greater
than this server setting.
Messages are deleted from the
device during the next folder synchronization (see note below*), after the server message availability
date.
Messages are flagged for a delete from the database according to the Max ActiveSync Message Availability setting. The actual deletion from the database does not occur until 7 days after the Max ActiveSync Message Availability setting.
Example: Device = One Month, Max ActiveSync Message Availability = Two Weeks
Messages are deleted from the device at 14-21 days if the folder syncs prior to 21 days, which is when the database delete occurs. If folder sync does not occur in this time frame, the messages remain on the device.
*Note: There may be cases where mail folder does not synchronize and messages remain on the device until manually deleted. For example, an iOS device may not access the mail folder in which the message resides before the message is deleted from the database, therefore the folder does not synchronize and the automatic delete does not occur on the device. Users will have to manually delete such items from the device.
Changes to messages that remain on the device after they have been deleted from the database are not synchronized to the server. Changes such as, marking as read/unread, deleting, or moving to a different folder will only occur on the device. In addition, Quick Replies and Quick Forwards from the device will fail.
Related Topics:
• Maximum Message Availability for classified users can be set in User Administration > Manage User Classes > (select a class) > Edit Class > Maximum Message Availability.
• A similar setting for NotifyLink Device Client users can be configured in IT Policy Management > (select a policy) > Edit IT Policy > Control Options > Message Availability.
Internal Gateway Settings
Internal Server Address is the internal address of the machine where the Enterprise Server HTTP/Web Component is installed.
External Server Address is the external address of the machine where the Enterprise Server HTTP/Web Component is installed. The external server address must be accessible from the Internet.
You can test this by entering http://<Your External Server Address>/hwp/get.asp into a web browser located outside of your Intranet. (You might try this from a BlackBerry or Windows Mobile device’s browser.) The message “Error: Invalid Parameters” indicates that you have a connection.