Contributions to specs - grommunio/gromox GitHub Wiki
Instances where we found underspecifications or outright bugs in Microsoft documentation/specifications:
- PT_LONG is not for the unsigned
- Outlook invokes unspecified behavior with regard to PR_SENSITIVITY
- Fix size mentions for named properties
- Mention EX2019 behavior with regard to SPropertyRestriction
- MAPI_HARD_DELETE not fully documented
- relationship between DIR_ENTRYID and CONTAB_ENTRYID
- EWS: Month can have value 0 as well
- EWS: Default property table with bogus entry
- PT_LONG is wrongly documented to be unsigned
- EX Server 2019 behavior when evaluating a NULL value with a SPropertyRestriction
- Mention DELETE_HARD_DELETE flag for IMAPIFolder::DeleteFolder
- Update flag descriptions of PR_RECIPIENT_FLAGS
- Synchronize commonly-used-property-sets.md with info from MS-OXPROPS
- Document more flags returned by IMAPIContainer::GetSearchCriteria
- SCountRestriction
Major unsolved annoyances:
- The repository open_specs_exchange is erroneously set to private and cannot be edited like the others, wth (bugreport)
Filed without PR (because open_specs_exchange):
Still to be filed:
- MS-OXCMAPIHTTP fails to mentions that OXNSPI, when run over MAPIHTTP rather than RPC, has different serialization:
** (§2.2.1) extra HasValue bytes in STRING_ARRAY, WSTRING_ARRAY, BINARY_ARRAY, restrictions and propvals ** PT_OBJECT is serialized without the uint32 filler value ** emsmdb32.dll supports receiving PT_FLOAT, PT_DOUBLE and PT_I8 over MH (just not RPC) ** (The OXCMAPIHTTP spec is not in github, which means there is no classic pull-request-based collaboration possible.) * MS-OXCRPC fails to mention AUX header type 0x52 (sent by Outlook) and what it means * MS-OXCRPC fails to mention AUX header type 0x43 (sent by Exchange) and what it means
Specifications written ourselves:
- PR_RW_RULES_STREAM:
gromox/doc/outlook_rule_spec.rst