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 [6/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/mailing_lists.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/mailing_lists.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/mailing_lists.html (added)
+++ james/server/trunk/phoenix-deployment/www/mailing_lists.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,280 @@
+<?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 - Creating Mailing Lists</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="How To Create Mailing Lists">
+<strong>How To Create Mailing Lists</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<p>One of the frequent questions on the James-User Mailing List is how
+to create a mailing list. This document explains one way of using the
+currently supplied Matchers and Mailets in James v2.3.</p>
+
+<p>Basically, the process requires creating two <mailet> entries
+and a repository. The first mailet handles list commands (currently
+only <i>list-name</i>-on and <i>list-name</i>-off). The second mailet
+handles list messages. The repository will hold the e-mail addresses
+of list subscribers.</p>
+
+<p>The mailets go into the processor chain (e.g., at the top of the
+<i>transport</i> processor), the repository goes into the
+<users-store> block.</p>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Setting up the Mailets">
+<strong>Setting up the Mailets</strong>
+</a>
+</div>
+<div class="subsection-body">
+
+<p>You need to setup two mailets.</p>
+
+<p>The first mailet that you need to setup is an instance of the <a href="provided_mailets.html#AvalonListservManager">Avalon Listserv
+Manager</a> mailet. This will handle subscribing and unsubscribing.
+[Note: the current code does not support confirmed opt-in, just basic
+commands.] The <a href="provided_matchers.html#CommandForListserv">CommandForListserv</a>
+matcher is used to invoke match messages containing commands for the
+mailing list.</p>
+
+<p>The second mailet is an instance of the <a href="provided_mailets.html#AvalonListserv">Avalon Listserv</a>
+mailet. That mailet actually receives messages for the list and
+causes them to be distributed. The <a href="provided_matchers.html#RecipientIs">RecipientIs</a> matcher
+is used to match messages intended for the mailing list.</p>
+
+<p>The following illustrates the two <mailet> elements that need to be added:</p>
+
+<div class="source">
+ <mailet match="CommandForListserv=list-name@domain"
+ class="AvalonListservManager">
+ <repositoryName>list-name</repositoryName>
+ </mailet>
+
+ <mailet match="RecipientIs=list-name@domain" class="AvalonListserv">
+ <repositoryName>list-name</repositoryName>
+ ... list options ...
+ </mailet>
+</div>
+
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Setting up the Repository">
+<strong>Setting up the Repository</strong>
+</a>
+</div>
+<div class="subsection-body">
+
+<p>The mailing list mailets need a repository within which to store
+the subscriber list. There is a separate repository for each mailing
+list, and is completely independent of the user repository used by
+James to manage e-mail accounts. This is configured in the
+<users-store> block of config.xml.</p>
+
+<p>The following illustrates a database-backed repository using JDBC
+with the ListUsersJdbcRepository class. Notice that there will be a
+single table, <i>lists</i>, created in the db://maildb resource
+defined elsewhere. There are currently two columns: the list name and
+the list subscriber.</p>
+
+<div class="source">
+ <repository name="list-name"
+ class="org.apache.james.userrepository.ListUsersJdbcRepository"
+ destinationURL="db://maildb/lists/list-name">
+ <sqlFile>file://conf/sqlResources.xml</sqlFile>
+ </repository>
+</div>
+
+<p>The following illustrates a file-system repository using the
+UsersFileRepository class. [Note: the destination URL is a child
+element when configuring a file-system repository, and an attribute
+when configuring a database-backed repository. This inconsistency
+will be addressed in a future version of James.]</p>
+
+<div class="source">
+ <repository name="list-name"
+ class="org.apache.james.userrepository.UsersFileRepository">
+ <destination URL="file://var/lists/list-name/" />
+ </repository>
+</div>
+
+</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/migrating_datasource.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/migrating_datasource.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/migrating_datasource.html (added)
+++ james/server/trunk/phoenix-deployment/www/migrating_datasource.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,222 @@
+<?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 - Migrating from Avalon database connections to DataSource</title>
+<LINK TITLE="Style" HREF="stylesheet.css" TYPE="text/css" REL="stylesheet"/>
+<meta value="Serge Knystautas" name="author"/>
+<meta value="serge@apache.org" name="email"/>
+</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="Migrating from Avalon database connections to DataSource">
+<strong>Migrating from Avalon database connections to DataSource</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>
+ In James version 2.3, we expose database connections via the javax.sql.DataSource. This document describes how to update code using James previous database connectivity (Avalon's DataSourceComponent).
+</p>
+<ol>
+<li>Remove references to DataSourceSelector.</li>
+<li>Change references of DataSourceComponent to DataSource</li>
+<li>Add imports:
+<div class="source">
+import javax.naming.InitialContext;
+import javax.naming.NamingException;
+import javax.sql.DataSource;
+</div>
+</li>
+<li>Change how the datasource is looked up
+<br/>
+Replace:
+<div class="source">
+ ComponentManager componentManager = (ComponentManager)getMailetContext().getAttribute(Constants.AVALON_COMPONENT_MANAGER);
+ // Get the DataSourceSelector service
+ DataSourceSelector datasources = (DataSourceSelector)componentManager.lookup(DataSourceSelector.ROLE);
+ // Get the data-source required.
+ datasource = (DataSourceComponent)datasources.select(datasourceName);
+</div>
+with
+<div class="source">
+ InitialContext ctx = new InitialContext();
+ datasource = (DataSource) ctx.lookup("java:comp/env/jdbc/" + datasourceName);
+</div>
+Then update exception handling appropriately.
+</li>
+</ol>
+ <p>
+ That's all there is to it. Enjoy!
+ </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/nntp_configuration.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/nntp_configuration.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/nntp_configuration.html (added)
+++ james/server/trunk/phoenix-deployment/www/nntp_configuration.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,282 @@
+<?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 - Configuring the NNTP Service</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="NNTP Configuration">
+<strong>NNTP Configuration</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<p>The NNTP service is controlled by a two configuration blocks in the config.xml. These are the nntpserver block and the nntp-repository block.</p>
+<div class="subsection">
+<div class="subsection-header">
+<a name="The nntpserver block">
+<strong>The nntpserver block</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>The nntpserver tag defines the boundaries of the configuration block. It encloses
+much of the relevant configuration for the NNTP server.</p>
+
+<p>This tag has an optional boolean attribute - <strong>enabled</strong> - that defines whether the service is active or not. The value defaults to "true" if
+not present.</p>
+<p>The standard children of the nntpserver tag are:</p>
+<ul>
+<li>
+<strong>port</strong> - This is an optional integer value. This value is the port on which this NNTP server is configured
+to listen.If the tag or value is omitted, the value will default to the standard NNTP port, 119.</li>
+<li>
+<strong>bind</strong> - This is an optional value. If present, this value is a string describing
+the IP address to which this service should be bound. If the tag or value is absent then the service
+will bind to all network interfaces for the machine.</li>
+<li>
+<strong>useTLS</strong> - This is an optional boolean value. If this value is true, then the "ssl"
+server socket factory is used to generate the server socket for this service. If it is false, the
+"plain" server socket factory is used. In either case this behavior is overridden by the serverSocketType
+tag which is described under the expert configuration options.</li>
+<li>
+<strong>handler</strong> - This is an artifact preserved for backwards compatibility. This tag
+was used to group related parameters. It should disappear in future versions.</li>
+<ul>
+<li>
+<strong>helloName</strong> - This is a required tag with an optional body that defines the server name
+used in the initial service greeting. The tag may have an optional attribute - <strong>autodetect</strong>. If
+the autodetect attribute is present and true, the service will use the local hostname
+returned by the Java libraries. If autodetect is absent or false, the body of the tag will be used. In
+this case, if no body is present, the value "localhost" will be used.</li>
+<li>
+<strong>connectionTimeout</strong> - This is an optional tag with a non-negative integer body. </li>
+<li>
+<strong>authRequired</strong> - This is an optional tag with a boolean body. If true, then the server will
+require authentication before allowing the client to view news articles. If this tag is absent, or the value
+is false then the client will not be prompted for authentication. Only simple user/password authentication is
+supported at this time.</li>
+</ul>
+</ul>
+<p>There are a few additional children of the nntpserver tag that are appropriate for advanced
+configurations. These should only be used by expert administrators. All tags in this group are optional.</p>
+<ul>
+<li>
+<strong>serverSocketFactory</strong> - This is an optional tag with a string body. If the tag is present,
+the body must be the name of one of the server socket factories specified in the socket manager block. Any other
+value will result in an error. If present, this tag overrides the useTLS tag.</li>
+<li>
+<strong>threadGroup</strong> - This is an optional tag with a string body. If the tag is present,
+the body must be the name of one of the thread groups specified in the thread manager block. Any other
+value will result in an error. This tag is best used to fine tune thread allocation between the services.</li>
+<li>
+<strong>connectionLimit</strong> - The connectionLimit parameter specifies the maximum number of client
+connections that this service will allow. If no value is specified, the value defaults to that specified in
+the connectionmanager block. A value of 0 means that there is no limit imposed
+by the service, although resource limitations imposed by other components
+(i.e. max # of threads) may serve to limit the number of open connections.</li>
+</ul>
+</div>
+</div>
+<div class="subsection">
+<div class="subsection-header">
+<a name="The nntp-repository block">
+<strong>The nntp-repository block</strong>
+</a>
+</div>
+<div class="subsection-body">
+The remainder of the NNTP service configuration is controlled by the nntp-repository configuration block. This
+section of configuration data relates to the server-side NNTP article repository.
+<ul>
+<li>
+<strong>readOnly</strong> - This is a required boolean tag. If the value is true, posting will not be
+permitted by the NNTP server.</li>
+<li>
+<strong>rootPath</strong> - This is a required string tag. It must be in the form of a URL with a "file:" prefix. This
+specifies the root directory for the NNTP repository. Groups hosted on the NNTP server will be represented as
+folders under this root, and articles will be stored in the appropriate folders.</li>
+<li>
+<strong>tempPath</strong> - This is a required string tag. It must be in the form of a URL with a "file:" prefix. This
+specifies the directory where the NNTP server will store posted articles before they are added to the spool.</li>
+<li>
+<strong>articleIDPath</strong> - This is a required string tag. It must be in the form of a URL with a "file:" prefix. This
+specifies the directory where the NNTP server will store the mappings between article ID and the groups containing that article.</li>
+<li>
+<strong>articleIDDomainSuffix</strong> - This is a required string tag. It is the suffix appended to all article IDs generated
+by this NNTP server.</li>
+<li>
+<strong>newsgroups</strong> - This is a required container tag. It has a single <strong>newsgroup</strong> child for each newsgroup
+hosted on the server. The body of each of those <strong>newsgroup</strong> tags is the name of the newsgroup.</li>
+</ul>
+</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/pop3_configuration.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/pop3_configuration.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/pop3_configuration.html (added)
+++ james/server/trunk/phoenix-deployment/www/pop3_configuration.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,237 @@
+<?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 - Configuring the POP3 Service</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="POP3 Configuration">
+<strong>POP3 Configuration</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+<p>The POP3 service is controlled by a configuration block in the config.xml.
+The pop3server tag defines the boundaries of the configuration block. It encloses
+all the relevant configuration for the POP3 server. The behavior of the POP service is
+controlled by the attributes and children of this tag.</p>
+
+<p>This tag has an optional boolean attribute - <strong>enabled</strong> - that defines whether the service is active or not. The value defaults to "true" if
+not present.</p>
+<p>The standard children of the pop3server tag are:</p>
+<ul>
+<li>
+<strong>port</strong> - This is an optional integer value. This value is the port on which this POP3 server is configured
+to listen.If the tag or value is omitted, the value will default to the standard POP3 port, 110.</li>
+<li>
+<strong>bind</strong> - This is an optional value. If present, this value is a string describing
+the IP address to which this service should be bound. If the tag or value is absent then the service
+will bind to all network interfaces for the machine.</li>
+<li>
+<strong>useTLS</strong> - This is an optional boolean value. If this value is true, then the "ssl"
+server socket factory is used to generate the server socket for this service. If it is false, the
+"plain" server socket factory is used. In either case this behavior is overridden by the serverSocketType
+tag which is described under the expert configuration options.</li>
+<li>
+<strong>handler</strong> - This is an artifact preserved for backwards compatibility. This tag
+was used to group related parameters. It should disappear in future versions.</li>
+<ul>
+<li>
+<strong>helloName</strong> - This is a required tag with an optional body that defines the server name
+used in the initial service greeting. The tag may have an optional attribute - <strong>autodetect</strong>. If
+the autodetect attribute is present and true, the service will use the local hostname
+returned by the Java libraries. If autodetect is absent or false, the body of the tag will be used. In
+this case, if no body is present, the value "localhost" will be used.</li>
+<li>
+<strong>connectionTimeout</strong> - This is an optional tag with an integer body. </li>
+</ul>
+</ul>
+<p>There are a few additional children of the pop3server tag that are appropriate for advanced
+configurations. These should only be used by expert administrators. All tags in this group are optional.</p>
+<ul>
+<li>
+<strong>serverSocketFactory</strong> - This is an optional tag with a string body. If the tag is present,
+the body must be the name of one of the server socket factories specified in the socket manager block. Any other
+value will result in an error. If present, this tag overrides the useTLS tag.</li>
+<li>
+<strong>threadGroup</strong> - This is an optional tag with a string body. If the tag is present,
+the body must be the name of one of the thread groups specified in the thread manager block. Any other
+value will result in an error. This tag is best used to fine tune thread allocation between the services.</li>
+<li>
+<strong>connectionLimit</strong> - The connectionLimit parameter specifies the maximum number of client
+connections that this service will allow. If no value is specified, the value defaults to that specified in
+the connectionmanager block. A value of 0 means that there is no limit imposed
+by the service, although resource limitations imposed by other components
+(i.e. max # of threads) may serve to limit the number of open connections.</li>
+</ul>
+</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/provided_mailets.html
URL: http://svn.apache.org/viewvc/james/server/trunk/phoenix-deployment/www/provided_mailets.html?view=auto&rev=521427
==============================================================================
--- james/server/trunk/phoenix-deployment/www/provided_mailets.html (added)
+++ james/server/trunk/phoenix-deployment/www/provided_mailets.html Thu Mar 22 12:57:00 2007
@@ -0,0 +1,1156 @@
+<?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 - Provided Mailets</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="Mailets">
+<strong>Mailets</strong>
+</a>
+</div>
+<p>
+<div class="section-body">
+
+<p>James provides a number of implemented Mailets for use by James administrators in their
+configurations. These are primarily mailets that members of the James developer or user
+communities have found useful in their own configurations. A description of how to configure
+Mailets and use them in the James SpoolManager can be found <a href="spoolmanager_configuration.html">here</a>.</p>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="AddFooter">
+<strong>AddFooter</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet adds a text footer to the message.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>text</strong> (required) - the text that will be added as a footer to the message.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="AddHabeasWarrantMark">
+<strong>AddHabeasWarrantMark</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet adds a Habeas warrant mark (see <a href="http://habeas.com">http://habeas.com</a> for details) to the message.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="AddHeader">
+<strong>AddHeader</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet is <strong>deprecated</strong> .Please use SetMimeHeader .</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="AvalonListserv">
+<strong>AvalonListserv</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Provides basic list server functionality. Implements basic filters for emails sent to the list,
+including restriction of senders to members, diallowing attachments in list messages, and subject line
+processing</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryName</strong> (required) - the name of the user repository that contains the users
+for this list.</li>
+<li>
+<strong>membersonly</strong> (optional) - whether only members of the list can send messages to this
+list. Defaults to false.</li>
+<li>
+<strong>attachmentsallowed</strong> (optional) - whether attachments are allowed in messages sent to this
+list. Defaults to true.</li>
+<li>
+<strong>replytolist</strong> (optional) - whether the reply-to address for all messages sent to this
+list is set to the list address. Defaults to true.</li>
+<li>
+<strong>subjectprefix</strong> (optional) - a String value. If set, this value is prepended to the subject
+line of all messages sent to the list.</li>
+<li>
+<strong>autobracket</strong> (optional) - a boolean value. If a subjectprefix is set, this value determines
+whether the prefix is bracketed before being prepended to the subject line. Defaults to true.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="AvalonListservManager">
+<strong>AvalonListservManager</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Processes list management commands of the form <list-name>-on@<host> and
+<list-name>-off@<host> where <list-name> and lt;host> are arbitrary. Note
+that this should be used in tandem with a CommandForListserv matcher to ensure that only commands
+intended for a specific list are processed.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryName</strong> (required) - the name of the user repository that contains the users
+for this list.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="BayesianAnalysis">
+<strong>BayesianAnalysis</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Spam detection mailet using bayesian analysis techniques.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryPath</strong> (required) - The repositoryPath which is used.</li>
+<li>
+<strong>headerName</strong> - The HeaderName which get adds to holds the Probalitity. Default is <i>X-MessageIsSpamProbability</i>.</li>
+<li>
+<strong>ignoreLocalSender</strong> - Set to true if you want to ignore messages from local senders. By local sender we mean a return-path
+with a local server part (server listed in <servernames> in config.xml). Default is <i>false</i>.</li>
+<li>
+<strong>maxSize</strong> - Set this to the maximum message size (in bytes) after analysis will be skipped. Default is <i>100000</i>.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="BayesianAnalysisFeeder">
+<strong>BayesianAnalysisFeeder</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Feeds ham OR spam messages to train the BayesianAnalysis mailet.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryPath</strong> (required) - The repositoryPath which is used.</li>
+<li>
+<strong>feedType</strong> (required) - The type of the message which is used to feed the mailet. Allowed values are <i>spam</i> and <i>ham</i>.</li>
+<li>
+<strong>maxSize</strong> - Set this to the maximum message size (in bytes) after analysis will be skipped. Default is <i>100000</i>.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Bounce">
+<strong>Bounce</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Generates a response to the reverse-path address.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>sender</strong> - The senderAddress which will be used for sending the bounce. Possible values: <i>address</i>, <i>postmaster</i> , <i>sender</i>,
+<i>unaltered</i>. Default <i>postmaster</i>.</li>
+<li>
+<strong>attachError</strong> - Attach error. Default is false.</li>
+<li>
+<strong>message</strong> - Set the message which get included in the bounce.</li>
+<li>
+<strong>prefix</strong> - Optional subject prefix prepended to the original message.</li>
+<li>
+<strong>inline</strong> - Specify which mailpart will be included in the email body. Possible values: <i>unaltered</i>, <i>heads</i>, <i>body</i> , <i>all</i>,
+"none". Default "none".</li>
+<li>
+<strong>attachment</strong> - Specify which mailpart will be attached to the email. Possible values: <i>none</i>, <i>heads</i>, <i>body</i>, <i>all</i>,
+<i>message</i>. Default <i>message</i>.</li>
+<li>
+<strong>passThrough</strong> - If set to false the email will not processed after the bounce. Possible values: <i>true</i>, <i>false</i>.
+Default <i>true</i>.</li>
+<li>
+<strong>fakeDomainCheck</strong> - If set to false true will check if the sender domain is valid. Possible values: <i>true</i>, <i>false</i>.
+Default <i>true</i>.</li>
+<li>
+<strong>debug</strong> - If set true you can enable debugging. Possible values: <i>true</i>, <i>false</i>.
+Default <i>false</i>.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="ClamAVScan">
+<strong>ClamAVScan</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Does an antivirus scan check using a ClamAV daemon (CLAMD).</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>host</strong> - The host name of the server where CLAMD runs. The default is <i>localhost</i>
+</li>
+<li>
+<strong>port</strong> - The port on which CLAMD listens. The default is <i>3310</i>.</li>
+<li>
+<strong>maxPings</strong> - The maximum number of connection retries during startup. If the value is <i>0</i> no startup
+test will be done.</li>
+<li>
+<strong>pingIntervalMillis</strong> (required) - The interval (in milliseconds) between each connection retry during startup.
+The default is <i>30000</i> (30 seconds)</li>
+<li>
+<strong>streamBufferSize</strong> - the BufferedOutputStream buffer size to use writing to the <I>stream connection</I>. The
+default is <i>8192</i>.</li>
+<li>
+<strong>debug</strong> - If set true you can enable debugging. Possible values: <i>true</i>, <i>false</i>.
+Default <i>false</i>.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="CommandListservFooter">
+<strong>CommandListservFooter</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: CommandListservFooter is based on the AddFooter mailet. It is used by the CommandListservProcessor to inject a footer into mailing list.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="CommandListservManager">
+<strong>CommandListservManager</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p> Description: CommandListservManager is the default implementation of ICommandListservManager.
+It loads all the configured IListServCommands and delegates to them at runtime.
+<br/>
+It isn't responsible for procesing messages sent to the main mailing list, but is responsible for
+individual commands sent by users, such as: info, subscribe, etc...
+<br/>
+Requests sent to the CommandListservManager take the form of:
+<pre>
+<listName>-<commandName>@domain
+</pre>
+
+If the command isn't recognized an error will be sent.
+<br/>
+<br/>
+The configuration for this mailet sould be in the 'root' processor block.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>listName</strong> - The listname </li>
+<li>
+<strong>displayName</strong> - The full listname</li>
+<li>
+<strong>listOwner</strong> - An emailaddress which will be used as owneraddress.</li>
+<li>
+<strong>repositoryName</strong> - the repository name </li>
+<li>
+<strong>listDomain</strong> - The domain</li>
+</ul>
+</p>
+<br/>
+<p> Example configuration:
+<div class="source">
+<mailet match="CommandListservMatcher=announce@localhost" class="CommandListservManager">
+ <listName>announce</listName>
+ <displayName>Announce mailing list</displayName>
+ <listOwner>owner@localhost</listOwner>
+ <repositoryName>list-announce</repositoryName>
+ <listDomain>localhost</listDomain>
+
+ <commandpackages>
+ <commandpackage>org.apache.james.transport.mailets.listservcommands</commandpackage>
+ </commandpackages>
+
+ <commands>
+ <command name="subscribe" class="Subscribe"/>
+ <command name="subscribe-confirm" class="SubscribeConfirm"/>
+ <command name="unsubscribe" class="UnSubscribe"/>
+ <command name="unsubscribe-confirm" class="UnSubscribeConfirm"/>
+ <command name="error" class="ErrorCommand"/>
+ <command name="owner" class="Owner"/>
+ <command name="info" class="Info"/>
+ </commands>
+ </mailet>
+</div>
+</p>
+</div>
+</div>
+
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="DSNBounce">
+<strong>DSNBounce</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Generates a Delivery Status Notification (DSN). Note that this is different than a mail-client's
+reply, which would use the Reply-To or From header.Bounced messages are attached in their entirety (headers and
+content) and the resulting MIME part type is "message/rfc822".
+The reverse-path and the Return-Path header of the response is set to <i>null</i> (<i><></i>),
+meaning that no reply should be sent.
+A sender of the notification message can optionally be specified.
+If one is not specified, the postmaster's address will be used.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>sender</strong> - An address, postmaster,sender or unaltered. Default is <i>postmaster</i>
+</li>
+<li>
+<strong>prefix</strong> - Optional subject prefix prepended to the original message.</li>
+<li>
+<strong>attachment</strong> - Values are message, heads or none. Default is <i>message</i>.
+test will be done.</li>
+<li>
+<strong>messageString</strong> - the message sent in the bounce, the first occurrence of the pattern [machine] is replaced with the name of the executing machine, default=Hi. This is the James mail server at [machine] .... </li>
+<li>
+<strong>passThrough</strong> (optional) - a boolean value (true/false) indicating whether
+processing should continue on the message is on. If false, the original message is GHOSTed. Defaults to false.</li>
+<li>
+<strong>debug</strong> - If set true you can enable debugging. Possible values: <i>true</i>, <i>false</i>.
+Default <i>false</i>.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Forward">
+<strong>Forward</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet forwards the message to a set of recipients.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>forwardto</strong> (required) - a comma delimited list of email addresses.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="FromRepository">
+<strong>FromRepository</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet ee-spools mail found in the specified Repository.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryPath</strong> (required) - The repositoryPath which is used.</li>
+<li>
+<strong>processor</strong> (required) - The target processor to move the mails to.</li>
+<li>
+<strong>delete</strong> - If set to true the mails get deleted after re-spooling. Default is <i>false</i>.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="ICommandListservManager">
+<strong>ICommandListservManager</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: ICommandListservManager is the interface that describes the functionality of any command based list serv managers.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="JDBCAlias">
+<strong>JDBCAlias</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet does alias translation for email addresses stored in a database table.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>mappings</strong> (required) - a URL of the form db://<data-source>/<table>, where
+<table> is the table in the database containing the alias info and <data-source> is the name
+of the data-source in config.xml that is to be used.</li>
+<li>
+<strong>source_column</strong> (required) - the column containing the aliases.</li>
+<li>
+<strong>target_column</strong> (required) - the column containing the alias targets.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="JDBCVirtualUserTable">
+<strong>JDBCVirtualUserTable</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet does complex alias translation for email addresses stored in a database table.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>table</strong> (required) - the URL describing the database table. This URL has the form
+db://<data-source>/<table> where <data-source> and <table> are the names of
+the data-source as defined in config.xml and the table in the database.</li>
+<li>
+<strong>sqlquery</strong> (optional) - the text of the SQL query used by the mailet to do user
+lookup. The default is "select VirtualUserTable.target_address from VirtualUserTable, VirtualUserTable as VUTDomains where (VirtualUserTable.user like ? or VirtualUserTable.user like '\\%') and (VirtualUserTable.domain like ? or (VirtualUserTable.domain like '\\%' and VUTDomains.domain like ?)) order by concat(VirtualUserTable.user,'@',VirtualUserTable.domain) desc limit 1"</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="LocalDelivery">
+<strong>LocalDelivery</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet delivers messages to local mailboxes.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="LogMessage">
+<strong>LogMessage</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Logs Message Headers and/or Body.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>passThrough</strong> (optional) - If the "passThrough" in confs is true the mail will be left untouched in
+the pipe. If false will be destroyed. Default is true.</li>
+<li>
+<strong>headers</strong> (optional) - If set to true the headers get logged. Default is true"</li>
+<li>
+<strong>body</strong> (optional) - If set to true the body get logged. Default is true.</li>
+<li>
+<strong>bodyMax</strong> (optional) - The max length wich should be logged. Default is log all.</li>
+<li>
+<strong>comment</strong> (optional) - The comment which should be logged Default is none.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="NotifyPostmaster">
+<strong>NotifyPostmaster</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet forwards the message as an attachment to the James postmaster.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>sendingAddress</strong> (optional) - the address from which the forwarded email will be
+sent. Defaults to the postmaster address.</li>
+<li>
+<strong>notice</strong> (optional) - the text message that will accompany the forwarded message. Defaults
+to "We were unable to deliver the attached message because of an error in the mail server."</li>
+<li>
+<strong>attachStackTrace</strong> (optional) - whether an error stack trace is attached to the forwarded message.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="NotifySender">
+<strong>NotifySender</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet forwards the message as an attachment to the original sender.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>sendingAddress</strong> (optional) - the address from which the forwarded email will be
+sent. Defaults to the postmaster address.</li>
+<li>
+<strong>notice</strong> (optional) - the text message that will accompany the forwarded message. Defaults
+to "We were unable to deliver the attached message because of an error in the mail server."</li>
+<li>
+<strong>attachStackTrace</strong> (optional) - whether an error stack trace is attached to the forwarded message.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Null">
+<strong>Null</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet ends processing for this mail.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="PostmasterAlias">
+<strong>PostmasterAlias</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Intercepts all mails addressed to postmaster@<domain> where <domain> is one
+of the domains managed by this James server and substitutes the configured James postmaster address for
+the original recipient address. This mailet is inserted automatically by James at the head of the root
+processor.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Redirect">
+<strong>Redirect</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: A mailet providing powerful, configurable redirection services.<br/>
+ This mailet can produce listserver, forward and notify behaviour, with the
+ original message intact, attached, appended or left out altogether.<br/>
+ This built in functionality is controlled by the configuration as described
+ <a href="apidocs/org/apache/james/transport/mailets/Redirect.html">here</a>.</p>
+<p>It is also intended to be easily subclassed to make providing bespoke redirection
+ mailets simple. <br/>
+ By extending it and overriding one or more of its methods new behaviour can
+ be quickly created without the author having to address any other issue than
+ the relevant one. For more information see the javadocs
+ <a href="apidocs/org/apache/james/transport/mailets/Redirect.html">here</a>.</p>
+
+<p>Parameters: <a href="apidocs/org/apache/james/transport/mailets/Redirect.html">See javadocs.</a>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="RemoteDelivery">
+<strong>RemoteDelivery</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Manages delivery of messages to recipients on remote SMTP hosts.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>outgoing</strong> (required) - The URL for the repository that will hold messages being processed
+by the RemoteDelivery Mailet.</li>
+<li>
+<strong>delayTime</strong> (optional) - a non-negative Long value that is the time in
+milliseconds between redelivery attempts for a particular mail. Defaults to six hours.</li>
+<li>
+<strong>maxRetries</strong> (optional) - a non-negative Integer value that is number of times
+the Mailet will attempt to deliver a particular mail. Defaults to five.</li>
+<li>
+<strong>timeout</strong> (optional) - The SMTP connection timeout for SMTP connections generated
+by this Mailet. Defaults to 60 seconds.</li>
+<li>
+<strong>deliveryThreads</strong> (optional) - The number of threads this Mailet will use to generate
+SMTP connections.</li>
+<li>
+<strong>gateway</strong> (optional) - The host name of the SMTP server
+to be used as a gateway for this server. If this value is set, then all
+messages will be delivered to the gateway server, regardless of recipient
+address. To specify more than one gateway server, add multiple gateway tags,
+each containing one value. If more than one server is specified, they will be
+tried in order until one is successful. In addition the port may be specified
+for each gateway in the format <host>:<port>. If this
+value is unset, delivery will occur to SMTP servers resolved by MX lookup.</li>
+<li>
+<strong>gatewayPort</strong> (optional) - The default port number of the
+SMTP server to be used as a gateway for this server. This value will be
+employed when a gateway is set <em>and</em> the gateway value does not specify
+a port as described above.</li>
+<li>
+<strong>bind</strong> (optional) - If present, this value is a string
+describing the local IP address to which the mailet should be bound while
+delivering emails. If the tag is absent then the service will bind to the
+default local address of the machine. This tag is useful for multihomed machines.<br/>
+Note: Currently you must use the same IP address for all of those RemoteDelivery
+instances where you explicitly supply a bind address.</li>
+<li>
+<strong>debug</strong> (optional) - a boolean value (true/false) indicating whether debugging is
+on. Defaults to false.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="RemoveAllMailAttributes">
+<strong>RemoveAllMailAttributes</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Removes all attributes on the Mail instance.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="RemoveMailAttributes">
+<strong>RemoveMailAttributes</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Remove attributes on the Mail instance.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>name</strong> (required) - The name of the attribute to remove.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="Resend">
+<strong>Resend</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description:A mailet providing configurable redirection services. For more information see
+the javadocs <a href="apidocs/org/apache/james/transport/mailets/Resend.html">here</a>.</p>
+
+<p>Parameters: <a href="apidocs/org/apache/james/transport/mailets/Resend.html">See javadocs.</a>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="ServerTime">
+<strong>ServerTime</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet sends a message to the sender of the original mail message with a server timestamp.</p>
+
+<p>Parameters: None.</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="SetMailAttributes">
+<strong>SetMailAttributes</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Set attributes on the Mail instance.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>name</strong> (required) - The name of the attribute to set.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="SetMimeHeader">
+<strong>SetMimeHeader</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Set an MimeHeader on a MimeMessage.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>name</strong> (required) - the name of the header to be added to the message.</li>
+<li>
+<strong>value</strong> (required) - the text that will be added as a header to the message.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="SMIMECheckSignature">
+<strong>SMIMECheckSignature</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Verifies the s/mime signature of a message. The s/mime signing ensure that
+the private key owner is the real sender of the message. To be checked by
+this mailet the s/mime signature must contain the actual signature, the
+signer's certificate and optionally a set of certificate that can be used to
+create a chain of trust that starts from the signer's certificate and leads
+to a known trusted certificate.
+</p>
+<p>
+This check is composed by two steps: firstly it's ensured that the signature
+is valid, then it's checked if a chain of trust starting from the signer
+certificate and that leads to a trusted certificate can be created. The first
+check verifies that the the message has not been modified after the signature
+was put and that the signer's certificate was valid at the time of the
+signing. The latter should ensure that the signer is who he declare to be.
+</p>
+
+<p>Parameters: <a href="apidocs/org/apache/james/transport/mailets/smime/SMIMECheckSignature.html">See javadocs.</a>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="SMIMEDecrypt">
+<strong>SMIMEDecrypt</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: This mailet decrypts a s/mime encrypted message. It takes as input an
+encrypted message and it tries to dechiper it using the key specified in its
+configuration. If the decryption is successful the mail will be changed and
+it will contain the decrypted message. The mail attribute
+<code>org.apache.james.SMIMEDecrypt</code> will contain the public
+certificate of the key used in the process. </p>
+
+<p>Parameters: <a href="apidocs/org/apache/james/transport/mailets/smime/SMIMEDecrypt.html">See javadocs.</a>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="SMIMESign">
+<strong>SMIMESign</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Puts a <i>server-side</i> SMIME signature on a message.
+It is a concrete subclass of SMIMEAbstractSign, with very few modifications to it.</p>
+<p>A text file with an explanation text is attached to the original message,
+and the resulting message with all its attachments is signed.
+The resulting appearence of the message is almost unchanged: only an extra attachment
+and the signature are added.</p>
+
+<p>Parameters: <a href="apidocs/org/apache/james/transport/mailets/smime/SMIMESign.html">See javadocs.</a>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="ToProcessor">
+<strong>ToProcessor</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Redirects processing of the mail message to the specified processor.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>processor</strong> (required) - the name of the processor to which the message
+is to be redirected.</li>
+<li>
+<strong>noticeText</strong> (optional) - a String value that, if present,
+is set as the error message of the redirected message. If this value is not
+present, no error message is set.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="ToMultiRepository">
+<strong>ToMultiRepository</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Receives a Mail from JamesSpoolManager and takes care of delivery of the
+message to local inboxes or a specific repository.
+
+Differently from LocalDelivery this does not lookup the UserRepository This
+simply store the message in a repository named like the local part of the
+recipient address.
+
+If no repository is specified then this fallback to MailServer.getUserInbox.
+Otherwise you can add your own configuration for the repository.</p>
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryUrl</strong> (required) - the URL of the repository to which the message
+is to be added.</li>
+<li>
+<strong>addDeliveryHeader</strong> (optional) - a String value which can be used specify a header which will add to the message.
+Default is to not add a header.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="ToRepository">
+<strong>ToRepository</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Places a copy of the message in the specified repository.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryPath</strong> (required) - the URL of the repository to which the message
+is to be added.</li>
+<li>
+<strong>passThrough</strong> (optional) - a boolean value (true/false) indicating whether
+processing should continue on the message is on. If false, the original message is GHOSTed. Defaults to false.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="UseHeaderRecipients">
+<strong>UseHeaderRecipients</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Description: Ignores the recipients associated with the Mail interface. Instead, it regenerates the
+mail recipients from the MimeMessage headers (To, Cc, Bcc) and inserts a new message at the queue root
+these new recipients. The original message is GHOSTed.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>debug</strong> (optional) - a boolean value (true/false) indicating whether debugging is
+on. Defaults to false.</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="UsersRepositoryAliasingForwarding">
+<strong>UsersRepositoryAliasingForwarding</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Receives a Mail from JamesSpoolManager and takes care of delivery of the
+message to local inboxes.</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>enableAliases</strong> (optional) - Specify wether the user aliases should
+be looked up or not. Default is false.</li>
+<li>
+<strong>enableForwarding</strong> (optional) -Enable the forwarding. Default to
+false.</li>
+<li>
+<strong>usersRepository</strong> (optional) - Specific users repository
+name. Default to empty. If empty does lookup the default userRepository.
+</li>
+</ul>
+</p>
+</div>
+</div>
+
+<div class="subsection">
+<div class="subsection-header">
+<a name="WhiteListManager">
+<strong>WhiteListManager</strong>
+</a>
+</div>
+<div class="subsection-body">
+<p>Manages for each local user a "white list" of remote addresses whose messages
+should never be blocked as spam.</p>
+<p>The normal behaviour is to check, for a local sender, if a remote recipient
+is already in the list: if not, it will be automatically inserted.
+This is under the interpretation that if a local sender <i>X</i> sends a message to a
+remote recipient <i>Y</i>, then later on if a message is sent by <i>Y</i> to <i>X</i> it should be
+considered always valid and never blocked; hence <i>Y</i> should be in the white list
+of <i>X</i>.</p>
+<p>Another mode of operations is when a local sender sends a message to <i>whitelistManagerAddress</i>
+with one of three specific values in the subject, to
+(i) send back a message displaying a list of the addresses in his own list;
+(ii) insert some new addresses in his own list;
+(iii) remove some addresses from his own list.
+In all this cases the message will be ghosted and the postmaster will reply
+to the sender.</p>
+<p> The sender name is always converted to its primary name (handling aliases).</p>
+
+<p>Parameters:
+<ul>
+<li>
+<strong>repositoryPath</strong> - The repository path.</li>
+<li>
+<strong>automaticInsert</strong> (optional) - If true automatically inserts the local sender to remote
+recipients entries in the whitelist. Default is false.</li>
+<li>
+<strong>whitelistManagerAddress</strong> (optional) - Set this to an email address of the "whitelist manager" to send
+commands to (default is null).</li>
+<li>
+<strong>displayFlag</strong> (optional) - Set this to a unique text that you can use (by sending a
+message to the "whitelist manager" above) to tell the mailet to send back the contents of the white list. Default is null.</li>
+<li>
+<strong>insertFlag</strong> (optional) - Set this to a unique text that you can use (by sending a message to the "whitelist manager" above)
+to tell the mailet to insert some new remote recipients to the white list. Default is null.</li>
+<li>
+<strong>removeFlag</strong> (optional) - Set this to a unique text that you can use (by sending a message to the "whitelist manager" above)
+to tell the mailet to remove some remote recipients from the white list. Default is null.</li>
+</ul>
+</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>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org