You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by ba...@apache.org on 2007/03/22 20:57:23 UTC
svn commit: r521427 [8/9] - in /james/server/trunk: ./ build-tools/
core-library/ core-library/src/ core-library/src/main/
core-library/src/main/config/ core-library/src/main/java/
core-library/src/main/java/org/ core-library/src/main/java/org/apache/ ...
Added: james/server/trunk/phoenix-deployment/www/stylesheets/project.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/stylesheets/project.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/stylesheets/project.html (added)
+++ james/server/trunk/phoenix-deployment/www/stylesheets/project.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,123 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE site PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<site name="James Site" href="http://james.apache.org/">
+ <title>Apache James - Mail and News server</title>
+ <logo href="/images/james-logo.jpg">James - Java Apache Mail Enterprise Server</logo>
+ <body>
+ <navbar name="lhs">
+
+ <p>
+<strong>Concepts</strong>
+</p>
+<ul>
+<li>
+<a href="./summary.html">Summary</a>
+</li>
+<li>
+<a href="./spoolmanager.html">SpoolManager</a>
+</li>
+<li>
+<a href="./repositories.html">Repositories</a>
+</li>
+<li>
+<a href="./mailet_api.html">The Mailet API</a>
+</li>
+</ul>
+
+ <p>
+<strong>How to...</strong>
+</p>
+<ul>
+<li>
+<a href="./build_instructions.html">Build James</a>
+</li>
+<li>
+<a href="./installation_instructions.html">Install James</a>
+</li>
+</ul>
+
+ <p>
+<strong>Configuration</strong>
+</p>
+<ul>
+<li>
+<a href="./dns_configuration.html">DNS Server</a>
+</li>
+<li>
+<a href="./pop3_configuration.html">POP3 Server</a>
+</li>
+<li>
+<a href="./smtp_configuration.html">SMTP Server</a>
+</li>
+<li>
+<a href="./nntp_configuration.html">NNTP Server</a>
+</li>
+<li>
+<a href="./fetchmail_configuration.html">FetchMail</a>
+</li>
+<li>
+<a href="./remotemanager_configuration.html">RemoteManager</a>
+</li>
+<li>
+<a href="./spoolmanager_configuration.html">SpoolManager</a>
+</li>
+<li>
+<a href="./serverwide_configuration.html">Server-wide</a>
+</li>
+<li>
+<a href="./adding_users.html">Adding Users</a>
+</li>
+<li>
+<a href="./provided_matchers.html">Provided Matchers</a>
+</li>
+<li>
+<a href="./provided_mailets.html">Provided Mailets</a>
+</li>
+</ul>
+
+ <p>
+<strong>Common Configurations</strong>
+</p>
+<ul>
+<li>
+<a href="./smtp_auth.html">Using SMTP AUTH</a>
+</li>
+<li>
+<a href="./using_database.html">Using a Database with James</a>
+</li>
+<li>
+<a href="./usingTLS.html">Using TLS/SSL</a>
+</li>
+<li>
+<a href="./james_and_sendmail.html">James and Sendmail</a>
+</li>
+<li>
+<a href="./mailing_lists.html">Creating Mailing Lists</a>
+</li>
+</ul>
+
+ <p>
+<strong>Customization</strong>
+</p>
+<ul>
+<li>
+<a href="./custom_matcher.html">How to write a custom Matcher</a>
+</li>
+<li>
+<a href="./custom_mailet.html">How to write a custom Mailet</a>
+</li>
+</ul>
+
+ <p>
+<strong>Project</strong>
+</p>
+<ul>
+<li>
+<a href="./changelog.html">Changelog</a>
+</li>
+</ul>
+
+ </navbar>
+
+ </body>
+</site>
Added: james/server/trunk/phoenix-deployment/www/summary.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/summary.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/summary.html (added)
+++ james/server/trunk/phoenix-deployment/www/summary.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,332 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>Apache James - Mail and News server - James 2.3 - Component Summary</title>
+<LINK TITLE="Style" HREF="stylesheet.css" TYPE="text/css" REL="stylesheet"/>
+</head>
+<body>
+<table cellspacing="0" width="100%" border="0" class="page-header">
+<!--PAGE HEADER-->
+<tr>
+<td colspan="2">
+<!--ASF LOGO-->
+<a href="http://www.apache.org/">
+<img border="0" alt="The ASF" align="left" src="http://www.apache.org/images/asf_logo_wide.gif"/>
+</a>
+<!--PROJECT LOGO-->
+<a href="http://james.apache.org/">
+<img border="0" alt="James - Java Apache Mail Enterprise Server" align="right" src="./images/james-logo.jpg"/>
+</a>
+</td>
+</tr>
+</table>
+<table cellspacing="4" width="100%" border="0">
+<tr>
+<!--LEFT SIDE NAVIGATION-->
+<td nowrap="true" valign="top" class="left-navbar">
+<table cellpadding="0" cellspacing="0" width="100%" border="0">
+<tr>
+<td>
+<a href="http://apachecon.com">
+<img border="0" alt="ApacheCon Promotion" align="left" src="http://www.apache.org/ads/ApacheCon/234x60-2006-us.gif"/>
+</a>
+</td>
+</tr>
+</table>
+<navbar name="lhs">
+
+ <p>
+<strong>Concepts</strong>
+</p>
+<ul>
+<li>
+<a href="./summary.html">Summary</a>
+</li>
+<li>
+<a href="./spoolmanager.html">SpoolManager</a>
+</li>
+<li>
+<a href="./repositories.html">Repositories</a>
+</li>
+<li>
+<a href="./mailet_api.html">The Mailet API</a>
+</li>
+</ul>
+
+ <p>
+<strong>How to...</strong>
+</p>
+<ul>
+<li>
+<a href="./build_instructions.html">Build James</a>
+</li>
+<li>
+<a href="./installation_instructions.html">Install James</a>
+</li>
+</ul>
+
+ <p>
+<strong>Configuration</strong>
+</p>
+<ul>
+<li>
+<a href="./dns_configuration.html">DNS Server</a>
+</li>
+<li>
+<a href="./pop3_configuration.html">POP3 Server</a>
+</li>
+<li>
+<a href="./smtp_configuration.html">SMTP Server</a>
+</li>
+<li>
+<a href="./nntp_configuration.html">NNTP Server</a>
+</li>
+<li>
+<a href="./fetchmail_configuration.html">FetchMail</a>
+</li>
+<li>
+<a href="./remotemanager_configuration.html">RemoteManager</a>
+</li>
+<li>
+<a href="./spoolmanager_configuration.html">SpoolManager</a>
+</li>
+<li>
+<a href="./serverwide_configuration.html">Server-wide</a>
+</li>
+<li>
+<a href="./adding_users.html">Adding Users</a>
+</li>
+<li>
+<a href="./provided_matchers.html">Provided Matchers</a>
+</li>
+<li>
+<a href="./provided_mailets.html">Provided Mailets</a>
+</li>
+</ul>
+
+ <p>
+<strong>Common Configurations</strong>
+</p>
+<ul>
+<li>
+<a href="./smtp_auth.html">Using SMTP AUTH</a>
+</li>
+<li>
+<a href="./using_database.html">Using a Database with James</a>
+</li>
+<li>
+<a href="./usingTLS.html">Using TLS/SSL</a>
+</li>
+<li>
+<a href="./james_and_sendmail.html">James and Sendmail</a>
+</li>
+<li>
+<a href="./mailing_lists.html">Creating Mailing Lists</a>
+</li>
+</ul>
+
+ <p>
+<strong>Customization</strong>
+</p>
+<ul>
+<li>
+<a href="./custom_matcher.html">How to write a custom Matcher</a>
+</li>
+<li>
+<a href="./custom_mailet.html">How to write a custom Mailet</a>
+</li>
+</ul>
+
+ <p>
+<strong>Project</strong>
+</p>
+<ul>
+<li>
+<a href="./changelog.html">Changelog</a>
+</li>
+</ul>
+
+ </navbar>
+</td>
+<!--MAIN BODY-->
+<td align="left" valign="top" class="main-body">
+<div class="section">
+<div class="section-header">
+<a name="The James Server">
+<strong>The James Server</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>James is an open source project intended to produce a robust, flexible, and powerful
+enterprise class server that provides email and email-related services. It is also designed to
+be highly customizable, allowing administrators to configure James to process email in a
+nearly endless variety of fashions.</p>
+
+<p>The James server is built on top of the Avalon Framework. The standard James distribution
+deploys inside the Phoenix Avalon Framework container. In addition to providing a robust
+server architecuture for James, the use of Phoenix allows James administrators to deploy
+their own applications inside the container. These applications can then be accessed during
+mail processing.</p>
+
+<p>The James server is implemented as a complete collection of servers and related components that, taken together,
+provide an email solution. These components are described below.</p>
+
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="POP3 Service">
+<strong>POP3 Service</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>The POP3 protocol allows users to retrieve email messages. It is the method
+most commonly used by email clients to download and manage email messages.</p>
+
+<p>The James version of the POP3 service is a simple and straightforward implementation that
+provides full compliance with the specification and maximum compatibility with common
+POP3 clients. In addition, James can be configured to require SSL/TLS connections for
+POP3 client connecting to the server.</p>
+
+<p>More information on configuring the POP3 service can be found <a href="pop3_configuration.html">here</a>.</p>
+
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="SMTP Service">
+<strong>SMTP Service</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>SMTP (Simple Mail Transport Protocol) is the standard method of sending and delivering
+email on the internet. James provides a full-function implementation of the SMTP specification,
+with support for some optional features such as message size limits, SMTP auth, and encrypted
+client/server communication.</p>
+
+<p>More information on configuring the SMTP service can be found <a href="smtp_configuration.html">here</a>.</p>
+
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="NNTP Service">
+<strong>NNTP Service</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>NNTP is used by clients to store messages on and retrieve messages from news servers. James provides
+the server side of this interaction by implementing the NNTP specification as well as an appropriate
+repository for storing news messages. The server implementation is simple and straightforward, but
+supports some additional features such as NNTP authentication and encrypted client/server communication.</p>
+
+<p>More information on configuring the NNTP service can be found <a href="nntp_configuration.html">here</a>.</p>
+
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="FetchMail">
+<strong>FetchMail</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>FetchMail, unlike the other James components, is not an implementation of an RFC. Instead, it's a
+component that allows the administrator to configure James to retrieve email from a number of POP3
+servers and deliver them to the local spool. This is useful for consolidating mail delivered to a
+number of accounts on different machines to a single account.</p>
+
+<p>More information on configuring FetchMail can be found <a href="fetchmail_configuration.html">here</a>.</p>
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="The SpoolManager, Matchers, and Mailets">
+<strong>The SpoolManager, Matchers, and Mailets</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>James separates the services that deliver mail to James (i.e. SMTP, FetchMail)
+from the engine that processes mail after it is received by James. The
+SpoolManager component is James' mail processing engine. James' SpoolManager component
+is a Mailet container. It is these mailets and matchers that actually carry out mail processing.</p>
+
+<p>More on the structure of the SpoolManager and the Mailet API can be found <a href="spoolmanager.html">here</a>.</p>
+
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="Repositories">
+<strong>Repositories</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>James uses a number of different repositories to both store message data (email, news messages) and
+user information. User repositories store user information, including user names, authentication
+information, and aliases. Mail repositories store messages that have been delivered locally. Spool
+repositories store messages that are still being processed. Finally, news repositories are used to
+store news messages. Aside from what type of data they store, repositories are distinguished by
+where they store data. There are three types of storage - File, Database, and DBFile.</p>
+
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="RemoteManager">
+<strong>RemoteManager</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>James provides a simple telnet-based interface for control. Through this interface you can add
+and delete users, configure per-user aliases and forward addresses, and shut down the server.</p>
+
+<p>More on the configuring the RemoteManager can be found <a href="remotemanager_configuration.html">here</a>.</p>
+
+</div>
+</p>
+</div>
+</td>
+</tr>
+<!--FOOTER SEPARATOR-->
+<tr>
+<td colspan="2">
+<hr size="1" noshade=""/>
+</td>
+</tr>
+<tr>
+<td colspan="2">
+<div class="page-footer">
+<em>
+ Copyright © 1999-2006, The Apache Software Foundation
+ </em>
+</div>
+</td>
+</tr>
+</table>
+</body>
+</html>
Added: james/server/trunk/phoenix-deployment/www/upgrade_instructions.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/upgrade_instructions.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/upgrade_instructions.html (added)
+++ james/server/trunk/phoenix-deployment/www/upgrade_instructions.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,367 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>Apache James - Mail and News server - James 2.3 - Upgrading</title>
+<LINK TITLE="Style" HREF="stylesheet.css" TYPE="text/css" REL="stylesheet"/>
+</head>
+<body>
+<table cellspacing="0" width="100%" border="0" class="page-header">
+<!--PAGE HEADER-->
+<tr>
+<td colspan="2">
+<!--ASF LOGO-->
+<a href="http://www.apache.org/">
+<img border="0" alt="The ASF" align="left" src="http://www.apache.org/images/asf_logo_wide.gif"/>
+</a>
+<!--PROJECT LOGO-->
+<a href="http://james.apache.org/">
+<img border="0" alt="James - Java Apache Mail Enterprise Server" align="right" src="./images/james-logo.jpg"/>
+</a>
+</td>
+</tr>
+</table>
+<table cellspacing="4" width="100%" border="0">
+<tr>
+<!--LEFT SIDE NAVIGATION-->
+<td nowrap="true" valign="top" class="left-navbar">
+<table cellpadding="0" cellspacing="0" width="100%" border="0">
+<tr>
+<td>
+<a href="http://apachecon.com">
+<img border="0" alt="ApacheCon Promotion" align="left" src="http://www.apache.org/ads/ApacheCon/234x60-2006-us.gif"/>
+</a>
+</td>
+</tr>
+</table>
+<navbar name="lhs">
+
+ <p>
+<strong>Concepts</strong>
+</p>
+<ul>
+<li>
+<a href="./summary.html">Summary</a>
+</li>
+<li>
+<a href="./spoolmanager.html">SpoolManager</a>
+</li>
+<li>
+<a href="./repositories.html">Repositories</a>
+</li>
+<li>
+<a href="./mailet_api.html">The Mailet API</a>
+</li>
+</ul>
+
+ <p>
+<strong>How to...</strong>
+</p>
+<ul>
+<li>
+<a href="./build_instructions.html">Build James</a>
+</li>
+<li>
+<a href="./installation_instructions.html">Install James</a>
+</li>
+</ul>
+
+ <p>
+<strong>Configuration</strong>
+</p>
+<ul>
+<li>
+<a href="./dns_configuration.html">DNS Server</a>
+</li>
+<li>
+<a href="./pop3_configuration.html">POP3 Server</a>
+</li>
+<li>
+<a href="./smtp_configuration.html">SMTP Server</a>
+</li>
+<li>
+<a href="./nntp_configuration.html">NNTP Server</a>
+</li>
+<li>
+<a href="./fetchmail_configuration.html">FetchMail</a>
+</li>
+<li>
+<a href="./remotemanager_configuration.html">RemoteManager</a>
+</li>
+<li>
+<a href="./spoolmanager_configuration.html">SpoolManager</a>
+</li>
+<li>
+<a href="./serverwide_configuration.html">Server-wide</a>
+</li>
+<li>
+<a href="./adding_users.html">Adding Users</a>
+</li>
+<li>
+<a href="./provided_matchers.html">Provided Matchers</a>
+</li>
+<li>
+<a href="./provided_mailets.html">Provided Mailets</a>
+</li>
+</ul>
+
+ <p>
+<strong>Common Configurations</strong>
+</p>
+<ul>
+<li>
+<a href="./smtp_auth.html">Using SMTP AUTH</a>
+</li>
+<li>
+<a href="./using_database.html">Using a Database with James</a>
+</li>
+<li>
+<a href="./usingTLS.html">Using TLS/SSL</a>
+</li>
+<li>
+<a href="./james_and_sendmail.html">James and Sendmail</a>
+</li>
+<li>
+<a href="./mailing_lists.html">Creating Mailing Lists</a>
+</li>
+</ul>
+
+ <p>
+<strong>Customization</strong>
+</p>
+<ul>
+<li>
+<a href="./custom_matcher.html">How to write a custom Matcher</a>
+</li>
+<li>
+<a href="./custom_mailet.html">How to write a custom Mailet</a>
+</li>
+</ul>
+
+ <p>
+<strong>Project</strong>
+</p>
+<ul>
+<li>
+<a href="./changelog.html">Changelog</a>
+</li>
+</ul>
+
+ </navbar>
+</td>
+<!--MAIN BODY-->
+<td align="left" valign="top" class="main-body">
+<div class="section">
+<div class="section-header">
+<a name="Upgrading Comments">
+<strong>Upgrading Comments</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<p>James upgrading involves a number of steps, each of which is described in some detail in the
+following sections. But as this sequence of steps has confused some users in the past, additional
+comments seem warranted.</p>
+<p>It is important to realize that the James configuration files are not unpacked from the James
+distribution until the first time James is started. This is a consequence of the design of the
+Avalon Phoenix container used to run James. Once James has been started, the distribution will
+be unpacked. The server should be stopped, the configuration files edited, and the server restarted.</p>
+<p>So the Upgrading sequence is: <b>1) Start, 2) Stop, 3) Move 4) Edit, 5) Restart</b>.</p>
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="Copy mailboxes and users">
+<strong>Copy mailboxes and users</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<div class="subsection">
+<div class="subsection-header">
+<a name="Copy mailboxes and users">
+<strong>Copy mailboxes and users</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Remove the apps/james/var directory and copy the apps/james/var directory of the old james
+installation in this place.</p>
+</div>
+</div>
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="Copy and modify config.xml">
+<strong>Copy and modify config.xml</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<div class="subsection">
+<div class="subsection-header">
+<a name="Remove the fetchpop block">
+<strong>Remove the fetchpop block</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>It's necessary to remove the fetchpop block in config.xml because fetchpop was removed in 2.3.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Move mailet and matcher packages config">
+<strong>Move mailet and matcher packages config</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Move <mailetpackages> and <matcherpackages> outside of the <spoolmanager> block.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Add necessary mailets">
+<strong>Add necessary mailets</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Add the following line as the first mailet of the "root" processor:</p>
+<div class="source">
+<mailet match="All" class="PostmasterAlias"/>
+</div>
+<p>This was hardcoded in 2.2.0 and previous. Now we made it configurable.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Move the spoolrepository config">
+<strong>Move the spoolrepository config</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Move the spoolrepository out of the mailstore. Its also necessary to change the config syntax. For example:</p>
+<div class="source">
+<spoolRepository>
+ <repository destinationURL="db://maildb/spool/spool" type="SPOOL"/>
+</spoolRepository>
+</div>
+Must converted to
+<div class="source">
+<spoolrepository destinationURL="db://maildb/spool/spool" type="SPOOL"/>
+</div>
+
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Move the objectstore">
+<strong>Move the objectstore</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Move the objectstore config into the mailstore config.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Add SSL to server-sockets">
+<strong>Add SSL to server-sockets</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p> To be able to use SSL you need to add this SSL config to the server-sockets block:</p>
+<div class="source">
+<!--
+<factory name="ssl" class="org.apache.avalon.cornerstone.blocks.sockets.TLSServerSocketFactory">
+ <ssl-factory>
+ <keystore>
+ <file>conf/keystore/</file>
+ <password>secret</password>
+ <key-password>keysecret</key-password>
+ <type>JKS</type>
+ <protocol>TLS</protocol>
+ <algorithm>SunX509</algorithm>
+ <authenticate-client>false</authenticate-client>
+ </keystore>
+ </ssl-factory>
+</factory>
+-->
+</div>
+</div>
+</div>
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="Modify costum mailets if necessary">
+<strong>Modify costum mailets if necessary</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<p> Please note the following things that were changed. So maybe it's necessary for you to change some stuff in your mailets. </p>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Avalon updates">
+<strong>Avalon updates</strong>
+</a>
+</div>
+<div class="subsection-body">
+<ul>
+<li>avalon Component has been replaced by avalon Service</li>
+<li>avalon Composable has been replaced by avalon Serviceable</li>
+<li>avalon ComponentManager has been replaced by avalon ServiceManager</li>
+</ul>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Cornerstone updates">
+<strong>Cornerstone updates</strong>
+</a>
+</div>
+<div class="subsection-body">
+<ul>
+<li>MailStore interface has been removed: mailets looking up the MailStore should now lookup
+a Store (org.apache.avalon.cornerstone.services.store.Store)</li>
+</ul>
+</div>
+</div>
+</div>
+</p>
+</div>
+<div class="section">
+<div class="section-header">
+<a name="Start James">
+<strong>Start James</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<p> Now you should be able to start james without problems.</p>
+</div>
+</p>
+</div>
+</td>
+</tr>
+<!--FOOTER SEPARATOR-->
+<tr>
+<td colspan="2">
+<hr size="1" noshade=""/>
+</td>
+</tr>
+<tr>
+<td colspan="2">
+<div class="page-footer">
+<em>
+ Copyright © 1999-2006, The Apache Software Foundation
+ </em>
+</div>
+</td>
+</tr>
+</table>
+</body>
+</html>
Added: james/server/trunk/phoenix-deployment/www/usingTLS.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/usingTLS.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/usingTLS.html (added)
+++ james/server/trunk/phoenix-deployment/www/usingTLS.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,276 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>Apache James - Mail and News server - James 2.3 - Using TLS</title>
+<LINK TITLE="Style" HREF="stylesheet.css" TYPE="text/css" REL="stylesheet"/>
+</head>
+<body>
+<table cellspacing="0" width="100%" border="0" class="page-header">
+<!--PAGE HEADER-->
+<tr>
+<td colspan="2">
+<!--ASF LOGO-->
+<a href="http://www.apache.org/">
+<img border="0" alt="The ASF" align="left" src="http://www.apache.org/images/asf_logo_wide.gif"/>
+</a>
+<!--PROJECT LOGO-->
+<a href="http://james.apache.org/">
+<img border="0" alt="James - Java Apache Mail Enterprise Server" align="right" src="./images/james-logo.jpg"/>
+</a>
+</td>
+</tr>
+</table>
+<table cellspacing="4" width="100%" border="0">
+<tr>
+<!--LEFT SIDE NAVIGATION-->
+<td nowrap="true" valign="top" class="left-navbar">
+<table cellpadding="0" cellspacing="0" width="100%" border="0">
+<tr>
+<td>
+<a href="http://apachecon.com">
+<img border="0" alt="ApacheCon Promotion" align="left" src="http://www.apache.org/ads/ApacheCon/234x60-2006-us.gif"/>
+</a>
+</td>
+</tr>
+</table>
+<navbar name="lhs">
+
+ <p>
+<strong>Concepts</strong>
+</p>
+<ul>
+<li>
+<a href="./summary.html">Summary</a>
+</li>
+<li>
+<a href="./spoolmanager.html">SpoolManager</a>
+</li>
+<li>
+<a href="./repositories.html">Repositories</a>
+</li>
+<li>
+<a href="./mailet_api.html">The Mailet API</a>
+</li>
+</ul>
+
+ <p>
+<strong>How to...</strong>
+</p>
+<ul>
+<li>
+<a href="./build_instructions.html">Build James</a>
+</li>
+<li>
+<a href="./installation_instructions.html">Install James</a>
+</li>
+</ul>
+
+ <p>
+<strong>Configuration</strong>
+</p>
+<ul>
+<li>
+<a href="./dns_configuration.html">DNS Server</a>
+</li>
+<li>
+<a href="./pop3_configuration.html">POP3 Server</a>
+</li>
+<li>
+<a href="./smtp_configuration.html">SMTP Server</a>
+</li>
+<li>
+<a href="./nntp_configuration.html">NNTP Server</a>
+</li>
+<li>
+<a href="./fetchmail_configuration.html">FetchMail</a>
+</li>
+<li>
+<a href="./remotemanager_configuration.html">RemoteManager</a>
+</li>
+<li>
+<a href="./spoolmanager_configuration.html">SpoolManager</a>
+</li>
+<li>
+<a href="./serverwide_configuration.html">Server-wide</a>
+</li>
+<li>
+<a href="./adding_users.html">Adding Users</a>
+</li>
+<li>
+<a href="./provided_matchers.html">Provided Matchers</a>
+</li>
+<li>
+<a href="./provided_mailets.html">Provided Mailets</a>
+</li>
+</ul>
+
+ <p>
+<strong>Common Configurations</strong>
+</p>
+<ul>
+<li>
+<a href="./smtp_auth.html">Using SMTP AUTH</a>
+</li>
+<li>
+<a href="./using_database.html">Using a Database with James</a>
+</li>
+<li>
+<a href="./usingTLS.html">Using TLS/SSL</a>
+</li>
+<li>
+<a href="./james_and_sendmail.html">James and Sendmail</a>
+</li>
+<li>
+<a href="./mailing_lists.html">Creating Mailing Lists</a>
+</li>
+</ul>
+
+ <p>
+<strong>Customization</strong>
+</p>
+<ul>
+<li>
+<a href="./custom_matcher.html">How to write a custom Matcher</a>
+</li>
+<li>
+<a href="./custom_mailet.html">How to write a custom Mailet</a>
+</li>
+</ul>
+
+ <p>
+<strong>Project</strong>
+</p>
+<ul>
+<li>
+<a href="./changelog.html">Changelog</a>
+</li>
+</ul>
+
+ </navbar>
+</td>
+<!--MAIN BODY-->
+<td align="left" valign="top" class="main-body">
+<div class="section">
+<div class="section-header">
+<a name="James 2.3 - Using TLS">
+<strong>James 2.3 - Using TLS</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>
+This document explains how to enable James 2.3 services to use Transport Layer Security (TLS) for encrypted client-server communication.</p>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Making TLS/SSL Server Sockets Available Inside James">
+<strong>Making TLS/SSL Server Sockets Available Inside James</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>James uses the Sun Java Secure Sockets Extension (JSSE) infrastructure to provide TLS/SSL
+sockets. JSSE comes packaged with several vendor Java distributions (i.e. Sun Java 1.4.x,
+IBM Java 1.3.x). For these distributions, please follow the vendor provided instructions for
+configuring the JVM to use JSSE services.</p>
+
+<p>If you are using a Java distribution that does not include JSSE as part of the
+distribution you will need to download the JSSE package separately. It can be obtained from
+<a href="http://java.sun.com/products/jsse">here</a>. Please follow Sun's instructions for installation
+and configuration of JSSE.</p>
+<p>In either case, you will need to statically define a JSSE TLS provider. In general, this
+is the default installation.</p>
+<p>Once you've installed JSSE, James still needs to be configured to take advantage of the JSSE
+functionality.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Certificate Keystores">
+<strong>Certificate Keystores</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>To use TLS/SSL inside James you will need a certificate keystore.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Configuring the Server Socket Factory">
+<strong>Configuring the Server Socket Factory</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>The out of the box configuration file contains a template for the SSL configuration in place. Specifically,
+in the sockets block, under the server-sockets element, there is a commented out factory with the
+name "ssl". The first step to configuring the server socket factory is uncommenting out this element.</p>
+<p>The factory element contains several children. Of these, it should only be necessary to adjust two or three children.</p>
+<p>The required file element specifies the location of the keystore to be used by the factory. This is specified
+as a file path using Unix-style formatting. The path is taken to be relative to the apps/james/ subdirectory of
+the application installation directory unless an absolute path is specified.</p>
+<p>The password element should be set to the keystore password. This password should have been specified
+when the keystore was created, and it is required to open the keystore. This value is required.</p>
+<p>Finally, it may be necessary to adjust the type element. This element can take on any keystore type
+supported by the JSSE provider being used (see the JSSE documentation for details). The out of the box
+configuration specifies JKS (Java Keystore).</p>
+<p>The remaining children should not need to be deleted or adjusted.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Configuring a Service to Use TLS">
+<strong>Configuring a Service to Use TLS</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Each of the services - <a href="smtp_configuration.html">SMTP</a>,
+<a href="pop3_configuration.html">POP3</a>, <a href="nntp_configuration.html">NNTP</a>,
+and <a href="remotemanager_configuration.html">RemoteManager</a> - supports use of TLS. Each of
+these services has an optional boolean configuration element <b>useTLS</b> which is used to toggle
+use of TLS for the service. When this value is set to true, that particular service will use the "ssl"
+server socket factory to spawn server sockets.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Verifying a TLS-enabled James Service">
+<strong>Verifying a TLS-enabled James Service</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>After you've configured a particular service to use TLS/SSL connections, the service port
+should no longer accept unencrypted TCP/IP connections. This can be tested by using a telnet
+client to directly connect to the service port. The telnet connection should simply hang until
+the client times out.</p>
+<p>
+To validate that the port is properly accepting SSL connections an SSL client can be used to
+open a connection to the service port. One such client is OpenSSL, available from the
+<a href="http://www.openssl.org">OpenSSL web site</a>. Follow the instructions provided with
+the SSL client to create a connection to the service port. Upon connection, the usual
+service greeting should appear.</p>
+</div>
+</div>
+</div>
+</p>
+</div>
+</td>
+</tr>
+<!--FOOTER SEPARATOR-->
+<tr>
+<td colspan="2">
+<hr size="1" noshade=""/>
+</td>
+</tr>
+<tr>
+<td colspan="2">
+<div class="page-footer">
+<em>
+ Copyright © 1999-2006, The Apache Software Foundation
+ </em>
+</div>
+</td>
+</tr>
+</table>
+</body>
+</html>
Added: james/server/trunk/phoenix-deployment/www/using_database.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/using_database.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/using_database.html (added)
+++ james/server/trunk/phoenix-deployment/www/using_database.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,337 @@
+<?xml version="1.0" encoding="iso-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+<title>Apache James - Mail and News server - James 2.3 - Using a Database</title>
+<LINK TITLE="Style" HREF="stylesheet.css" TYPE="text/css" REL="stylesheet"/>
+</head>
+<body>
+<table cellspacing="0" width="100%" border="0" class="page-header">
+<!--PAGE HEADER-->
+<tr>
+<td colspan="2">
+<!--ASF LOGO-->
+<a href="http://www.apache.org/">
+<img border="0" alt="The ASF" align="left" src="http://www.apache.org/images/asf_logo_wide.gif"/>
+</a>
+<!--PROJECT LOGO-->
+<a href="http://james.apache.org/">
+<img border="0" alt="James - Java Apache Mail Enterprise Server" align="right" src="./images/james-logo.jpg"/>
+</a>
+</td>
+</tr>
+</table>
+<table cellspacing="4" width="100%" border="0">
+<tr>
+<!--LEFT SIDE NAVIGATION-->
+<td nowrap="true" valign="top" class="left-navbar">
+<table cellpadding="0" cellspacing="0" width="100%" border="0">
+<tr>
+<td>
+<a href="http://apachecon.com">
+<img border="0" alt="ApacheCon Promotion" align="left" src="http://www.apache.org/ads/ApacheCon/234x60-2006-us.gif"/>
+</a>
+</td>
+</tr>
+</table>
+<navbar name="lhs">
+
+ <p>
+<strong>Concepts</strong>
+</p>
+<ul>
+<li>
+<a href="./summary.html">Summary</a>
+</li>
+<li>
+<a href="./spoolmanager.html">SpoolManager</a>
+</li>
+<li>
+<a href="./repositories.html">Repositories</a>
+</li>
+<li>
+<a href="./mailet_api.html">The Mailet API</a>
+</li>
+</ul>
+
+ <p>
+<strong>How to...</strong>
+</p>
+<ul>
+<li>
+<a href="./build_instructions.html">Build James</a>
+</li>
+<li>
+<a href="./installation_instructions.html">Install James</a>
+</li>
+</ul>
+
+ <p>
+<strong>Configuration</strong>
+</p>
+<ul>
+<li>
+<a href="./dns_configuration.html">DNS Server</a>
+</li>
+<li>
+<a href="./pop3_configuration.html">POP3 Server</a>
+</li>
+<li>
+<a href="./smtp_configuration.html">SMTP Server</a>
+</li>
+<li>
+<a href="./nntp_configuration.html">NNTP Server</a>
+</li>
+<li>
+<a href="./fetchmail_configuration.html">FetchMail</a>
+</li>
+<li>
+<a href="./remotemanager_configuration.html">RemoteManager</a>
+</li>
+<li>
+<a href="./spoolmanager_configuration.html">SpoolManager</a>
+</li>
+<li>
+<a href="./serverwide_configuration.html">Server-wide</a>
+</li>
+<li>
+<a href="./adding_users.html">Adding Users</a>
+</li>
+<li>
+<a href="./provided_matchers.html">Provided Matchers</a>
+</li>
+<li>
+<a href="./provided_mailets.html">Provided Mailets</a>
+</li>
+</ul>
+
+ <p>
+<strong>Common Configurations</strong>
+</p>
+<ul>
+<li>
+<a href="./smtp_auth.html">Using SMTP AUTH</a>
+</li>
+<li>
+<a href="./using_database.html">Using a Database with James</a>
+</li>
+<li>
+<a href="./usingTLS.html">Using TLS/SSL</a>
+</li>
+<li>
+<a href="./james_and_sendmail.html">James and Sendmail</a>
+</li>
+<li>
+<a href="./mailing_lists.html">Creating Mailing Lists</a>
+</li>
+</ul>
+
+ <p>
+<strong>Customization</strong>
+</p>
+<ul>
+<li>
+<a href="./custom_matcher.html">How to write a custom Matcher</a>
+</li>
+<li>
+<a href="./custom_mailet.html">How to write a custom Mailet</a>
+</li>
+</ul>
+
+ <p>
+<strong>Project</strong>
+</p>
+<ul>
+<li>
+<a href="./changelog.html">Changelog</a>
+</li>
+</ul>
+
+ </navbar>
+</td>
+<!--MAIN BODY-->
+<td align="left" valign="top" class="main-body">
+<div class="section">
+<div class="section-header">
+<a name="Database Configuration">
+<strong>Database Configuration</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<p>James has the capacity to use a JDBC-compatible database for storage of both message and user
+data. This section explains how to configure James to utilize a database for storage.</p>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Requirements">
+<strong>Requirements</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Using James with a database backend has certain requirements. Database configuration is
+extremely vendor-specific, so we can only state the requirements in general terms.</p>
+<p>There must be a database instance accessible from the James server. An account with appropriate
+privileges (select, insert, delete into tables, and on initial startup creation of tables) and
+with sufficient quota for the data to be inserted into the database must be available. Also,
+since James will use JDBC to access the database, an appropriate JDBC driver must be
+available for installation.</p>
+<p>It is important to verify the functionality of the database before attempting to configure
+James to use it as a repository. This will help ensure that configuration issues are properly
+identified.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Connection Configuration">
+<strong>Connection Configuration</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Configuring the Phoenix container to work with JDBC is the first step in enabling James database support.</p>
+<p>First, Phoenix must be able to load the JDBC classes. To make these classes available to Phoenix, place the
+jar/zip files for the JDBC driver in the lib subdirectory of the James installation directory. Any additional
+libraries upon which the JDBC library depends that are not part of the standard Java distribution should also be
+added to this directory.</p>
+<p>Please note that a MySQL driver is included as part of the James distribution and
+so there is no need to add such a driver to the lib directory.</p>
+<p>Second, the config.xml must be modified so that Phoenix initializes the database connections. The relevant
+configuration is in the database-connections block. The database-connections tag has only a single child tag,
+data-sources. This latter tag is a simple container tag for a number of child elements. It is these child
+elements, <strong>data-source</strong> elements, that define the database connections.</p>
+<p>Each <strong>data-source</strong> tag has a required attribute, <strong>name</strong>. This value
+must be unique to each <strong>data-source</strong> element. It is this <strong>name</strong> that will
+be used to specify the database connection in other parts of the config.xml file.</p>
+<p>The <strong>data-source</strong> element has five children, all of whom are required.
+<ul>
+<li>
+<strong>driver</strong> - The class name of the database driver to be used.</li>
+<li>
+<strong>dburl</strong> - The JDBC connection URL for your database/driver.</li>
+<li>
+<strong>user</strong> - The user id of the database account to be used by this connection.</li>
+<li>
+<strong>password</strong> - The password of the database account to be used by this connection.</li>
+<li>
+<strong>max</strong> - The maximum number of JDBC connections to be used concurrently by this data-source.</li>
+</ul>
+</p>
+
+<p>Generally, you simply configure these entries in the config.xml
+file, which are commented, in order to use a database with James. You
+would then use the db: or dbfile: prefix instead of the file: prefix
+for a particular repository. You are currently free to mix and match
+your use of these different storage types for different repositories.
+See <a href="repositories.html">Repository Configuration</a> for
+more details. A sample configuration is described below.</p>
+
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="SQL Statement Configuration">
+<strong>SQL Statement Configuration</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>The precise SQL statements used by James to modify and view data stored in the database are specified in
+an external configuration file. The sqlResources.xml file
+(which can be found in the apps/james/conf directory) is a sample configuration file that contains the SQL
+statements used by James. The purpose of each of these statements, as well as the repository with which
+they are associated, is documented in situ.</p>
+
+<p>If you are using a SQL database with unusual SQL commands or data types, you may
+need to add special entries to this file. The James team
+does try to keep sqlResources.xml updated, so if you do run into a
+special case, please let us know.</p>
+
+<p>Also, if the database tables are not created a priori, but rather are to be created by James
+upon startup, special attention should be paid to the "create table" statements in this file. Such
+statements tend to be both very database and very database instance specific.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Sample James Configuration">
+<strong>Sample James Configuration</strong>
+</a>
+</div>
+<div class="subsection-body">
+
+<p>The config.xml file has commented out examples for MySQL and
+MSSQL data sources, and for each of the standard repositories. For
+example, to use MySQL, you would uncomment and adjust the following
+data-source element.</p>
+
+<p>You must create the database, in this case named
+<strong>mail</strong>, the user, and assign the user privileges.
+You may create the tables before running James or, if you so choose, James
+will automatically create the tables it needs. In the latter case the user
+must have table creation privileges.</p>
+
+<div class="source">
+<data-source name="maildb" class="org.apache.james.util.mordred.JdbcDataSource">
+ <driver>org.gjt.mm.mysql.Driver</driver>
+ <dburl>jdbc:mysql://127.0.0.1/mail</dburl>
+ <user>username</user>
+ <password>password</password>
+ <max>20</max>
+</data-source>
+</div>
+
+<p>Once the data-source element has been created, it can be referenced elsewhere in the config.xml
+file. For example, the following element tells James to use the maildb data-source and dbfile
+storage mechanism for the message spool:</p>
+
+<div class="source">
+<spoolRepository>
+ <repository destinationURL="dbfile://maildb/spool/spool" type="SPOOL"/>
+</spoolRepository>
+</div>
+
+<p>The following element tells James to store mailboxes in a the maildb data-source:</p>
+
+<div class="source">
+<inboxRepository>
+ <repository destinationURL="db://maildb/inbox/" type="MAIL"/>
+</inboxRepository>
+</div>
+
+<p>The configuration file contains further examples.</p>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="Known Issues">
+<strong>Known Issues</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>There are some vendor-specific subtleties in using databases with James that have been observed
+by some users. These issues (and methods to resolve them) are recorded on the
+<a href="../FAQ.html">James FAQ</a> as they are reported. Please consult the FAQ if you encounter any
+difficulties.</p>
+</div>
+</div>
+</div>
+</p>
+</div>
+</td>
+</tr>
+<!--FOOTER SEPARATOR-->
+<tr>
+<td colspan="2">
+<hr size="1" noshade=""/>
+</td>
+</tr>
+<tr>
+<td colspan="2">
+<div class="page-footer">
+<em>
+ Copyright © 1999-2006, The Apache Software Foundation
+ </em>
+</div>
+</td>
+</tr>
+</table>
+</body>
+</html>
Added: james/server/trunk/pop3server-function/LICENSE.txt
URL: http://svn.apache.org/viewvc/james/server/trunk/pop3server-function/LICENSE.txt?view=auto&rev=521427
==============================================================================
--- james/server/trunk/pop3server-function/LICENSE.txt (added)
+++ james/server/trunk/pop3server-function/LICENSE.txt Thu Mar 22 12:57:00 2007
@@ -0,0 +1,218 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+
+
+
+ THIS PRODUCT ALSO INCLUDES THIRD PARTY SOFTWARE REDISTRIBUTED UNDER THE
+ FOLLOWING LICENSES:
+
+
+
+ Concurrent, Public Domain (see lib/concurrent.LICENSE)
+
+ BouncyCastle, MIT License (see lib/BouncyCastle.LICENSE)
+ http://www.bouncycastle.org/licence.html
+
+ DnsJava, BSD License (see lib/dnsjava.LICENSE)
+ http://www.dnsjava.org/README
+
+ JavaBeans Activation Framework, CDDL License
+ http://glassfish.dev.java.net/public/CDDLv1.0.html
+
+ JavaMail, CDDL License
+ http://glassfish.dev.java.net/public/CDDLv1.0.html
+
+ QDox, ASL 1.1 License (see tools/lib/qdox.LICENSE)
+ http://qdox.codehaus.org/license.html
+
+ MX4J, ASL 1.1 License (see phoenix-bin/bin/lib/mx4j.LICENSE)
+
+ Spice, ASL 1.1 License (see phoenix-bin/bin/lib/spice.LICENSE)
+ http://spice.codehaus.org/license.html
+
+ Wrapper, MIT License (see phoenix-bin/bin/Wrapper.LICENSE)
+ http://wrapper.tanukisoftware.org/doc/english/license.html
+
+ ISO-Relax, MIT License (see phoenix-bin/tools/lib/isorelax.LICENSE)
+
+ MSV, BSD License (see phoenix-bin/tools/lib/msv.LICENSE)
+
+ RelaxNG-Datatype, BSD License (see phoenix-bin/tools/lib/relaxngDatatype.LICENSE)
+
+ XSDLib, BSD License (see phoenix-bin/tools/lib/xsdlib.LICENSE)
+
\ No newline at end of file
Added: james/server/trunk/pop3server-function/NOTICE.txt
URL: http://svn.apache.org/viewvc/james/server/trunk/pop3server-function/NOTICE.txt?view=auto&rev=521427
==============================================================================
--- james/server/trunk/pop3server-function/NOTICE.txt (added)
+++ james/server/trunk/pop3server-function/NOTICE.txt Thu Mar 22 12:57:00 2007
@@ -0,0 +1,11 @@
+
+=========================================================================
+== NOTICE file for use with the Apache License, Version 2.0, ==
+=========================================================================
+
+Apache JAMES
+Copyright 2007 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
\ No newline at end of file
Added: james/server/trunk/pop3server-function/build.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/pop3server-function/build.xml?view=auto&rev=521427
==============================================================================
--- james/server/trunk/pop3server-function/build.xml (added)
+++ james/server/trunk/pop3server-function/build.xml Thu Mar 22 12:57:00 2007
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project default="main" name="pop3server-function">
+ <description>Builds pop3server-function module. This is an function module.</description>
+ <property name="name.module" value="pop3server-function" />
+ <import file="../build-tools/function-build.xml" optional="no" />
+</project>
Added: james/server/trunk/remotemanager-function/LICENSE.txt
URL: http://svn.apache.org/viewvc/james/server/trunk/remotemanager-function/LICENSE.txt?view=auto&rev=521427
==============================================================================
--- james/server/trunk/remotemanager-function/LICENSE.txt (added)
+++ james/server/trunk/remotemanager-function/LICENSE.txt Thu Mar 22 12:57:00 2007
@@ -0,0 +1,218 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+
+
+
+ THIS PRODUCT ALSO INCLUDES THIRD PARTY SOFTWARE REDISTRIBUTED UNDER THE
+ FOLLOWING LICENSES:
+
+
+
+ Concurrent, Public Domain (see lib/concurrent.LICENSE)
+
+ BouncyCastle, MIT License (see lib/BouncyCastle.LICENSE)
+ http://www.bouncycastle.org/licence.html
+
+ DnsJava, BSD License (see lib/dnsjava.LICENSE)
+ http://www.dnsjava.org/README
+
+ JavaBeans Activation Framework, CDDL License
+ http://glassfish.dev.java.net/public/CDDLv1.0.html
+
+ JavaMail, CDDL License
+ http://glassfish.dev.java.net/public/CDDLv1.0.html
+
+ QDox, ASL 1.1 License (see tools/lib/qdox.LICENSE)
+ http://qdox.codehaus.org/license.html
+
+ MX4J, ASL 1.1 License (see phoenix-bin/bin/lib/mx4j.LICENSE)
+
+ Spice, ASL 1.1 License (see phoenix-bin/bin/lib/spice.LICENSE)
+ http://spice.codehaus.org/license.html
+
+ Wrapper, MIT License (see phoenix-bin/bin/Wrapper.LICENSE)
+ http://wrapper.tanukisoftware.org/doc/english/license.html
+
+ ISO-Relax, MIT License (see phoenix-bin/tools/lib/isorelax.LICENSE)
+
+ MSV, BSD License (see phoenix-bin/tools/lib/msv.LICENSE)
+
+ RelaxNG-Datatype, BSD License (see phoenix-bin/tools/lib/relaxngDatatype.LICENSE)
+
+ XSDLib, BSD License (see phoenix-bin/tools/lib/xsdlib.LICENSE)
+
\ No newline at end of file
Added: james/server/trunk/remotemanager-function/NOTICE.txt
URL: http://svn.apache.org/viewvc/james/server/trunk/remotemanager-function/NOTICE.txt?view=auto&rev=521427
==============================================================================
--- james/server/trunk/remotemanager-function/NOTICE.txt (added)
+++ james/server/trunk/remotemanager-function/NOTICE.txt Thu Mar 22 12:57:00 2007
@@ -0,0 +1,11 @@
+
+=========================================================================
+== NOTICE file for use with the Apache License, Version 2.0, ==
+=========================================================================
+
+Apache JAMES
+Copyright 2007 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
\ No newline at end of file
Added: james/server/trunk/remotemanager-function/build.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/remotemanager-function/build.xml?view=auto&rev=521427
==============================================================================
--- james/server/trunk/remotemanager-function/build.xml (added)
+++ james/server/trunk/remotemanager-function/build.xml Thu Mar 22 12:57:00 2007
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project default="main" name="remotemanager-function">
+ <description>Builds remotemanager-function module. This is an function module.</description>
+ <property name="name.module" value="remotemanager-function" />
+ <import file="../build-tools/function-build.xml" optional="no" />
+</project>
Added: james/server/trunk/smtpserver-function/LICENSE.txt
URL: http://svn.apache.org/viewvc/james/server/trunk/smtpserver-function/LICENSE.txt?view=auto&rev=521427
==============================================================================
--- james/server/trunk/smtpserver-function/LICENSE.txt (added)
+++ james/server/trunk/smtpserver-function/LICENSE.txt Thu Mar 22 12:57:00 2007
@@ -0,0 +1,218 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+
+
+
+ THIS PRODUCT ALSO INCLUDES THIRD PARTY SOFTWARE REDISTRIBUTED UNDER THE
+ FOLLOWING LICENSES:
+
+
+
+ Concurrent, Public Domain (see lib/concurrent.LICENSE)
+
+ BouncyCastle, MIT License (see lib/BouncyCastle.LICENSE)
+ http://www.bouncycastle.org/licence.html
+
+ DnsJava, BSD License (see lib/dnsjava.LICENSE)
+ http://www.dnsjava.org/README
+
+ JavaBeans Activation Framework, CDDL License
+ http://glassfish.dev.java.net/public/CDDLv1.0.html
+
+ JavaMail, CDDL License
+ http://glassfish.dev.java.net/public/CDDLv1.0.html
+
+ QDox, ASL 1.1 License (see tools/lib/qdox.LICENSE)
+ http://qdox.codehaus.org/license.html
+
+ MX4J, ASL 1.1 License (see phoenix-bin/bin/lib/mx4j.LICENSE)
+
+ Spice, ASL 1.1 License (see phoenix-bin/bin/lib/spice.LICENSE)
+ http://spice.codehaus.org/license.html
+
+ Wrapper, MIT License (see phoenix-bin/bin/Wrapper.LICENSE)
+ http://wrapper.tanukisoftware.org/doc/english/license.html
+
+ ISO-Relax, MIT License (see phoenix-bin/tools/lib/isorelax.LICENSE)
+
+ MSV, BSD License (see phoenix-bin/tools/lib/msv.LICENSE)
+
+ RelaxNG-Datatype, BSD License (see phoenix-bin/tools/lib/relaxngDatatype.LICENSE)
+
+ XSDLib, BSD License (see phoenix-bin/tools/lib/xsdlib.LICENSE)
+
\ No newline at end of file
Added: james/server/trunk/smtpserver-function/NOTICE.txt
URL: http://svn.apache.org/viewvc/james/server/trunk/smtpserver-function/NOTICE.txt?view=auto&rev=521427
==============================================================================
--- james/server/trunk/smtpserver-function/NOTICE.txt (added)
+++ james/server/trunk/smtpserver-function/NOTICE.txt Thu Mar 22 12:57:00 2007
@@ -0,0 +1,11 @@
+
+=========================================================================
+== NOTICE file for use with the Apache License, Version 2.0, ==
+=========================================================================
+
+Apache JAMES
+Copyright 2007 The Apache Software Foundation
+
+This product includes software developed at
+The Apache Software Foundation (http://www.apache.org/).
+
\ No newline at end of file
Added: james/server/trunk/smtpserver-function/build.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/smtpserver-function/build.xml?view=auto&rev=521427
==============================================================================
--- james/server/trunk/smtpserver-function/build.xml (added)
+++ james/server/trunk/smtpserver-function/build.xml Thu Mar 22 12:57:00 2007
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project default="main" name="smtpserver-function">
+ <description>Builds smtpserver-function module. This is an function module.</description>
+ <property name="name.module" value="smtpserver-function" />
+ <import file="../build-tools/function-build.xml" optional="no" />
+</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org