2
0

Mail.sgm 4.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128
  1. <!-- $XConsortium: Mail.sgm /main/5 1996/08/30 14:53:44 rws $ -->
  2. <!-- (c) Copyright 1995 Digital Equipment Corporation. -->
  3. <!-- (c) Copyright 1995 Hewlett-Packard Company. -->
  4. <!-- (c) Copyright 1995 International Business Machines Corp. -->
  5. <!-- (c) Copyright 1995 Sun Microsystems, Inc. -->
  6. <!-- (c) Copyright 1995 Novell, Inc. -->
  7. <!-- (c) Copyright 1995 FUJITSU LIMITED. -->
  8. <!-- (c) Copyright 1995 Hitachi. -->
  9. <![ %CDE.C.CDE; [<RefEntry Id="CDEMX.XCDI.MAN296.rsml.1">]]>
  10. <![ %CDE.C.XO; [<RefEntry Id="XCDI.MAN296.rsml.1">]]>
  11. <RefMeta>
  12. <RefEntryTitle>Mail</RefEntryTitle>
  13. <ManVolNum>special file</ManVolNum>
  14. </RefMeta>
  15. <RefNameDiv>
  16. <RefName><Symbol Role="Message">Mail</Symbol></RefName>
  17. <RefPurpose>compose or mail a document
  18. </RefPurpose>
  19. </RefNameDiv>
  20. <!-- $XConsortium: Mail.sgm /main/5 1996/08/30 14:53:44 rws $-->
  21. <!-- CDE Common Source Format, Version 1.0.0-->
  22. <!-- (c) Copyright 1993, 1994, 1995 Hewlett-Packard Company-->
  23. <!-- (c) Copyright 1993, 1994, 1995 International Business Machines Corp.-->
  24. <!-- (c) Copyright 1993, 1994, 1995 Sun Microsystems, Inc.-->
  25. <!-- (c) Copyright 1993, 1994, 1995 Novell, Inc.-->
  26. <RefSynopsisDiv>
  27. <Synopsis>[<Symbol Role="Variable">file</Symbol>] Mail(in <Emphasis>mediaType contents</Emphasis>);
  28. [<Symbol Role="Variable">file</Symbol>] Mail([out|inout] <Emphasis>mediaType contents</Emphasis>
  29. [in title <Emphasis>docName</Emphasis>]);
  30. </Synopsis>
  31. </RefSynopsisDiv>
  32. <RefSect1>
  33. <Title>DESCRIPTION</Title>
  34. <Para>The
  35. <Symbol Role="Message">Mail</Symbol> request causes the handler to route a document to a destination using the
  36. mail message handling system.
  37. The handler is responsible for finding routing information in the document.
  38. </Para>
  39. <Para>When the
  40. <Emphasis>contents</Emphasis> argument is of mode
  41. <Literal>in</Literal>, the handler must deliver the document as is,
  42. without interacting with the user.
  43. </Para>
  44. <Para>When the
  45. <Emphasis>contents</Emphasis> argument is of mode
  46. <Literal>inout</Literal> or
  47. <Literal>out</Literal>, the handler must allow the user to compose or edit the document
  48. (and any embedded routing information)
  49. before it is delivered.
  50. If the handling tool supports some form of intermediate ``save''
  51. operation, it must send a
  52. <Symbol Role="Message">Deposit</Symbol> request back to the tool that initiated the
  53. <Symbol Role="Message">Mail</Symbol> request.
  54. </Para>
  55. <Para>The
  56. <Emphasis>contents</Emphasis> argument
  57. is the contents of the document.
  58. If this argument is unset
  59. (in other words, has a value of
  60. <Literal>(char *)0</Literal>), then the contents of the document are in
  61. the file named in the message's
  62. <Symbol Role="Variable">file</Symbol> attribute.
  63. The data type
  64. (<Emphasis>mediaType</Emphasis>) of the
  65. <Emphasis>contents</Emphasis> argument should be
  66. <Literal>string</Literal>, unless nulls are valid in the given media type,
  67. in which case the data type must be
  68. <Literal>bytes</Literal>.</Para>
  69. <Para>The
  70. <Emphasis>docName</Emphasis> argument contains the name of the document.
  71. If the
  72. <Emphasis>docName</Emphasis> argument is absent and the
  73. <Symbol Role="Variable">file</Symbol> attribute is set,
  74. the file name is considered to be the title of the document.
  75. This string would be suitable for display in a window title bar, for example.
  76. </Para>
  77. </RefSect1>
  78. <RefSect1>
  79. <Title>APPLICATION USAGE</Title>
  80. <Para>The
  81. &cdeman.ttmedia.ptype.declare; function can be used to register for,
  82. and help process, this message.
  83. </Para>
  84. <Para>This message can be sent with the
  85. &cdeman.ttmedia.load; function.
  86. </Para>
  87. </RefSect1>
  88. <RefSect1>
  89. <Title>ERRORS</Title>
  90. <Para>The ToolTalk service may return one of the following errors
  91. in processing the
  92. <Symbol Role="Message">Mail</Symbol> request:
  93. </Para>
  94. <VariableList>
  95. <VarListEntry>
  96. <Term>TT_DESKTOP_ENOENT</Term>
  97. <ListItem>
  98. <Para>The file that was alleged to contain the document does not exist.
  99. </Para>
  100. </ListItem>
  101. </VarListEntry>
  102. <VarListEntry>
  103. <Term>TT_DESKTOP_ENODATA</Term>
  104. <ListItem>
  105. <Para>The in-mode
  106. <Emphasis>contents</Emphasis> argument had no value and the
  107. <Symbol Role="Variable">file</Symbol> attribute
  108. of the message was not set.
  109. </Para>
  110. </ListItem>
  111. </VarListEntry>
  112. <VarListEntry>
  113. <Term>TT_MEDIA_ERR_FORMAT</Term>
  114. <ListItem>
  115. <Para>The document is not a valid instance of the media type.
  116. </Para>
  117. </ListItem>
  118. </VarListEntry>
  119. </VariableList>
  120. </RefSect1>
  121. <RefSect1>
  122. <Title>SEE ALSO</Title>
  123. <Para>&cdeman.ttmedia.ptype.declare;, &cdeman.ttmedia.load;; <Emphasis>Intro</Emphasis>, <Symbol Role="Message">Edit</Symbol> requests.
  124. </Para>
  125. </RefSect1>
  126. </RefEntry>
  127. <!--fickle 1.12 mancsf-to-docbook 1.2 08/07/95 23:18:47-->