AMOS Mail Administrator's Guide - Nautilus One · Contents of this administrator's guide shall not be duplicated, used, or disclosed – in whole or in part – for any purpose other

AMOS Mail

Administrator's Guide

Version 5.0

Edition Note

The document is prepared for the version 5.0 of AMOS Mail.

Acknowledgements

Contents of this administrator's guide shall not be duplicated, used, or disclosed – in whole or in part – for any purpose other than the legitimate development of AMOS Mail™ documentation and shall not be disclosed to persons outside the establishment. Information subject to this restriction is contained on all pages of this guide.

All terms referenced in this guide that are known to be trademarks or service marks are so indicated upon first iteration and are appropriately capitalised throughout this guide. SpecTec Group cannot attest to the accuracy of all such information. Use of a term should not be regarded as affecting the validity of any trademark or service mark.

Microsoft and Windows are registered trademarks of Microsoft Corporation.

AMOS Mail is a trademark of SpecTec Group.

Page iv of 100 Administration Guide v.3.3

Foreword

This guide has been written for advanced users, as well as consultants and other professionals who are configuring and administrating the AMOS Mail program. The objective of this guide is to provide the technical information needed to perform these tasks.

Since many of the configuration features described in this guide affect the way a system function or module operates, it assumed that the reader is familiar with the AMOS Mail program. A good knowledge of automatic data processing and general familiarity with the Windows® operating environment are also assumed.

The aim of this manual is to cover all relevant technical issues of the program. However, it does not include topic oriented user instructions, which is to be found in the User's Guide. The remaining documentation for AMOS Mail is to be found in the following manuals:

• AMOS Mail Installation Guide

• AMOS Mail User's Guide

Please note that this manual is not meant to be read from cover to cover, but rather to serve as a reference manual over the topics listed above.

Page v of 100 Administration Guide v.3.3

Contents

Introduction.........................................................................................1 Product Description................................................................................................... 1 Hardware and Software Requirements................................................................... 1 Related Documents.................................................................................................... 2

Connecting to Post Offices.............................................................3 Connecting to Post Offices....................................................................................... 3

Mailbox Management........................................................................5 Mailbox Management ............................................................................................... 5 General settings.......................................................................................................... 5 Capabilities ................................................................................................................. 7 List Memberships ...................................................................................................... 8

Workgroup Management.................................................................9 Workgroup Management.......................................................................................... 9 Workgroup Properties ............................................................................................. 11

Defining and Connecting to Remote Post Offices..................15 Remote Post Offices ................................................................................................ 15 Gateway on this Post office.................................................................................... 18 Host connected via Modem.................................................................................... 19 Host connected via TCP/IP.................................................................................... 23 Rerouted Host or Gateway ..................................................................................... 24 Host connected via Internet Tunneling ................................................................ 26 Host connected via file exchange (AMF) ............................................................ 27

In the Office .............................................................................................. 27 Onboard the ship...................................................................................... 28

Schedule Maintenance...................................................................31 Schedule Maintenance............................................................................................ 31

Distribution Rules............................................................................32 Distribution Rules .................................................................................................... 32

Least Cost Routing .........................................................................35

Least Cost Routing .................................................................................................. 35

Fax Headers ......................................................................................37

Fax Headers .............................................................................................................. 37 Sending Fax via other Post offices........................................................................ 38

Page vi of 100 Administration Guide v.3.3

Distribution and Printing of Messages...................................... 39

Message Distribution...............................................................................................39 Distribution elements...............................................................................................39 Distribute Outgoing Mail ........................................................................................39 Distribute Incoming Mail ........................................................................................40 Printing of messages ................................................................................................40 Examples of Distribution ........................................................................................41

Time and Time Zones..................................................................... 47 Time and Time Zones..............................................................................................47

The use of Aliases in AMOS Mail ................................................ 48

Aliases ........................................................................................................................48 Internet Aliases .........................................................................................................48

Application Interface ...................................................................... 50

Application Interface ...............................................................................................50 Starting the API Server............................................................................................50 Addressing Applications.........................................................................................50 Defining Applications..............................................................................................51 Specifying API Options...........................................................................................53

The AMOS Mail Utility Programs ................................................ 54

The AMutlDir Program...........................................................................................54 To Run the AMutlDir Program..............................................................54 Configuration of AMutlDir.....................................................................55 Specifying the Directories to scan.........................................................56

Interface with AMOS-D..........................................................................................57 AMOS-D Export and Import ..................................................................57 Sending Faxes from AMOS-D and other DOS applications ............57 Sending Faxes from AMOS4W and other Windows applications...57

Using Mail from Applications ...................................................... 58

Using Mail from Applications................................................................................58 MAPI Interface .........................................................................................................58

Sending E-Mail with the MAPISendMail function............................58 Enabling AMOS Mail Simple MAPI ....................................................59

Using 3rd party E-Mail clients ................................................................................59 Configure and start the SMTP and POP3 servers on the AMOS Mail server...........................................................................................................59 Example: Install and Configure Internet Mail .....................................61

DDE Command Interface........................................................................................63 Using the AMOS Mail Fax Printer........................................................................63 Sending Mail from MS-DOS..................................................................................64 Sending Fax Images from MS-DOS .....................................................................65 Using the MAPITIF.DLL interface.......................................................................65

Database Administration .............................................................. 68

Introduction...............................................................................................................68 Database Integrity Checker.....................................................................................68 Database Reorganization.........................................................................................69 Local Post office Check and Repair ......................................................................70 Post office Backup ...................................................................................................71

Directory Management .................................................................. 72

Page vii of 100 Administration Guide v.3.3

Directory Management ........................................................................................... 72 Directory Templates ................................................................................................ 72

Template Details ...................................................................................... 72 Directory Export and Import .................................................................................. 73

Pointed Brackets ...................................................................................... 74 Automatic Directory Synchronization ................................................................. 76

Telex Monitor ....................................................................................77 The Telex Monitor................................................................................................... 77

Accounting Module .........................................................................78

The Accounting Module......................................................................................... 78 Program Settings...................................................................................................... 78 Import of Billing Transactions.............................................................................. 79 Cost Table ................................................................................................................. 81

Cost Table Buttons.................................................................................. 81 The Cost Detail Window........................................................................ 82

Reports....................................................................................................................... 83

A4W Interface to AMOS Mail.........................................................86 The A4W interface .................................................................................................. 86 Pre Installation Requirements................................................................................ 86 Procedure................................................................................................................... 87 Configure A4W for Export .................................................................................... 88 Configure A4W for import ..................................................................................... 88 Configure AMOS Mail for Import ........................................................................ 89 Sample SENDALL.BAT........................................................................................ 90 Troubleshooting....................................................................................................... 92

Page 1 of 100 Administration Guide v.3.3

Introduction

Product Description AMOS Mail is a mail software package for the Microsoft Windows family of operating systems. The package supports both local (in-house mail) and external mail through gateways or direct links to external PTT carriers such as fax and telex.

Exchange of local mail is based on a common database (Post office) shared among a number of Mailboxes. The package will run on any networking environment that support shared files. The software may be run in a client-server configuration in a Microsoft Windows-NT environment.

AMOS Mail can also be installed on a standalone PC acting as a single Mailbox remote Post office.

Post offices may be interconnected using either dial up lines, X.25 lines, ISDN lines, Cellular Phones, Satellite links or local-area networks.

Mail can also be exchanged with a wide range of third party mail packages through gateways.

Hardware and Software Requirements The following is a list of the minimum configuration required to run AMOS Mail on a Personal Computer.

• Industry standard PC

• Color monitor

• Windows-95, Windows-98, Windows NT 4.0 or Windows 2000

• A mouse or other compatible pointing device

• A 3½-inch (1.44 megabyte) floppy disk or access to a CD-ROM for installation

The AMOS Mail modem gateway require the following additional components:

• A supported modem

• A buffered serial I/O port (16650 UART) is highly recommended for high-speed (above 9600 baud) modem communication.

The optional AMOS Mail Client/Server configuration requires a Windows-NT Workstation or Server.


Related Documents This document describes the administrative functions of AMOS Mail. The following additional documents are available:

• AMOS Mail Installation Guide

• AMOS Mail User's Guide


Connecting to Post Offices

Connecting to Post Offices Even though you usually only connect to one Post office, you have the option to connect to several Post offices in AMOS Mail. From the Sign in window in AMOS Mail you can select different Post offices from the drop down box.


You can define new connections by using the Property button (to the right of the drop down box).

You can create shortcuts to the different Post Offices by adding the Post Office code to the command line

Winms s32 –p Postoffice


Mailbox Management

Mailbox Management Each person requiring access to the AMOS Mail system must have a personal Mailbox. The Mailbox defines the users local access capabilities and preferences. Mailboxes are created through menu item “Setup – Mailbox Management”.

Some mailbox settings can only be altered by an administrator. These settings are described in the following sections.

Other settings can be altered both by the administrator and by the user, through menu item “Setup – User Preferences”. Please see the AMOS Mail User’s guide for a description on these.

General settings

The General, Capabilities and List Membership tabs are only available to the Post office Manager and should be filled in for each new user added. The other tabs are accessible to the respective user from the menu item “Setup – User Preferences”.


Mailbox ID The Mailbox identification used when signing on to AMOS Mail. The Mailbox ID must be unique within a Post office.

Mailbox Password The password used to gain access to the Mailbox. This password can be changed using the «Change Password» command on the AMOS Mail Setup menu. If the selected password is equal to the Mailbox ID, you will not be prompted for password.

Mailbox Name Full name of the Mailbox. This will be used by AMOS Mail when creating the from line for outgoing mail. The from line is created using the Post office name followed by a dash followed by this entry.

From Line AMOS Mail will assemble the from line for outgoing mail using the Post office name followed by the Mailbox name if this entry is left blank. If this is inadequate any text written here will override the default from line.

Workgroup The selected Workgroup will by default be associated with new messages and used for accounting and access control purposes. This selection can be changed when creating a new message.

Internet Address This address will be set as your preferred reply address when sending messages to the Internet. If the entry is empty, a default reply address will be assigned by the Internet gateway.

Default aging after Specify the maximum number of days a user can keep messages in his folders. Messages older than indicated by this entry will be deleted by the automatic aging utility. This setting applies to folders that do not have an entry for aging. If left empty, the system default will apply.

Max message size Maximum size of messages this mailbox is allowed to send over gateways where per user size limits are enforced. See also “Defining and Connecting to Remote Post Offices”.


Capabilities Tick adequate options to authorize access to selected features of the AMOS Mail system. At all times you must ensure that a minimum of one Mailbox has full access rights to all features. These options are not available in the AMOS Mail single user version.

Post office Management The Post office Manager can define new Mailboxes and modify the Local Post office variables.

Workgroup Management The Workgroup Manager can define and manage Workgroups.

Rule Management Use this option to grant selective access to menu item “Distribution Rules”.

Gateway Management The Gateway Manager can define and configure the external gateways and servers available in the system.

Gateway Operations With this capability a user can initiate remote connections such as dialing a remote post office.

Message Management When disabled there is no access to any messages. The disabled setting can be combined with Gateway Operations to create a profile suitable for a server user.

Forward Management This option controls whether a user is allowed access to the automatic copy and forward utilities through menu item “User Preferences”.

Mail Distribution Mail Distribution is used to tell the system that a user has the function of distributing mail. When this user forwards messages to other users, the From address will not be changed.


Empty Waste Basket Check this option if the user’s WasteBasket may be emptied during automatic aging of old messages.

Hide from directory lists Use these options to selectively suppress some users from all or specifically the Global directory list. If you don't want this mailbox to appear in a directory list (take it away from the address list), check one of these options. It is particularly useful when working with automatic directory replication.

Note:

At least one of mailbox must have Post office Manager capabilities. Otherwise it is not possible to maintain the Post office.

For this reason, a Post Office manager is not able to remove this capability from his/her own mailbox.

List Memberships This tab shows the distribution lists the mailbox is member of.

Press the Modify button to update add or remove the mailbox from a distribution list.


Workgroup Management

Workgroup Management The concept of Workgroups may be used to create collections of folders and directory entries. Members of a Workgroup have common access to these folders and directory entries. Workgroup members can thus share message archives. Workgroups may also be created to represent collections of Mailboxes (e.g. a business department). All Mailboxes are by default member of Workgroup Everyone. There is no limit to the number of Workgroups that can be created or the number of members (Mailboxes, folders and directory entries) they may contain. A single Mailbox client may be a member of any number of Workgroups. Workgroups are particularly useful in a configuration where a Post office has a large number of folders, directory entries or Mailboxes. When using AMOS Mail single user, the following screen is used for Workgroup Management:

Visibility of folders and address directories is controlled through Workgroup membership. Any Mailbox may read any message within a folder or directory entry belonging to a Workgroup for which he is a member. The right to create and delete a folder or directory entry for a particular Workgroup is controlled by Member Rights. If you are using the AMOS Mail Server, the following dialog is used for Workgroup Management:


The buttons New, Delete and Update are used to create, remove and update Workgroups respectively. Members are managed by using the Add and Del buttons. The following rights may be associated with each Workgroup member and applies to the currently displayed group only:

Folder Manager

The right to manage (create, update and delete) folders belonging to the currently selected Workgroup. Other Workgroup members may still view the contents of and create messages in folders belonging to this particular Workgroup. A Folder Manager may in addition to above, delete or move any message. Other members may only delete or move messages put there by themselves.

Directory Manager

The right to manage (create, update and delete) directory entries belonging to the currently selected Workgroup. Other Workgroup members may still view and use directory entries belonging to this particular Workgroup.


Workgroup Properties The following dialog is used to enter general properties associated with workgroups.

Name Descriptive name of the Workgroup

Account Account code for this Workgroup. This option is used by the Accounting Module to split communication cost. An account code is associated with each message when it is created.

Views This option can suppress the display of this Workgroup in the Folder, Directory, Account or Member Lists.

If you want to create a Workgroup but don’t want to share address lists within this Workgroup, you can just suppress the listing of this Workgroup in the Directory List.

Class The Class code (if entered) used by this Workgroup. This Class code must correspond to the Class code given to the Fax and Telex gateways. This code may be used to reserve modem or telex devices to a limited number of users.

Deny members access

Use these options to deny access to selected gateways for members of a Workgroup.


If you use the AMOS Mail system to send faxes, enter the information related to fax headers, footers and fax-ID (your fax number) in this Window.

Sender ID

The phone number which will be supplied as originator (reply to number) when sending fax messages. The telephone number supplied when answering calls is set when you define the fax gateway.

Header The fax header displayed at the top of the page. Different headers for the first page and the other pages are supported.

Footer The fax footer displayed at the bottom of the page. Different footers for the first page and the other pages are supported.


If you use the GSM text option on your system, enter the sender ID in this Window.

Sender ID

The telephone number that will be displayed on the receivers GSM phone as the senders phone number.


Sender ID

When using this field, the answerback programmed into the telex device will be suppressed (not used) for outbound messages and the entered text will be displayed as is on the first line of outgoing messages.

This may be used if sender wants to specify a different return address (e.g. a hosted service). For most installations, this entry is typically left blank.

By double clicking on a Mailbox in the Member List or in the Mailbox List you may display a list of Workgroups for which that particular Mailbox client belongs as follows:

Press Continue to return to the Workgroup Management dialog.


Defining and Connecting to Remote Post Offices

Remote Post Offices Your Post office may be interconnected with remote Post offices using dial-up lines, the TCP/IP protocol, via Internet or file interchange. For each external Post office you exchange messages with, directly or routed via other Post offices, should have a Remote Post office entry. This is accomplished by selecting the “Remote PO Management” dialog from the AMOS Mail Setup menu.

The definition of Remote Post offices serves three purposes. First of all it is to define how a Post office can be reached (which gateway shall be used). The second purpose is to define distribution and printing of messages. The last purpose is to associate a Remote Post office with a workgroup for access control to selected gateways and use of custom fax headers.

Note:

All external Post offices that you communicate with should be defined as a Remote Post office via the Gateway you are using, or if it is reached via another Post office it should be defined as a Router. This will allow you to define all directory entries as ID@PO.

The “Remote Post Office Management” dialog (below) is used to create entries for local or remote gateways and remote post offices.

The following items must be filled in:

PO ID An alphanumeric identification code. Use this ID when addressing the remote Post office or Gateway with an «@» prefix followed by the ID (e.g. «BF@AM»).

PO Name A free format descriptive text naming the entry.


The “Miscellaneous” tab is used to enter common information for all entry types.


Association Use the Workgroup selection to associate incoming messages from the Post office or Gateway defined by this entry.

Size restriction The maximum size of a message that will be accepted by this entry. If messages exceed the indicated max size, it will be rejected with a notification to the sender. When set to zero, no restriction applies.

Enforce per user size limit

When this option is checked, only messages smaller than the sender’s mailbox max message size is accepted for delivery over this gateway.

Note:

When a max messages size is set both on the gateway and the sender’s mailbox, and the “Enforce per user size limit” option in checked, then the smallest of the two values applies.

The “Distribution” tab is used to define extra distribution of messages passing through the gateway.

Association Use the Workgroup selection to associate incoming messages from the Post office or Gateway defined by this


entry.

Send a copy of outgoing mail to

Specify the address you want outgoing messages distributed to. To activate the distribution, check either of the “Enable for…” options. Local messages apply to messages sent from the local Post office. Relayed messages apply to messages sent from another site (e.g. ship).

Send a copy of incoming mail to

Specify the address you want incoming messages distributed to. To activate the distribution, check the “Enable for all messages” option.

In the following chapters, specific details with respect to the various entry types will be explained.

Gateway on this Post office This entry type refers to a gateway that is directly connected to your local AMOS Mail server. The main reason for using this entry type is to add the distribution and printing options or override the use of “Default Routing” as configured under Local PO Management. AMOS Mail will recognize the following gateways as direct by default:

FAX Gateway to Fax

TLX Gateway to Telex

SMT Gateway to Internet e-mail

TXT Gateway to GSM text messages

MHS Gateway to Novell Message Handling Services (MHS)

CTX Gateway to GN-Comtext


Host connected via Modem All Post offices connected via modems should be defined using this option. This relates to Post offices that we dial (other branch offices), but also Post offices that only dial us (vessels and laptop PCs).

Host Password The password supplied to the remote host when making outgoing connections and the password checked against the incoming host’s supplied password. This is the common password agreed upon between the two parties wishing to exchange mail

Primary Select the default phone number to use for auto-dial connections. See also chapter on «Remote Services» for more information on Phone Book Management and automatic mail delivery.

Alt 1, Alt 2 and Alt 3 These phone numbers will be used as alternatives if connection fails. These entries may be used in combination with the next option to keep track of ships switching satellite as the move between different ocean regions.

Use as primary If one of the alternative numbers is used for successful connection, this number will move to the top of the list.

Enable transparent Internet relay

Use this option if the remote host is used as a relay server connected to a third party mail system based on the Internet SMTP protocol

Locked out When this option is checked, the remote Post Office is not allowed to dial in. It is still possible to dial the remote PO, however.


The following dialog is used to control scheduling of outgoing or polled connections:

Connect immediately when a message is queued

Use this option for automatic and immediate delivery of outgoing mail.

Connect according to schedule if a message is queued

This option may be used as an alternative to above to have more control of when and how frequent outgoing connections will be made.

Connect according to schedule always

This option may be used to instruct the gateway to schedule an outgoing connection even if there are no messages queued for delivery. The purpose of this would be to poll for messages.

Connect immediately for high priority messages

This option may be used to in combination with scheduled delivery to ensure that high priority messages are delivered immediately.

Schedule Use this entry to select a schedule to use for auto dial. More information on this topic can be found in the chapter “Schedule Maintenance”.

Interval The minimum number of minutes that should elapse between two sessions of mail exchange. This entry may be used as an extra precaution to avoid unnecessary frequent connections when using immediate delivery.

The following dialog may be used to specify that notifications shall be given to a system operator in case there are delivery problems or to notify a remote user that new messages are waiting for download.


A new message is queued for delivery

A notification will be sent whenever a new message is queued for delivery. The message will include a list of messages with headers and the total number of new, sent and failed messages in its subject. The address button is used to select the address to which the notification shall be sent (e.g. to GSM Text). A notification will be sent only if scheduling is set to manual or if there is a problem with delivering messages automatically.

A negative notification is queued for delivery

Use this to trigger a notification when a non delivery report is queued.

A positive notification is queued for delivery

Use this to trigger a notification when a positive delivery report is queued.

Only send notification once

Notifications will be sent each time a message according to above is queued for delivery unless this option is checked. Notifications will be reenabled after a successful download.

Send alert messages to SysOp

The gateway’s will monitor critical events and alert a system operator when abnormalities are detected by means of an e-mail. You can select to uncheck this option if such notification messages are undesired. The message will be posted in the InBox of the user running the gateway (e.g. the NT office server).

Send alert if mail not connected after

Causes a notification if a remote Post Office (e.g. a ship) has not dialed in to collect queued messages after the specified number of hours.


The following dialog is used to configure directory synchronization between local host and remote sites. Each site you wish to send to or receive directory updates from mu st be configured through this option.

Send Updates on Everyone

Any changes to the local Everyone directory will be sent to the remote host.

Accept inbound updates to Everyone

Incoming updates to the Everyone directory will be accepted from the remote host.

Send updates on Global Any changes to the local Global directory will be sent to the remote host.

Accept inbound updates to Global

Incoming updates to the Global directory will be accepted from the remote host.

Manually Outgoing directory updates will have to scheduled to this host manually through the “Remote – Send Directory Subscriptions” menu item.

Automatically Outgoing directory updates will be generated and scheduled for immediate delivery to this host.

When a subscription for outbound updates is activated the first time, a full copy of the respective directory will be generated and posted for delivery. Succeeding updates will only include modifications since the previous posting.

If for some reason the directories are believed to be out of sync, you should first disable outbound subscriptions and then re-enable to trigger a full update.


Host connected via TCP/IP The following is a definition of a Post office connected via TCP/IP:

The following items can be entered:

Host password The password supplied to the remote host when making outgoing connections and the password checked against the incoming host’s supplied password. This is the common password agreed upon between the two parties wishing to exchange mail

Host (name or IP number)

Type the symbolic Internet name or IP number (dot notation) of the host you wish to exchange mail with.

Port number This is the TCP/IP port number used when connecting to the remote host. The selected port must mach the port that the remote host listens on.



Enable logging Check this option to generate connection log entries for TCP/IP connections to this PO.

Read the section on “Host connected via Modem” for details on how to configure the Scheduling, Notification and Directory options .


Rerouted Host or Gateway A definition of a Router may be used to simplify addressing and ease the job of moving gateway services between different computers. If you would like to route all outgoing Fax messages through another Post office, this may be accomplished as follows:

The following “Route” states that all outgoing messages to “…@FAX” will be rerouted to “…@FAX@AM”. The AM host may again do additional routing or deliver messages using a local fax gateway.


It is also valid to specify an empty route. In this case the routed element (PO ID of the routing entry) will be discarded from the address.

Read the section on “Host connected via Modem” for information on how to configure the Directory option.


Host connected via Internet Tunneling To install the tunneled mail option, you will need complete the following steps:

If you don’t have a network connection (leased line or a router) to Internet, install dial-up networking on your NT server.

Test your connection to Internet to verify that it works.

Configure AMOS Mail to poll your Internet POP3 account.

Change the definition of Remote PO from type “Host connected via Modem” to “Host connected via Internet Tunneling”. In the "Address" item you must enter the Internet address of the Remote PO.

AMOS Mail allows sending of tunneled mail via Internet. Outgoing messages will be compressed and encrypted before it is sent via the Internet. On the receiving side, the steps will be reversed and the messages will be distributed.

The following items must be configured:

Address The Internet address to the mailbox where tunneled e-mail shall be collected.

Use 7-bit AMF format Use this option when sending messages to Inmarsat Standard-C terminals. This requires that the ship use AMOS Mail onboard.





Host connected via file exchange (AMF) If you want to use the Inmarsat Standard-C gateway in AMOS Mail, this will be limited to Inmarsat providers supporting an Internet to SAT-C interface. The advantage of the SAT-C interface is that you can use the same software onboard all your ships regardless of type of satellite terminal. Full delivery notification will be supported and all features such as sending messages to the Application Interface can be used onboard.

In the Office You have to define a Remote Post office for the ship you want to communicate with. The Post office for the ship must be defined as gateway type “Host connected via Internet Tunneling”. In addition, you have to specify that it shall use the AMF format option. The messages sent to the SAT-C ship will automatically be converted to an Internet message with an attachment of type ‘AMF’. The Internet message will then be sent to the specified address. The Inmarsat provider will forward this message to the ship where it will be decoded and distributed.

In the same way, messages sent from the ship will be received in the office like messages from any office using tunneled mail. The message received will include an attachment of type ‘AMF’. This file will automatically be decoded by AMOS Mail and distributed.

Above is a sample configuration when using an imaginary Internet to Inmarsat-C service. In order to use Internet to Inmarsat-C services, you will need a subscription with a provider.



Onboard the ship The messages received onboard can either be imported manually (from a diskette or from a directory) or automatically. This will depend on the brand of satellite terminal and the software supplied with it. For some terminals, the incoming files can be sent to a directory where AMOS Mail can scan for new messages. All messages will then be imported into AMOS Mail (also regular messages) and the ‘AMF’ files received from the office will be converted to AMOS Mail messages and distributed accordingly.

The following dialog selected from the “Remote – Other Services” menu may be used onboard the ship to configure AMOS Mail to automatically import incoming Inmarsat-C messages:

Check in directory Scan this directory for messages.

Move to directory Move all files to this directory after they have been imported to AMOS Mail.

Auto import Check this option if you want AMOS Mail to check the import directory and import the files automatically.

Delete import Check this option if the files in the import directory shall be deleted after the import in AMOS Mail.

Address The address where you want to send all non-addressed mail.


In addition you must define the office as a Remote Post office onboard. The office must be type “Host connected via File Exchange (AMF).

Details for this definition may be specified as follows for an imaginary Internet to SAT-C provider. Specific details with respect to addressing conventions must be obtained from the service provider.

When you want to export the messages from the ship, this has to be done manually. Select the AMF Export option on the Remote menu.


You will then be prompted for the name of the export file. This file can be located in the send directory for the SAT-C terminal or on a diskette if you have to transfer the file via diskette to the Inmarsat-C terminal.


Schedule Maintenance

Schedule Maintenance Schedules are used in the AMOS Mail system by the Internet / POP3 client gateway, by the aging facility and to schedule connections with remote post offices through the modem gateway. The following dialog is used to define a schedule. The schedule can be composed of several schedule lines.

Days Specify the weekdays when the process shall be activated. Several values can be specified separated by commas, or an interval by '-'.

Hours Specify the hours when you want the process to be activated

Minutes Specify the minutes when you want the process to be activated

The schedule above tells that the process should be activated each half-hour (15 and 45 minutes after each hour) for all the weekdays between 8 and 17. For the rest of the day and night the process will be activated each hour (30 minutes after each hour). In the weekends, the process will be activated 30 minutes after 7, 15 and 18.


Distribution Rules

Distribution Rules Distribution rules can be used to automate the internal distribution and archiving of messages. Messages can be sent to a public rule set as to any other address in AMOS Mail. The Alias assigned to the Rule set is the address that shall be used.

The main purpose of public rules is to enable you to search the incoming message for specific text strings. If a match is found, the message may then be rerouted or copied to a specific address. Public rules can also be used to control distribution of outgoing messages. One exa mple might be to print copies of outgoing messages to a specific printer based on who sent the message. An unlimited number of rules can be created for a single rule set.

The following is the dialog used to create and manage the individual rules making up the rule set.


Limit match to delimited string

If you check this option, the search will be limited to strings enclosed by delimiters (e.g. blank space or new line).

If no rules apply (Copy-To)

If no rules apply, the message will be copied to the specified address. This address can be any valid AMOS Mail address (including new Rule sets).


The following is the dialog use to create or change an individual rule.

To The destination address (both name and address part) will be searched for a matching string.

From The sender’s address (both name and address part) will be searched for a matching string.

Subject The Subject field will be searched for a matching string.

Text The body part of the messages will be searched for a matching string.

Workgroup The Workgroup associated with the message will be compared to this selection.

Less than Only messages with a size less than the specified limit will result in a match.

Larger than Only messages with a size larger than the specified limit will result in a match.

Copy-To If the rule applies (a match is found), the message will be copied to the specified address. This address can be any valid AMOS Mail address (including new rule sets). Please note that all criteria entered for a single rule must match (logical AND). If you want multiple criteria to work in a logical OR fashion, you must create multiple rules with a single criteria in each rule.


Least Cost Routing

Least Cost Routing The concept of least cost routing is implemented to reduce your total communication cost. A telex or fax message can be routed either to another location or to another provider based on the number to dial.

The following is the dialog used to create or change an individual route.

In this case, all faxes for UK (+44) will be routed via the AMOS Mail server at the SpecTec office in the UK.


In this case, all faxes for UK will be sent via the Provider named ‘Telia’ instead of your regular telephone provider.


Fax Headers

Fax Headers Graphical Fax header and footer files may be used to create an attractive first page for outgoing fax messages. The header may include your company logo, mail address, phone number etc. as in the following example:

The “header” in above example is all information visible on the screen. The top line, from- and address-sections however will be supplied by AMOS Mail and included regardless of the presence of a fax header. To create and use a fax header, you must complete the following steps:

Create your fax header using a Windows application (e.g. Microsoft Word, AMI-PRO, WordPerfect, Write, Paintbrush etc.).

Print the newly created document using the «AMOS Mail Fax Printer» (remember to start AMOS Mail prior to selecting Print). The document will then be converted to a Fax image and transferred to AMOS Mail.

Position your mouse pointer on the topmost left corner of the section of the document you want to use as fax header. Then press the left mouse-button while moving your mouse, until the dotted rectangle includes the section you want to use as part of your fax header.

Release your mouse and select the «Save Fax Header» command from the AMOS Mail Edit menu.

Type a filename and press the «OK» button to save the fax header to disk.


Use the «Workgroup Maintenance»option on the AMOS Mail Setup menu to enter the name of the newly created fax header. Once the filename has been entered, the fax header will be included on the first page of all outgoing fax messages for that Workgroup.

Sending Fax via other Post offices Sometimes you may like to send faxe s via another office. This is often the case for a ship. You will then also like o use a dedicated fax header for this ship. In this case you must to do the following:

• Define a Workgroup for the ship.

• Create fax headers for this Workgroup.

• Change the associated Workgroup for the ship under Remote PO Management.


Distribution and Printing of Messages

Message Distribution Internal distribution and archiving of messages is a powerful feature of the AMOS Mail system. There are several possible distribution and printing options available. Both outgoing and incoming messages can be printed and archived automatically.

Distribution elements

E-Mail address or Mailbox

At the user level, distribution lists can be added for all outgoing messages. This option can be limited to external mail only and is configured through menu items “User Preferences” and/or “Mailbox Management”.

Folder

A folder can be assigned an Alias that can be used as a valid site address. Copy of messages can then be saved in specified folders.

Distribution Rules

A rule set can be assigned an Alias that can be used as a valid site address. This option can automate archiving based on keywords, workgroup, sender or receiver.

Printer

A printer can be given an address code and addressed in the same way as a Mailbox.

Distribute Outgoing Mail Automated distribution and filing of outgoing messages can be specified under Remote PO Management. This can be specified for all the defined Remote PO’s, - dial-up, TCP/IP, direct etc. In addition to this option it is also possible to add distribution to the user mailbox for outgoing messages. The user can also add address entries manually for distribution and archiving purposes when sending message.

Forward (User Preferences)

At the user level, distribution lists can be added for all outgoing messages. This option can be limited to external mail only.

Gateway or Server At the Gateway or Server (remote site) level, distribution of all outgoing messages can be specified.


Distribute Incoming Mail Distribution of incoming messages has to be specified on the Gateway property screen, like on the telex and Modem properties. In addition distribution or copying of messages can be added to the user mailbox.

Forward (User Preferences)

At the user level, distribution lists can be added for all incoming messages. This option can be limited to external mail only.

Gateway

At the Gateway level (e.g. the Fax gateway) distribution of all incoming messages can be specified.

Printing of messages Both incoming and outgoing messages can be printed. You can decide if the message shall be printed immediately, or if the message shall be printed when the message are confirmed delivered at the recipients. Options are available for a single printout for the message, or separate copies for all recipients.

A printer address is defined as:

Full printer name [/D] [/M]@PRN

E.g. ”HP DeskJet 870C/D@PRN”

Printer Options:

/D Deferred printing. The message will be printed when all statuses have changed to confirmed for all recipients.

/M

This option will print one copy for each recipient as the status is changed to confirmed.

When these options are used, the local addresses, printer addresses and Bcc addresses will not be taken into consideration when printing the ‘Deferred’ print or when making printouts for each address line.


Examples of Distribution We will here give a sample of how to print and distribute incoming and outgoing faxes. We will first look at the distribution of incoming faxes.

We assume the following rules for the distribution and printing of incoming faxes:

• Faxes shall be printed when they arrive

• They should be archived in a Folder named Incoming Faxes (which will be split by month)

• All incoming faxes shall be copied to the persons John and Paul

We first create the folder for incoming faxes:

We give the folder the name ‘Incoming Faxes’ and place it in a Workgroup where all the users we want will have access to it (e.g. Everyone). We have to give the folder an Alias, in this case FAXIF (FAX Incoming Folder).

The sub mask option is enabled to automate the archiving of faxes by month.

Then the following addresses have to be created:


It can be a good idea to place all addresses used for internal distribution in a separate address list (Workgroup). So what we have done in this sample is to create a Workgroup named ‘Distribution’ where all these addresses are placed.

The Folder address to the folder with the name ‘Incoming Faxes’ and the Address ‘FAXIF’ has to be created.

Then the printer address with the name ‘Printer Incoming’ has to be created (address could possibly be “HP LaserJet 4L@PRN”).

In addition the addresses to the persons that shall receive a copy of the faxes also have to be created if not already defined.

Now that all the addresses and the folder are created, we will create the distribution list to be used for distribution of faxes. This group address will be given an alias, and we will send all the incoming faxes to this group.

This distribution list will include the folder, the printer and the persons. (See “Creating Distribution Lists” in the AMOS Mail User’s Guide).

The distribution list is given the alias – FAXIG (FAX Incoming Group).

The last step will be to configure the Fax modem so that all incoming faxes are copied to the group ‘Distribution of Incoming Faxes’. This is done on the ‘Remote menu’, where you select the ‘Modem Properties’ option. On the Fax tab you can enter the information about where incoming faxes can be sent.


Use the Address button on the Fax label and select the group address ‘Distribution of Incoming Faxes’ that we defined with the Alias FAXIG.

If you have more than one modem supporting incoming faxes, the same distribution information has to be given for all modems.

The system is now configured for automated distribution of all the incoming faxes.

Then we will look at the distribution of outgoing faxes, which shall have the same type of automated distribution.

We assumes the following rules for the distribution and printing of outgoing faxes:

• Faxes shall be printed when the recipient confirms the arrival.

• They should be archived in a Folder named Outgoing Faxes (which will be split by month)

• All outgoing faxes shall be copied to the persons John and Paul

Then again we will first create the folder. We will give the folder the name ‘Outgoing Faxes’ and will place it in a Workgroup where all the users we want will have access to it (like Everyone).


We have to give the folder an Alias, in this case FAXOF (FAX Outgoing Folder). The sub mask option is enabled to automate the archiving of faxes by month The Sent View option shall also be checked, since this is a folder for outgoing messages.

The next step is then to create the addresses.

The Folder address to the folder with the name ‘Outgoing Faxes’ and the Address ‘FAXOF’ must be created.

Then again we will have to create a printer address for the outgoing printing with the name ‘Printer Outgoing’ (address could possibly be “HP LaserJet 4L/D@PRN”). The new printer address is created even tough it may refer to the same physical printer as the incoming printer since we add the ‘/D’ (Deferred) option.

The addresses for John and Paul are already created in our sample.

Now all the addresses and the folder are created, we will create the group address to be used for distribution of the outgoing faxes. This group address will be given an alias, and we will send all the incoming faxes to this group.


This group address will include the folder, the printer and the persons. The distribution list is assigned the alias – FAXOG (FAX Outgoing Group).

The automated distribution of outgoing faxes cannot be specified on the modem as we did with the incoming faxes. In this case a ‘router’ definition has to be used. We will therefore select the ‘Remote PO Management’ option on the ‘Setup menu’.

Define a new Remote Post office with the PO ID ‘FAX’ and the PO Name ‘Fax Gateway’. This entry shall be defined with the entry type ‘Gateway on this Post office’

Then use the Address button on the “Common” tab and select the group address for ‘Distribution of outgoing Faxes’.


All faxes sent by local users will now be copied to the address ‘Distribution of Outgoing Faxes’.

The option “Enable Copy-To for relayed messages” can be used to include messages routed via the local site from other remo te sites like a ship or a laptop.


Time and Time Zones

Time and Time Zones As for all e-mail systems, the use of correct date, time and time zone is critical to AMOS Mail. All time fields are stored in the mail database with reference to UTC (Universal Time Coordinated). The local time is read from your computer’s real time clock and converted to UTC time before it is saved. When you display or print time, it will be converted to your choice of local time zone. AMOS Mail is also designed to automatically handle daylight savings time if properly configured on your computer. To be able to rely on time associated with messages and notifications, all PC’s using e-mail must have a correct time setting with respect to time zone.

There is no problem with different computers having different time zones (even on the same local area network), as long as they use the correct local time with respect to their preference of time zone. The time will always be presented to the user in his preferred time zone.

The time zone used by AMOS Mail is taken from the operating system (Windows 95 and Windows NT). However, if the environment variable TZ (Time Zone variable) is set on your computer, this information will be used. The TZ environment variable may be set (often incorrectly) by older applications during installation.

You should also be aware of the potential problems related to different computers not having synchronized time on the same network (same Post office). In the Send Queue in AMOS Mail, the time variable is also used to schedule the sending of messages. A consequence of not having the correct time with respect to time zone on one or more computers in the local network could be that transmission is delayed by the difference in time on the server and the user PC’s.

The command ‘NET TIME’ can be used in logon scripts to synchronize the time on a network.


The use of Aliases in AMOS Mail

Aliases In AMOS Mail, users can send mail to other places than to a mailbox, like to folders, printers and addresses. To achieve this , these items have to be given an alias (or a code). This alias is then used for addressing purposes in the same way as a mailbox ID.

The addresses will then look like:

>>>>>> ALIAS@PO

The only way you can forward messages to an address (indirect addressing) is by giving it an alias. Whenever you select the forward option, you will only see a list of those addresses that have an alias.

Two scenarios where you may benefit from using aliases are as follows:

Hide addressing details from remote users

If an address or its routing is expected to change, you may advice remote users to use the alias as opposed to specifying the full address otherwise required. This gives you more control and flexibility with respect to changes.

More effective use of alternate addresses

If you define an address to have alternates, the alternatives will be evaluated at the computer where they are defined. This is appropriate for an office installation, but not so for remote users that dial in to use the office computer’s telex or fax gateway. If the remote users send their telex or fax to an alias address with alternates however, they will benefit from the extended retry cycle that include the alternative addresses.

Note:

Please note that there is no internal checking or validation of the alias codes used. This means that you will manually have to control that duplicate codes are not used.

Internet Aliases The aliases used by the Internet mail gateway serves a different purpose. These aliases are used to map incoming addresses from the Internet to valid AMOS Mail addresses. You will have the option to associate your AMOS Mail mailbox with a more descriptive mail


address for use on the Internet. This is done through the Internet Mail Server configuration.


Application Interface

Application Interface The Application Interface, provided with the AMOS Mail Server version, allows applications (programs) to be the destination of mail. This facility may be used to trigger user-defined events on any local or remote system running AMOS Mail. Such events may be anything from simple housekeeping (empty WasteBasket, delete old mail) to sophisticated distributed systems.

The following sections explain how you can use AMOS Mail to create and configure an interface to your applications.

Starting the API Server The computer(s) selected to process inbound application requests must enable the following option through menu item “Other Services” and the “System Tasks” tab.

Addressing Applications Mail to an Application is created and sent in exa ctly the same way as other mail. The distinction lies with the address, which by definition must be specified as follows:

xxxx@API@PO


In above example «xxxx» represents a 1 to 6-character alias associated with the application you want to execute at Post office «PO». The address should be created and saved in the directory database on the originating computer. Prior to sending the message, an Application Definition of «xxxx» must be created at Post office «PO». If «@PO» is not used, «xxxx» must be defined at the local computer.

Defining Applications At «PO», an example application may be defined, using the «Application Definition» dialog on the AMOS Mail Setup menu as follows:

Information in above screen may be used as follows:

Address A 1 to 6-character code used when addressing the application (e.g. EDIT@API).

Computer The name of the computer where the application will be executed. Please note that this computer should have the API interface activated (Other Services on the Remote menu). The name of the computer you are sitting on is displayed after the “-“ in the dialog header.


Name A short description of your application.

Command The command to be executed. This may be a DOS «exe», «com» or «bat» file as well as any executable Windows application. This entry may be left blank, in which case only file export (see API Options) is considered. If no path is specified, AMOS Mail will attempt to locate the application in the current directory, the Windows directory, the Windows system directory, the AMOS Mail application directory, directories listed in your PATH statement or finally mapped network paths.

Argument This entry is used when composing arguments to be supplied when executing «Command». The following codes may be used to supply arguments that depend on the received message:

%s The Subject. You must enclose «%s» in double quotes if you expect a multiword subject.

%t File name of the message’s note text. This argument will only be supplied if the «Export Text Note» option is checked.

%f All filenames of any attach files separated with a single space. This argument will only be supplied if the «Export Attachments» option is checked.

%m The originators message reference (message number).

%a The Address Text of the originator. You must enclose «%a» in double quotes if this description is composed of more than one word.

%p The originators reply address.

Any other text will be included as is in the argument string supplied to «Command».

Directory Any Text Note or Attach Files exported will be placed in this directory. This entry may be left unspecified in which case files will be exported to the directory specified by the «TEMP» environment variable.


Text Note This will be used as a file name when exporting the Text Note. This entry may be left unspecified in which case a name will be assigned by AMOS Mail at the time of export. If a path is specified, this will be used. Otherwise the file will be placed in a directory according to the above description of «Directory».

Printer Select the printer to be used when printing attachment files. Printing of attachment files may be enabled by the «Print Attachments» option.

Specifying API Options The following options may be used to specify how AMOS Mail will carry out the requests to execute your applications:

Run Minimized Check this option if you want the application to be reduced to an icon every time it is executed. Do not use this for MS-DOS applications unless Background execution is enabled (see information on PIF settings in your operating system documentation).

Print Attachments Use this option to copy data in attachment files to the selected printer’s device. Data may be prepared on the originating computer by printing to file. No processing, character conversion or alteration of any kind will be applied to the files prior to printing. Hence, the data sent to the printer must be prepared specifically for the device it is sent to.

Export Text Note Check this option if you want the text note part of the message to be saved to a file.

Export Attachments Check this option if you want attachments to the message saved as files.

Delete Exported Files If checked, AMOS Mail will automatically delete all exported files (including the text note) when processing has been completed. This has no effect on the copy stored in the Post office database.

Application Definitions are known and shared by all Mailboxes belonging to the Post office in which they are defined, but will only be executed on the computer specified in API definition. Any number of applications may be defined


The AMOS Mail Utility Programs

The AMutlDir Program The AMutlDir program is a utility for automated scanning of directories for new or updated files. The utility can be used in two ways. It can scan a directory or directory structure for new files, which will be sent, or it can scan for new or updated files since the last run. The files selected can be specified using wildcards. The files can be sent to any e-mail address including AMOS Mail API-addresses. By using this together with the Application Interface in AMOS Mail, you can automate this process. Many directories can be scanned and sent to different addresses.

When using the utility to scan for new files in a directory or directory structure, the files will be sent to the specified address and the files will be deleted or copied to a backup directory. The files can then be sent to any address. The typical use is send exported files from one applications export directory to the import directory of another application on another computer.

If the utility is used to scan for new or updated files in a directory structure, the usage is usually to replicate a directory structure to another destination. This can be done to replicate report forms, standard documents etc. from the office to several other locations, like all the ships.

Note:

AMutlDir has the same functionality as the Scan Directory feature within AMOS Mail. (See the chapter on Other Services in the AMOS Mail Installation Guide for further information on this feature). For new installations, it is recommended to use the Scan Directory feature rather than AMutlDir.

To Run the AMutlDir Program To start the program, use the Start button in Windows or create a Shortcut to the program ‘AMUTLDIR.EXE’.

When running, the following window is displayed. It shows the number of minutes remaining for the next run to start (if the selection is based on filenames), or the date and time for the next run (if the selection is based on the modification date):


Configuration of AMutlDir The program has to be configured for the relevant usage. When completing the task by pressing the OK button, the program will be terminated and has to be restarted.

Type The type of search. If ‘By Date’, all files modified since last run will be sent, while ‘By Name’ will send all files corresponding to the Directory given.

Sub-directories If checked, all sub-directories will be included in the search for files.

Delete The file will be deleted after the sending if checked.

Copy The file will be copied to the backup directory.

Include Path The message file will include all commands necessary to copy the file to the right directory. The message file can then be exported and used as a batch file.

All in one message All files will be included in one message.

Last Run Date and time of the last run.

Next Run Date and time of the next run.


Minutes Minutes between each run.

Notify The address where you can send a notification message. The address can be given as ‘Address/Description’.

Specifying the Directories to scan The AMutlDir utility program supports multiple directories to be scanned for files to send. When completing the task by pressing the OK button, the program will be terminated and has to be restarted.

The Grid contains one row for each directory and file-type to scan. Typically there would be one line for each ship, specifying the address and the files to send for that ship.

Address The address to which the message will be sent. The address can be given as ‘Address/Description’.

Directory The Directory, which will be scanned for, files to send. The Directory entry can include wildcards.

Backup The Backup directory if backup is checked.

Subject The Subject that will be given to the message when sent.


Interface with AMOS-D AMOS Mail can be used to automate the sending and receiving of export / import files to and from the AMOS-D and AMOS4W programs. This can be done by using the utility program AMutlDir in combination with the AMOS Mail application interface.

AMOS-D Export and Import To interface AMOS Mail with AMOS-D you can use the DOS interface on the sending computer. Use the program MSSINP in the batch file from the sender. The files should be addressed to an API on the import side.

The import API can copy the files to the AMOS-D import directory. It could also be automated to start the import program.

Sending Faxes from AMOS-D and other DOS applications To send faxes from the AMOS-D program, you have to have a report writing to a text file. This file can then be sent using the MSSINP program and giving an address which will send it out of AMOS Mail as a fax.

Sending Faxes from AMOS4W and other Windows applications To send faxes from the AMOS4W program, you have to create a report using the writing to a text file. This file can then be sent using the MSSINP program and giving an address which will send it out of AMOS Mail as a fax.


Using Mail from Applications

Using Mail from Applications Several features have been added to AMOS Mail so that external programs such as word processors and spreadsheet applications may easily be integrated with AMOS Mail. The following sections describe some approaches to how you may extend your favorite application with Mail capabilities.

MAPI Interface AMOS Mail support “Simple MAPI”. This feature allows other applications, such as Microsoft Office and AMOS Replication, to send and receive mail messages via AMOS Mail.

Sending E-Mail with the MAPISendMail function The MAPISendMail function can be used to send a mail message from an application. This function takes as parameter one MAPI address string for each message recipient. The format of this string depends on the recipient type.

• AMOS Mail mailbox: “X-AM:<Mailbox ID>” , e.g. “X-AM:ADMIN”

• Fax: “FAX:<faxnumber>”, e.g. “FAX:123456” .

• Telex: “TLX:<Telex number>”, e.g. “TLX:123456”.

• Internet: “SMTP:<address>”, e.g. “SMTP:[email protected]”.

Please refer to the MAPI specification and the documentation provided with your programing environment for further information on how to use this and other MAPI functions.


Enabling AMOS Mail Simple MAPI Simple MAPI is installed automatically by AMOS Mail setup. The functionality can also be added or removed from the system at a later stage:

• Start MS Internet Explorer (version 4.0 or later).

• Select menu ToolsèInternet Options…

• Select tab “Programs”, and select AMOS Mail as E-Mail client.

Using 3rd party E-Mail clients The AMOS Mail Server can be used with 3rd party E-Mail clients such as Netscape Mail, MS Outlook/Express and Eudora Mail. The clients must support the “POP3” protocol for connecting to the server.

These clients connects to the POP3 / SMTP server of AMOS Mail.

Configure and start the SMTP and POP3 servers on the AMOS Mail server Both the SMTP server and the POP3 server have to be configured and started on the AMOS Mail server. This is required since the


Internet Mail program will use the POP3 protocol to connect to the AMOS Mail server.

See the AMOS Mail Installation Guide for details about how to configure the SMTP and POP3 servers.


Example: Install and Configure Internet Mail The following example describes how to install and configure Microsoft Internet Mail Service for MS Outlook 97.

• Open Control Panel, and double click icon “Mail”.

• The following screen will then be displayed. Select the Internet E-Mail entry and click the Properties button.

• A new screen with the logon options from Internet Mail to the POP3 server on AMOS Mail will be displayed. The Account and password information is a defined mailbox ID and password in AMOS Mail.

• If an Internet E-Mail entry is not present, click the “Add…” button to add one.


Note:

All addresses used from Internet Mail should be defined as type Internet addresses.


DDE Command Interface AMOS Mail may be used with external software packages to send WYSIWYG fax images. Prior to invoking the DDE interface you must prepare an image file suitable for fax transmission. This is accomplished by printing to a file using the «MSS Fax Image» printer. This printer will produce a black and white image file. The following commands may then be used by any application supporting DDE as follows:

DDEInitiate WinMss WinMss DDEExecute WinFax FaxFile

The highlighted words above are reserved words and must appear exactly as written.

The following is an example macro for Microsoft Word using the above DDE commands. The macro assumes that a fax image named faxfile.prn has been prepared:

Sub MAIN Channel = DDEInitiate(«WinMss», «WinMss») DDEExecute Channel, «WinFax » + «faxfile.prn» DDETerminate Channel End Sub

Using the AMOS Mail Fax Printer When AMOS Mail was installed on your computer, a printer named «AMOS Mail Fax» was automatically added to your list of available printers. Any document printed from a Windows application to this printer will automatically be converted to one or more fax image pages. These pages are picked up by AMOS Mail and prepared for transmission. AMOS Mail will prompt you for the address of recipients prior to sending the fax.

For convenience, the necessary steps may be prepared as a macro and even assigned to a menu or command button for easy access from within your favorite word processor. Please refer to documentation on your word processing application for information on assigning these macros to menus or command buttons.


Sending Mail from MS-DOS The command line utility application «mssinp.exe» may be used to send messages from the DOS prompt. If mssinp is run with no arguments it reports a usage statement as follows:

usage: mssinp [-t text_file] [-s subject] -a addr[/name] [-o] [-rt] [-rf] [-f attach_file] [-c account]

The arguments to be supplied are as follows:

-t text_file Substitute with the name of a file to be used as the text note portion of your message. The argument is optional.

-s subject The text supplied will be used as the subject of your message. The default is no subject. A multiword subject must be enclosed in double quotes. The argument is optional.

-a addr A minimum of one address must be entered. All addresses will be validated prior to creating the message. An address must be specified in one of two formats as follows: Address or Address/name If the second format is used, «name» will be used as the name of the recipient. If you specify a multiword name you must enclose the entire «address/name» argument in double quotes.

-o Characters in the file referenced by the “-t” argument will be translated from the default OEM code page to the default ANSI code page. Use this option if the supplied text use 8-bit DOS characters (e.g. solid lines or specific national characters). If not used, the text is assumed to only use characters from the default ANSI code page.

-f attach_file Substitute with the name of a file to be included as an attachment to your message. You may specify any number of attachments. The file name may contain wildcard characters, such as ‘*’ (matches 0 or more characters), and ‘?’ (matches 1 character). The argument is optional.

-rt The text file will be deleted when the message has been put in the mail queue.

-rf The attach file will be deleted when the message has been put in the mail queue.

-c account Use this option to associate a specific Workgroup with the new message. If not used, the message will be associated with the default users default Workgroup. If used, a search for a Workgroup with matching “account” will be made. If there is no match, the message will be associated with the “Everyone” Workgroup.

-cf cmd_file Specifies a file to read optional command line arguments from. The file must contain a valid lis t of command line arguments, optionally separated by line breaks.


The mssinp application uses the Registry database to locate the Postoffice directory and the Mailbox ID of the local client. This default database information is used for the ‘mssinp’ program.

Examples:

Send a message with no attach files to a local Mailbox:

mssinp -t note.txt -s «Test Message» -a «LM/Local Mailbox»

Send a message with two attach files to two Mailboxes (text portion will be empty):

mssinp -s «Worksheets Enclosed» -a «LM/Local Mailbox» -a «RM@PO/Remote Mailbox» -f c:\123r5\wk5\budget.wk5 -f c:\123r5\wk5\result.wk5

Sending Fax Images from MS-DOS The command line utility application «mssinp.exe» may also be used to send fax from the DOS prompt. Both text files and fax images can be sent as fax.

To send a fax image you use the AMOS Mail Fax Printer and print to a file, this file can be sent as a fax using the “mssinp.exe” application. The attached fax image-file will be deleted after sending.

Text files can also be sent as fax in the same way, but the text file will not be deleted unless the ‘-rt’ option is used.

In both methods described above, the address have to be a fax address like ‘12345678@FAX’.

Using the MAPITIF.DLL interface This DLL can be called from any programming language to interface the AMOS Mail system. Two functions are available in the DLL, the SendMail and the lpSendToFax functions.

• SendMail (lpHeaders):

LpHeaders: a zero terminated string including message header and address information.

• lpSendToFax (lpFileName,lpHeaders):

lpFileName: a fully qualified path to the file created by printing to the AMOS Mail Fax Printer.

LpHeaders: a zero terminated string including message header and address information.

For both functions:

The lpHeaders argument shall include a sequence of ASCII LF (0a hex) delimited strings according to the following format:

header-keyword : header-argument LF

The “:” should immediately follow the header-keyword. Any number of ASCII space-characters (20 hex) may optionally be inserted between the “:” and the header-argument for readability purposes.


The following header-keywords and their associated header-arguments are defined:

Keywords Arguments

From Sender-name reply-address

To Recipient-name recipient-address

Cc Recipient-name recipient-address

Bcc Recipient-name recipient-address

Subject Subject text

Ref 9 character alphanumeric field

Account 6 character alphanumeric filed

Attach File name of the attach file

Gui “yes” or “no”

All keywords are optional. A minimum of one To, Cc or Bcc header however must be supplied.

The length of the descriptive address, delivery address and subject elements will be subject to limitations in the underlying message store and transport. AMOS Mail has a 64-character limit for these elements whereas other transports may enforce other limits. It is recommended that these strings are limited to 256 characters or less.

The reply-address and recipient-address shall be defined as follows:

< address-type : address >

The left “<” (3c hex) and right “>” (3e hex) angle brackets are required elements. There should be no space character between the “address-type”, “:” and “address” elements.

The following address-type elements are defined:

Address type Description

FAX Delivery by fax

SMTP Delivery by Internet e-mail

X-AM AMOS Mail native address

The syntax for the address element is determined by the underlying message transport and not restricted by this specification.

It is assumed that all characters in the header section are based on the Windows code page ANSI-1252.


Sample source code for SendMail in Visual Basic:

' Declaring the AMOS Mail function

Private Declare Function SendMail Lib "mapitif.dll" _

(ByVal lpMessage As String) As Long

Private Sub Form_Load()

Dim tmpStr As String

' Building the header information

tmpStr = _

"To: <X-AM:TA>" & vbLf & _

"To: <SMTP:toma@SpecTec Group.no>" & vbLf & _

"Attach: C:\TEST.TXT" & vbLf & _

"Attach: C:\TEST2.TXT" & vbLf & _

"Subject: This is a test" & vbLf & vbLf & _

"This is the message part of the mail" & vbLf

' Calling the AMOS Mail function

SendMail (tmpStr)

End

End Sub

Sample source code for lpSendToFax in C:

// variable declarations

BOOL (WINAPI *lpSendToFax)(LPSTR lpFileName,LPSTR lpHeaders);

HINSTANCE hLib;

// load library and obtain pointer to function

hLib=LoadLibrary(“mapitif.dll”);

(FARPROC)lpSendToFax=GetProcAddress(hLib,"SendToFax");

// submit to MAPI or AMOS Mail

lpSendToFax(lpFileName,lpHeaders);

// unload library

FreeLibrary(hLib);


Database Administration

Introduction Various utilities to manage the Post office database are available to the Post office administrato.

• The Database Integrity Checker is used to check and repair indexes of individual database tables.

• The Database Reorganization Tool is used to free unnecessary disk space used by the database.

• Local Post Office Check and Repair is used to remedy other logical errors, such as loss of entire messages, folders and Mailboxes

Database Integrity Checker The Post office database is made up of a set of index sequential data tables. For each table there is one data file (*.dat) and one index file (*.idx). If you experience DBS errors, this may be due to corrupted index files. Such errors may come as a result of power failure during database updates or because of faulty hardware. If this is the case you will need to repair the index files.

When AMOS Mail was installed, a DOS utility program named «dcheck.exe» was copied to your install directory. This program allows you to check a file's integrity, repair a faulty index and rebuild an index from data.

If dcheck32 is executed with no parameters, it reports a usage statement as follows:

usage: dcheck32 [-bdehiklnoqrxyp] isamfile

The first parameter (optional) is a dash «-» followed by one or more of the listed letters, and the second is the full path name of the file to check. Option parameters should all be specified in one string, not individually (e.g. -eyp, not -e -y -p).

The optional parameters and their interpretation are as follows:

b build new index from data

d list deleted record numbers

e extended check (index/data cross-check)

h display header only

i check index only (default, see -e option)

k use exclusive lock

l list the index

n answer no to all queries

o record number list by primary key

q quiet mode

x hex list the index

y answer yes to all queries


p pause after each file

If an error is encountered, or if the -b option is used, what dcheck32 does is dispose of all of the indexes and then rebuild them from the data. The most extensive check can be done using the «-e» option. It is considered safe to rebuild all of the indexes (-b option) even when no error is suspected. The files will however be exclusively locked during rebuild in a multi-user environment and no clients should be allowed access to the Post office database during index repair.

Examples:

To perform an extensive integrity check of all files (rebuild of index files is optional):

dcheck32 -e \ampo\*

To rebuild indexes for all files:

dcheck32 -b \ampo\*

Database Reorganization Disk space is automatically allocated by the Post office database as new messages are saved. When messages are deleted, unused space will be put on a free-list and reused when new information is added. The effect of this approach is that the individual database files will only grow in size, but never shrink.

The DOS utility program «dpack.exe» may be used to reclaim free space (de-fragment) and reorganize the individual data and index files. If «dpack32» is run with no parameters, it reports a usage statement as follows:

usage: dpack32 isamfile

Use the following command to reorganize all files:

dpack32 \ampo\*

Although «dpack32» will reorganize data and index files in a more efficient manner, there is no need to run this program under normal circumstances. If however a group of users and their private messages have been removed from the database, the utility may be used to reclaim freed space and hence reduce storage requirements.

The utility works by copying the specified files one by one excluding deleted (free) records. The original file will be exclusively locked while copying. Once copying is completed, the original file will be removed and the new compressed file will be renamed to the original file’s name. Before running this utility, you must ensure that no other clients are allowed access to the database and that sufficient free storage capacity exists to hold an additional copy of the largest file packed.


Local Post office Check and Repair In addition to index errors as described in the previous section, other logical errors such as loss of messages, folders, Mailboxes or entire Workgroups may occur as a result of power failure or faulty hardware. In many of these cases a restore from backup may be the only possible remedy. The «Repair Local PO» (on the AMOS Mail Tools menu) utility however, will in addition to checking the indexes, also attempt to detect and correct some of the possible logical errors that may occur:

If «Check for Index Errors» is selected, an index check equivalent to running «dcheck32» as described above will be performed. If «Prompt for Corrections» is checked and errors are found, you will be prompted to answer «OK» or «Cancel» before any corrections are made. If the second choice, «Check for Logical Errors» is selected, a search for inconsistencies in the Post office database will be performed. Before accepting corrections to be made, you must observe the following:

No other clients should be allowed access to the database


Post office Backup The Post office database is organized as a relational database, meaning that a record in one table may depend on records in other tables. This problem complex is referred to as «referential integrity» which must be observed at all times. The AMOS Mail system is also a real time system, which further adds to the complexity. In order to make reliable backups of the AMOS Mail database, it is important that no modifications are made to the database during backup. Otherwise referential integrity will be compromised and the backup copy may be unusable.

In order to deal with the above problem and still be able to make reliable backup copies, the following should be considered:

• If the Post office database is stored on a network server, the network operating system may be used to disconnect all clients prior to initiating backup. The negative side to this approach is that all clients will be forced to log off and no clients will receive mail until they again log on.

• Use the «Backup PO Database» command on the AMOS Mail Tools menu. This utility will place a read lock on all database tables before the files are copied. This approach will effectively protect the database without forcing the clients to log off during backup.

Use the «Local PO Management» command on the AMOS Mail Setup menu and specify a downtime period to prevent simultaneous access and modification during backup.

The latter command can only be run by a Post office Manager. You must specify a destination directory with sufficient storage capacity to hold a complete copy of the Post office database. If other backup media, such as tape is used, the copy to tape must be taken from the backed up database rather than the working copy.

If the following is specified, a copy of the AMOS Mail Post office will be placed in the «c:\wmpo.bak» directory:

When a backup is restored, all clients must be denied access to the Post office database prior to restoring the backup copy. No attempt should be made to partially restore a database, as this will compromise referential integrity.


Directory Management

Directory Management This section describes the available tools to manage the AMOS Mail address books, the Directory.

Directory Templates All addresses in the AMOS Mail directory are based on a template. These templates determines the address’ behaviour in the address book, and also provides the user with a template address text.

The Directory Template List is available from the AMOS Mail Tools menu.

AMOS Mail has a set of built in templates. These can be altered by the AMOS Mail administrator, but they can not be removed. In addition, the administrator can create custom address book templates. This can be is convenient if the users frequently creates similar addresses, e.g. if the user’s frequently create Internet addresses to the domain “mydomain.com”, this can be simplified with a template that contains the address text “@mydomain.com@SMT”.

Template Details In the template list window, a click on the “Add” or “Details” button opens the “Template Details” window.


Name Template’s name. This is the name that will be shown in the “Template” drop-down in the address book’s address detail dialog.

Template Template address text.

Icon The icon that will be shown next to the addresses based on this template in the address book.

Hide from all users If this option is checked, the template will be hidden from the “Template” drop-down in the address book’s address detail dialog.

Visible to admins only Same as “Hide from all users”, except the template will still be available to users with Post Office Administrator capabilities.

Force uppercase If checked, addresses based on this template will be forced to use uppercase letters.

Note:

“Hide from all users” should be checked on all templates that are not in use on the system. That way, it is easier for the user to select correct template.

Directory Export and Import Two complementary commands are available in AMOS Mail to support file based directory exchange between AMOS Mail Post offices. These commands may be used to copy selected addresses to a text file (Directory Export) and importing addresses from a text file (Directory Import). Both commands are available from the AMOS Mail Tools menu. The «Directory Export» command displays the following dialog:


Directory Choose the directory (Workgroup) you want to export.

File The name and location of the file where the exported directory entries should be placed. The file will be created if it does not exis t. If the file does exist it will be truncated without warning.

Addresses of type «Local Mailbox» will be converted to type «MSS Person» when exported. The local Post office code will be appended to the address (e.g. MB becomes MB@PO where MB is a local Mailbox and PO is the Post office). The following dialog is displayed when you choose the «Directory Import» command:

Directory Choose the directory (Workgroup) where you want to import the addresses. You will only be allowed to select directories for which you have Directory Management rights.

File The name and location of the file to read directory entries from. The file must have been created using the «Directory Export» command.

If you have previously imported directory entries from the same Post office, only the new directory entries will be added. Updated entries will replace entries previously added.

Pointed Brackets The “Pointed Brackets” directory format is suitable during system implementation when it is desirable to import directory entries from a foreign system. A text file will have to be prepared that meet a set of criteria as outlined in the following sections:

Each line in the file must have two parts. The first part is the “Name” and the second part is the “Address”. “Name” is the full name of the recipient with no syntactical requirements. The


“Address” part must be enclosed within pointed brackets and comply with the address requirements set by AMOS Mail. Each line must be terminated by a single LF (line feed) or a pair of CR (carriage return) and LF. The following is an example import file:

SpecTec Group <+4767525553@FAX> Bill Gates

<[email protected]@SMT> SpecTec Norway <+5611246@TLX> Ocean Dream <MASTER@ODREAM> When entries are imported, they will all be tagged as belonging to a single “import set”. Whenever the import option is run a second time, the previous import set will be amended to avoid duplicates. If you need to import from several sources, all files will have to be combined in a single file prior to import. Lines that do not comply with the format requirements of this specification will be silently ignored. The effect of importing an empty file will be an empty import set.

AMOS Mail regular addresses are written as MAILBOX_ID@POSTOFFICE_ID (MB@PO for short). Addresses used for gateways must end with the “@” sign and a reserved suffix. The following suffixes are currently recognized:

TLX Telex

FAX Fax

SMT Internet e-mail

MHS Novel Message Handling System e-mail

CTX GN-Comtext

QIC GEIS QuikCom

TXT GSM Text

PRN Printer

API Application Interface

The icons associated with the imported directory entries are based on the suffix used. If the suffix is not recognized, the address will be marked as being of type “Mailbox”.

All AMOS Mail specific addresses must be uppercase. Syntactical requirements for gateway addresses are determined by the specific gateway. E.g. addresses ending with “@SMT” must follow the conventions for Internet e-mail addresses.

The “Name” and “Address” elements (excluding brackets) are currently limited to 64 characters each. If either of these parts is longer, they will be truncated to 64 characters.


Automatic Directory Synchronization The Global and Everyone directories can be automatically replicated between AMOS Mail sites. That is to say that any modification of the directory list done in one site will be reflected in the same directory on all the other participating sites. Both the Global and Everyone directory will initially include all local users. This means that the addresses of new users will be distributed and available for participating sites to use shortly after they are added. Other addresses created directly in the respective lists will be distributed in the same manner. The actual content and usage of the Global and Everyone directories is left to the Post office Administrator. One possible configuration is to limit distribution of Everyone to a small number of sites (e.g. remote users) with close ties whereas Global could be distributed to all sites in a potentially large corporate network. Other implementations may choose only to use one of the directories for automatic replication.

Directory updates received by one site will automatically be reflected to all other participating sites. This is to avoid the need for one particular site to know about sites other than its immediate neighbors. It is possible however to create directory subscriptions for sites routed via non-participating hosts (e.g. public hubs).

Directory replication is designed to work with all site-to-site transports offered by the various AMOS Mail gateways (e.g. Internet Tunneling, TCP/IP, Modem etc.).

Subscriptions for particular hosts are managed through menu option “Setup – Remote PO Management” which is documented in a separate chapter in this manual.

The directory synchronization agent must be started on each site that will use automatic replication with the Immediate or Scheduled options. This is done through menu item “Remote – Other Services” and the Directory tab. Manually initiated updates may be scheduled through menu option “Remote – Send Directory Subscriptions”.


Telex Monitor

The Telex Monitor The telex monitor is a utility program enabling the user to monitor the telex lines and the status of the different AMOS Mail services and gateways. For telex the user can in addition to status changes, also see all incoming and outgoing telex messages if the broadcast option is checked.

If you want to turn off all broadcast messages, you first stop the AMOS Mail program and then delete (or rename) the file named ‘MSSUDP32.DLL’. When you restart AMOS Mail, there will be no broadcasts.


Accounting Module

The Accounting Module The AMOS Mail Accounting module enables you to make reports for splitting and re-charging of communication costs. The Accounting module is separate from AMOS Mail. In order to use the application, accounting data must be exported from AMOS Mail, and imported into the accounting module. The export/import process is described in section 19.2, ‘Import of Billing Transactions’.

When starting the Accounting module, the main window is displayed. The main window is a ‘tabbed panel’, with 5 tabs: ‘Reports’, ‘Cost Table’, ‘Program Settings’, ‘Import Data’ and ‘About’. Use the ‘About’ tab to obtain version information for the application. The other four tabs are described in the following sections.

Program Settings

See screenshot above. The first time you start the Accounting module, this tab will be activated, and the following information must be entered.


License ID Enter your license ID.

License # Enter your license number.

Database Name Enter a valid path and file name for the database.

Company Name The Company Name displayed in the reports.

Address The company address

City The Company City

Country The Country

Printer Use this button to select which printer the application should print to.

Note: You will not be able to switch to any other tab unless the fields ‘License ID’, ‘License Number’ and ‘Database File’ are valid.

Import of Billing Transactions The billing transactions have to be transferred from AMOS Mail to the Accounting module before any reports can be made. This is done from the “ToolsàAccounting Export…” in AMOS Mail. You will then be asked for a file name and a time period:

After the transactions are exported, they must be imported into the Accounting module. Select the ‘Import Data’ tab in AMOS Mail Accounting (see screenshot on next page). Fill in the data fields in the tab as explained below, and press ‘Start import’. This will import accounting information from the file into the accounting database.


File The name of the file that was exported from AMOS Mail. You can press the ‘Browse…’ button at the right side of the field to search for the file.

Default Account The default account code that will be added to all entries not having an associated account code. Use the pull down list to select an existing account, or type in a new account name.

Default Provider The default provider added to all record not having an associated provider. Use the pull down list to select an existing provider, or type in the name of a new provider.

Note: If accounting data for the same time period are present in the database, this data will be deleted before import! The same file can, therefore, be imported many times without producing duplicates in the database.


Cost Table The ‘Cost Table’ tab is used to build a database of airtime/telecom provider charge rates, which the accounting module use to calculate the cost of each modem/telex connection, and each individual message. Each cost table entry consists of a provider, a dial number prefix, and the costs for making a connection with that provider to a number with that prefix.

In the above example, there is one record for calls made with Xantic airtime, one for calls made to Norway (country code 47) via Telenor, and another one for calls via Telenor terminated outside Norway.

Note:

Records with phone prefix ‘+’ has special meaning. These records are used for all calls over the specified not matching any other records.

Cost Table Buttons

Details Opens the “Cost Detail” window (described below), with details for the selected entry.

Add Adds a new entry to the list, and opens the ‘Cost Detail’ window with that entry.


Clone Creates a copy, ‘clone’, of the selected entry, and opens the ‘Cost Detail’ window with that entry. To avoid duplicates in the database table, the ‘Provider’ or ‘Phone’ fields of the new entry must be changed before the entry can be saved.

Remove Removes the selected entry.

Print Report Creates a printable report of all the cost list entries.

The Cost Detail Window

Provider The telephone or telex provider.

Phone The number prefix these data applies to, or ‘+’ for the provider’s default record. All calls made with this provider to numbers starting with this prefix will be charged according to these data.

Handshake Time The additional time you will charge for calls with this provider, e.g. for modem handshake. (Seconds)

TimeOfDayStart The time when daytime (peak) charges start. If the provider does not distinguish between a ‘Daytime’ charge and a ‘Nighttime’ charge, leave this field blank. In that case, only daytime charge data will be used.

TimeOfDayStop The time when daytime charges end.

Initial Cost The initial cost for setting up a call. The price the provider always charges, regardless of the duration of


the call.

Initial Time (seconds) The initial time included with the Initial Cost.

Period Cost The cost for a time period.

Period Length (secs.) The length of the period.

Charge Period (secs.) The length of the charge period.

Grace Period (secs.) Some providers only charge calls of more than a minimum duration, while calls of shorter duration is free. In such cases, enter the maximum duration of such free calls here.

Use in Weekends If the rates for nighttime shall be used in the weekend, check this option.

The ‘Initial Cost’ and ‘Initial Time’ fields are used to specify call setup charges. Some providers charge for a minimum duration of all calls, regardless of the call’s actual duration. In such cases, enter the minimum charge under initial cost, and the time this charge covers under initial time. Other providers charge an additional fee for setting up the connection, without giving any call time for it. In such cases, initial time should be set to 0. A combination of the two – minimum call duration and setup fee – is of course also possible. Initial time and initial cost must then be calculated to reflect the provider’s charge schema.

‘Period Cost’, ‘Period Length’ and ‘Charge Period’ are used to describe the time based charging. Period cost is the cost per time unit for the call, while period length is the length, in seconds, of that time unit. For instance, if the provider charges $0.10 pr minute, period cost is set to ‘0.10’, and period length is set to ‘60’.

Charge Period is the charge time steps. For instance, if a provider charges $0.10 pr minute, and has 15 sec charge steps, a call of 15-29 seconds duration would cost $0.05, while a call of 30-45 seconds duration would cost $0.075.

Note that charge periods and the cost period often differ in provider’s price plans, e.g. pr. Minute pricing and 15-second charge periods. If the provider does not specify a charge period, a charge period of one second should be used.

Reports Several standard reports are available in the Accounting module. Reports are prepared from the ‘Reports’ tab.


FROM – TO The period you want to select (the date from and the date to).

PO The Post office for which you want to report (data from this Post office must have been imported).

Original PO The original Post office, which have generated the transaction.

Account The Account codes you want to select.

Provider The Provider codes you want to select

Message The message numbers you want to include.

Report Text An optional text line that can be added to the report header.

Add % An optional percentage, which can be added to all charges when printing the report.

Detail lines Check this box if you want the detail lines to be included.

Report Type The type of report to create.

Run Create the report. Pressing this button will create the report, and show it in a new window.

The above selection will give all transaction from the 1st of October to the 31st of October, for accounts alphabetically larger than ‘BHT’ in Post office AM.

Note that many selection-criteria fields have associated drop-down lists. These lists can be used to select among existing names from the database. The criteria can also be typed into the fields.



A4W Interface to AMOS Mail

The A4W interface Amos for Windows (A4W) export files are sent through AMOS Mail with the MSSINP command line utility, which is installed with the AMOS Mail program files. Usually, this is done with a batch file that call MSSINP with the correct parameters (see Appendix A for an example SENDALL.BAT file).

To receive an A4W export file requires the Application Interface facility that is built in to AMOS Mail. A message with attachment (where the attachment is the export file) is addressed to the appropriate API. This AMOS Mail dial in server will then save the export file into the correct transfer directory to be processed later by A4W.

Therefore, each installation will use both MSSINP and SENDALL.BAT to send exports. Each installation will also use the API gateway to receive imports.

Pre Installation Requirements Each AMOS Mail license must include the API gateway (all vessels and the office).


If there will be a dedicated import / export server in the office then this must be included in the A4W license.

Because each export will be addressed directly to an API address at the remote side, you will need to decide on an addressing convention for the company. We suggest that you base this upon the installation numbers in A4W. For example, exports to the office will be addressed to A4W001 and exports to vessel number 258 will be addressed to A4W258.

Procedure This procedure assumes that you have already installed A4W and AMOS Mail and that you already have a working import / export set up, including selection files.


Configure A4W for Export Start A4W and check that the Transfer directory is set correctly for each installation (there is only one Transfer directory onboard and several in the office).

Save a copy of the SENDALL.BAT file into each transfer directory.

Create an export task for each installation (i.e. one on board and several in the office) with suitable settings, including selection file to use. Type the full path to the SENDALL.BAT in the relevant transfer directory in the post-process field. For example:-

T:\DATABASE\TESTSHIP\TRANSFER\SENDALL.BAT

Save the export task.

Edit the SENDALL.BAT file in each Transfer directory and set the following variables:-

Variable Usage Example

TRANSFER The full drive and path to this transfer directory (check against the Transfer Directory setting for this installation in A4W)

T:\DATABASE\TESTSHIP\TRANSFER

SUFFIX The file suffix used for exported files (check against the File Extension for Export Files setting in A4W)

LND

DESTAPI The Address of the AMOS Mail Application Definition at the remote side

A4W225

DESTHUB The Post office ID of the remote AMOS Mail hub ABC123

AMOSMAIL The directory containing MSSINP.EXE C:\AM32

Configure A4W for import Create an import task for each installation using normal settings including the selection file to use. No special settings are required for import, because AMOS Mail automatically leaves incoming files in the correct Transfer directory. A shipboard installation needs one import task while an office installation needs one import task for each vessel.


Configure AMOS Mail for Import Start AMOS Mail on the computer that will receive and save incoming export files into the transfer directory (this is the AMOS Mail communications server).

Log in to AMOS Mail then select Remote then Other Services. Select the API tab and select to process API messages on this computer. Click OK.

From the main menu select Setup and then Application Definition.

Create an Application Definition for each installation in the database (A vessel needs one Application Definition. An office needs an Application Definition for each vessel). Complete details as follows –

Setting Usage Example

Address This is the e-mail address which remote systems will address their attachments to

A4W001

Computer The is the name of the computer which will save the files

Amosmail

Name Descriptive name A4W import

Directory The directory in which to save import files (check in relation to the setting for Transfer Directory for each installation in the database)

T:\DATABASE\TESTSHIP\TRANSFER

Export Attachments Always selected Selected

Example:

Once this procedure had been followed for the office and ship installations, you are now ready to start exchanging files. You should test the transfer several times in both directions to be sure that everything is working correctly.


Sample SENDALL.BAT @ECHO OFF CLS ECHO SENDALL v1.5 Copyright (c) 1999-2000, SpecTec Group ECHO Posting export files... REM REM ----------------- System Variables ---------------- REM REM TRANSFER = Transfer directory REM SUFFIX = Suffix for export files REM DESTAPI = Destination API address REM DESTHUB = Destination post office ID i.e. ship or shore REM AMOSMAIL = Path to AMOS Mail programs REM REM --------------- Initialise Variables -------------- REM REM (These variables have to be adopted to each installation) REM (Remember to use the short DOS name for directories, not REM the long Windows names) REM REM SET TRANSFER=C:\DATABASE\VER3_1~1\TRANSFER SET TRANSFER=C:\test SET SUFFIX=EXP SET DESTAPI=A4W001 SET DESTHUB=STUKAM SET AMOSMAIL=C:\am32 REM REM ---------------- Initialize folders --------------- REM IF NOT "%OS%"=="Windows_NT" GOTO NOT_NT SUBST Z: %TRANSFER% IF NOT ERRORLEVEL 1 GOTO SUBST_OK ECHO Error: Could not map drive %TRANSFER% to letter Z! GOTO END :SUBST_OK SET TRANSFER=Z: :NOT_NT IF NOT EXIST %TRANSFER%\SENT\NUL MKDIR %TRANSFER%\SENT IF EXIST %TRANSFER%\TEMP RMDIR /S /Q %TRANSFER%\TEMP MKDIR %TRANSFER%\TEMP REM REM ------ Move export files to temp folder ----------- REM MOVE /Y %TRANSFER%\*.%SUFFIX% %TRANSFER%\TEMP > NUL REM REM ------------------- Send files -------------------- REM %AMOSMAIL%\MSSINP -s "A4W Export" -F %TRANSFER%\TEMP\*.* -A %DESTAPI%@API@%DESTHUB% REM REM ------------- Rollback and cleanup ---------------- REM SET ROLLBACK=0 IF ERRORLEVEL 1 SET ROLLBACK=1 IF "%ROLLBACK%"=="1" ECHO MssInp Failed, Rollback in progress... IF "%ROLLBACK%"=="1" MOVE /Y %TRANSFER%\TEMP\*.* %TRANSFER% > NUL IF NOT "%ROLLBACK%"=="1" MOVE /Y %TRANSFER%\TEMP\*.* %TRANSFER%\SENT > NUL RMDIR /Q /S %TRANSFER%\TEMP IF "%OS%"=="Windows_NT" SUBST /d Z:


:END


Troubleshooting

Problem Cause / solution

The export file is transmitted but A4W does not import it.

An import task will only import the next file in the numbered sequence. Perform a manual import to update the counter and the next transfer should import automatically.