Export (0) Print
Expand All

2.1.3.4 Attachments

Each Attachment object in a Message object represents one attachment. MIME writers SHOULD classify Attachment objects based on the value of the PidTagAttachMethod property ([MS-OXCMSG] section 2.2.2.9), as specified in the following table.

PidTagAttachMethod property value

Attachment object classification

5

Embedded Message object attachments

6

OLE attachments

All other values

Ordinary file attachments

Note that ordinary file attachments can contain additional Macintosh-specific data. These attachments require special handling, as specified in section 2.1.3.4.3.

MIME writers SHOULD generate a vCard 3.0 attachment when generating contact (3) information in a MIME message, as specified in section 2.1.3.4.6.

Additionally, MIME writers SHOULD classify Attachment objects as inline or not inline, as specified in section 2.1.3.4.1.

MIME writers SHOULD generate different MIME structures for the message depending on the presence of inline and non-inline attachments, as specified in the following three examples:

If both inline and non-inline attachments are present, MIME writers SHOULD generate the structure shown in the following figure. For an example of this structure, see section 3.1.2.

Ee202889.4fdc8d13-79ca-431f-860c-d26227ea94b1(en-us,EXCHG.80).jpg

Figure 1: Inline and non-inline attachments present

If only inline attachments are present, MIME writers SHOULD generate the structure shown in the following figure. For an example of this structure, see section 3.1.3.

Ee202889.6209bd88-2bdf-497a-96d1-191389410ca4(en-us,EXCHG.80).jpg

Figure 2: Only inline attachments present

If only non-inline attachments are present, MIME writers SHOULD generate the structure shown in the following figure. For an example of this structure, see section 3.1.4.

Ee202889.1ff8bb77-d80f-428b-a49e-97ec5ce070c2(en-us,EXCHG.80).jpg

Figure 3: Only non-inline attachments present

Show:
© 2014 Microsoft