X.400 P7 User Agent File Interface

   The messaging client MaXware UA-FI is used to message enable EDI or electronic commerce applications with X.400 communication capabilities, easily and at low cost. No communication expertise is needed for using UA-FI.
 

Working concept

   UA-FI provides a script based file interface to X.400. By using simple scripts and batch jobs your applications are enabled with X.400 communication capabilities.

   The application generates the files to be sent, and the command file script instructing UA-FI which files to send. Then the applications starts UA-FI.
        • UA-FI reads the command file and puts the files into X.400 messages
        • UA-FI connects to the mailbox and sends and receives messages            according to the commands in the command file
        • When finished communicating, UA-FI extracts the files from incoming messages and writes the result of the performed commands into the response file
        • The application processes the response file, checking the status of sent files and reading incoming files
 

Features

        • Well documented file interface.
        • Easy to integrate with applications.
        • UA-FI hides the complexity of X.400, allowing you to work with files in known environments.
        • Cross platform support. UA-FI is well suited for mail enabling both desktop and server applications.
        • Send files from any directory on the file system, and store received files in any directory.
        • UA-FI is a native X.400/P7 compliant messaging client.
        • Requires minimal system resources. May be used on IBM compatible PC’s.
        • Supports the commands Submit message, Fetch message from           mailbox, List messages in mailbox, Delete messages in mailbox, Change mailbox password.
        • Supports filter on the commands Fetch, List and Delete. Like "Fetch all PEDI messages", "List new messages", "Fetch messages from a specific originator", "Fetch Delivery Reports" etc.
        • UA-FI performs character set conversion for text files, between the application format and the X.400 transfer format.
        • UA-FI can be configured to automatically send receipt notifications for fetched messages.
 

Network access support

   UA-FI is available in several variants, supporting different network access methods. The following UA-FI versions exist:

Asynch (Dial-up)
   The Asynch version supports the APS/X.445 protocol (Asynchronous Protocol Specification). APS is an industry-standard for communication over asynchronous connections. The APS version is used to establish dial-up connections (to the MS) via the Telephone network (PSTN), ISDN network, Cellular networks (GSM, Mobitex, NMT), Satellite (Inmarsat).

   The APS version accesses the COM-port on the PC. If modem sharing SW is installed on the LAN, the Asynch driver can access a modem pool.

TCP/IP
   The TCP/IP version of UA-FI supports the RFC 1006 standard for running OSI Transport protocol over a TCP/IP connection. UA-FI accesses third party TCP/IP SW via the Winsock 1.1 interface.

   UA-FI for TCP/IP can be used in TCP/IP based LAN configurations, allowing UA-FI to be the client of an X.400 based corporate messaging system.

   If the installed TCP/IP SW supports the PPP/SLIP protocols, the MS can be remotely accessed by UA-FI via a dial-up connection (PSTN, ISDN).

ISDN
   UA-FI for ISDN accesses the network via an ISDN board installed on the PC that supports the CAPI 2.0 (Common ISDN API) interface.

X.25
   UA-FI versions supporting Eicon X.25 boards and Atlantis X.25 boards are supported. LAN solutions enabling many users to share the same X.25 board is available from the Eicon/Atlantis manufacturers.

Note:
        • Not all variants are available for all operating system platforms. Please, see the table on your right.
 

Standards

    UA-FI is conformant to the 1992 version of X.400.

   Supports the P7 (X.413) protocol operations Bind, Un-Bind, Submit, Fetch, List, Delete and Register-MS.

   Supports the content types P2 (X.420), P22 (X.420), PEDI (X.435) and P772 (Military).

   Supports the basic body part types IA5, Teletex, Bilaterally defined, G3Fax, Message and Military Message.

   Supports the Externally defined body part types IA5, Teletex, Message, File Transfer (FTAM) and General Text. The General Text body part includes support for the ISO 8859 character sets.

   For the FTAM body part the parameters Contents Type, Application Reference, User Visible String, Pathname, Date and Time of Last Modification, and Object Size are supported.

   Supports the ETSI/EWOS ISPs 10611-5 (AMH13), 12062-2 (AMH21), 12062-5 (AMH24). For the FTAM Body part the EMA MAWG profile is supported. See the MaXware PICS for a detailed description of the conformance.
 

Platform and network support

IPM elements of service support
        • Access Management
        • Blind Copy Recipient Indication
        • Content Type Indication
        • Deferred Delivery
        • Delivery Notification
        • Delivery Time Stamp Indication
        • Designation of Recipient by Directory Name
        • Distribution List Expansion Prohibited
        • Expire Time
        • Forwarded IP-message Indication
        • Grade of Delivery Selection
        • Implicit Conversion Prohibited
        • Implicit Conversion with Loss Prohibited
        • Importance Indication
        • IP-message Identification
        • Latest Delivery Designation
        • Message Identification
        • Message Security Labeling
        • MS Register
        • Multi-destination Delivery
        • Multi-part Body
        • Non-delivery Notification
        • Non-receipt Notification Request Indication
        • Originator Indication
        • Prevention of Non-delivery Notification
        • Primary and Copy Recipients Indication
        • Receipt Notification Request Indication
        • Reply Request Indication
        • Reply Time
        • Replying IP-message Indication
        • Sensitivity Indication
        • Stored Message Deletion
        • Stored Message Fetching
        • Stored Message Listing
        • Subject Indication
        • Submission Time Stamp Indication
        • Typed Body
        • Use of Distribution List

EDI elements of service support
        • Character Set
        • EDI Message Identification
        • EDI Message Types(s)
        • EDI Notification Request
        • EDI Standard Indication
        • EDIM Responsibility Forwarding Indication
        • EDIN Receiver
        • Interchange Header
        • Originator Indication
        • Recipient Indication
        • Typed Body

Military elements of service support
        • Primary Precedence
        • Copy Precedence
        • Extended Authorization Info
        • Distribution Code

System requirements
        • MS DOS version: 286 AT compatible PC. 2MB of RAM, and at least 480 KB of free memory to run UA-FI. 2MB of free disk space
        • Other version: 4MB of RAM, 4 MB of free disk space.
        • A modem and a telephone line, or an Eicon/Atlantis/HP X.25 board and a subscription for X.25, or TCP/IP SW and a TCP/IP connection, or a CAPI compliant ISDN board