Copyright (c) 2005-2017, Isode Limited, London, England
This document is a specification of the Isode X.400 MS Client Library API. This API allows client programs to connect to the Isode X.400 Message Store, using the P7 protocol, or directly to the Isode X.400 MTA, using the P3 protocol. The API is suitable for building the functionality of a User Agent or an Access Unit.
A summary of this product, which sets out its general function and intended application is given in http://www.isode.com/products/x400-client-api.html
P3 and P7 client applications bind as a User Agent (to the MTA and Message Store respectively). Submission work in a similar way. However P7 is a retrieval protocol, whereas P3 is a delivery protocol.
P7 applications bind as a Message Store user to the Message Store. The P7 application can retrieve messages, which can be deleted from this user's mailbox. Only messages for the bound user can be retrieved, deleted etc. When submitting messages, the originator of the message must be the bound user.
P3 applications bind to the P3 channel of the MTA. They bind to a P3 passive channel (ie a channel which has no "program" value in its configuration). Although the P3 client authenticates as a Message Store user (using the user's MTS password), this means that all messages which are routed for delivery to the P3 passive channel are delivered when a P3 client binds to the P3 server of the MTA. P3 clients are responsible for reliable storage of the messages. P3 clients should only unbind after an X400msWait() operation has returned indicating that there are no further messages for delivery by the MTA; ie all queued messages must be delivered. If this is not done, the MTA will conclude that the p3channel has failed, and will impose a delay before the delivery of the remaining messages on the channel can be attempted.
If you wish to "Jump right in" then the best thing to do is:
It is highly recommended you are familiar with the following standards:
The X.400 MS API is available in C, Tcl and Java bindings.
Top-level message objects are built, submitted, retrieved and examined using the X400 MS Client API. In particular, functions specific to X.400 MS message objects are used to get and set attribute values within messages. For example, X400msMsgAddStrParam() would be used to set a string parameter value in such a message.
There is one specific situation where protocol-independent functions need to be used to manipulate messages: this is when dealing with forwarded messages (i.e. messages which have been included as bodyparts of "top-level" X.400 MS messages). In this case, the equivalent "pure X.400" functions must be used - X400MsgAddStrParam() in the equivalent case to the one described above.
The example code is in:
The details of the C bindings are here:
The example code is in
The example code is in
The APIs use an object-oriented style, and rely on arguments which are
Please send any comments on the API to email@example.com.