NET-TEL Computer Systems Ltd - Products - Internet Mail Gateway

<BODY BGCOLOR=#FFFFFF> <P ALIGN=CENTER> <A HREF="/frames/news.shtml"> <IMG src="/images/nof_new1.gif" WIDTH=48 HEIGHT=21 BORDER=0 NAME="news" ALT="News"></A>  <A HREF="/frames/strategy.shtml"> <IMG src="/images/nof_str1.gif" WIDTH=78 HEIGHT=21 BORDER=0 NAME="strategy" ALT="Strategy"></A>  <A HREF="/frames/products.shtml"> <img src="/images/nof_prd1.gif" WIDTH=80 HEIGHT=21 BORDER=0 NAME="products" ALT="Products"></a>  <A HREF="/frames/services.shtml"> <IMG src="/images/nof_srv1.gif" WIDTH=76 HEIGHT=21 BORDER=0 NAME="services" ALT="Services"></A>  <A HREF="/frames/support.shtml"> <IMG src="/images/nof_sup1.gif" WIDTH=72 HEIGHT=21 BORDER=0 NAME="support" ALT="Support"></A>  <A HREF="/frames/links.shtml"> <IMG src="/images/nof_lnk1.gif" WIDTH=50 HEIGHT=21 BORDER=0 NAME="links" ALT="Links"></A> <BR> <A HREF="/frames/search.shtml"> <IMG src="/images/nof_src1.gif" WIDTH=80 HEIGHT=16 BORDER=0 NAME="search" ALT="Search"></A>  <A HREF="/frames/company.shtml"> <IMG src="/images/nof_com1.gif" WIDTH=63 HEIGHT=16 BORDER=0 NAME="company" ALT="Company"></A>  <A HREF="/frames/vacancies.shtml"> <IMG src="/images/nof_job1.gif" WIDTH=69 HEIGHT=16 BORDER=0 NAME="vacancies" ALT="Vacancies"></A>  <A HREF="/index.html"> <IMG src="/images/nof_hom1.gif" WIDTH=39 HEIGHT=16 BORDER=0 NAME="home" ALT="Home"></A>  </P> <HR> <P ALIGN=CENTER> <A HREF="/frames/prod-2.shtml">Route400 Clients</A>  <A HREF="/frames/prod-3.shtml">Route400 Servers</A>  <A HREF="/frames/prod-4.shtml">Route400 Optional</A> <BR> <A HREF="/frames/prod-5.shtml">Route500 Directory</A>  <A HREF="/frames/api.shtml">API</A>  <A HREF="/products/information.html">Information</A> </P> <HR> <table border=0 cellpadding=0 cellspacing=0 width=502> <tr> <td rowspan=4 width=19> <img src="/images/onepix.gif" width=1 height=1 hspace=9 border=0 ALT=""> </td> <td colspan=3 width=483 height=130 valign=bottom> <map name="r400opt"> <area shape="rect" coords="77,41,161,58" href="/frames/background.shtml" TARGET="_top"> <area shape="rect" coords="186,41,305,57" href="/frames/doc-conv.shtml" TARGET="_top"> <area shape="rect" coords="328,43,400,57" href="/frames/dca.shtml" TARGET="_top"> <area shape="rect" coords="75,58,161,75" href="/frames/security-bg.shtml" TARGET="_top"> <area shape="rect" coords="184,60,273,75" href="/frames/virus.shtml" TARGET="_top"> <area shape="rect" coords="311,58,433,77" href="/frames/smg.shtml" TARGET="_top"> <area shape="rect" coords="76,78,133,94" href="/frames/smtpmime.shtml" TARGET="_top"> <area shape="rect" coords="160,79,229,94" href="/frames/lotus.shtml" TARGET="_top"> <area shape="rect" coords="265,77,311,94" href="/frames/ms-mail.shtml" TARGET="_top"> <area shape="rect" coords="344,77,390,95" href="/frames/cc-mail.shtml" TARGET="_top"> <area shape="rect" coords="422,76,449,96" href="/frames/fax-au.shtml" TARGET="_top"> </map> <img src="/images/hd_r4opn.gif" alt="Optional Route400 Products" width=480 height=102 border=0 usemap="#r400opt"> </td> </tr> <tr> <td colspan=3 width=409 valign=top> <font face="arial,helvetica"><font size=+1> <BR> <B><FONT COLOR=#404040>Internet Mail Gateway with MIME Support</FONT></b><BR><BR> <font face="arial,helvetica"><font size=-1> <UL COMPACT TYPE=circle> <LI>Easy to install <LI>Bi-directional message format conversion <LI>Delivery reports and "Mail failure" reports <LI>Full support for binary attachments using MIME <LI>Built-in, rules-based and table-based address mapping <LI>Activity logging <LI>Enables optimal interworking between the two leading messaging technologies </UL> The Route400 Internet Mail Gateway with MIME Support provides seamless integration between Internet mail and global X.400 messaging systems, allowing Internet and X.400 messaging users to exchange mail in a manner consistent with their normal way of working. <BR><BR> The gateway relays messages between the Internet and a Route400 <A HREF="/frames/prod-3.shtml" TARGET="_top">Message Server</A> (MTA) associated with the gateway, using SMTP (Simple Mail Transfer Protocol) and converting message header, text and body parts in accordance with RFC 822 (a standard for the format of Internet text messages) and MIME (the Multipurpose Internet Mail Extension). The 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 cc:Mail, GroupWise, Microsoft Mail & Exchange and Lotus Notes, where necessary making use of other gateway products from the NET-TEL range or third parties. <BR><BR> The Route400 gateway architecture enables an organisation to construct a single, logically integrated, messaging network from a number of existing, but incompatible, messaging systems. <BR><BR> <B>Gateway Architecture</B><BR> <UL COMPACT TYPE=circle> <LI>The Route400 Internet Mail Gateway with MIME Support runs on a UNIX, OS/2 or Windows NT system associated with a Route400 Message Server (MTA) <LI>According to system requirements, the gateway may be run on the same machine as the associated MTA or another. The message transfer interface between MTA and gateway is achieved through shared files <LI>The gateway is able to handle SMTP protocol itself or it can take RFC 822 messages on a "pipe" from an associated RFC 822/SMTP mailer such as sendmail or MMDF, converting message content and address information between RFC 822/SMTP and X.400 formats <LI>All Internet messages destined for X.400 are routed to the gateway through normal RFC 822 message routing <LI>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 are determined to be in the Internet, to the gateway <LI>With Route400 Internet Mail Gateways in two or more locations, it is possible to "tunnel" X.400 messages across the Internet in circumstances where it is not possible to implement direct X.400 connections using RFC 1006 over IP </UL> <B>Address Management</B><BR> <UL COMPACT TYPE=circle> <LI>X.400 and Internet users need not be concerned with the details of address management. X.400 and Internet address styles may be used freely <LI>In an Internet message, any specific X.400 address that is required may be entered (in keyword format) on the left hand side of the Internet address (before the "@" sign) <LI>Internet users accessible from X.400 have standard X.400 addresses. These are matched by the Route400 MTA against routing rules corresponding to the Internet gateway <LI>In addition, Internet users can always be addressed from X.400 using traditional "Domain Defined Attribute" style addresses, if required <LI>The Route400 Internet Mail Gateway with MIME Support uses intelligent mapping algorithms together with user configurable mapping tables to translate addresses in real-time as they transit the gateway, as specified in RFC 1327 <LI>The address mapping tables are held in files and may be easily updated by an administrator </UL> <B>Inter-system Message Transfer</B><BR> <UL COMPACT TYPE=circle> <LI>Bi-directional support for primary (To), copy (Cc) and blind copy (Bcc) <LI>Bi-directional support for multi-recipient messages <LI>Bi-directional support for all X.400 text body types, including IA5 text, General Text, Teletex (T.61) <LI>Bi-directional support for nested messages arising from forwarded messages <LI>An option is provided to require that the gateway generates only X.400 (1984) based messages for interworking with legacy systems. In this case the contents of the MIME message are encapsulated in text body parts as specified in RFC 1496 (Harpoon) <LI>Delivery reports are generated for outgoing messages when the message is passed to the Internet <LI>"Mail failure" messages are generated by the gateway and sent to the Internet mail originator if the message is not deliverable to an X.400 recipient <LI>Configurable retry strategies are implemented in accordance with RFC 1123 for mail which fails transmission to the Internet </UL> <B>MIME support</B><BR> <UL COMPACT TYPE=circle> <LI>MIME provides support for international character sets, multi-part messages, comprehensive file-attachment information, and a wide range of formats - including multimedia - and extensions for user defined body part types that are not standardised <LI>Conversion between MIME "content types" and X.400 (1988) "body part types" is provided in accordance with RFCs 1494, 1495 and 1327, which have been designed to allow the maximum amount of information to be retained in each direction when messages are moved between the Internet and an X.400 network <LI>Unconstrained numbers of text and file attachments allowed per message <LI>Bilateral support for Undefined (Bilaterally defined/BP14), External, File Transfer or Route400-specific (DataFile) body parts with an option to select which type is to be generated for message attachments sent from the Internet <LI>Default conversion from MIME to X.400 (1988) <LI>Optional conversion to X.400 (1984) using RFCs 1496 (Harpoon) and 1328 <LI>Decodes messages encoded in base64 or quoted printable <LI>Other messages treated as binary or text and not decoded <LI>X.400 message body parts are encoded in base64 or quoted printable where necessary, choosing the most efficient of these encodings for each body-part <LI>Conversions from/to the following MIME formats: <UL COMPACT TYPE=circle> <LI>Image/Jpeg <LI>Image/Gif <LI>Image/G3fax <LI>Application/Octet-stream <LI>Application/Postscript <LI>Message/RFC 822 <LI>Message/partial - no reassembly is done in the gateway <LI>Multipart/Mixed, including nested multipart body parts <LI>Multipart/Digest <LI>Text/Plain with US-ASCII translation to/from IA5 Text, General Text (ISO 8859-1) and ISO6937 </ul> <LI>Other character sets received (e.g. Teletex/T.61) are assumed to be bilaterally agreed. They are mapped to the MIME X.400 extended body-part so that there is no loss of information <LI>As the MIME encoding scheme is extensible, mappings for other part types may be configured by the administrator. The MIME type/subtype and Object Identifiers for the X.400 extended body part are specified in the gateway configuration file <LI>Any MIME body parts which are not recognised are mapped to the MIME X.400 extended body part <LI>Any unrecognised RFC 822 or MIME header lines are preserved </UL> <B>Message Connectivity</B><BR> Internet users gain access via the gateway and its associated Route400 message server to: <UL COMPACT TYPE=circle> <LI>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 <LI>Users in the same organisation connected to separate proprietary e-mail systems via other Route400 gateway products <LI>Users in other organisations who are reachable via public or private X.400 messaging networks </UL> <B>Addressing X.400 users from the Internet</B><BR> <UL COMPACT TYPE=circle> <LI>Internet users address X.400 recipients using conventional RFC 822 Internet addresses (in "user@domain" format) <LI>The domain part (after the "@" sign) of the RFC 822 address identifies the X.400 domain reached via the gateway <LI>The local part (before the "@" sign) identifies the recipient user and gives an address in either X.400 or Internet domain-type syntax <LI>If X.400-type syntax is used, the gateway passes the recipient address unchanged to the associated Route400 MTA <LI>If domain-type syntax is used, the gateway uses its own mapper to generate an address with X.400 syntax <LI>The mapping rules are stored in a text format database file </UL> <B>Addressing Internet users from Route400</B><BR> <UL COMPACT TYPE=circle> <LI>X.400 users address Internet recipients either with an RFC 822 address supplied in the form of a Domain Defined Attribute (DDA) or by using normal X.400 address values <LI>At the gateway, the Internet address is derived from the DDA containing the RFC 822 address information, if present, or by mapping the X.400 address fields that have been supplied (algorithmically or by table look-up in accordance with RFC1327 (MIXER)) <LI>Route400 message clients support entry of Internet addresses (in "user@domain" form). A full X.400 address is then constructed by combining the pre-configured X.400 address of the gateway with a DDA containing the Internet address entered by the user <LI>Where X.400 addressing is used to refer to Internet recipients, a user enters the individual Internet address components into the Route400 message client addressing screens using administrator-defined rules for the relationship between X.400 address fields and RFC 822 address components. This method provides the user with a uniform X.400 address space <LI>Internet addresses are stored in Route400 address books in a manner that is uniform with addresses of X.400 users and those within other domains reached via gateways (e.g. cc:Mail, Microsoft Mail etc.) <LI>Route400 message client users can simply save additional Internet destination addresses into their own private address books <LI>At the gateway, mapping rules are easily maintained by an administrator and held in text format database files <LI>MIXER style address maps may also be imported </UL> <B>Logging</B><BR> <UL COMPACT TYPE=circle> <LI>Gateway logging is provided at six levels and there is an option to save logging information in daily log files <LI>The lowest level logs errors only <LI>The second level logs errors, collection and delivery notifications <LI>The higher levels provide further diagnostics and traces <LI>The system administrator defines how long log files will be kept before they are automatically deleted </UL> <B>RFC Conformance</B><BR> <UL COMPACT TYPE=circle> <LI>RFC 821: Simple Mail Transfer Protocol (SMTP) <LI>RFC 822: Standard for Internet text messages <LI>RFC 1123: Requirements for Internet Hosts - Application and Support <LI>RFC 1327: Mapping between X.400 (1988) and RFC 822 messages <LI>RFC 1328: X.400 (1988) to X.400 (1984) downgrading <LI>RFC 1494: Equivalence between X.400 and RFC 822 message bodies <LI>RFC 1495: Mapping between X.400 and RFC 822 message bodies <LI>RFC 1496: Rules for downgrading messages from X.400 (1988) to X.400 (1984) when MIME content-types are present in messages (Harpoon) <LI>RFC 1521: Multipurpose Internet Mail Extensions (MIME) Part 1: Mechanisms for specifying and describing the format of Internet message bodies <LI>Draft RFC 1327bis etc.: MIXER (Mime Internet X.400 Enhanced Relay). Development of these RFCs, which are updates of RFCs 1327, 1494 & 1495, is being tracked </UL> <B>Installation and Configuration</B><BR> <UL COMPACT TYPE=circle> <LI>Simple to install <LI>Easy configuration process using mapping tables compatible with those specified in RFC 1327 </UL> <B>SMTP connectivity</B><BR> <UL COMPACT TYPE=circle> <LI>Connections to multiple SMTP hosts/peers <LI>SMTP connections may be received from any host or restricted to specified hosts <LI>Gateway is configurable as a standalone Internet RFC 822 MTA for sending/receiving mail using SMTP. Received mail is either converted to X.400 (and sent to the X.400 MTA) or forwarded to another Internet MTA as appropriate <LI>Gateway is configurable as an addition to a standard SMTP mailer such as sendmail and MMDF, with the standard mailer acting as the Internet MTA <LI>Communication between the gateway and mailer, when installed, is via "pipes" or files </UL> <B>Platforms supported</B><BR> <UL COMPACT TYPE=circle> <LI>Windows NT 4, where the Gateway operates as a native NT Service exploiting the common service management and logging facilities of NT <LI>IBM OS/2 v3 ("Warp") <LI>Digital Alpha OSF/1 v2 <LI>DG Aviion DG-UX v5.4 r3.10 <LI>HP-UX v9 and v10 <LI>ICL DRS/NX 3000 v6 level 3 and ICL TeamServer (Intel) SVR4.2 v7 level 5 <LI>ICL DRS/NX 6000 v7Mplus level 3 and ICL TeamServer (SPARC) SVR4.2 v7 level 5 <LI>IBM AIX v3 and v4 <LI>SCO UNIXWARE Version v1 and v2 <LI>SCO OpenServer v3 and v5 <LI>Stratus FTX v2.3 <LI>Sun Solaris (Sparc) v2.3 or higher <LI>Sun Solaris (x86) v2.4 or higher <LI>Tandem NonStop-UX B series <LI>Unisys System V release 4.0 v2.0 or higher </UL> </td> </tr> <TR> <TD COLSPAN=3 ALIGN=CENTER> <IMG SRC="/images/bot02.gif" WIDTH=480 HEIGHT=24 BORDER=0 ALT=""><BR><BR> </TD> </TR> <TR> <TD VALIGN=CENTER> <A HREF="/index.html" TARGET="_top" onMouseOver="window.status = 'NET-TEL Home'; return true;" onMouseOut="window.status = '';"><IMG SRC="/images/home.gif" BORDER=0 WIDTH=75 HEIGHT=16 ALT="NET-TEL Home"></A> </TD> <TD VALIGN=CENTER ALIGN=CENTER> <font face="arial,helvetica"><font size=-2> <A HREF="/copyright.shtml" onMouseOver="window.status = 'Copyright Information'; return true;" onMouseOut="window.status = '';">Copyright © 1998-2007 NET-TEL Computer Systems Ltd</A> </TD> <TD WIDTH=75> </TD> </TR> </table> </BODY>