Search results
Results from the WOW.Com Content Network
Initial release: May 23, 1997. Introduced the new Exchange Administrator console, as well as opening up "integrated" access to SMTP-based networks for the first time.. Unlike Microsoft Mail (which required a standalone SMTP relay), Exchange Server 5.0 could, with the help of an add-in called the Internet Mail Connector, communicate directly with servers using
Microsoft had sold a number of simpler email products before, but the first release of Exchange (Exchange Server 4.0 in April 1996 [1]) was an entirely new X.400-based client–server groupware system with a single database store, which also supported X.500 directory services.
Main page; Contents; Current events; Random article; About Wikipedia; Contact us; Donate
Microsoft's Exchange Server was developed in this time period, and internally based on X.400/X.500 - with the initial release "equally happy to dispatch messages via Messaging API (MAPI), X.400, or Simple Mail Transfer Protocol (SMTP)". [4] In practice however, most of these were poorly produced, and seldom put into operation.
Unix-based mail servers are built using a number of components because a Unix-style environment is, by default, a toolbox [1] operating system. A stock Unix-like server already has internal mail; more traditional ones also come with a full MTA already part of the standard installation.
Shiloh — Microsoft SQL Server 2000 (8.0) Shiner HE — Apple Network Server 700; Shiner LE — Apple Network Server 500; Shitake — Zen Linux 1.1; Shogun — Show & Tell — Apple Macintosh LC 630; Show & Tell — Apple Macintosh Performa 630; Show & Tell — Apple Macintosh Quadra 630–638; Show Biz — Apple Macintosh Quadra 630–638
Version number [i] Release date [12] Notes Outlook 97 8.0 January 16, 1997 Included in Office 97 and bundled with Exchange Server 5.0 and 5.5. This was a renamed and slightly upgraded version of the Microsoft Exchange client. Outlook 98 8.5 June 21, 1998
MAPI uses functions loosely based on the X.400 XAPIA standard. It includes facilities to access message transports, message stores, and directories.. While Simple MAPI (SMAPI) is a subset of 12 functions which enable developers to add basic messaging functionality, Extended MAPI (EMAPI) allows complete control over the messaging system on the client computer.