2.1.3.2.4 Type: PHOTO
RFC reference: [RFC2425] section 3.1.4.
vCard data format: PHOTO; ENCODING=b; TYPE=<type>:<data>
Brief description: An image or photograph that illustrates some aspect of the object that the vCard represents.
Importing to Contact Objects
The binary data for the associated photo is stored as an attachment. For more details about Message object attachments, see [MS-OXCMSG] section 2.2.2. The properties listed in the following table MUST be set on the Attachment object, as specified in [MS-OXCMSG].
|
Attachment object property |
Reference |
Value |
|---|---|---|
|
PidTagAttachmentContactPhoto |
[MS-OXOCNTC] section 2.2.1.8.3 |
TRUE. |
|
PidTagAttachDataBinary |
[MS-OXCMSG] section 2.2.2.7 |
Photo stream in binary format. |
|
PidTagAttachExtension |
[MS-OXCMSG] section 2.2.2.12 |
".jpeg", ".bmp", ".gif", or ".png", according to the TYPE parameter. |
|
PidTagAttachLongFilename |
[MS-OXCMSG] section 2.2.2.10 |
"ContactPhoto.<ext>". The extension is the value of the TYPE parameter. |
Only binary data types with the ENCODING parameter set to "b" are supported. The TYPE parameter MUST be one of the following image type values:
.bmp
.gif
.jpeg
.png
Exporting from Contact Objects
The PHOTO type is exported from the Attachment object with the ENCODING parameter set to "b" and the TYPE parameter set to the image type (.bmp, .gif, .jpeg, or .png). The image is exported in binary format, as specified in [RFC2047] section 4.