Sun Java System Messaging Server

• Extremely scalable server components
• Open interfaces for client support and extensibility
• AJAX Web 2.0 client that integrates messaging, calendaring, address book, and instant messaging services
• "Push" email support for mobile devices
• 2-way SMS support
• Encrypted secure messaging
• Foundation for unified and mobile communications
• Proven, high performance message transfer agent (MTA)
• Flexible delegated administration and virtual domain hosting
• Seamless integration with LDAP-based Sun Java System Directory Server
• Sophisticated anti-spam controls
• Pluggable architecture for integrating third party anti-virus controls
• Three modes of high availability support for Veritas and Sun Cluster
• Robust content and attachment search through integration with the Java Indexing and Search Service

Sun Java System Messaging Server has multi-purpose functionality and is well-suited to a variety of circumstances. It can function as a backbone, gateway, and mail switch. The high-performance MTA engine utilizes a sophisticated modular channel architecture for handling a variety of data types, including email, fax, SMS, voice, and video. The flexible channel architecture gives service providers the ability to finely control the behavior of mail flow to and from different domains, allowing service providers to drive revenue by creating new classes of service for their customers. The multi-threaded design is optimized for maximum message throughput.

The MTA includes an open, interoperable design with an Application Programming Interface (API) that allows service providers or third-parties to create their own channels for service and content integration. Through the API, such channels have access to all the core functionality of the MTA.

• Use START TLS to talk to the POP server directly on the standard port 110
• Use the alternate port 995 to establish an SSL session to the POP server
• Use START TLS to talk to the MMP on the standard port 110
• Use the alternate port 995 to establish an SSL session with the MMP

• The server uses counted strings and not NULL terminated buffers, for additional security against buffer overrun attacks.
• Rather than use a few monolithic processes, Messaging Server uses a number of smaller, task-oriented processes for robustness against DOS and DDOS attacks.
• Server processes do not run as root. While some of the servers must start as root in order to bind to TCP ports in the &quotprivileged" range, these servers then do a one-time change of effective and real UID and GID. They change to the identity specified at install time. For purposes of delivery to /var/mail/spool and running third-party software on the behalf of users (e.g., procmail), some programs setuid to root. These programs are started and stopped only when needed and they are not fed command line input, which comes from the outside world. They need to run as root so that they can set their UID and GID to that of the local (login) user for whom either the mail is being delivered (/var/mail/) or the filter is being run. (Only sysadmins can say what filtering programs can or cannot be run.) Note that the typical site running Java System Messaging Server does not use /var/mail.