What Is Apache James Protocols IMAP4?

A library providing a flexible codec for IMAP4, command processors and a sample data access layer.

In combination with a socket layer, and a mailbox persistence, this library can be used to create an IMAP server.

RFC 2060 IMAP4rev1 is functionally complete, tested and usable. The data access layer is still under optimization on performance perspectives. API is susceptible to change.

You can download current 0.3 release. The API are susceptible to evolve.

There are many extensions defined for IMAP (see a list here)

Apache James IMAP implements the following:

  • IMAP4rev1 (RFC 3501 http://www.ietf.org/rfc/rfc3501.txt)
  • NAMESPACE (in release 0.2) (RFC 2342 http://www.ietf.org/rfc/rfc2342.txt)
  • IDLE (in release 0.2) (RFC 2177 http://www.ietf.org/rfc/rfc2177.txt)
  • LITERAL+ (in release 0.2)
  • CHILDREN (in release 0.2)
  • WITHIN (in release 0.2)
  • UIDPLUS (in release 0.2)
  • UNSELECT (in release 0.2)
  • I18NLEVEL=1 (in release 0.2.1)
  • ESEARCH (in release 0.2.1)
  • SEARCHRES (in release 0.2.1)
  • AUTH=PLAIN (in release 0.2.1)
  • SASL-IR (in release 0.2.1)
  • ENABLE (in release 0.2.1)
  • CONDSTORE (RFC 4551 http://www.ietf.org/rfc/rfc4551.txt in release 0.3)
  • RESYNCH (RFC 5162 http://www.ietf.org/rfc/rfc5162.txt in trunk)

We follow RFC2683 recommandations for our implementations:

  • IMAP4 Implementation Recommandations (RFC 2683 http://www.ietf.org/rfc/rfc2683.txt)

Interesting features:

  • Users FLAGS

Other RFCs of interest we are looking at:

  • IMAP4 SORT and THREAD Extensions (RFC 5256 http://www.ietf.org/rfc/rfc5256.txt)

We have integration tests for IMAP.

Our implementation is also tested against external tools such as http://www.imapwiki.org/ImapTest.

Apache James IMAP in Server and as component

Apache James Server 3 supports IMAP (using this library).

The source code page contains information on how to develop on James IMAP.