Share via

6 Appendix A: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft Exchange Server 2003

  • Microsoft Exchange Server 2007

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 2016

  • Microsoft Exchange Server 2019

  • Microsoft Office Outlook 2003

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Microsoft Outlook 2016

  • Microsoft Outlook 2019

  • Microsoft Outlook 2021

  • Microsoft Outlook LTSC 2024

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.2.1.7: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 support whatever the Microsoft Windows API WINMM!PlaySound is able to play.

<2> Section 2.2.1.9: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 preserve the value if already set.

<3> Section 2.2.2.3.1: Office Outlook 2003 does not set the PidLidTaskDueDate property ([MS-OXOTASK] section 2.2.2.2.5) for Message objects other than Task objects, so when a reminder signals for a Message object that can be flagged, the "due in" time is calculated based on the value of the PidLidReminderTime property (section 2.2.1.4). Microsoft Office Outlook 2007 Service Pack 1 does set the PidLidTaskDueDate property for Message objects that can be flagged and so has a more intuitive "due in" time when the reminder signals. Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not set the PidLidTaskDueDate property for tasks when the user only specifies a reminder on a Task object without also specifying a due date. In other words, this property can be set on a Task object in the context of setting a due date. The task due date is independent of the signal time. For more information about the conditions under which the PidLidTaskDueDate property is set on a Task object, see [MS-OXOTASK].

<4> Section 3.1.3.1: Office Outlook 2003 follows the minimal reminder domain scope strategy.

<5> Section 3.1.3.1: Office Outlook 2003 does not set the piReminderUpgradeTime property (section 2.2.3.1). Under normal operation, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not change the piReminderUpgradeTime property after the value is initialized. However, when the "cleanreminders" feature is invoked via command-line parameter, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 set the piReminderUpgradeTime property to 0 to clean the reminders search folder (1), after which all reminders would be eligible to signal again.

<6> Section 3.1.4.1.2: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 set the PidTagReplyTime property ([MS-OXOFLAG] section 2.2.3.1) when setting a reminder on a Message object that is already flagged. Setting the PidTagReplyTime property is not required for reminders to signal locally, but this property is used to transmit a reminder on a sent message.

<7> Section 3.1.4.1.2: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not set all the specified properties when the reminder is created, because some of the properties were set in a previous operation (such as Message object creation or flagging for follow-up), or are set independent of the reminder itself (such as for Task objects), and the values did not change during the reminder creation process. Because Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not expose UI to just set a reminder on an e-mail message without also flagging, some properties, such as the PidLidFlagRequest property ([MS-OXOFLAG] section 2.2.1.9), happen to get set by Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 when a reminder is added to an e-mail message. These properties are not required for the reminder to function but are listed for completeness.

<8> Section 3.1.4.1.3: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 set the PidLidReminderTime property (section 2.2.1.4) to the start time of the first instance. They set the property only when creating the Recurring Calendar object or modifying the series such that the series start date changes. Therefore the PidLidReminderTime property cannot be assumed to have a specific value for Recurring Calendar objects.

<9> Section 3.1.4.4.1: In addition to the properties specified, Office Outlook 2003 deletes the PidTagReplyTime property ([MS-OXOFLAG] section 2.2.3.1) for a Message object that is neither a Calendar object nor a Task object. Office Outlook 2007 deletes the PidLidReminderTime (section 2.2.1.4), PidLidReminderSignalTime (section 2.2.1.2), and PidTagReplyTime properties when removing the reminder from a Message object that is neither a Calendar object nor a Task object. For the remaining cases, Office Outlook 2003 and Office Outlook 2007 do not delete the PidLidReminderTime or PidLidReminderSignalTime properties when removing the reminder for Calendar objects or Task objects; this is for user convenience to persist the signal time values even when the reminder is disabled.

<10> Section 3.1.4.5.1:  Office Outlook 2003 does not ignore Message objects that have the PidTagSwappedToDoStore property ([MS-OXOFLAG] section 2.2.1.8) set. Office Outlook 2003 also does not ignore meeting-related Message objects, but this is not a problem because it uses the minimal reminder domain, which does not include special folders such as the Sent Items folder.

<11> Section 3.1.4.5.3: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use the PidTagNormalizedSubject ([MS-OXCMSG] section 2.2.1.10), PidLidFlagRequest ([MS-OXOFLAG] section 2.2.1.9), and PidLidLocation ([MS-OXOCAL] section 2.2.1.4) properties. Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use the PidLidTaskDueDate property ([MS-OXOTASK] section 2.2.2.2.5).

<12> Section 3.1.4.5.3: Office Outlook 2003 displays DueIn "Now" when first signaling a reminder for a Task object or flagged Message object; Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 display a more intuitive time-until-DueDate value for these Message object types. Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 use the PidLidTaskDueDate property ([MS-OXOTASK] section 2.2.2.2.5) and the "end of workday" value to determine the due time. Office Outlook 2003 uses the value of the PidLidReminderTime property (section 2.2.1.4) as the due time.

<13> Section 3.1.4.5.3: Office Outlook 2003 uses the signal time as the due time.

<14> Section 3.1.4.5.3.1: The PidLidAutoStartCheck property ([MS-OXPROPS] section 2.41) is deprecated and SHOULD NOT be used. Office Outlook 2003 reads and writes this property. This property is not read by Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019.

<15> Section 3.1.4.6.3: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 set the PidLidTaskResetReminder property ([MS-OXOTASK] section 2.2.2.2.6).