Isode Limited is a software company based in the United Kingdom. Isode develops and markets messaging and directory server software based on the LDAP and X.500 protocols (directory) and SMTP, IMAP, POP3, XMPP and X.400 protocols (messaging).
Isode was formed in 1992, originally as the not-for-profit ISODE Consortium,<ref name="consortium">Template:Cite web</ref> to develop Internet/X.400 messaging and LDAP/X.500 directory servers. It became a commercial operation, Isode Limited, in 1996. In 1999, Isode merged with Execmail to form Messaging Direct<ref name="merge">Template:Cite webTemplate:Dead link</ref>Template:Dead link and in 2001 was purchased by Transaction Systems Architects (later ACI Worldwide).<ref name="aci">Template:Cite web</ref> Isode was re-established as an independent company on November 1, 2002.<ref name="newisode">Template:Cite web</ref>
Isode currently employs 25 people, Isode's CEO is Steve Kille who founded the ISODE consortium in 1992. Steve Kille, together with Tim Howes of the University of Michigan, Wengyik Yeong of Performance Systems International, and Colin Robbins of Nexor authored the original LDAP protocol.
Isode has four major product lines:
- Directory servers.
- Messaging servers based on the SMTP, IMAP, POP3 protocols.
- Instant Messaging and Presence based on the XMPP protocol.
- Directory and messaging APIs.
M-Vault is an LDAP and X.500 compatible directory server.
M-Switch SMTP is a MTA based on the SMTP protocol. M-Switch X.400 is a MTA using the X.400 protocol. M-Box is a mail server, delivering mail using the IMAP and POP3 protocols. M-Store is an X.400 message store.
M-Link is an XMPP instant messaging and presence server. Swiften is an open source C++ XMPP client library. Swift is an open source C++ XMPP client created with it.
Isode supplies three APIs:
- A directory client API to enable applications to access a directory in order to perform authentication and to obtain configuration information.
- An X.400 Client API designed for use by vendors building X.400 client applications (this API was originally developed for AMHS applications).
- An X.400 gateway API for integrating X.400 messaging services with other messaging services.
Isode and the Internet Engineering Task Force (IETF)
Isode has a long history with the IETF and employees of Isode and its predecessor, the ISODE Consortium, have since 1993 authored or co-authored a number of Internet standards (RFCs) with the company's support. These include RFCs covering LDAP, X.500, MIXER and IMAP.
|RFC||Title||Date published||Isode Contributing Author(s)||Obsoleted by|
|RFC 1430||A Strategic Plan for Deploying an Internet X.500 Directory Service||February 1993||Steve Kille|
|RFC 1484||Using the OSI Directory to achieve User Friendly Naming (OSI-DS 24 (v1.2))||July 1993||Steve Kille|
|RFC 1485||A String Representation of Distinguished Names (OSI-DS 23 (v5))||July 1993||Steve Kille|
|RFC 1487||X.500 Lightweight Directory Access Protocol||July 1993||Steve Kille|
|RFC 1495||Mapping between X.400 and RFC-822 Message Bodies||August 1993||Steve Kille||RFC 2156|
|RFC 1565||Network Services Monitoring MIB||January 1993||Steve Kille||RFC 2248|
|RFC 1566||Mail Monitoring MIB||January 1993||Steve Kille||RFC 2789|
|RFC 1567||X.500 Directory Monitoring MIB||March 1995||Steve Kille||RFC 2605|
|RFC 1617||Naming and Structuring Guidelines for X.500 Directory Pilots||May 1994||Steve Kille|
|RFC 1777||Lightweight Directory Access Protocol||March 1995||Steve Kille||RFC 3494|
|RFC 1778||The String Representation of Standard Attribute Syntaxes||March 1995||Steve Kille||RFC 3494|
|RFC 1779||A String Representation of Distinguished Names||March 1995||Steve Kille||RFC 3494|
|RFC 1801||X.400-MHS use of the X.500 Directory to support X.400-MHS Routing||June 1995||Steve Kille|
|RFC 1836||Representing the O/R Address hierarchy in the X.500 Directory Information Tree||August 1995||Steve Kille||RFC 2294|
|RFC 1837||Representing Tables and Subtrees in the X.500 Directory||August 1995||Steve Kille||RFC 2293|
|RFC 1838||Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses||August 1995||Steve Kille||RFC 2164|
|RFC 2156||MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIMEs||January 1998||Steve Kille|
|RFC 2164||Use of an X.500/LDAP directory to support MIXER address mapping||January 1998||Steve Kille|
|RFC 2247||Using Domains in LDAP/X.500 Distinguished Names||January 1998||Steve Kille|
|RFC 2248||Network Services Monitoring MIB||January 1998||Steve Kille||RFC 2278|
|RFC 2251||Lightweight Directory Access Protocol (v3)||December 1997||Steve Kille||RFC 4513|
|RFC 2252||Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions||December 1997||Steve Kille||RFC 4523|
|RFC 2253||Lightweight Directory Access Protocol (v3): UTF-8 String Representation of Distinguished Names||December 1997||Steve Kille||RFC 4514|
|RFC 2293||Representing Tables and Subtrees in the X.500 Directory||March 1998||Steve Kille|
|RFC 2294||Representing the O/R Address hierarchy in the X.500 Directory Information Tree||March 1998||Steve Kille|
|RFC 2605||Directory Server Monitoring MIB||June 1999||Steve Kille|
|RFC 2788||Network Services Monitoring MIB||March 2000||Steve Kille|
|RFC 2789||Mail Monitoring MIB||March 2000||Steve Kille|
|RFC 3691||Internet Message Access Protocol (IMAP) UNSELECT command||February 2004||Alexey Melnikov|
|RFC 4314||IMAP4 Access Control List (ACL) Extension||December 2005||Alexey Melnikov|
|RFC 4422||Simple Authentication and Security Layer (SASL)||June 2006||Alexey Melnikov|
|RFC 4466||Collected Extensions to IMAP4 ABNF||April 2006||Alexey Melnikov|
|RFC 4549||Synchronization Operations for Disconnected IMAP4 Clients||June 2006||Alexey Melnikov|
|RFC 4551||IMAP Extension for Conditional STORE Operation or Quick Flag Changes Resynchronization||June 2006||Alexey Melnikov|
|RFC 4731||IMAP4 Extension to SEARCH Command for Controlling What Kind of Information Is Returned||November 2006||Alexey Melnikov|
|RFC 4752||The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) Mechanism||November 2006||Alexey Melnikov|
|RFC 4954||SMTP Service Extension for Authentication||July 2007||Alexey Melnikov|
|RFC 5020||The Lightweight Directory Access Protocol (LDAP) entryDN Operational Attribute||August 2007||Kurt Zeilenga|
|RFC 5092||IMAP URL Scheme||October 2007||Alexey Melnikov|
|RFC 5819||IMAP4 Extension for Returning STATUS Information in Extended LIST||March 2010||Alexey Melnikov|