cc:Mail Gateway Easy to install Bi-directional message format conversion Delivery reports, Exception reports and bi-directional Receipt reports Support for text and binary attachments Built-in or address book-based mapping of addresses Directory synchronisation Activity logging The Route400 cc:Mail Gateway provides seamless integration between a proprietary cc:Mail network and global X.400 messaging systems, allowing cc:Mail users to send and receive messages in a manner consistent with their normal way of working. The gateway relays messages and conveniently translates addresses between the cc:Mail messaging environment and a Route400 Message Server (MTA) associated with the gateway. This MTA may be configured as a stand-alone system, providing access to other private and public X.400-based systems, or may be one of a network of Route400 MTAs belonging to an X.400 backbone, giving access to native X.400 users within the network and world-wide. In addition, messages can be exchanged with users connected to different messaging systems such as the Internet, GroupWise, Microsoft Mail & Exchange, Lotus Notes and Fax, where necessary making use of other gateway products from the NET-TEL range or third parties. The Route400 gateway architecture enables an organisation to construct a single, logically integrated, messaging network from a number of existing, but incompatible, messaging systems. Gateway Architecture The Route400 cc:Mail Gateway runs under Windows on a dedicated PC connected to a LAN, shared between a cc:Mail network, with one or more Post Offices, and a Route400 Message Server (MTA) The gateway processes messages to and from an associated cc:Mail Post Office, the "Gateway Post Office", converting message content and address information between cc:Mail and X.400 formats The "Gateway Post Office" is configured using standard cc:Mail tools All cc:Mail messages destined for transmission to the X.400 network are addressed to "logical" users at the Gateway Post Office, each with a standard name and Post Office address The associated Route400 MTA delivers all messages originating at the gateway into the X.400 network. It also delivers all X.400 messages, whose addresses correspond to users within the cc:Mail network, to the gateway Address Management cc:Mail users need not be concerned with the gateway architecture. Addressing of X.400 users is transparent, using conventional cc:Mail methods Messages to most X.400 recipients may be simply addressed by taking a name from the cc:Mail directory In addition, the cc:Mail "Post Office addressing" dialog can be used to enter any required X.400 address in keyword format cc:Mail users accessible from X.400 have standard X.400 addresses. These are matched by the Route400 MTA against routing rules corresponding to the cc:Mail gateway Address synchronisation and mapping is performed automatically by the gateway Address mapping between X.400 and cc:Mail can be built-in, rules-based or address book-based In addition, cc:Mail users can always be addressed from X.400 using traditional "Domain Defined Attribute" style addresses, if required Inter-system Message Transfer Bi-directional support for primary (To), copy (Cc) and blind copy (Bcc) Bi-directional support for multi-recipient messages Bi-directional support for X.400 Body Part types, including IA5 text, General Text, Undefined (Bilaterally Defined), File Transfer and the Route400 specific DataFile Multiple text and file attachments allowed per message For messages from the Route400 MTA to cc:Mail: First text body part is attached as a text attachment, others are attached as files Route400-specific DataFiles and File Transfer Body Parts are attached preserving the original file name Other body part types are attached as files Text attachments are accurately converted between the IA5 (or General Text if accented characters are present) used in X.400 and the ANSI character set before being passed to cc:Mail An option is provided to select whether Route400-specific (DataFile), Undefined or File Transfer body parts are generated for file attachments sent from cc:Mail An option is provided to require that the gateway generates only X.400 (1984) based messages for interworking with legacy systems. Messages that cannot fulfil this requirement will be rejected and an exception report message returned to the cc:Mail originator Delivery reports are generated by the gateway for messages from the Route400 MTA to cc:Mail Exception reports are generated by the gateway and sent to the cc:Mail originator if the message is not deliverable to an X.400 recipient Full bi-directional support of receipt reports Message Connectivity cc:Mail users gain access via the gateway and its associated Route400 Message Server to: Any user in the same organisation using Route400 or third party message clients attached to the associated message server or any other Route400 server in the backbone network Users in the same organisation connected to separate proprietary e-mail systems via other Route400 gateway products Users in other organisations who are reachable via public or private X.400 messaging networks Internet e-mail users via the Route400 Internet Mail Gateway product Fax users via the Route400 Fax Access Unit product Addressing X.400 users from cc:Mail cc:Mail users find all known X.400 destination addresses pre-defined (by Directory Synchronisation) in the cc:Mail directory cc:Mail users can reach additional, unconfigured, destination addresses by entering the X.400 address details (in a simple keyword format) in the "Post Office addressing" dialog box when sending mail Fax users can be addressed with cc:Mail "Post Office Addressing" Addressing cc:Mail users from Route400 Route400 keeps all synchronised cc:Mail addresses in a nominated address book Users can enter additional destination addresses into their own private address book cc:Mail recipients can reside on any cc:Mail Post Office, not just the gateway-attached one In order to provide seamless X.400 integration, all cc:Mail users can be made to appear to have full X.400 addresses Addresses for cc:Mail recipients take the form of the X.400 address of the gateway together with the recipient’s personal name and post office Address conversion between X.400 and cc:Mail is performed by mapping X.400 addresses into cc:Mail "name and Post Office" form, or by look-up in the Route400 shared address book Domain Defined Attributes (DDA) may also be used to supply the recipient’s Post Office name and user name to the gateway, if desired Directory synchronisation Synchronises a nominated Route400 address book and the cc:Mail directory System administrator defines when synchronisation takes place using the gateway’s configuration menu Gateway supports automatic synchronisation at a predefined time each day, or on demand by administrator command Automatic synchronisation eliminates manual intervention and errors Optional administrator-definable prefixes may be added to cc:Mail addresses and Route400 ShortForm names copied from one directory to the other, enabling easy identification of recipients connected to the other messaging system The format of cc:Mail addresses and Route400 ShortForm names constructed automatically by the gateway may be specified, if required, to enforce organisation-wide naming conventions (with default formatting) Logging Gateway logging is provided at three levels and there is an option to save logging information in daily log files The lowest level logs errors only The medium level logs errors, collection and delivery notifications plus directory synchronisation problems The highest level adds diagnostics and traces The system administrator defines how long log files will be kept before they are automatically deleted Installation Simple to install using its Windows-based installer Easily configured into the cc:Mail environment as a "Gateway Post Office" using the standard cc:Mail "admin" program Technical Requirements Windows NT 4 and 3.51 Windows 3.1, 3.11 or Windows 95 IBM compatible PC with 486 processor or faster and a minimum of 8 MB of RAM Access to Route400 MTA and cc:Mail Post Office via LAN and any suitable network operating system supporting shared files
		Copyright © 1998-2007 NET-TEL Computer Systems Ltd