Mail Input Servers

Two major enhancements have been made to the Mail Input Servers in this release:

·     The ability to receive EMail through the Vendor Independent Messaging (VIM) API

·     Monitoring multiple Email addresses from a single Input Server

There is no safe mechanism for processing incoming email without deleting it from the mail system, so Delete Source Data? is disabled for all Mail Input Servers. Communication logging (Log Comm?) is available, however, and the check interval must be specified (Check Interval (secs)).

The following image shows the Mail Settings frame that is displayed for Mail Input Servers:

When checked, the new field Use Sender’s To Info? directs the Input Server to use the Email address that is being monitored for Sent-To routing lookup rather than the address in the received message. This field is not checked by default because it would break the Sent-To routing setup for current customers. However, it is recommended that this be changed if a site is experiencing problems with incoming Email not being routed correctly due to invalid information in the received messaged. When this field is set, the Input Server will build the user name using the FaxAction configuration information rather than using what the user sent. This constructed Email address is stored with the document (it can be seen in the View | Info Window while editing the document in the FaxAction Client) and is used to determine whether Sent-To Routing applies to the document. The Email address is constructed differently for each of the Sub Types as follows:

VIM Mail Servers

Lotus Notes is the primary Email system that uses the VIM API. FaxAction supports Lotus Notes Email systems, but the support programs for this support are installed separately from the standard FaxAction installation.

When configuring Notes users for use in FaxAction, each user must be specified as a separate login. No aliases should be used as the mechanism for processing them requires the Notes application to run, which can cause problems if the Notes application presents dialogs or the failover software is in use.

Please contact Competent Technologies, Inc. for additional information.

Monitoring Multiple Email Addresses

Prior to this release, a separate Input Server had to be created for each Email address that was to be monitored. This was a very inefficient use of server resources and could be quite cumbersome for sites to configure. Now, a single Input Server can monitor any number of Email systems (of the same Sub Type) and addresses.

The Email addresses that are to be monitored are displayed in the list that appears in the parameters frame above. At least one item must be entered in the list before the Input Server record can be filed.

Items in the list can be added, changed, or deleted by pressing the Manage button. When the button is pressed, the list of directories for the current Input Server is displayed in a new window and items in the list can be created, changed, and deleted using the standard list buttons described in the FaxAction Admin Manual.

The following form is displayed for when a record in the list of Email addresses is opened:

Host Name contains the name of the host that is to be monitored. This field is only enabled for POP mail systems due to the way that MAPI and VIM sources are monitored.

User Name specifies the name of the user that the Input Server uses to connect to the mail system. For MAPI mail systems, the name of the Mail Profile (defined in Microsoft’s Mail Control Panel applet) is stored in this field.

Password stores the password for the mail system user. The password for MAPI systems is generally saved in the Mail Profile and thus does not need to be entered in this field.

When an Input Server monitors more than one Email address, it disconnects from and reconnects to the mail system for each address. This mechanism is slightly slower than reusing the same connection, but is the only that multiple addresses can be monitored for Microsoft Mail and Lotus Notes mail systems.