
The X.400 network architecture is a store-and-forward system that relies on a directory service to manage and route messages. Each X.400 user is assigned a unique identifier, called the Directory System Identifier (DSI).
This identifier is used to look up a user's directory entry, which contains their message handling parameters. The directory service is essential for X.400 messaging, as it enables users to locate and communicate with one another.
The X.400 network architecture consists of several components, including the Message Transfer Agent (MTA) and the Directory System Agent (DSA). The MTA is responsible for transferring messages between users, while the DSA manages the directory service.
In an X.400 network, messages are routed through a series of MTAs and DSAs, which use the directory service to determine the next hop for the message. This process continues until the message reaches its final destination.
A different take: Broadband Integrated Services Digital Network
What is X.400
X.400 is an alternative to classic Internet e-mail. It was first adopted as a standard in 1984 by the Comité Consultatif International Téléphonique et Télégraphique (CCITT), now the International Telecommunication Union (ITU).

X.400 is a complex protocol family with additional functionalities compared to Internet e-mail. It has been completely replaced in the interpersonal messaging sector, but still exists for the transmission of EDI messages.
In Germany, X.400 is marketed by Deutsche Telekom under the name BusinessMail X.400 – formerly Telebox or Telebox400. This is often referred to as a synonym for an X.400 mailbox.
There are different protocols and procedures in X.400, including the P1 and P7 protocols. P1 is the most secure e-mail protocol with international standardization and is usually used via TCP/IP.
The P7 protocol is an inexpensive alternative to P1 and only requires a P7 client, an inexpensive X.400 mail software, to connect to the clearing center.
Here are the main differences between the P1 and P7 protocols:
X.400 offers different modes of operation, including mailbox operation, throughput operation, and mixed operation. The standard routing provides X.400/P7 access for sender and receiver.
Key Components

An X.400 message has two main components: an envelope and its content. The envelope contains addressing information, including the originator and recipient addresses, delivery priority, and message trace information.
The envelope is formatted using the P1 protocol. This is a crucial step in the X.400 message transfer process.
The content of an X.400 message is made up of one or more body parts, along with header information. The body parts contain the actual message, which can be text, graphics, voice, or other types of data.
Here's a breakdown of the different types of body parts and their corresponding numbers:
The header fields of an X.400 message contain useful information such as the message originator, recipients, and expiration time. This is useful for tracing messages and troubleshooting.
EDI and X.400
EDI and X.400 is a match made in heaven. X.400 is still a crucial technology in the EDI sector, despite predictions of its demise due to high costs.
The principle of "never touch a running system" is a major advantage of X.400 in EDI. This means that existing systems can continue to operate without interruption.
Security is a top priority in EDI, and X.400 delivers. Every participant is authenticated, minimizing the potential for abuse.
X.400 is a separate network, physically separated from the Internet. This reduces the risk of security breaches and other issues that can arise from Internet-based communication.
Complicated VAN landscapes are common in EDI, but X.400 can help simplify message routing.
Intriguing read: Signed and Encrypted Email over the Internet
Benefits and Functionality
The X.400 Client API offers a simple abstraction for developers, making it easier to create X.400 client applications.
Developers can focus on their application's logic without worrying about the complexity of X.400, as the API handles the underlying details.
The API is cross-platform, available on both Windows and Linux, making it a versatile tool for developers.
Here are the core functionalities provided by the API:
- Bind: connects securely to MTA or Message Store
- Unbind: application disconnects
- Create a new message with default settings
- Add parameters and content to a message
- Submit message: application sends a message
- Retrieve message: retrieves a message and provides a handle to the message
- List messages (P7 only)
- Get parameters and content from a message
- Delete message: deletes the message object and optionally the message itself
- Option to operate over TLS
Key Benefits

The Isode X.400 Client API offers a very simple abstraction for developers of X.400 client applications. This means that you can focus on building your application without getting bogged down in the complexities of X.400.
The API is designed to be flexible, allowing you to select and modify X.400 services as needed. This level of control is a major advantage for developers who require a high degree of customization.
The API is available on both Windows and Linux platforms, making it a versatile choice for cross-platform development. This means you can develop your application once and deploy it on multiple operating systems.
You can use the same basic API for deployment over either P3 or P7, which simplifies the development process and reduces the need for duplicate code.
Broaden your view: Set up Gmail with a Third-party Email Client
Core Functionality
The X.400 Client API offers a wide range of core functionalities that make it a powerful tool for handling messages and data.
You can securely connect to an MTA or Message Store using the Bind functionality, which also returns the number of messages waiting in a Message Store.
Consider reading: How to Email Text Messages

The API provides a straightforward way to disconnect from the service with the Unbind function.
Creating a new message with default settings is as simple as calling the Create a new message with default settings function.
You can add parameters and content to a message using the Add parameters and content to a message function.
The Submit message function sends the message securely over the network.
The Retrieve message function allows you to retrieve a message and provides a handle to the message, which can be used for further operations.
A P3 variant of the Retrieve message function is also available, which secures the message before transfer.
If you're using the P7 variant, you can also list messages using the List messages function.
You can get parameters and content from a message using the Get parameters and content from a message function.
The Delete message function deletes the message object and optionally deletes the message from the Message Store for P7 variants.
The X.400 Client API also provides the option to operate over TLS for secure communication.
Take a look at this: Changing Dns over Https Settings

Here are the core functionalities of the X.400 Client API:
- Bind: Connects securely to MTA or Message Store
- Unbind: Disconnects from the service
- Create a new message with default settings
- Add parameters and content to a message
- Submit message: Sends a message securely over the network
- Retrieve message: Retrieves a message and provides a handle
- List messages (P7 only): Lists messages
- Get parameters and content from a message
- Delete message: Deletes the message object and optionally deletes the message
- Operate over TLS: Provides secure communication
Architecture and Conformance
The X.400 architecture is designed to connect applications to M-Switch X.400 using P3, which is suitable for applications that need to send and receive messages and handle message storage. This connection enables applications to deal with message storage as a part of the application.
The library also connects to Isode’s X.400 Message Store using P7, which provides message storage and is suitable for applications that need infrastructure to support message storage. This enables access to a message by a second terminal in the event of a hardware failure.
The core X.400 Client API is a synchronous API, designed to be used with a multi-threaded process, and provides an asynchronous option for P3. Each association should only be accessed by a single thread.
X.400 conformance is defined for servers and Clients (UAs), and Isode’s X.400 P3 server conformance (M-Switch) and P7 server conformance (M-Store X.400) are set out separately. An X.400 client conformance statement may be developed by Isode customers building products using the X.400 Client API.
You might enjoy: Google Email Storage
Structure of Networks

X.400 networks have a two-tier domain structure, consisting of ADMDs, which are public service areas operated by telecommunications companies, and PRMDs, which are private utility areas managed independently by companies.
ADMDs and PRMDs are often treated as a single entity in practice, with a company typically operating a single X.400 mailbox for exchanging EDI messages.
An X.400 mailbox is managed by a Message Store (MS) and identified by a unique address, allowing messages to be transmitted to it via Message Transfer Systems (MTS) or Message Transfer Agents (MTA).
Users access their X.400 mailbox via User Agents, which are client software programs.
X.400 networks rely on a hierarchical structure, with ADMDs serving as public service areas and PRMDs serving as private utility areas.
Curious to learn more? Check out: Transfer Godaddy Email to Google Workspace
Network Addressing
Network addressing is a fundamental aspect of X.400 networks, where each mailbox is identified by a unique address. This address is semantically structured, similar to SMTP e-mail addresses, but with a more complex notation.

The attributes used in X.400 addresses are crucial for identification. The example address G=Max; S=sample man; O=sample company; OU=purchasing; A=X400EXAMPLE; C=AT breaks down as follows:
- C (Country name) identifies the country, in this case, Austria.
- ADMD (Administration Management Domain) identifies the Austrian ADMD X400EXAMPLE.
- O (Organisation name) identifies the organisation, Musterfirma.
- OU (Organisational Unit Names) identifies the organisational unit, purchasing.
- G (Given name) and S (Surname) identify the person, Max Mustermann.
Deutsche Telekom's X.400 network uses additional attributes, CN (Common Name) and n-id (User Agent Numeric ID), which can cause problems when addressing from/into an older IPM84 network. A simple workaround is to omit these attributes, as the unique identification of the X.400 mailbox in the VIAT network can be done without them, using G and S.
Explore further: Intelligent Network
Architecture
The architecture of the X.400 system is designed to be flexible and adaptable to different use cases. The library connects the application to M-Switch X.400 using P3, which is suitable for applications that require sending and receiving messages.
There are two main options for connecting to the X.400 Message Store: P3 and P7. P3 is a synchronous API that provides a simple model for application developers.
Here are the key differences between P3 and P7:
The core X.400 Client API is designed to be used with a multi-threaded process, which allows for multiple associations. Each association should only be accessed by a single thread to ensure smooth operation.
Conformance
Conformance is a critical aspect of the X.400 architecture, ensuring that servers and clients work together seamlessly. Isode's X.400 P3 server conformance, also known as M-Switch, is detailed in the relevant documentation.
Servers and clients must adhere to specific standards to achieve conformance. Isode's X.400 P7 server conformance, or M-Store X.400, is another example of conformance in action.
Client conformance is also an important consideration, as it depends on the services and API features used. Isode customers can develop their own client conformance statements by building products using the X.400 Client API.
The X.400 Client API exposes all the services provided by Isode servers, making it a valuable tool for developers. By using these services and API features, customers can ensure their clients meet the necessary conformance standards.
Here are some specific examples of X.400 conformance:
- Isode’s X.400 P3 server conformance (M-Switch)
- Isode’s X.400 P7 server conformance (M-Store X.400)
These conformance statements provide a clear understanding of what is expected from servers and clients. By following these guidelines, developers can create products that work together smoothly and efficiently.
API and Protocols

API and Protocols are crucial components of X.400. The Isode manual provides a comprehensive description of all the Isode messaging APIs.
You can find the 'C' language Isode X.400 Client API definitions online, which include example programs. The Java language Isode X.400 Client API definitions and example programs are also available.
The Tcl language Isode X.400 Client API examples can be found in the product release, and are described in the documentation.
Check this out: Email Bounce Back Message Example
API Definition
API definition is a crucial step in developing and using APIs. The Isode manual provides a comprehensive description of all the Isode messaging APIs.
To access the manual, simply click on the provided link. This will give you a detailed understanding of the APIs and how to use them.
The Isode X.400 Client API definitions are available in multiple programming languages, making it easy to integrate with various systems. The 'C' language API definitions can be found here.
For Java developers, the Isode X.400 Client API definitions and example programs are available here. These examples provide a hands-on way to learn how to use the API.
Tcl language Isode X.400 Client API examples can be found in the product release and are described here.
Explore further: Examples of Email Addresses
Protocols

Protocols are the backbone of any API, and in the context of X.400, we have several protocols that play a crucial role in message transport and delivery.
X.400 P1 is provided by the X.400 P1 Channel, which can be initiated in two ways: by a QMGR to connect to remote MTAs or by an incoming X.400 P1 connection through the Isode OSI transport service listener.
The X.400 P3 is implemented in two different channels: the P3 Delivery Channel and the P3 Client Channel. The P3 Delivery Channel is initiated by QMGR to deliver messages to a server, while the P3 Client Channel is initiated by incoming X.400 P3 connections.
M-Switch X.400 operates primarily at the message transport level, making it independent of message content. This means that any X.400 content can be transferred, including the X.400 Interpersonal Message format (P2/P22), the Military P772 format, and the X.400 EDI Format (Pedi).
Discover more: Corporate Email Format
Here are the two ways X.400 P1 can be initiated:
- Initiated by QMGR to connect to remote MTAs to send and receive messages.
- Initiated by an incoming X.400 P1 connection, through the Isode OSI transport service listener.
And here are the two channels used by X.400 P3:
- The P3 Delivery Channel, initiated by QMGR, used to deliver messages to a server.
- The P3 Client Channel, initiated by incoming X.400 P3 connections, used by P3 Client applications sending and receiving messages.
Message Routing
Message Routing is a crucial aspect of X.400, allowing messages to be delivered efficiently and effectively. Routing is primarily done at the time the message is submitted, with directory checks also performed by the X.400 channels.
The routing tree mechanism allows for flexible routing configuration, including alternate routing to support fall-back routing and load balancing. Multiple routing trees may be used to allow some routing configuration to be shared between MTAs, without requiring each MTA to route in the same manner.
Routing can be done on all X.400 address components, including support for wild card routing, with pattern matching on address component values. This allows for more precise control over message delivery.
Here are some key routing options:
The routing tree mechanism is a powerful tool for configuring message routing in X.400. It allows administrators to create flexible routing configurations that meet the needs of their organization.
Lower Layers: RTSE

The X.400 protocol supports three application contexts: mts-transfer (P1-1988, RTSE normal-mode), mts-transfer-protocol (P1-1988, RTSE X.410(1984)-mode), and mts-transfer-protocol-1984 (P1-1984, RTSE X.410(1984)-mode).
Full RTSE recovery is supported for both inbound and outbound transfers, which is a significant advantage for users.
A receiving channel can support all three application contexts on a single Session address, making it easier to manage and configure.
There is full support for Two-Way Alternate, allowing for more flexibility in communication.
Intriguing read: Asynchronous Transfer Mode
Frequently Asked Questions
Is X-400 still used?
Yes, X.400 is still used in select industries like the military and aviation due to its advanced security features. Its early adoption of encryption and security protocols makes it a legacy system still in use today.
Featured Images: pexels.com

