title: "MAPI �t�H���_�[���\������܂��B" ms.author: v-tirob author: v-tirob manager: soliver ms.date: 3/9/2015 ms.audience: Developer ms.topic: overview ms.prod: office-online-server localization_priority: Normal api_type:

適用対象: Outlook 2013 | Outlook 2016

A receive folder holds inbound messages of a particular message class. Receive folder associations can be established by clients, by the message store provider, or by MAPI. MAPI has two default receive folders: the root folder of the message store, and the Inbox folder of the interpersonal message (IPM) subtree. The root folder of the message store is the default receive folder for all interprocess communication (IPC) messages.

The Inbox folder is created by MAPI for every new message store and acts as the default receive folder for the following message classes:

• IPM ���b�Z�[�W �N���X�ł��B

• ���|�[�g�̃��b�Z�[�W �N���X�ł��B

• ��̏ꍇ�A�܂��͕s�����Ă���A�N���X�łł��B

All report messages, even those sent in response to an IPC message, are placed in the Inbox folder. IPC client applications that process their own reports must explicitly add a receive folder for the particular class of report. For example, if a client expects to receive messages with the class IPC.Paper.Order, it should call the IMsgStore::SetReceiveFolder method to establish a receive folder for reports with the class Report.IPC.Paper.Order.

Receive folder associations are based on the hierarchical organization of message classes. Clients can explicitly establish an association between a receive folder and a message class or use the MAPI default receive folders. Typically, clients designate one folder to receive messages for a base class and all of its subclasses. For example, a typical client would establish an association for messages with the class MyClass. Then if the client received messages with classes MyClass.Home or MyClass.Home.Kitchen.Computer, these messages would go to the receive folder for the base class, MyClass.

�X�g�A�g�p���@��N���C�A���g�𑀍삷��ɂ́A�t�H���_�[���\������鎟�� 3 �‚̃��b�Z�[�W������܂��B

• IMsgStore::GetReceiveFolderTable

• IMsgStore::GetReceiveFolder

• IMsgStore::SetReceiveFolder

The receive folder table is a listing of information about all of the receive folders established for a message store. Its required column set includes the message class, record key, and entry identifier.

To retrieve a receive folder for a particular message class, clients pass the message class string to the IMsgStore::GetReceiveFolder method. The message store provider returns an entry identifier for the corresponding folder. To implement GetReceiveFolder, a message store provider should use an algorithm that selects the folder whose associated message class matches the longest possible prefix of the specified message class. For example, assume the message store has the following associations between receive folders and message classes in its receive folder table:

• IPM���b�Z�[�W�́A��M�g���C] �t�H���_�[�Ɋi�[����܂��B

• IPM.Note.Sample���b�Z�[�W�́A[�T���v��] �t�H���_�[�Ɋi�[����܂��B

�K�؂Ȃ��܂��܂ȃN���X�Ń��b�Z�[�W��ǂ̂悤�Ƀ��[�e�B���O����A���̕\�ł́A�t�H���_�[���\������܂��B

Clients call the SetReceiveFolder method to make an explicit association between a particular message class and receive folder. When a message is delivered to an empty message class, MAPI places the message in the receive folder that is defined for a prefix of the empty class. For example, if your client has a receive folder established for messages with class IPM and a message with class IPM.Note.Test is delivered, this message will be placed in the receive folder for the IPM message class.

SetReceiveFolder を呼び出す場合、クライアントは通常、メッセージ クラス文字列と新しい受信フォルダーのエントリ識別子を渡します。 ただし、クライアントは、これらのパラメーターの一方または両方に対して NULL を渡すことができます。 次の表では、メッセージ クラスとエントリ識別子パラメーターに NULL を指定した結果の動作について説明します。

メッセージのクラスを空にしないでくださいが、空のメッセージ クラスが発生する可能性があります。 空のクラスを持つ新しい送信メッセージの場合、メッセージ クラスを IPM に割り当てるのはメッセージ ストアの責任です。IPM を割り当てるのはトランスポート プロバイダーの責任 です。 空のクラスを持つ受信メッセージの クラスとして注意してください。

関連項目

[MAPI �t�H���_�