1、STD.ITU-T RECMN X.44b-ENGL 1997 m 4862591 Ob3982b 820 E INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08197) SERIES X: DATA NETWORKS AND OPEN SYSTEM COM M U N I CATI ON Message Handling Systems Common messaging call API I TU -T Recom mend at ion X .446
2、(Previously CCIlT Recommendation) STDmITU-T RECMN X-qib-ENGL L977 m 48b2571 Ob37827 7b7 ITU-T X-SERIES RECOMMENDATIONS DATA NETWORKS AND OPEN SYSTEM COMMUNICATION PUBLIC DATA NETWORKS X . 1 -X. 1 99 Services and facilities X.l-X.19 Interfaces X.20-X.49 Transmission, signalling and switching X.50-X.8
3、9 Network aspects X.90-X.149 Maintenance X. 150-X. 179 Administrative arrangements X. 180-X. 199 OPEN SYSTEM INTERCONNECTION X.200-X.299 Model and notation X.200-X.209 Service definitions X.210-X.219 Connection-mode protocol specifications X.220-X.229 Connectionless-mode protocol specifications X.23
4、0-X.239 PICS proformas X.240-X.259 Protocol Identification Security Protocols X.270-X.279 Layer Managed Objects X.280-X.289 Conformance testing X.290-X.299 INTERWORKING BETWEEN NETWORKS X.300-X.399 X.300-X.349 Satellite data transmission systems X.350-X.399 DIRECTORY X.500-X.599 OS1 NETWORKING AND S
5、YSTEM ASPECTS X.600-X.699 X.630-X.649 Naming, Addressing and Registration X.650-X.679 Abstract Syntax Notation One (ASN. 1) OS1 MANAGEMENT X.700-X.799 Systems Management framework and architecture Management Communication Service and Protocol X.7 1 O-X .7 1 9 Structure of Management Information X.72
6、0-X.729 Management functions X.730-X.799 X.800-X.849 OSI APPLICATIONS X.850-X.899 Commitment, Concurrency and Recovery Transaction processing Remote operations X.880-X.899 OPEN DISTRZBUTED PROCESSING X.900-X.999 For further details, please refer to ITU-T List of Recommendations ITU-T RECOMMENDATION
7、X.446 COMMON MESSAGING CALL API Summary This Recommendation specifies a simple call interface through which messaging-reliant applications may invoke the services of MHS across a standardized programming interface. The Recommendation was generated cooperatively with the XAPI Association and defines
8、the application programming interface being implemented for MHS by the worlds major vendors and service providers. Source ITU-T Recommendation X.446 was prepared by -T Study Group 7 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 9th of August 1997. Recommendation X.446
9、 (08197) 1 STD-ITU-T RECMN XP44b-ENGL 1797 D 4862573 Ob37829 53T FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommuni- cations. The IT Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is r
10、esponsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by
11、 the IT-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by ihe procedure laid down in WTSC Resolution No. 1. In some areas of information technology which fall within ITU-Ts purview, the necessary st
12、andards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS The IT draws attention to the possi
13、bility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of t
14、he Recommendation development process. As of the date of approval of this Recommendation, the ITU hadhad not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the lat
15、est information and are therefore strongly urged to consult the TSB patent database. O ITU 1997 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing fi
16、om the ITU. 11 Recommendation X.446 (08197) STD-ITU-T RECMN X-Vqb-ENGL 1997 D 48b257L Ob39830 251 CONTENTS 1 Introduction 1.1 Purpose . 1.2 Overview 1.3 Terminology . 1.3.1 Definitions 1.3.2 Abbreviations 1.4 References 1.4.1 Identical Recommendations - International Standards . 1.4.2 Paired Recomme
17、ndations - International Standards equivalent in technical content . 1.4.3 Additional references 1.5 Levels 1.6 C naming conventions 2 CMC architecture . 2.1 Functional model 2.2 Computational model 2.2.1 Interfaces . 2.2.2 Session 2.2.3 Wide character support . 2.2.4 Event notification 2.2.5 Extens
18、ions . 2.3.1 CMC manager . 2.3.2 Guidelines for platform bindings 2.3.3 Query for configuration information . 2.4 Object model . 2.4.1 Model components 2.3 Configuration model . 3 CMC object classes CMC AFI object classes . 3.1.1 Address book 3.1.2 Content item 3.1.3 Distribution list . 3.1.4 Messag
19、e 3.1.5 Message container . 3.1.6 Per Recipient Information . 3.1.7 Profile Container . 3.1.8 Recipient . 3.1.9 Report 3.1.10 Root Container 3.1 4 Data structures 4.1 Basic data types 4.2 Array data types 4.3 Attachment 4.4 Boolean . 4.5 Buffer 4.6 Callback Data Structures 4.7 Counted String 4.8 Cur
20、sor Handle . 4.9 Cursor Restriction . 4.10 Cursor Sort Key Recommendation X.446 (08197) Page 1 1 1 2 2 2 3 3 3 3 4 4 5 5 6 6 7 7 7 8 8 9 10 10 10 10 13 13 14 14 14 14 15 15 16 16 16 17 17 18 18 20 21 21 21 23 24 24 26 . 111 STD-ITU-T RECMN X.44b-ENGL 1797 D 48b257L Ub3783L 178 D 4.1 1 Dispatch Table
21、 4.12 Enumerated . 4.13 Events . 4.14 Extension 4.15 Flags 4.16 GUID 4.18 4.20 Message Reference . 4.22 Name . 4.17 Identifier . IS0 Date and Time . 4.19 Message 4.21 Message Summary 4.23 Object Handle . 4.24 Object Identifier 4.25 Opaque Data . 4.26 Property . 4.28 Report . 4.27 Recipient . 4.29 Re
22、turn Code 4.30 Session Id 4.3 1 Stream Handle 4.32 String 4.33 Time 4.34 User Interface Identifier 5 Object properties Address book object properties 5.1.1 Child allowed 5.1.2 Comment . 5.1.3 Location 5.1.4 Name . 5.1.5 Object class . 5.1.6 Parent 5.1.7 Server name 5.1.8 Shared . 5.1.9 Type Content
23、item object properties 5.2.1 Character set 5.2.2 Content information 5.2.3 Content type 5.2.4 Create time . 5.2.5 Encoding type . 5.2.6 File directory . 5.2.7 File name . 5.2.8 Item number 5.2.9 Item type . 5.2.1 1 Object class . 5.2.14 Title . Distribution list object properties . 5.3.2 Comment . 5
24、.1 5.2 5.2.1 O Last modified 5 2.12 Render position . 5.2.13 Size 5.3 5.3.1 Address . 5.3.3 Last modification time Page 27 33 33 33 34 35 35 35 36 38 39 39 40 40 40 41 42 43 44 44 44 45 45 46 46 56 56 56 57 57 57 58 58 58 58 59 59 59 60 62 62 63 63 64 64 64 64 65 65 65 66 66 66 66 iv Recommendation
25、X.446 (08197) STD * ITU-T RECMN X.44b-ENGL 2997 48b2591 Ob39832 O24 5.3.4 Name . 5.3.5 Object class . 5.3.6 Parent 5.3.7 Shared . 5.4 Message object properties . 5.4.1 5.4.2 5.4.3 5.4.4 5.4.5 5.4.6 5.4.7 5.4.8 5.4.9 5.4.10 5.4.11 5.4.12 5.4.13 5.4.14 5.4.15 5.4.16 5.4.17 5.4.18 5.4.19 5.4.20 5.4.21
26、5.4.22 5.4.23 Application Id . Application message status . Auto-Action Deferred delivery time Id . In message status . In reply to Item count . NRN diagnostic . NRN reason . Object class . Out message status . Priority Receipt requested Receipt type Report requested . Role . Sensitivity . Size Subj
27、ect Time received Time sent . Type 5.5 Message container object properties . 5.5.1 Child allowed 5.5.2 Comment . 5.5.3 Location 5.5.4 Name . 5.5.5 Object class . 5.5.6 Parent 5.5.7 Server name 5.5.8 Shared . 5.5.9 Type Per recipient information object properties . 5.6.1 Comment . 5.6.2 Delivery time
28、 5.6.3 Diagnostic . 5.6.4 Object class . 5.6 5.6.5 Reason . 5.6.6 Recipient address 5.6.7 Recipient name . 5.6.8 Type Profile container object properties 5.7 5.7.1 5.7.2 5.7.3 5.7.4 5.7.5 5.7.6 5.7.7 5.7.8 5.7.9 5.7.10 5.7.1 1 5.7.12 5.7.13 Auto-Action Character Set . Conformance . Default Service D
29、efault User Line Terminator Object Class Object Extensions Supported Objects Supported . Properties Supported . Property Extensions Supported . Required Password Required Service . Recommendation X.446 (08197) Page 66 67 67 67 67 68 68 68 69 69 69 70 70 70 70 71 71 72 72 73 73 73 74 74 75 75 75 75 7
30、6 76 76 77 77 77 78 78 78 78 79 79 79 79 80 80 80 80 81 81 81 82 82 82 83 83 83 83 84 84 84 84 85 V . STDaITU-T RECMN X.44b-ENGL 1977 W 48b2591 Ob39833 TbO W 5.7.14 Required User . 5.7.15 Support Counted Strings . 5.7.16 Support No Mark As Read 5.7.17 User Interface Available . 5.7.19 Version of the
31、 Implementation . 5.7.20 5.7.18 Users . Version of the Specification 5.8 Recipient object properties . 5.8.1 Address . 5.8.3 Name . 5.8.4 Object Class 5.8.6 Report Requested 5.8.7 Responsibility Flag . 5.8.8 Role . : 5.8.9 Type 5.9 Report object properties 5.9.2 Id . 5.9.3 Item Count 5.9.4 Messaging
32、 System Id 5.9.6 Read 5.9.7 Size 5.9.8 Subject 5.9.1 1 Time Sent 5.9.12 Unsent . 5.10.1 Child Allowed . 5.10.2 Comment . 5.10.4 Name . 5.10.5 Object Class 5.10.6 Shared . 6.1 Simple CMC functions . 6.1.2 Receiving messages 5.8.2 Content Retuni Requested 5.8.5 Receipt Requested . . 5.9.1 Application
33、Id . 5.9.5 Object Class 5.9.9 Subject Message Id . 5.9.1 O Time Received 5.10 Root container object properties . 5.10.3 Location 6 Functional interface 6.1.1 Sending messages . 6.1.3 Looking up names . 6.1.4 Administration 6.2.1 Bind functions . 6.2 Full CMC functions 6.2.2 Composition functions 6.2
34、.3 Enumeration functions 6.2.4 Event notification functions 6.2.5 Messaging functions . 6.2.6 Name handling functions 6.2.7 Stream functions . 7 Return codes . 8 Conformance Annex A - C declaration summary A.l C declaration summary . Page 85 85 85 86 86 86 86 87 87 87 87 87 88 88 89 89 90 90 90 90 9
35、1 91 91 91 92 92 92 92 93 93 93 93 93 94 94 94 95 95 95 96 100 106 109 116 117 119 130 144 149 152 154 160 175 177 177 vi Recommendation X.446 (08197) Page Annex B . CMC vendor extensions . B.l CMC vendor extensions . B . 1.1 Function extensions B.1.2 Data extensions . Extension set C declaration su
36、mmary . B.2.1 X.400 extension set . B.2.2 Additional extensions for simple CMCB(400 mapping B.2.3 Other extension sets B.2.4 Platform-specific information including run-time bindings B.2.5 Simple CMC usage of X.400 backbone services B.2 Annex C - Programming examples Programming examples C . 1.1 Que
37、ry Configuration, Logon, and Logoff . C.1.2 Send and Send Documents functions C . 1.3 List, read, and delete the first unread message C . 1.4 Look up a specific recipient and get its details . C.1.5 Use of extensions C.1.6 cmc-bind-implementation C.2 Example of cmc-bind-implementation C.3 Composing
38、a message . Check for new messages . C.5 Filing a message . C.6 Deleting a message . C.7 Retrieving a message C . 1 C.4 220 220 221 227 229 230 231 234 234 236 255 255 255 255 257 258 258 259 261 262 265 267 271 273 vii Recommendation X.446 (08/97) . STD.ITU-T RECMN X.44b-ENGL 1997 D 48b2571 b37835
39、833 Recommendation X.446 COMMON MESSAGING CALL API (Geneva, 1997) 1 Introduction This clause introduces the Common Messaging Call (CMC) Application Program Interface (API) and its specifications. It indicates the purpose of the interface, provides an overview of it, details abbreviations, provides d
40、ocument references, explains the level of abstraction of the interface, defines C naming conventions, and specifies conformance requirements. This Recommendation is an enhancement of the first version of the CMC MI, published in June 1993 by the X.400 MI Association. This Recommendation extends the
41、messaging-aware application support in the original document with support for messaging-reliant applications. 1.1 Purpose The purpose of this Recommendation is to specie a high-level messaging application program interface that can be supported by most messaging services deployed today. The API is i
42、ntended to enable application programmers to easily integrate messaging, and thus communications, into their applications, creating a large body of messaging-enabled applications. This Recommendation is directed toward messaging service developers who might wish to support such an application progra
43、m interface. This Recommendation may also guide application developers in understanding implementation-independent features of the Common Messaging Call APL The application developers must follow manuals provided by the system they are using for messaging support. 1.2 Overview The Common Messaging C
44、all Application Program Interface provides a set of high-level functions for messaging-enabled applications to send and receive electronic messages. Within the range of messaging-enabled applications, there are messaging-aware applications and messaging-reliant applications. Messaging-aware applicat
45、ions are those that can function quite satisfactorily as stand-alone applications, but which might connect to a messaging service to provide enhanced functionality. An example would be a word processing or spreadsheet application that has the capability to send the document or file using a FILE-SEND
46、 option off of the menu. Messaging-reliant applications are those which are inherently dependent on the existence of a messaging service to carry out their functionality. Examples of these are Electronic Data Interchange (EDI), information distribution applications, conferencinglcollaboration applic
47、ations, and possibly some distributed databases. This interface is designed to be independent of the actual messaging protocol employed between sender and recipient. The interface will support the creation and reception of standard message formats such as X.400 and SMTPNIME (RFC 822RFC 1521) as well
48、 as proprietary message formats. This is achieved through generic definition of capabilities common to most messaging protocols, plus a mechanism for defining extensions, which can be used to invoke protocol-specific services. The interface is also designed to be independent of the operating system
49、and underlying hardware used by the messaging service. Recommendation X.446 (08/97) 1 Another important consideration in the design of this API is to enable simple application actions to be taken with a minimum number of function calls while allowing more complex actions to be possible as well. To achieve these often conflicting objectives, the CMC AFI has two interfaces: a Simple CMC interface and a Full CMC interface. The Simple CMC interface provides a minimum number of function calls needed to send or receive a message by messaging-aware applications. The Full CMC
