All Element Summary (local elements unified by type) |
||||||||||||
|
||||||||||||
|
||||||||||||
Specifies an individual action to perform if the select element
matches minOccurs-maxOccurs messages.
|
||||||||||||
|
||||||||||||
|
||||||||||||
The contents of the body.
|
||||||||||||
|
||||||||||||
This calculated attribute indicates how many subfolders that folder contains.
|
||||||||||||
This element represents a complete local message to add to myInbox.
|
||||||||||||
This element's select attribute specifies the xpath expression used to evaluate if the this
rule applies to the active message.
|
||||||||||||
This read only element is set by the myInbox service when the message was delivered and indicates
if the message was determined to contain adult content by the adult content mail filter.
|
||||||||||||
content (type xsd:base64Binary) |
|
|||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
contentType (type xsd:string) |
|
|||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
This message allows clients to copy one or more messages to a folder.
|
||||||||||||
The response from copyMessage includes a newBlueId element for each successfully copied message.
|
||||||||||||
This read-only element contains the UTC date/time the message was received, and
appears in all messages except ones that were sent by the user.
|
||||||||||||
This read-only element contains the UTC date/time the message was sent.
|
||||||||||||
|
||||||||||||
|
||||||||||||
The contents of this element represent the content of the draft.
|
||||||||||||
This element is used to identify an existing draft to send.
|
||||||||||||
The element and it's children define the message structure (including the mime body)
|
||||||||||||
The contents of this element represent the status metadata of the draft.
|
||||||||||||
The subelements of this element describe the contents of the message.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
hasAttachments (type xsd:boolean) |
|
|||||||||||
|
||||||||||||
|
||||||||||||
This element represents an inline attachment
|
||||||||||||
This read only element is set by the myInbox service when the message was delivered and indicates
if the message was marked as junk mail by the junk mail filter.
|
||||||||||||
isRead (type xsd:boolean) |
|
|||||||||||
|
||||||||||||
This element contains a select statement that contains an XPATH expression
indicating a message message for which to copy the associated message.
|
||||||||||||
|
||||||||||||
This element defines the content of the message.
|
||||||||||||
|
||||||||||||
The element and it's children define the message structure (including the mime body)
This element is returned by passing the 'includeMessagePartStructure' element in query options
|
||||||||||||
|
||||||||||||
This element defines the status of the email and frequently changes.
|
||||||||||||
|
||||||||||||
The subelements of this element describe the contents of the message.
|
||||||||||||
|
||||||||||||
|
||||||||||||
The client defined name of the attachment
|
||||||||||||
|
||||||||||||
|
||||||||||||
The unique order that this attachment should appear relative to all other attachments.
|
||||||||||||
order (type xsd:unsignedLong) |
|
|||||||||||
This element contains a ref attribute that specifies the ID of the parent folder.
|
||||||||||||
|
||||||||||||
partContent (type xsd:base64Binary) |
|
|||||||||||
The password of the POP3 account
|
||||||||||||
plainBody (type xsd:string) |
|
|||||||||||
If this account is a POP3 account, this defines pop3 settings.
|
||||||||||||
The prefix of a message subject(ex: 'FW: ')
|
||||||||||||
|
||||||||||||
This element defines this account as a primary or non-primary account.
|
||||||||||||
The application-defined provider of the rule.
|
||||||||||||
raw2822Content (type xsd:base64Binary) |
|
|||||||||||
raw2822Headers (type xsd:base64Binary) |
|
|||||||||||
This element is used to specify a raw message to send.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
The client defined reminder date of the flag.
|
||||||||||||
|
||||||||||||
This required attribute specifes where the rule must run.
|
||||||||||||
This required attribute specifes when the rule must run.
|
||||||||||||
|
||||||||||||
This method is used to save a local message (for example in a PST file) into myInbox.
|
||||||||||||
The saveMessage response contains a newBlueId for each message that was successfully saved.
|
||||||||||||
This method is used to send a message from myInbox.
|
||||||||||||
The response to sendMessage is used to indicate the success of the operation as well
as the new id associated with any messages that were saved as a result of this method.
|
||||||||||||
|
||||||||||||
The name of the POP3 server
|
||||||||||||
|
||||||||||||
A plain text simple body that should be sent from the server.
|
||||||||||||
|
||||||||||||
size (type xsd:unsignedLong) |
|
|||||||||||
The value of this element will always be 'draft' and is provided for compatability with messages
|
||||||||||||
The state of a message flag.
|
||||||||||||
This element defines the sent/received state of the message.
|
||||||||||||
This element defines the sent/received state of the message.
|
||||||||||||
Indicates whether the rule is currently enabled.
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
Contains the id of an existing folder to copy the message(s) to.
|
||||||||||||
|
||||||||||||
The subject of a message minus the prefix (ex: 'hello there')
|
||||||||||||
The client defined text of the flag.
|
||||||||||||
This element contains a type identifier for this folder.
|
||||||||||||
Specifies if this is of type 'oof' or 'normal'
|
||||||||||||
|
||||||||||||
The calculated count of the unread messages associated with this folder.
|
||||||||||||
The client defined unique identifier for the inline attachment.
|
||||||||||||
The username of the POP3 account
|
Complex Type Summary |
||||||||||
Represents a provisioned users' email account.
|
||||||||||
Used in rule actions to indicate that the active message should have the included cat element added to it.
|
||||||||||
This element represents a mail attachment
|
||||||||||
|
||||||||||
Represents a complete RFC2822 / MIME message.
|
||||||||||
This action is used to copy the active message in rules processing to another folder specified by the
'targetFolder' element
|
||||||||||
Used in rule actions to indicate that the active message should be deleted
|
||||||||||
|
||||||||||
Rules specify actions that should be performed on the active message during sending or delivery.
|
||||||||||
Defines the part structure of the draft (including the mime parts)
|
||||||||||
|
||||||||||
This element defines a single draft in myInbox in the base schema.
|
||||||||||
|
||||||||||
Specifies an e-mail address and display name
|
||||||||||
Specifies an e-mail address and display name
|
||||||||||
Specifies an e-mail address and display name, or the PUID that represents them.
|
||||||||||
Used in rule actions to indicate that the active message should have the included flag added to it.
|
||||||||||
This optional element defines the flag state of the message.
|
||||||||||
Folder elements in myInbox are containers for messages, although not directly.
|
||||||||||
Used in rule actions to indicate that the active message should be forwarded to the included recipients as an attachment.
|
||||||||||
Used in rule actions to indicate that the active message should be forwarded to the included recipients.
|
||||||||||
This element represents the html body of a message or draft.
|
||||||||||
This element represents an inline attachment
|
||||||||||
|
||||||||||
Used in rule actions to indicate that the active message should be marked as read.
|
||||||||||
|
||||||||||
messageParts define the part structure of the message (including the mime parts)
|
||||||||||
|
||||||||||
This element defines a single message in myInbox in the base schema.
|
||||||||||
|
||||||||||
Used in rule actions to indicate that the active message should be moved to the targetFolder
|
||||||||||
This represents the root element of myInbox
|
||||||||||
For myInbox services that support POP3 aggregation, this element defines the POP3 settings
necessary for the myInbox service to locate and download messages from that account.
|
||||||||||
|
||||||||||
Used in rule actions to indicate that the active message should be redirected to the included recipient.
|
||||||||||
|
||||||||||
This element is used to specify one or more recipients that this message
should be delivered to, if the identity who receives the message chooses
to reply.
|
||||||||||
Rules specify actions that should be performed on the active message during sending or delivery.
|
||||||||||
|
||||||||||
|
||||||||||
This element represents a raw header not included in the base schema
|
||||||||||
|
||||||||||
The complete prefix and text of a subject. prefix is separated by
the server to allow sorting on the actualy subject of the message.
|
||||||||||
This element specifies the folder to save the message to.
|
Simple Type Summary |
||||||
This element identifies the 'conversation' or e-mail thread of which this message belongs
|
||||||
This element identifies the index of the conversation to which this message belongs.
|
||||||
|
||||||
|
||||||
|
||||||
This type defines the allowable flag state values
|
||||||
Defines the allowable values for a folder/type element
|
||||||
This element indicates the importance of this message.
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
|
||||||
This element indicates the sensitivity of the message.
|
<xsd:schema elementFormDefault="qualified" targetNamespace="http://schemas.microsoft.com/hs/2001/10/myInbox" version="1.0" xmlns="http://schemas.microsoft.com/hs/2001/10/myInbox" xmlns:hs="http://schemas.microsoft.com/hs/2001/10/core" xmlns:xdb="urn:schemas-microsoft-com:xdb" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:annotation>
<xsd:documentation>
</xsd:annotation>
Schema for .NET Inbox service
</xsd:documentation>
Copyright (c) 2001 Microsoft Corporation. All rights reserved.
<xdb:blue select="/myInbox"/>
</xsd:appinfo>
<xdb:blue select="/myInbox/$any"/>
<xdb:blue select="/myInbox/account"/>
<xdb:blue select="/myInbox/subscription"/>
<xdb:blue select="/myInbox/folder"/>
<xdb:blue select="/myInbox/message"/>
<xdb:blue select="/myInbox/draft"/>
<xdb:blue select="/myInbox/rule"/>
<xdb:blue select="/myInbox/message/messageStatus"/>
<xdb:blue select="/myInbox/message/messageContent"/>
<xdb:blue select="/myInbox/draft/draftStatus"/>
<xdb:blue select="/myInbox/draft/draftContent"/>
<xdb:blue select="/myInbox/draft/draftContent/draftPart"/>
<xdb:red select="//@creator"/>
<xdb:red select="//@changeNumber"/>
<xdb:red select="//@id"/>
<xdb:red select="//cat"/>
<xdb:red select="//cat/@ref"/>
<xdb:red select="/myInbox/account/email"/>
<xdb:red select="/myInbox/account/primary"/>
<xdb:red select="/myInbox/account/$any"/>
<xdb:red select="/myInbox/folder/type"/>
<xdb:red select="/myInbox/folder/$any"/>
<xdb:red select="/myInbox/folder/parentFolder/@ref"/>
<xdb:red select="/myInbox/folder/childFolderCount"/>
<xdb:red select="/myInbox/folder/name"/>
<xdb:red select="/myInbox/folder/unread"/>
<xdb:red select="/myInbox/message/messageStatus/$any"/>
<xdb:red select="/myInbox/message/messageStatus/folder/@ref"/>
<xdb:red select="/myInbox/message/messageStatus/isRead"/>
<xdb:red select="/myInbox/message/messageStatus/flag/state"/>
<xdb:red select="/myInbox/message/messageStatus/flag/$any"/>
<xdb:red select="/myInbox/message/messageStatus/state"/>
<xdb:red select="/myInbox/message/messageContent/$any"/>
<xdb:red select="/myInbox/message/messageContent/size"/>
<xdb:red select="/myInbox/message/messageContent/messageType/type"/>
<xdb:red select="/myInbox/message/messageContent/messageType/$any"/>
<xdb:red select="/myInbox/message/messageContent/account/@ref"/>
<xdb:red select="/myInbox/message/messageContent/importance"/>
<xdb:red select="/myInbox/message/messageContent/hasAttachments"/>
<xdb:red select="/myInbox/message/messageContent/conversationId"/>
<xdb:red select="/myInbox/message/messageContent/dateReceived"/>
<xdb:red select="/myInbox/message/messageContent/dateSent"/>
<xdb:red select="/myInbox/message/messageContent/subject/text"/>
<xdb:red select="/myInbox/message/messageContent/from/name"/>
<xdb:red select="/myInbox/message/messageContent/from/email"/>
<xdb:red select="/myInbox/draft/draftStatus/$any"/>
<xdb:red select="/myInbox/draft/draftStatus/folder/@ref"/>
<xdb:red select="/myInbox/draft/draftStatus/isRead"/>
<xdb:red select="/myInbox/draft/draftStatus/flag/state"/>
<xdb:red select="/myInbox/draft/draftStatus/flag/$any"/>
<xdb:red select="/myInbox/draft/draftStatus/state"/>
<xdb:red select="/myInbox/draft/draftContent/$any"/>
<xdb:red select="/myInbox/draft/draftContent/size"/>
<xdb:red select="/myInbox/draft/draftContent/draftType/type"/>
<xdb:red select="/myInbox/draft/draftContent/draftType/contentType"/>
<xdb:red select="/myInbox/draft/draftContent/draftType/$any"/>
<xdb:red select="/myInbox/draft/draftContent/account/@ref"/>
<xdb:red select="/myInbox/draft/draftContent/hasAttachments"/>
<xdb:red select="/myInbox/draft/draftContent/importance"/>
<xdb:red select="/myInbox/draft/draftContent/sensitivity"/>
<xdb:red select="/myInbox/draft/draftContent/conversationId"/>
<xdb:red select="/myInbox/draft/draftContent/conversationIndex"/>
<xdb:red select="/myInbox/draft/draftContent/subject"/>
<xdb:red select="/myInbox/draft/draftContent/from/name"/>
<xdb:red select="/myInbox/draft/draftContent/from/email"/>
<xdb:red select="/myInbox/draft/draftContent/subject/text"/>
<xdb:red select="/myInbox/draft/draftContent/recipient/email"/>
<xdb:red select="/myInbox/draft/draftContent/recipient"/>
<xdb:red select="/myInbox/draft/draftContent/plainBody"/>
<xdb:red select="/myInbox/draft/draftContent/htmlBody"/>
<xdb:red select="/myInbox/draft/draftContent/htmlBody/inlineAttachment"/>
<xdb:red select="/myInbox/draft/draftContent/htmlBody/inlineAttachment/uri"/>
<xdb:red select="/myInbox/draft/draftContent/htmlBody/inlineAttachment/contentType"/>
<xdb:red select="/myInbox/draft/draftContent/htmlBody/inlineAttachment/content"/>
<xdb:red select="/myInbox/draft/draftContent/attachment"/>
<xdb:red select="/myInbox/draft/draftContent/attachment/name"/>
<xdb:red select="/myInbox/draft/draftContent/attachment/ord"/>
<xdb:red select="/myInbox/draft/draftContent/attachment/contentType"/>
<xdb:red select="/myInbox/draft/draftContent/attachment/content"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/parentPart/@ref"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/order"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/contentType"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/contentTransferEncoding"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/size"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/contentDisposition"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/contentId"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/contentLocation"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/partContent"/>
<xdb:red select="/myInbox/draft/draftContent/draftPart/$any"/>
<xdb:red select="/myInbox/rule/$any"/>
<xdb:red select="/myInbox/rule/@sequence"/>
<xdb:red select="/myInbox/rule/runat"/>
<xdb:red select="/myInbox/rule/runwhen"/>
<xdb:red select="/myInbox/rule/type"/>
<xdb:red select="/myInbox/rule/state"/>
<xdb:red select="/myInbox/rule/provider"/>
<xdb:sqlScript source="myInboxCustomSQL.sql"/>
<xdb:sqlScript source="myInboxCustomSQLAccount.sql"/>
<xdb:sqlScript source="myInboxCustomSQLFolder.sql"/>
<xdb:sqlScript source="myInboxCustomSQLMessage.sql"/>
<xdb:sqlScript source="myInboxCustomSQLRule.sql"/>
<xdb:sqlScript source="myInboxCustomSQLAction.sql"/>
<xdb:namespaceMap>
<xdb:mapping alias="m" uri="http://schemas.microsoft.com/hs/2001/10/myInbox"/>
</xdb:namespaceMap>
<xdb:mapping alias="hs" uri="http://schemas.microsoft.com/hs/2001/10/core"/>
<xsd:import namespace="http://schemas.microsoft.com/hs/2001/10/core" schemaLocation="hscommon.xsd"/>
<!--
// // myInbox // - root element for the .NET Inbox service // -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
</xsd:sequence>
<!-- standard attributes for the root element -->
<!--
// // folderType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Folder elements in myInbox are containers for messages, although not directly. Messages are related
</xsd:documentation>
to folders via the /myInbox/message/messageStatus/folder ref="" attribute. Folders can be orgainized heirarchically, although again not directly. Instead, folder containment is modeled using the /myInbox/folder/parentFolder ref="" attribute. If a folder is deleted, all associated messages, folders and their messages are deleted. It is recommended that instead of deleting a folder directly, you move it to the type="deleted" folder first. There are 4 built in types of folders and these can be identified by four special type element values: /folder/type = 'inbox' is the Inbox folder /folder/type = 'sent' is the Sent Items folder /folder/type = 'drafts' is the Drafts folder /folder/type = 'deleted' is the Deleted Items folder These four special folders will always exist in a provisioned .NET Inbox account. They can never be deleted or modified. To create user defined folders, you can use the standard .NET My Services insert method and set the type to 'custom'. Custom folders can be deleted or modified. <xsd:sequence>
<xsd:element name="name" type="hs:localizableString">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the name of the e-mail folder. For the four special folders,
</xsd:documentation>
this element is read only. For custom folders, this element can be edited.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains a type identifier for this folder. And will contain the value
</xsd:documentation>
'inbox, 'sent', 'drafts' or 'delete' for the four special folders. For all other folders, this value will be 'custom'
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The calculated count of the unread messages associated with this folder. This element is read only.
</xsd:documentation>
<xdb:system type="calculatedFieldEarlyBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains a ref attribute that specifies the ID of the parent folder.
</xsd:documentation>
For top-level folders, this attribute == "". This attribute cannot be set on the four special folders as they must always remain top level folders
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This calculated attribute indicates how many subfolders that folder contains. See also 'parentFolder'.
</xsd:documentation>
<xdb:system type="calculatedFieldEarlyBound"/>
</xsd:appinfo>
<!--
// // folderTypeEnum // -->
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="inbox"/>
</xsd:restriction>
<xsd:enumeration value="drafts"/>
<xsd:enumeration value="deleted"/>
<xsd:enumeration value="sent"/>
<xsd:enumeration value="custom"/>
<!--
// // messageType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element defines a single message in myInbox in the base schema. A message represents an email and is
</xsd:documentation>
divided into two sub-groups 'messageStatus' and 'messageContent'. <xsd:sequence>
<xsd:element name="messageStatus" type="messageStatusType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the status of the email and frequently changes. Caching clients should take
</xsd:documentation>
advantage of this when deciding which part of the message to change
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the content of the message. This data changes rarely in a normal application.
</xsd:documentation>
<!--
// // messageStatusType // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element name="isRead" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the read/unread state of the message and can be modified.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the single folder that this message logically belongs to.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element defines the flag state of the message. It includes an {any} element
</xsd:documentation>
that can be used for extensible flags.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the sent/received state of the message. This element is read only, which
</xsd:documentation>
means that it can be queried for, but not updated <!--
// // sendMessageStatusType // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element minOccurs="0" name="saveInFolder" type="refType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the folder that a copy of this message should be saved in.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element defines the flag state of the message. It includes an {any} element
</xsd:documentation>
that can be used for extensible flags. <!--
// // localMessageStatusType // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element name="isRead" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the read/unread state of the message and can be modified.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the single folder that this message logically belongs to.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element defines the flag state of the message. It includes an {any} element
</xsd:documentation>
that can be used for extensible flags.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the sent/received state of the message.
</xsd:documentation>
<!--
// // messageTypeEnum // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="voice"/>
</xsd:restriction>
<xsd:enumeration value="subscription"/>
<xsd:enumeration value="fax"/>
<xsd:enumeration value="dsn"/>
<xsd:enumeration value="readReceipt"/>
<xsd:enumeration value="meetingResponse"/>
<xsd:enumeration value="meetingRequest"/>
<xsd:enumeration value="email"/>
<xsd:enumeration value="liveEmail"/>
<!--
// // draftTypeEnum // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="voice"/>
</xsd:restriction>
<xsd:enumeration value="subscription"/>
<xsd:enumeration value="fax"/>
<xsd:enumeration value="dsn"/>
<xsd:enumeration value="readReceipt"/>
<xsd:enumeration value="meetingResponse"/>
<xsd:enumeration value="meetingRequest"/>
<xsd:enumeration value="email"/>
<xsd:enumeration value="liveEmail"/>
<!--
// // messageStateEnum // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="sent"/>
</xsd:restriction>
<xsd:enumeration value="received"/>
<!--
// // localMessageStateEnum // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="sent"/>
</xsd:restriction>
<xsd:enumeration value="received"/>
<!--
// // draftStateEnum // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="draft"/>
</xsd:restriction>
<!--
// // messageContentType // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains a reference to the /myInbox/account element that this message was sent to.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The subelements of this element describe the contents of the message.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains the size, in bytes, of the entire RFC2822 message in the store.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element indicates the importance of this message. The value can be 'low', 'normal', or 'high'.
</xsd:documentation>
The default is 'normal'.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element indicates the sensitivity of the message. The value
</xsd:documentation>
can be 'normal', 'personal', 'private', or 'confidential'.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element indicates whether a message has one or more attachments. The value will either be 0
</xsd:documentation>
(to indicate that the message has no attachments) or 1 (to indicate that the message has one or more attachments).
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This read only element is set by the myInbox service when the message was delivered and indicates
</xsd:documentation>
if the message was marked as junk mail by the junk mail filter.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This read only element is set by the myInbox service when the message was delivered and indicates
</xsd:documentation>
if the message was determined to contain adult content by the adult content mail filter. <!-- optional element -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element identifies the 'conversation,' or e-mail thread of which this message
</xsd:documentation>
is a part. <!-- optional element -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element identifies the 'conversation,' or e-mail thread of which this message
</xsd:documentation>
is a part.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This read-only element contains the UTC date/time the message was received, and
</xsd:documentation>
appears in all messages except ones that were sent by the user.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This read-only element contains the UTC date/time the message was sent. For /messsage/messageStatus/state="sent"
</xsd:documentation>
messages, this element represents the time the message was sent. For /messsage/messageStatus/state="received" this element represents the time the sender sent the message.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The subject of the message. This element contains both a prefix and text sub-elements to allow clients
</xsd:documentation>
to sort on the non-prefix part of the subject (so RE: RE: doesn't get sorted)
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Specifies the recipient of this message and where they appear. A collection of recipient elements is
</xsd:documentation>
only returned if the query option 'expandRecipients' is specified.
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The plain body representation of the message.
</xsd:documentation>
This element is returned by passing the 'includeSimpleMessageView' element in query options
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The html body representation of the message. This element can also contain inline attachments that are
</xsd:documentation>
related to the html content via the 'uri' element of the inline attachment. This element is returned by passing the 'includeSimpleMessageView' element in query options.
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element represents a mail attachment and is returned by passing the 'includeSimpleMessageViewAttachments' element in query options.
</xsd:documentation>
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The element and it's children define the message structure (including the mime body)
</xsd:documentation>
This element is returned by passing the 'includeMessagePartStructure' element in query options
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The first 256 characters of the message body. This element is only returned if the query option
</xsd:documentation>
'includePreview' is specified.
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="single2822Header" type="single2822HeaderType">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The rfc2822 headers not included in the base schema (ex: x-apparently-to)
</xsd:documentation>
This element is returned by passing the 'includeSingle2822Headers' element in query options
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The raw 2822 message (including headers and body)
</xsd:documentation>
This element is returned by passing the includeRaw2822Contentelement in query options
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The raw rfc2822 headers not included in the base schema (ex: x-apparently-to)
</xsd:documentation>
This element is returned by passing the 'includeRaw2822Headers' element in query options
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<!--
// // completeMessageContentType // -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // draftType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element defines a single draft in myInbox in the base schema. A draft represents an unsent email and is
</xsd:documentation>
divided into two sub-groups 'messageStatus' and 'messageContent'. <xsd:sequence>
<xsd:element name="draftStatus" type="draftStatusType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The contents of this element represent the status metadata of the draft.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The contents of this element represent the content of the draft.
</xsd:documentation>
<!--
// // draftStatusType // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element name="isRead" type="xsd:boolean">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the read/unread state of the message and can be modified.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the single folder that this message logically belongs to.
</xsd:documentation>
For drafts this must always point to the drafts folder
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element defines the flag state of the message. It includes an {any} element
</xsd:documentation>
that can be used for extensible flags.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The value of this element will always be 'draft' and is provided for compatability with messages
</xsd:documentation>
<!--
// // draftContentType // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="cat" type="hs:catType"/>
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains a reference to the /myInbox/account element ref that this message should be sent from
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The subelements of this element describe the contents of the message.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This read only element contains the size, in bytes, of the entire RFC2822 message in the store.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element indicates the importance of this message. The value can be 'low', 'normal', or 'high'.
</xsd:documentation>
The default is 'normal'.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element indicates the sensitivity of the message. The value
</xsd:documentation>
can be 'normal', 'personal', 'private', or 'confidential'.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This read only element indicates whether a message has one or more attachments. The value will either be 0
</xsd:documentation>
(to indicate that the message has no attachments) or 1 (to indicate that the message has one or more attachments). <!-- optional element -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element identifies the 'conversation,' or e-mail thread of which this message
</xsd:documentation>
is a part. <!-- optional element -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This optional element identifies the 'conversation,' or e-mail thread of which this message
</xsd:documentation>
is a part.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The subject of the message. This element contains both a prefix and text sub-elements to allow clients
</xsd:documentation>
to sort on the non-prefix part of the subject (so RE: RE: doesn't get sorted)
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This read-only element describes who this message is from. To set this value, set the account element.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Specifies the recipient of this message and where they appear.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The html body representation of the draft. This element can optionally contain inline
</xsd:documentation>
attachments
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The element and it's children define the message structure (including the mime body)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The first 256 characters of the message body. This element is only returned if the query option
</xsd:documentation>
'includePreview' is specified.
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="single2822Header" type="single2822HeaderType">
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The rfc2822 headers not included in the base schema (ex: x-apparently-to)
</xsd:documentation>
This element is returned by passing the 'includeSingle2822Headers' element in query options
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The raw 2822 message (including headers and body)
</xsd:documentation>
This element is returned by passing the includeRaw2822Contentelement in query options
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The raw rfc2822 headers not included in the base schema (ex: x-apparently-to)
</xsd:documentation>
This element is returned by passing the 'includeRaw2822Headers' element in query options
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<!--
// // htmlBodyType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element represents the html body of a message or draft.
</xsd:documentation>
<xsd:sequence>
<xsd:element name="body" type="xsd:string">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="inlineAttachment" type="inlineAttachmentType">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // inlineAttachmentType // -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element name="uri" type="xsd:string">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The client defined unique identifier for the inline attachment. This element is used to identify
</xsd:documentation>
this attachment location within the html body of a message
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // attachmentType // -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:sequence>
<xsd:element name="name" type="xsd:string">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The unique order that this attachment should appear relative to all other attachments.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // draftMessagePointerType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Rules specify actions that should be performed on the active message during sending or delivery.
</xsd:documentation>
<xsd:sequence>
<xsd:element minOccurs="0" name="saveInFolder" type="refType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the folder that a copy of this message should be saved in.
</xsd:documentation>
<!--
// // ruleType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Rules specify actions that should be performed on the active message during sending or delivery.
</xsd:documentation>
<xsd:sequence>
<xsd:element name="name" type="hs:localizableString">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The application-defined, human readable identifier of the rule.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This required attribute specifes where the rule must run. The only allowable value
</xsd:documentation>
to date is 'server'.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This required attribute specifes when the rule must run. The only allowable values
</xsd:documentation>
are 'sending' and 'receiving'.
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The application-defined provider of the rule. This is provided so that multiple applicaions
</xsd:documentation>
can (if they so desire) only alter their own rules.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element's select attribute specifies the xpath expression used to evaluate if the this
</xsd:documentation>
rule applies to the active message.
<!-- empty content -->
</xsd:complexType>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This attribute specifies an xpath expression used to determine if this rule applies
</xsd:documentation>
to the active message. Because rules only apply to messages, this statement must be scoped to the message element: Legal examples: "./importance = 'high'" "./from/email = 'someone@microsoft.com' and contains(./subject/full, 'hello')" Illegal examples: "/myInbox/message[./importance = 'high']" "/myInbox/folder" "/myInbox/rule"
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Specifies an individual action to perform if the select element
</xsd:documentation>
matches minOccurs-maxOccurs messages.
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="1" minOccurs="0" name="copyMessage" type="copyMessageActionType"/>
</xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="0" name="forwardAsAttachment" type="forwardAsAttachmentActionType"/>
<xsd:element maxOccurs="1" minOccurs="0" name="stopProcessingRulesOfThisType" type="stopProcessingRulesOfThisTypeType"/>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This required attribute specifes the order that this action should be performed
</xsd:documentation>
in relative to all other actions for this rule.
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This required attribute specifes the order that this action should be performed
</xsd:documentation>
in relative to all other actions for this rule. <!--
// // runatType // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="server"/>
</xsd:restriction>
<!--
// // runwhenType // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="sending"/>
</xsd:restriction>
<xsd:enumeration value="receiving"/>
<!--
// // ruleStateType // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="enabled"/>
</xsd:restriction>
<xsd:enumeration value="disabled"/>
<xsd:enumeration value="invalid"/>
<!--
// // ruleTypeType // -->
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="oof"/>
</xsd:restriction>
<xsd:enumeration value="normal"/>
<!--
// // rule condition types // --> <!--
// // copyMessageActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This action is used to copy the active message in rules processing to another folder specified by the
</xsd:documentation>
'targetFolder' element <xsd:sequence>
</xsd:sequence>
<!--
// // moveMessageActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should be moved to the targetFolder
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!--
// // deleteMessageActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should be deleted
</xsd:documentation>
<!--
// // assignCategoryActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should have the included cat element added to it.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!--
// // forwardMessageActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should be forwarded to the included recipients.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!--
// // forwardAsAttachmentActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should be forwarded to the included recipients as an attachment.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!--
// // serverReplyActionType // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="1" minOccurs="1" name="subject" type="subjectType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
A plain text simple body that should be sent from the server.
</xsd:documentation>
<!--
// // redirectMessageActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should be redirected to the included recipient.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!--
// // flagMessageActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should have the included flag added to it.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
<!--
// // markAsReadActionType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Used in rule actions to indicate that the active message should be marked as read.
</xsd:documentation>
<!--
// // accountType Request // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Represents a provisioned users' email account. This element can optionally contain POP3 settings
</xsd:documentation>
for myInbox services that support POP3 aggregation. <xsd:sequence>
<xsd:element name="name" type="hs:localizableString">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines this account as a primary or non-primary account. There can be
</xsd:documentation>
only one primary account and it can never be deleted.
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
If this account is a POP3 account, this defines pop3 settings. Note that the primary
</xsd:documentation>
account can not be a POP3 account. <!--
// // common type definitions // // // messageTypeType definition (funny name, huh?) // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element name="type" type="messageTypeEnum">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains a value that provides the client with enough information to
</xsd:documentation>
render an 'Inbox' view of the messages. Valid values are 'voice', 'subscription', 'fax', 'dsn', 'readReceipt', 'meetingResponse', 'meetingRequest', 'email' or 'liveEmail'.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The contentType of the message (in accordance with RFC 2045). Examples of this are:
</xsd:documentation>
'text/plain' and 'multipart/mime'. <!--
// // common type definitions // // // messageTypeType definition (funny name, huh?) // -->
<xsd:sequence>
</xsd:complexType>
<xsd:element name="type" type="messageTypeEnum">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains a value that provides the client with enough information to
</xsd:documentation>
render an 'Inbox' view of the messages. Valid values are 'voice', 'subscription', 'fax', 'dsn', 'readReceipt', 'meetingResponse', 'meetingRequest', 'email' or 'liveEmail'.
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The contentType of the message (in accordance with RFC 2045). Examples of this are:
</xsd:documentation>
'text/plain' and 'multipart/mime'. <!--
// // importanceType definition // -->
<xsd:annotation>
</xsd:simpleType>
<xsd:documentation>
</xsd:annotation>
This element indicates the importance of this message. The value can be 'low', 'normal', or 'high'.
</xsd:documentation>
The default is 'normal' <xsd:restriction base="xsd:string">
<xsd:enumeration value="low"/>
</xsd:restriction>
<xsd:enumeration value="normal"/>
<xsd:enumeration value="high"/>
<!--
// // sensitivityType // -->
<xsd:annotation>
</xsd:simpleType>
<xsd:documentation>
</xsd:annotation>
This element indicates the sensitivity of the message. The value
</xsd:documentation>
can be 'normal', 'personal', 'private', or 'confidential'. If the identity using the .NET Inbox service is a member of the 'assistant' role, that identity will not have read access to e-mail messages that have a value other than 'normal'. <xsd:restriction base="xsd:string">
<xsd:enumeration value="normal"/>
</xsd:restriction>
<xsd:enumeration value="personal"/>
<xsd:enumeration value="private"/>
<xsd:enumeration value="confidential"/>
<!--
// // conversationIdType definition // -->
<xsd:annotation>
</xsd:simpleType>
<xsd:documentation>
</xsd:annotation>
This element identifies the 'conversation' or e-mail thread of which this message belongs
</xsd:documentation>
<!--
// // conversationIndexType definition // -->
<xsd:annotation>
</xsd:simpleType>
<xsd:documentation>
</xsd:annotation>
This element identifies the index of the conversation to which this message belongs. It is directly
</xsd:documentation>
related to conversationId. <!--
// // emailType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Specifies an e-mail address and display name, or the PUID that represents them.
</xsd:documentation>
<xsd:sequence>
<xsd:element name="name" type="hs:localizableString">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // emailToCcType // -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="emailType">
</xsd:complexContent>
<xsd:attribute name="type" use="required">
</xsd:extension>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
Specifies whether the recipient is in the 'to' or 'cc' list
</xsd:documentation>
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="to"/>
</xsd:restriction>
<xsd:enumeration value="cc"/>
<!--
// // emailToCcBccType // -->
<xsd:annotation>
</xsd:annotation>
</xsd:complexType>
<xsd:complexContent>
<xsd:extension base="emailType">
</xsd:complexContent>
<xsd:attribute name="type" use="required">
</xsd:extension>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
Specifies whether the recipient is in the 'to', 'cc' or 'bcc' list
</xsd:documentation>
<xsd:restriction base="xsd:string">
</xsd:simpleType>
<xsd:enumeration value="to"/>
</xsd:restriction>
<xsd:enumeration value="cc"/>
<xsd:enumeration value="bcc"/>
<!--
// // subjectType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
The complete prefix and text of a subject. prefix is separated by
</xsd:documentation>
the server to allow sorting on the actualy subject of the message. <xsd:sequence>
<xsd:element name="prefix" type="hs:string">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The subject of a message minus the prefix (ex: 'hello there')
</xsd:documentation>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This required attribute is used to specify an ISO 639 language code
</xsd:documentation>
or an ISO 3166 country code as described in <a href="http://www.ietf.org/rfc/rfc1766.txt">RFC 1766</a>
.
The value of this attribute indicates the language type of the content within this element.
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This optional attribute specifies the default layout direction
</xsd:documentation>
for the localized string. Valid values are rtl (right to left), and ltr (left to right). <!--
</xsd:simpleType>
// // emailAddressType // --> <!--
// // targetFolderType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element specifies the folder to save the message to. If omitted, the message
</xsd:documentation>
is saved in the drafts folder.
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
The location of the folder to which save the message.
</xsd:documentation>
For example, /myInbox/folder[@id=""]. <!--
// // flagType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This optional element defines the flag state of the message. It includes an {any} element
</xsd:documentation>
that can be used for extensible flags. <xsd:sequence>
<xsd:element name="state" type="flagStateType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // flagStateType // -->
<xsd:annotation>
</xsd:annotation>
</xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="flagged"/>
</xsd:restriction>
<xsd:enumeration value="completed"/>
<xsd:enumeration value="none"/>
<!--
// // single2822HeaderType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element represents a raw header not included in the base schema
</xsd:documentation>
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
</xsd:simpleContent>
<!-- for some reason, this is causing xsd to break
</xsd:extension>
//look into it and fix it <xsd:attribute name="name" use="required"> <xsd:annotation> <xsd:documentation> The name of the raw rfc822 header (ex: x-apparently-to) </xsd:documentation> </xsd:annotation> </xsd:attribute> --> <!--
// // replyToType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
This element is used to specify one or more recipients that this message
</xsd:documentation>
should be delivered to, if the identity who receives the message chooses to reply. <xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="recipient" type="emailToCcType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // messagePartType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
messageParts define the part structure of the message (including the mime parts)
</xsd:documentation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="parentPart" type="refType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the order of this part relative to its siblings
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the contentType of the part. Ex: message/rfc or text/plain.a
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The size in bytes of the message part (including mime headers)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The element defines the content-disposition of the part ex: attachment; filename="txt1.txt"
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The element defines the content-transfer-encoding of this part.
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This elements contains the content of this message part and is only returned by including the
</xsd:documentation>
'includePartContent' element in the query options.
<xdb:system type="calculatedFieldLateBound"/>
</xsd:appinfo>
<xsd:annotation>
</xsd:annotation>
</xsd:attribute>
<!--
// // draftPartType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
Defines the part structure of the draft (including the mime parts)
</xsd:documentation>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="parentPart" type="refType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the order of this part relative to its siblings
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element defines the contentType of the part. Ex: message/rfc or text/plain.a
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The size in bytes of the message part (including mime headers)
</xsd:documentation>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The element defines the content-disposition of the part ex: attachment; filename="txt1.txt"
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The element defines the content-transfer-encoding of this part.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // pop3SettingsType // -->
<xsd:annotation>
</xsd:complexType>
<xsd:documentation>
</xsd:annotation>
For myInbox services that support POP3 aggregation, this element defines the POP3 settings
</xsd:documentation>
necessary for the myInbox service to locate and download messages from that account. <xsd:sequence>
<xsd:element name="server" type="hs:string">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // myInbox specific methods // --> <!--
// // sendMessage Request // -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This method is used to send a message from myInbox. It takes either a pointer to a draft
</xsd:documentation>
message to send, or a raw message that represents a full RFC2822/Mime message. This method is accessed using a request message, and in response may generate a domain-specific response message, or may generate a SOAP fault message. The types used in these messages are fully specified in the services base schema document referenced above. The following sample document fragments illustrate the structure and meaning of the elements and attributes in the request and response messages.
<xsd:sequence>
</xsd:complexType>
<!-- TODO: make this a choice -->
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element is used to identify an existing draft to send.
</xsd:documentation>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // sendMessage Response // -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The response to sendMessage is used to indicate the success of the operation as well
</xsd:documentation>
as the new id associated with any messages that were saved as a result of this method.
<xsd:sequence>
</xsd:complexType>
<xsd:element name="newBlueId" type="hs:newBlueIdType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // saveMessage Request // -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This method is used to save a local message (for example in a PST file) into myInbox.
</xsd:documentation>
This method is accessed using a request message, and in response may generate a domain-specific response message, or may generate a SOAP fault message. The types used in these messages are fully specified in the services base schema document referenced above. The following sample document fragments illustrate the structure and meaning of the elements and attributes in the request and response messages.
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="1" minOccurs="0" name="completeLocalMessage" type="completeLocalMessageType">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element represents a complete local message to add to myInbox.
</xsd:documentation>
<!--
// // saveMessage Response // -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The saveMessage response contains a newBlueId for each message that was successfully saved.
</xsd:documentation>
<xsd:sequence>
</xsd:complexType>
<xsd:element name="newBlueId" type="hs:newBlueIdType">
</xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<!--
// // copyMessage Request // -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This message allows clients to copy one or more messages to a folder. The message data
</xsd:documentation>
(including attachments) is copied and new message messages are returned with unique message ID values. This element encapsulates the arguments to the copyMessage method. It must contain a message element and a targetFolder element.
<xsd:sequence>
</xsd:complexType>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="message">
</xsd:sequence>
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
This element contains a select statement that contains an XPATH expression
</xsd:documentation>
indicating a message message for which to copy the associated message.
<xsd:attribute name="select" type="hs:selectType" use="required">
</xsd:complexType>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
The location of the message (which is associated with the message) to copy.
</xsd:documentation>
For example, /myInbox/message[@id=""].
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
If this value is present and set to true, the message is copied as a draft into the target folder
</xsd:documentation>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
This attribute specifies that the server should use the value of this attribute as the id of the new message.
</xsd:documentation>
useClientIds should be present on the copyRequest element and set to true
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
Contains the id of an existing folder to copy the message(s) to.
</xsd:documentation>
<xsd:annotation>
</xsd:attribute>
<xsd:documentation>
</xsd:annotation>
If this optional attribute is present, each message elements id attribute will be used as the new id
</xsd:documentation>
<!--
// // copyMessage Response // -->
<xsd:annotation>
</xsd:element>
<xsd:documentation>
</xsd:annotation>
The response from copyMessage includes a newBlueId element for each successfully copied message.
</xsd:documentation>
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!--
// // rawMessageType // -->
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!--
// // completeLocalMessageType // -->
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
<!--
</xsd:complexType>
// // refType // --> <!--
// // queryOptions // --> <!--
<xsd:element name="markAsRead"> <xsd:annotation> <xsd:documentation> This query option will mark and returned unread messages as read </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="calculatePreview"> <xsd:annotation> <xsd:documentation> This query option return the first 256 characters of the message in the /message/messageContent/preview element </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="expandRecipients"> <xsd:annotation> <xsd:documentation> This query option return the the complete recipient list as a collection of /message/messageContent/recipient elements </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="includeRaw2822Headers"> <xsd:annotation> <xsd:documentation> This query option returns the the complete raw 2822 message header stream in the element /message/messageContent/raw2822Headers </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="includeRaw2822Content"> <xsd:annotation> <xsd:documentation> This query option returns the the complete raw 2822 message stream (including headers) in the element /message/messageContent/raw2822Content </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="includeSingle2822Headers"> <xsd:annotation> <xsd:documentation> This query option returns and xml version of all 2822 headers in a collection of /message/messageContent/raw2822Content single2822Header </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="includeSimpleMessageViewAttachments"> <xsd:annotation> <xsd:documentation> TODO </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:element name="includeSimpleMessageView"> <xsd:annotation> <xsd:documentation> TODO </xsd:documentation> </xsd:annotation> </xsd:element> --> </xsd:schema>
|