User:Lantizia/scratchpad

Microsoft Groupware Methods --- Any method which is capable (by itself) of sending/receiving e-mail and reading/writing to calendars and address books which are on an Exchange server. Maybe CDO needs to be in this list too? -- - MAPI/RPC (Outlook-Exchange Transport Protocol) - -- MAPI (Messaging Application Programming Interface) is a proprietay messaging architecture created by Microsoft and was mostly introduced in 1991 when the precursor to Exchange (Microsoft Mail) was created by acquiring and rebadging "Network Courier" from "Consumers Software". With the MAPI/RPC method, the MAPI messages are encapsulated in the Microsoft version of the RPC (Remote Procedure Call) protocol. This is analogous to HTML going within HTTP. The RPC protocol was only ever meant for LAN use and so doesn't work when connecting to a hosted Exchange server or the Office 365 service. Later on Microsoft openly documented this method calling it "Outlook-Exchange Transport Protocol". > Outlook support: All Windows versions > Exchange support: All versions > DNS Autodiscover: No > 3rd Party Implementations: Yes > Microsoft Documentation: Yes > Microsoft Licensing Required: Yes - DAV (Exchange Store) - This is WebDAV just with a short hand name given by Microsoft. Some early versions of Entourage for Mac used this method to do the usual mail, calendars and contacts. Previous versions of Entourage (and Outlook Express which it was based on) could only do POP, IMAP and SMTP. Outlook on the web (also known as Exchange Web Connect, Outlook Web Access, and Outlook Web App) also uses DAV. > Outlook support: Entourage X onwards > Exchange support: 2000 > DNS Autodiscover: No > 3rd Party Implementations: Yes > Microsoft Documentation: Yes > Microsoft Licensing Required: No - RPC over HTTP (Outlook Anywhere) - This is MAPI/RPC being sent through a HTTP proxy, essentially "MAPI over RPC over HTTP". MAPI/RPC is split between two HTTP connections and sent to a RPC/Proxy for re-assembly so it can properly traverse the Internet. Load balancers can cause issues if the 2 halves don't go the same way. As of Exchange 2007 it is now known as "Outlook Anywhere". > Outlook support: 2003 onwards > Exchange support: 2003 onwards > DNS Autodiscover: Yes > 3rd Party Implementations: Yes > Microsoft Documentation: Yes > Microsoft Licensing Required: Yes - - EAS (Exchange ActiveSync) - - This is an XML and HTTP based method that doesn't use MAPI at all. Originally designed with mobile devices in mind (not to be confused with an earlier version called AirSync or the Windows CE related program) Since this doesn't use RPC, it is better for low bandwidth situations. It is widely supported on nearly all popular phones and tablets on the market which makes it a de facto standard. > Outlook support: 2013 onwards > Exchange support: 2003 onwards > DNS Autodiscover: Yes > 3rd Party Implementations: Yes > Microsoft Documentation: Yes > Microsoft Licensing Required: Yes --- - EWS (Exchange Web Services) - --- This is a SOAP and HTTP based method which isn't related to either EAS or MAPI. Mail Clients like Entourage, Mac Mail, Evolution and Thunderbird can use this method (sometimes requiring extra plugins). > Outlook support: Entourage 2008 WSE and Outlook for Mac 2011 onwards > Exchange support: 2007 onwards > DNS Autodiscover: No > 3rd Party Implementations: Yes > Microsoft Documentation: Yes > Microsoft Licensing Required: No -- - MAPI over HTTP - -- This is MAPI being sent straight over HTTP. Unlike RPC over HTTP this requires less bandwidth and only one connection making it much more efficient. > Outlook support: 2010 with KB2878264 and 2013 SP1 onwards > Exchange support: 2016 onwards > DNS Autodiscover: Yes > 3rd Party Implementations: No > Microsoft Documentation: No > Microsoft Licensing Required: N/A