In today's society, it's second nature to contact family, friends, and colleagues via e-mail. E-mail has become so integral to our daily ritual
that we cannot stay away from it as we make use of personal digital assistants (PDAs) and other pervasive devices to have it readily
available. How do these billions of digital messages get to users across the globe?
A client/server setup is required to participate in the exchange of e-mails. It was just a few years ago that expensive server software
packages were used for the typical e-mail solution. Cheaper solutions have been plagued by a lack of robustness and scalability. To the
avail of shrinking corporate budgets comes the Java Apache Mail Enterprise Server (known as Apache James).
Apache James is a free, open source, robust offering from the Apache Software Foundation that aims to provide enterprises with a
Java-based mail server solution. James provides a Java API for developers to process e-mail services. In this article, we'll explore
James and what it can offer your enterprise operation.
In the world of e-mail, the senders and recipients of messages act as clients to e-mail servers. Senders create an e-mail using a Mail
User Agent (MUA) and transmit the message to an e-mail server using the Simple Mail Transfer Protocol (SMTP). The e-mail server
uses the same protocol to contact the recipient's e-mail server. Recipients then use the Post Office Protocol (POP3) or alternatively the
Internet Message Access Protocol (IMAP) to retrieve the message from their e-mail server. Note: IMAP support is currently experimental
in James 2.1.3.
As mentioned, e-mail servers use SMTP to transmit messages across the world. The default TCP port for this protocol is 25.
Accordingly, network administrators need to configure firewalls for access to the SMTP port.
POP3 is used to retrieve messages from the e-mail server. The default TCP port for this protocol is 110. Clients must provide security
information used fo