2.1.3.1.1.20.2 Property: ATTENDEE

RFC Reference: [RFC2445] section 4.8.4.1

Number of Instances Allowed: 0+

Format: Calendar User Address ([RFC2445] section 4.3.3)

Brief Description: An attendee for a meeting.

Importing to Calendar objects

If this property has the special value 'invalid:nomail', then the CN of this attendee SHOULD<77> be added to a list delimited by "; " (Unicode character U+003B followed by U+0020) in the appropriate string property, as specified in the following table. If an attendee matches more than one row in the following table, the first matching row applies.

CUTYPE

ROLE

Append CN to...

RESOURCE

(any)

PidLidNonSendableBcc ([MS-OXPROPS] section 2.177)

ROOM

(any)

PidLidNonSendableBcc

(any)

OPT-PARTICIPANT

PidLidNonSendableCc ([MS-OXPROPS] section 2.178)

(any)

NON-PARTICIPANT

SHOULD<78> import to PidLidNonSendableBcc, MAY<79> import to PidLidNonSendableCc

(any)

(any)

PidLidNonSendableTo ([MS-OXPROPS] section 2.179)

If this property is not 'invalid:nomail', it SHOULD<80> be parsed as a valid mailto URI (as specified in [RFC2368]). The resulting SMTP address SHOULD<81> be resolved against the address book [MS-OXOABK]. If no match was found, a one-off EntryID ([MS-OXCDATA] section 2.2.5.1) MUST be created using the SMTP address and the CN parameter. The Address Book object MUST be added to the recipient table of the Calendar object with properties specified in the following table.

Recipient Table Property

Value

PidTagAddressType ([MS-OXPROPS] section 2.567)

Resolved from the address book (see above). In the case of a one-off, set to 'SMTP'.

PidTagDisplayName

Resolved from the address book (see above). In the case of a one-off, set to the value of the CN parameter.

PidTagDisplayType ([MS-OXPROPS] section 2.670)

Set to 0x00000000<82>

PidTagEmailAddress ([MS-OXPROPS] section 2.672)

Resolved from the address book (see above). In the case of a one-off, set to the SMTP address parsed from the mailto URI.

PidTagEntryId ([MS-OXPROPS] section 2.674)

Resolved from the address book (see above). In the case of a one-off, use the one-off EntryID.

PidTagRecipientDisplayName ([MS-OXPROPS] section 2.890)

Copy of PidTagDisplayName<83>

PidTagRecipientEntryId ([MS-OXPROPS] section 2.891)

Copy of PidTagEntryId<84>

PidTagRecipientFlags ([MS-OXPROPS] section 2.892)

Set to 0x00000001<85>

PidTagRecipientType ([MS-OXPROPS] section 2.900)

See the next table.<86>

PidTagRecipientTrackStatus ([MS-OXPROPS] section 2.898)

Import from PARTSTAT as follows:<87>

PARTSTATPidTagRecipientTrackStatus
ACCEPTED0x00000003
DECLINED0x00000004
TENTATIVE0x00000002
(Any other value)0x00000000

 

PidTagRecipientTrackStatusTime ([MS-OXPROPS] section 2.899)

Import from X-MS-OLK-RESPTIME (as specified in section 2.1.3.1.1.20.2.6) if present.<88>

The correct value of PidTagRecipientType SHOULD<89> be determined based on the CUTYPE and ROLE (as specified in section 2.1.3.1.1.20.2.4) parameters as specified in the following table. If an attendee matches more than one row in the following table, the first matching row applies.

CUTYPE

ROLE

PidTagRecipientType

(Any)

CHAIR

0x00000001

(Any)

REQ-PARTICIPANT

0x00000001

(Any)

OPT-PARTICIPANT

0x00000002

RESOURCE

(Any)

0x00000003

ROOM

(Any)

0x00000003

(Any)

NON-PARTICIPANT

0x00000003<90>

(Any)

(Any)

0x00000001

Exporting from Calendar objects

If the 0x00000001 flag of PidLidAppointmentStateFlags ([MS-OXPROPS] section 2.30) is 0, then attendee properties SHOULD NOT<91> be exported.

Each row in the recipient table of the Calendar object that satisfies the constraints in the following table MUST be exported as an attendee property. The value of the property MUST be a mailto URI (as specified in [RFC2368]) with the SMTP address of the recipient from the address book [MS-OXOABK]. If the recipient does not have an SMTP address, then the value of the property SHOULD<92> be set to 'invalid:nomail'.

Recipient Table Property

Constraint

PidTagRecipientFlags

The bit denoted by 0x00000020 MUST be 0 and the bit denoted by 0x00000002 MUST be 0

PidTagRecipientType

MUST NOT be 0x00000000

In addition, each of the semicolon-delimited entries in PidLidNonSendableTo and PidLidNonSendableCc SHOULD<93> be exported with a URI of 'invalid:nomail'. For handling of PidLidNonSendableBcc, see 2.1.3.1.1.20.21.

Show: