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 no...@apache.org on 2007/01/08 13:20:56 UTC
svn commit: r494041 [1/2] - in /james/server/branches/v2.3/src/site/xdoc:
changelog.xml index.xml installation_instructions.xml provided_mailets.xml
stylesheets/project.xml summary.xml usingTLS.xml using_database.xml
Author: norman
Date: Mon Jan 8 04:20:55 2007
New Revision: 494041
URL: http://svn.apache.org/viewvc?view=rev&rev=494041
Log:
Copy xml files from next-minor to 2.3 branch for backport previous commits r469117 and r475204
Added:
james/server/branches/v2.3/src/site/xdoc/changelog.xml (with props)
james/server/branches/v2.3/src/site/xdoc/index.xml (with props)
james/server/branches/v2.3/src/site/xdoc/installation_instructions.xml (with props)
james/server/branches/v2.3/src/site/xdoc/provided_mailets.xml (with props)
james/server/branches/v2.3/src/site/xdoc/stylesheets/project.xml (with props)
james/server/branches/v2.3/src/site/xdoc/summary.xml (with props)
james/server/branches/v2.3/src/site/xdoc/usingTLS.xml (with props)
james/server/branches/v2.3/src/site/xdoc/using_database.xml (with props)
Added: james/server/branches/v2.3/src/site/xdoc/changelog.xml
URL: http://svn.apache.org/viewvc/james/server/branches/v2.3/src/site/xdoc/changelog.xml?view=auto&rev=494041
==============================================================================
--- james/server/branches/v2.3/src/site/xdoc/changelog.xml (added)
+++ james/server/branches/v2.3/src/site/xdoc/changelog.xml Mon Jan 8 04:20:55 2007
@@ -0,0 +1,363 @@
+<?xml version="1.0"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<document>
+
+ <properties>
+ <title>ChangeLog</title>
+ <author email="site-dev@james.apache.org">James Project Web Team</author>
+ </properties>
+
+<body>
+
+<p>This document records what was done between releases. As always, thank you to everyone who contributed code, documentation, bug reports, and feedback.
+</p>
+
+<section name="Version 2.3.0 Final">
+<p>Released 23 October 2006</p>
+</section>
+
+<section name="Version 2.3.0rc5">
+<p>Released 12 October 2006</p>
+<p>Detail</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-625'>JAMES-625</a>] - an empty mbox will cause an error at pop3 login</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-644'>JAMES-644</a>] - FileRegexMatcher possibly leaks minor memory on startup</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-649'>JAMES-649</a>] - error "OutOfMemoryError: JAVA HEAP SPACE" in connections log file when doing a POP TOP for 4000 messages</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-655'>JAMES-655</a>] - MboxMailRepository throws NPE when storing mail with mail from: <></li>
+</ul>
+</section>
+
+<section name="Version 2.3.0rc4">
+<p>Released 2 October 2006</p>
+<p>Detail</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-626'>JAMES-626</a>] - Invalid (outdated) urls in config files.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-631'>JAMES-631</a>] - Default host configuration for InSpammerBlacklist is relative: it should contain a trailing "." or it will reject all mail when the default domain has an "*" IN A rule.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-638'>JAMES-638</a>] - Wrong default encoding in text message (Autoconverted: from 8bit to quoted-printable)</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-639'>JAMES-639</a>] - SerialUID is not hardcoded</li>
+</ul>
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-618'>JAMES-618</a>] - Move server-site documents from james/server repository to james/site/server repository</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-634'>JAMES-634</a>] - Fix m2 projects to not lookup dependencies on ibiblio, to simplify the website build and to include 2.2.0 and 2.3.0 docs</li>
+</ul>
+</section>
+
+<section name="Version 2.3.0rc3">
+<p>Released 15 September 2006</p>
+<p>Detail</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-327'>JAMES-327</a>] - Mailet overview not complete</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-579'>JAMES-579</a>] - Update license headers and NOTICE to follow the latest ASF requirements</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-591'>JAMES-591</a>] - LogMessage mailet use wrong configutre option</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-594'>JAMES-594</a>] - JVM_OPTS get passed two times</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-603'>JAMES-603</a>] - Outgoing spooling stuck over old mails when more than 1000 old mails are present in outgoing.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-609'>JAMES-609</a>] - MailImpl.setMessage and possible NPE: regression from 2.2.0 and 2.3.0rc1</li>
+</ul>
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-541'>JAMES-541</a>] - Check what we need to bundle bcprov BouncyCastle JCE provider</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-613'>JAMES-613</a>] - Define a new version for Mailet API and update James.java to return the new version.</li>
+</ul>
+<subsection name="Wish"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-581'>JAMES-581</a>] - Add an "Upgrade documentation" to our docs explaining the upgrade from 2.2.0 to 2.3.0</li>
+</ul>
+</section>
+
+<section name="Version 2.3.0rc2">
+<p>Released 12 August 2006</p>
+<p>Detail</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-574'>JAMES-574</a>] - Annoying logging of whitelist/blacklist nomatching as "unknown host exception thrown: listname" if INFO is enabled</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-580'>JAMES-580</a>] - NPE is issued when receiving a "read receipt" from MS Outlook, and <checkValidSenderDomain> is set to true</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-584'>JAMES-584</a>] - FileStreamStore diskspace leak for removed messages in file based spool under windows</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-585'>JAMES-585</a>] - SMTP Server may leak temporary ($[JAMES}/temp/*.m64) files</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-587'>JAMES-587</a>] - CommandListServManager does not properly handle invalid commands.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-588'>JAMES-588</a>] - XMLResource getString methods have incorrect javadocs, and one will throw an NPE.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-612'>JAMES-612</a>] - James File Repository Error: Too many open files</li>
+</ul>
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-432'>JAMES-432</a>] - Reorganize and update xdocs documentation and site generation</li>
+</ul>
+<subsection name="Wish"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-582'>JAMES-582</a>] - Released packages confusions (name, artifacts)</li>
+</ul>
+</section>
+<section name="Version 2.3.0rc1">
+<p>Released 25 July 2006</p>
+<p>Detail</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-566'>JAMES-566</a>] - Fastfail DNSRBL blacklisted messages are rejected even if the sender user is successfully SMTP AUTHenticated</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-570'>JAMES-570</a>] - James insert a Return-Path: null in outgoing email</li>
+</ul>
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-568'>JAMES-568</a>] - reorganize download area structure</li>
+</ul>
+</section>
+<section name="Version 2.3.0b3">
+<p>Released 15 July 2006</p>
+<p>Detail</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-554'>JAMES-554</a>] - Set the right svn property for excutable files</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-559'>JAMES-559</a>] - Message body get lost after call saveChanges() and move to other processor</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-560'>JAMES-560</a>] - SetMimeHeader not throw an MessagingException if needed config values missed</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-561'>JAMES-561</a>] - User aliasing does not work</li>
+</ul>
+</section>
+<section name="Version 2.3.0b2">
+<p>Unreleased</p>
+<p>Detail</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-527'>JAMES-527</a>] - data-source for default derby maildb is configured with a relative path</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-535'>JAMES-535</a>] - Denial of service (CPU consumption) via a long argument to the MAIL command.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-538'>JAMES-538</a>] - Original headers are lost when trying to alter headers of a cloned message</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-540'>JAMES-540</a>] - catch lifecycle problems for handlers</li>
+</ul>
+<subsection name="Improvement"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-553'>JAMES-553</a>] - Upgrade to Derby 10.1.3.1</li>
+</ul>
+<subsection name="New Feature"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-537'>JAMES-537</a>] - Add ConfigOption to disable the RemoteManager</li>
+</ul>
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-496'>JAMES-496</a>] - Add a default hardcoded configuration for the SMTPHandlerChain</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-529'>JAMES-529</a>] - Add a GenericAddFooter for use in AddFooter and CommandListservFooter</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-536'>JAMES-536</a>] - Decide what to do with repository implementations configured by default (db/dbfile/file)</li>
+</ul>
+</section>
+<section name="Version 2.3.0b1">
+<p>Released 9 June 2006</p>
+<p>Details</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-499'>JAMES-499</a>] - Inconsistent usage of the lastUpdated field for Mail objects</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-505'>JAMES-505</a>] - ClassCastException in UsersRepositoryAliasingForwarding using file based users store</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-512'>JAMES-512</a>] - OutOfMemoryError -- object not released.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-522'>JAMES-522</a>] - Having the ClamAVScan mailet configured, but clamd unavailable when JAMES starts, keeps JAMES from starting.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-524'>JAMES-524</a>] - James fails to create mysql tables with mysql-4.1.</li>
+</ul>
+
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-513'>JAMES-513</a>] - Rename AddHeader and AddHeaderHandler</li>
+</ul>
+</section>
+<section name="Version 2.3.0a3">
+<p>Details</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-456'>JAMES-456</a>] - AddFooter mailet javax.mail.internet.ParseException</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-474'>JAMES-474</a>] - NullPointerException and bodymessage lost with weird configurations in message spooling</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-489'>JAMES-489</a>] - ArrayIndexOutOfBoundsException in RemoteDelivery when an mail has errorstate and error_message 0</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-490'>JAMES-490</a>] - Javamail 1.4 regression: SocketFetcher changed to require SocketFactory implementation</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-501'>JAMES-501</a>] - sendmail.py get not include in build</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-503'>JAMES-503</a>] - SpoolManager locking issues</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-504'>JAMES-504</a>] - RemoteDelivery threads do not unlock delayed mails</li>
+</ul>
+</section>
+<section name="Version 2.3.0a2">
+<p>Details</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-368'>JAMES-368</a>] - AddFooter couldn't process mails which MimeType is multipart/related</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-419'>JAMES-419</a>] - NPE during 8bit conversion of non-mime messages</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-434'>JAMES-434</a>] - NPE on empty sender and AUTHenticated user</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-443'>JAMES-443</a>] - AddFooter and Encoding issues</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-446'>JAMES-446</a>] - NPE while fetching mail (FetchMail)</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-447'>JAMES-447</a>] - ClassCastException when storing multipart message without Msg ID</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-452'>JAMES-452</a>] - Broken messages after passing james</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-455'>JAMES-455</a>] - AddFooter mailet throw UnsupportedEncodingException</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-458'>JAMES-458</a>] - SSL not working in James 2.3.0a1</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-459'>JAMES-459</a>] - Incompatible/Duplicate excalibur-cli-1.0.jar library in classpath</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-460'>JAMES-460</a>] - Running James as an NT service</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-462'>JAMES-462</a>] - Error in message.getLineCount (Error using NotifyPostmaster with James 2.3)</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-466'>JAMES-466</a>] - java.sql.SQLException: Error reading from InputStream java.io.IOException in current trunk</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-467'>JAMES-467</a>] - corrupt messages in james trunk</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-470'>JAMES-470</a>] - DNSRBLHandler config error</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-473'>JAMES-473</a>] - AddHeaderHandler configure bug</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-475'>JAMES-475</a>] - SQLException on james trunk after build and without modifications of config.xml</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-476'>JAMES-476</a>] - NPE in RemoteDelivery</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-482'>JAMES-482</a>] - incorrect state on duplicate mail (LinearProcessor)</li>
+</ul>
+
+<subsection name="Improvement"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-158'>JAMES-158</a>] - Stream body in JDBCMailRepository.store(Mail)</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-299'>JAMES-299</a>] - Support for SMTP auth to gateway server in RemoteDelivery mailet</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-371'>JAMES-371</a>] - Speed improvement in SpoolManager</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-438'>JAMES-438</a>] - add GenericMailet.getInitParameter(name,default)</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-440'>JAMES-440</a>] - Improve DBCP: provide more DBCP options, like removeAbandoned</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-441'>JAMES-441</a>] - Add an option to support aliases (CNAME) for MX records</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-445'>JAMES-445</a>] - Enforcement for HELO/EHLO commands before MAIL</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-450'>JAMES-450</a>] - "LocalUsers" user repository should be wired in the assembly and not hardcoded in components</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-469'>JAMES-469</a>] - Make SMTP message queuing configurable (as an Handler)</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-477'>JAMES-477</a>] - Configure option to disable heloEhloEnforcement to be compatible with james < 2.3.0</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-478'>JAMES-478</a>] - Only check against RBL if the client is not allowed to relay</li>
+</ul>
+
+<subsection name="New Feature"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-427'>JAMES-427</a>] - [PATCH] Introduce Unit Testing</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-437'>JAMES-437</a>] - add failed recipient address to log when authorization fails</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-465'>JAMES-465</a>] - Check for valid sender domain in mail from</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-468'>JAMES-468</a>] - Limit MaxRcpt per Email</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-471'>JAMES-471</a>] - Tarpit support</li>
+</ul>
+
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-416'>JAMES-416</a>] - Upgrade to javamail-1.3.3</li>
+</ul>
+
+<subsection name="Wish"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-451'>JAMES-451</a>] - Check for valid domain in HELO</li>
+</ul>
+</section>
+<section name="Version 2.3.0a1">
+<p>Released 15 February 2006</p>
+<p>
+James 2.3.0a1 is "storage" compatible with 2.2.0 (It uses the same files/db formats of James 2.2.0). Configuration should be updated following this instructions. Mailets developed against 2.2.0 are not binary compatible with 2.3.0 but rebuilding mailets in 2.3.0a1 should be an easy task: just replace "Component"s with "Service"s and replace "MailStore" with "Store" and rebuild. Below are some highlights of features and changes already available:
+<ul>
+<li>Phoenix container upgraded to the latest trunk: better classpath management for mailets</li>
+<li>Derby support: also made it the default storage engine</li>
+<li>JavaMail 1.3.2 (not JavaMail 1.3.3 because of known bugs with Base64 encoding)</li>
+<li>Upgraded dependencies to the latest known stable releases (dnsjava, excalibur components, cornerstone, etc.)</li>
+<li>Removed FetchPop</li>
+<li>Command pattern for SMTPServer configuration (make it easier for developers to customize fastfail)</li>
+<li>Increased components granularity/flexibility: many top level components have been refactored to be more modular (look at the new assembly.xml)</li>
+<li>SMTP server now supports 8BITMIME, ENHANCEDSTATUSCODES, PIPELINING</li>
+<li>Introduced a few experimental S/MIME and Bayesian matcher/mailets</li>
+<li>Fixed more than 40 bugs against 2.2.0</li>
+<li>And much more!</li>
+</ul>
+</p>
+<p>Details</p>
+<subsection name="Bug"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-138'>JAMES-138</a>] - Don't keep all mailboxes in-memory forever</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-152'>JAMES-152</a>] - When a Received header is invalid mail may be created with a null remote address and host name</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-154'>JAMES-154</a>] - fetchmail config. files not copied to .sar</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-237'>JAMES-237</a>] - J2 1.5'enum' is a keyword</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-250'>JAMES-250</a>] - fail to start if installed under a "bin" directory</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-264'>JAMES-264</a>] - mail list loop caused by using Return-Path</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-286'>JAMES-286</a>] - Exceeding maximum value with MAIL SIZE causes NullPointerException</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-295'>JAMES-295</a>] - Missing sqlDefs wont be detected</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-296'>JAMES-296</a>] - James does not handle Source Routing</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-300'>JAMES-300</a>] - Fetchmail can't fetch mails</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-305'>JAMES-305</a>] - AttachmentFileNameIs never matches if the message is S/MIME signed</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-306'>JAMES-306</a>] - AttachmentFileNameIs may throw UnsupportedEncodingException</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-311'>JAMES-311</a>] - Nntp very picky with clients</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-312'>JAMES-312</a>] - AttachmentFileNameIs matcher may throw an Exception examining a multipart/alternative message</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-316'>JAMES-316</a>] - java.lang.ArrayIndexOutOfBoundsException from RemoteDelivery</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-317'>JAMES-317</a>] - FromProcessor doesn't delete, throws ClassCastException</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-318'>JAMES-318</a>] - java.lang.NullPointerException when host is unknown</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-320'>JAMES-320</a>] - Some messages cause POP3 output stream to freeze on RETR.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-323'>JAMES-323</a>] - using toUppercase, toLowerCase, equalsIgnoreCase without specifying the locale is a bug</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-328'>JAMES-328</a>] - TOP <msg> 0 does not return a terminator on error</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-329'>JAMES-329</a>] - DefaultUsersJdbcRepository readUserFromResultSet incorrect</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-337'>JAMES-337</a>] - Exception when FromRepository tries to delete a message</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-343'>JAMES-343</a>] - James does not compile using Sun JDK 5.0</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-356'>JAMES-356</a>] - MimeMessageWrapper does not handle multiline headers</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-359'>JAMES-359</a>] - remote address from Received header is not handled</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-361'>JAMES-361</a>] - DSNBounce often report the dsn Status 5.5.0 incorrectly</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-372'>JAMES-372</a>] - Inboxes deleted during OutOfMemoryError</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-378'>JAMES-378</a>] - DSNBounce creates not rfc1894 compliant notifications</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-379'>JAMES-379</a>] - MailImpl.duplicate() should also clone attributes and not only the container HashMap</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-380'>JAMES-380</a>] - ESMTP Compliance fix</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-383'>JAMES-383</a>] - new posts hanging</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-387'>JAMES-387</a>] - Exception in BayesianAnalysis</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-396'>JAMES-396</a>] - Wrong column order (IMHO) in primary key definition for SpoolRepositories.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-413'>JAMES-413</a>] - James does not resolve CNAME DNS registrations</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-417'>JAMES-417</a>] - ClassCastException handling the recipients after a DSNBounce</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-418'>JAMES-418</a>] - Loader uses wrong method to obtain class loader/doesn't set context class loader</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-420'>JAMES-420</a>] - Sometimes messages are delayed or stalled in the spool</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-421'>JAMES-421</a>] - MailImpls sharing MimeMessages / LinearProcessor not cloning it after a partial match.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-428'>JAMES-428</a>] - Deadlock in ServerConnection</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-430'>JAMES-430</a>] - MailImpl#writeContentTo leaks thread</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-431'>JAMES-431</a>] - Line ending and CRLF.CRLF issues in POP3 and SMTP</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-435'>JAMES-435</a>] - James Service Wrapper displays wrong James version</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-436'>JAMES-436</a>] - James trunk cannot be built with jdk1.4</li>
+</ul>
+
+<subsection name="Improvement"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-270'>JAMES-270</a>] - Add MailAttributes to indicate when default values have been applied</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-303'>JAMES-303</a>] - AttachmentFileNameIs matcher should be able to analyze zip file attachments</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-321'>JAMES-321</a>] - Comments on configuri</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-333'>JAMES-333</a>] - Build Broken in HEAD revision</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-338'>JAMES-338</a>] - Upgrade to JavaMail 1.3.2</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-357'>JAMES-357</a>] - DSNBounce should be configured by default</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-360'>JAMES-360</a>] - Support for Additional "received for" headers: e.g. X-Envelope-To</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-363'>JAMES-363</a>] - Move PostmasterAlias from code to james-confix.xml</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-369'>JAMES-369</a>] - Always announce AUTH capability to clients</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-375'>JAMES-375</a>] - RFC 1854 - Command Pipelining support</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-377'>JAMES-377</a>] - rfc2034 ENHANCEDSTATUSCODES compliance</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-388'>JAMES-388</a>] - Upgrade to dnsjava 2.0.0</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-389'>JAMES-389</a>] - Invert "precompilation" logic for jdbc3</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-395'>JAMES-395</a>] - Support latest hsqldb in sqlResources.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-398'>JAMES-398</a>] - Add SMIME mailets for signature verification and message decrypt</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-399'>JAMES-399</a>] - Update bouncycastle to 129 and remove jdk13 compatibility</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-407'>JAMES-407</a>] - James inprotocol handling framework</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-410'>JAMES-410</a>] - Re-enable EHLO support in RemoteDelivery</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-411'>JAMES-411</a>] - update Mailet's Mail to support most of the current james mailets</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-412'>JAMES-412</a>] - Increase James component granularity / flexibility</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-414'>JAMES-414</a>] - Add more flexibility to LocalDelivery</li>
+</ul>
+
+<subsection name="New Feature"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-257'>JAMES-257</a>] - S/MIME Matchers/Mailets</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-258'>JAMES-258</a>] - Add Bayesian Filtering</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-381'>JAMES-381</a>] - Configurable RBL support</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-390'>JAMES-390</a>] - Add derby support</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-423'>JAMES-423</a>] - Give the remote manager a service promt</li>
+</ul>
+
+<subsection name="Task"></subsection>
+<ul>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-149'>JAMES-149</a>] - Add soft-fail to unresolved received from domains</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-190'>JAMES-190</a>] - Apache license 2.0</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-391'>JAMES-391</a>] - Move "candidates" libraries to the official lib / remove unused libraries</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-392'>JAMES-392</a>] - Resolve deprecation use from MailetAPI for the next release</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-393'>JAMES-393</a>] - Use Derby and db providers by default instead of file repositories.</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-394'>JAMES-394</a>] - Remove OLD mm.mysql driver (not compatible with newer MySQL db)</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-400'>JAMES-400</a>] - Move previous SMIME matcher/mailets to the new "smime" subpackages</li>
+<li>[<a href='http://issues.apache.org/jira/browse/JAMES-406'>JAMES-406</a>] - Investigate about libraries upgradability (cornerstone/excalibur/avalon/phoenix)</li>
+</ul>
+
+</section>
+
+</body>
+</document>
Propchange: james/server/branches/v2.3/src/site/xdoc/changelog.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: james/server/branches/v2.3/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/james/server/branches/v2.3/src/site/xdoc/index.xml?view=auto&rev=494041
==============================================================================
--- james/server/branches/v2.3/src/site/xdoc/index.xml (added)
+++ james/server/branches/v2.3/src/site/xdoc/index.xml Mon Jan 8 04:20:55 2007
@@ -0,0 +1,102 @@
+<?xml version="1.0"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<document>
+
+ <properties>
+ <title>James 2.3 - Table of Contents</title>
+ </properties>
+
+<body>
+<section name="James 2.3">
+<p>
+The Java Apache Mail Enterprise Server (a.k.a. Apache James) is a 100% pure Java SMTP and POP3 Mail
+server and NNTP News server designed to be a complete and portable enterprise mail engine
+solution. James is based on currently available open protocols.
+</p>
+<p>
+The James server also serves as a mail application platform. The James project hosts the Apache Mailet API,
+and the James server is a Mailet container. This feature makes it easy to design, write, and deploy
+custom applications for mail processing. This modularity and ease of customization is one of James'
+strengths, and can allow administrators to produce powerful applications surprisingly easily.
+</p>
+<p>
+James is built on top of trunk version of the <a href="http://avalon.apache.org/">Avalon Application Framework</a>. This
+framework encourages a set of good development practices such as Component Oriented Programming and
+Inversion of Control. The standard distribution of James includes
+<a href="http://avalon.apache.org/phoenix">Phoenix Avalon Framework container</a>. This stable
+and robust container provides a strong foundation for the James server.
+</p>
+<p>
+This documentation is intended to be an introduction to the concepts behind the James implementation, as well
+as a guide to installing, configuring, (and for developers) building the James server.
+</p>
+<subsection name="Table of Contents">
+<p>
+I. James Concepts
+<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>
+II. How To Build James
+<ul>
+<li><a href="build_instructions.html">Building James</a></li>
+</ul>
+III. How To Install James
+<ul>
+<li><a href="installation_instructions.html">Installing James</a></li>
+</ul>
+IV. Configuring James
+<ul>
+<li><a href="dns_configuration.html">DNS Server Configuration</a></li>
+<li><a href="pop3_configuration.html">POP3 Server Configuration</a></li>
+<li><a href="smtp_configuration.html">SMTP Server Configuration</a></li>
+<li><a href="nntp_configuration.html">NNTP Server Configuration</a></li>
+<li><a href="fetchmail_configuration.html">fetchMail Configuration</a></li>
+<li><a href="remotemanager_configuration.html">RemoteManager Configuration</a></li>
+<li><a href="repositories.html">Repository Configuration</a></li>
+<li><a href="spoolmanager_configuration.html">SpoolManager Configuration</a></li>
+<li><a href="serverwide_configuration.html">Server-wide Configuration</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>
+V. Common Configurations
+<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="mailing_lists.html">Creating Mailing Lists</a></li>
+</ul>
+VI. Customizing James
+<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>
+V. Other Information
+<ul>
+<li><a href="upgrade_instructions.html">Upgrade James</a></li>
+</ul>
+</p>
+</subsection>
+</section>
+</body>
+</document>
Propchange: james/server/branches/v2.3/src/site/xdoc/index.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: james/server/branches/v2.3/src/site/xdoc/installation_instructions.xml
URL: http://svn.apache.org/viewvc/james/server/branches/v2.3/src/site/xdoc/installation_instructions.xml?view=auto&rev=494041
==============================================================================
--- james/server/branches/v2.3/src/site/xdoc/installation_instructions.xml (added)
+++ james/server/branches/v2.3/src/site/xdoc/installation_instructions.xml Mon Jan 8 04:20:55 2007
@@ -0,0 +1,105 @@
+<?xml version="1.0"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<document>
+
+ <properties>
+ <title>James 2.3 - Installation</title>
+ </properties>
+<body>
+<section name="Requirements">
+<p>James requires a Java Runtime Environment of Java version 1.4 or higher installed to run the
+James application. The exact JREs available depend on the platform. A JRE must be downloaded and
+installed before James can run. In addition, the environment variable JAVA_HOME must be set to
+the JRE home directory before running James.</p>
+<p>
+On Unix platforms, root access will be required to run James. On these platforms, access to ports
+below 1024 is generally restricted to the root user. As SMTP, POP3, and NNTP all need to open
+server sockets on such ports in standard configurations, James requires root access.
+</p>
+<p>
+Obviously James also requires sufficient disk space, processor power, and network bandwidth. But,
+other than what's been discussed here, it has no additional special requirements.</p>
+</section>
+<section name="Installation Comments">
+<p>James installation 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 installation sequence is: <b>1) Start, 2) Stop, 3) Edit, 4) Restart</b>.</p>
+</section>
+<section name="Installing the Binary">
+<subsection name="Installing a Stand-alone James Server">
+<p>Obtain the full James binary distribution from the <a href="http://james.apache.org/download.cgi">James
+release mirrors</a>. Unpack the archive into your James installation directory. Go to the bin subdirectory of the
+installation directory and run the "run" script (either run.sh or run.bat, depending on your platform). The configuration
+file is now unpacked and available for editing.</p>
+</subsection>
+<subsection name="Deploying a James Server in a Pre-Existing Phoenix Container">
+<p><strong>Warning!</strong> - James requires Phoenix version 4.0.x to run. There is a known issue with logging in Phoenix 4.0, so version
+4.0.1 or higher is strongly recommended. Before attempting to deploy James in a Phoenix container, please make sure
+it meets these version criteria.</p>
+<p>Deploying James in Phoenix is fairly easy. Obtain the james.sar file from the <a href="http://james.apache.org/download.cgi">James
+release mirrors</a>. It can be found in the "Other Binaries"
+area of the distribution directory. After downloading the james.sar,
+simply place it in the apps subdirectory of your Phoenix installation. Restart Phoenix, and the james.sar should unpack and you
+will be ready to configure your James installation.</p>
+</subsection>
+</section>
+
+<section name="Initial Configuration">
+<p>
+After installing the binary, the next step is to adjust the initial configuration. The server should be stopped, and then
+configuration can proceed. The most essential configuration is set in the config.xml file. This file can be
+found in the apps/james/SAR-INF subdirectory of the installation directory.</p>
+<p>The out of the box configuration makes certain assumptions and has some default values that are unlikely to
+be appropriate for real-world servers. There are a few issues that should be addressed immediately upon installation:
+</p>
+<ul>
+<li>RemoteManager Administrator Account - Before the RemoteManager service can be used to add users to this server
+installation an administrator account must be created. More information can be found <a href="remotemanager_configuration.html">here</a>.</li>
+<li>DNS Servers - James needs to have access to a DNS server for domain resolution. The out of the box
+configuration assumes that there is a DNS server on localhost. In general administrators will have to change
+the configuration to point to a valid DNS server. This can be done by adjusting the dnsserver configuration
+block in the config.xml. More information can be found <a href="serverwide_configuration.html">here</a>.</li>
+<li>Managed Domain Names/IP Addresses - Out of the box, James only handles mail that is sent to recipients at
+localhost. It will attempt to deliver all other email to remote SMTP servers. To allow James to handle email
+for your domain or IP address, you simply need to add the appropriate domain name or IP address to the servernames
+section of the config.xml. More information can be found <a href="serverwide_configuration.html">here</a>.</li>
+<li>Postmaster Address - More information can be found <a href="serverwide_configuration.html">here</a>.</li>
+</ul>
+<p>In addition to adjusting these parameters, you may wish to consult the documentation for a discussion of
+common configurations. A list of such configurations, as well as the steps necessary to configure them, can
+be found <a href="index.html">here</a>.</p>
+</section>
+<section name="Starting James with Your Configuration">
+<p>Once you have edited the configuration file you will need to restart James so that the changes take
+effect. When James starts, a list of the James services and the ports on which they are listening should
+be displayed on the console. Additional information about the system configuration is printed in the James log files
+upon startup.</p>
+<p>Finally, after configuration is complete, it will be necessary to create user accounts before the James server
+will be fully operational. Instructions on creating user accounts can be found
+<a href="adding_users.html">here</a>.</p>
+</section>
+
+</body>
+</document>
Propchange: james/server/branches/v2.3/src/site/xdoc/installation_instructions.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: james/server/branches/v2.3/src/site/xdoc/provided_mailets.xml
URL: http://svn.apache.org/viewvc/james/server/branches/v2.3/src/site/xdoc/provided_mailets.xml?view=auto&rev=494041
==============================================================================
--- james/server/branches/v2.3/src/site/xdoc/provided_mailets.xml (added)
+++ james/server/branches/v2.3/src/site/xdoc/provided_mailets.xml Mon Jan 8 04:20:55 2007
@@ -0,0 +1,626 @@
+<?xml version="1.0"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<document>
+
+ <properties>
+ <title>James 2.3 - Provided Mailets</title>
+ </properties>
+
+<body>
+
+<section name="Mailets">
+
+<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>
+
+<subsection name="AddFooter">
+<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>
+</subsection>
+
+<subsection name="AddHabeasWarrantMark">
+<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>
+</subsection>
+
+<subsection name="AddHeader">
+<p>Description: This mailet is <strong>deprecated</strong> .Please use SetMimeHeader .</p>
+</subsection>
+
+<subsection name="AvalonListserv">
+<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>
+</subsection>
+
+<subsection name="AvalonListservManager">
+<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>
+</subsection>
+
+<subsection name="BayesianAnalysis">
+<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>
+</subsection>
+
+<subsection name="BayesianAnalysisFeeder">
+<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>
+</subsection>
+
+<subsection name="Bounce">
+<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>
+</subsection>
+
+<subsection name="ClamAVScan">
+<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>
+</subsection>
+
+<subsection name="CommandListservFooter">
+<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>
+</subsection>
+
+<subsection name="CommandListservManager">
+<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:
+<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>
+</source>
+</p>
+</subsection>
+
+
+<subsection name="DSNBounce">
+<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>
+</subsection>
+
+<subsection name="Forward">
+<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>
+</subsection>
+
+<subsection name="FromRepository">
+<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>
+</subsection>
+
+<subsection name="ICommandListservManager">
+<p>Description: ICommandListservManager is the interface that describes the functionality of any command based list serv managers.</p>
+
+<p>Parameters: None.</p>
+</subsection>
+
+<subsection name="JDBCAlias">
+<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>
+</subsection>
+
+<subsection name="JDBCVirtualUserTable">
+<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>
+</subsection>
+
+<subsection name="LocalDelivery">
+<p>Description: This mailet delivers messages to local mailboxes.</p>
+
+<p>Parameters: None.</p>
+</subsection>
+
+<subsection name="LogMessage">
+<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>
+</subsection>
+
+<subsection name="NotifyPostmaster">
+<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>
+</subsection>
+
+<subsection name="NotifySender">
+<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>
+</subsection>
+
+<subsection name="Null">
+<p>Description: This mailet ends processing for this mail.</p>
+
+<p>Parameters: None.</p>
+</subsection>
+
+<subsection name="PostmasterAlias">
+<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>
+</subsection>
+
+<subsection name="Redirect">
+<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>
+</subsection>
+
+<subsection name="RemoteDelivery">
+<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>
+</subsection>
+
+<subsection name="RemoveAllMailAttributes">
+<p>Description: Removes all attributes on the Mail instance.</p>
+
+<p>Parameters: None.</p>
+</subsection>
+
+<subsection name="RemoveMailAttributes">
+<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>
+</subsection>
+
+<subsection name="Resend">
+<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>
+</subsection>
+
+<subsection name="ServerTime">
+<p>Description: This mailet sends a message to the sender of the original mail message with a server timestamp.</p>
+
+<p>Parameters: None.</p>
+</subsection>
+
+<subsection name="SetMailAttributes">
+<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>
+</subsection>
+
+<subsection name="SetMimeHeader">
+<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>
+</subsection>
+
+<subsection name="SMIMECheckSignature">
+<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>
+</subsection>
+
+<subsection name="SMIMEDecrypt">
+<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>
+</subsection>
+
+<subsection name="SMIMESign">
+<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>
+</subsection>
+
+<subsection name="ToProcessor">
+<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>
+</subsection>
+
+<subsection name="ToMultiRepository">
+<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>
+</subsection>
+
+<subsection name="ToRepository">
+<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>
+</subsection>
+
+<subsection name="UseHeaderRecipients">
+<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>
+</subsection>
+
+<subsection name="UsersRepositoryAliasingForwarding">
+<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>
+</subsection>
+
+<subsection name="WhiteListManager">
+<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>
+</subsection>
+</section>
+</body>
+</document>
Propchange: james/server/branches/v2.3/src/site/xdoc/provided_mailets.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: james/server/branches/v2.3/src/site/xdoc/stylesheets/project.xml
URL: http://svn.apache.org/viewvc/james/server/branches/v2.3/src/site/xdoc/stylesheets/project.xml?view=auto&rev=494041
==============================================================================
--- james/server/branches/v2.3/src/site/xdoc/stylesheets/project.xml (added)
+++ james/server/branches/v2.3/src/site/xdoc/stylesheets/project.xml Mon Jan 8 04:20:55 2007
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<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">
+
+ <menu name="Concepts">
+ <item name="Summary" href="/summary.html" />
+ <item name="SpoolManager" href="/spoolmanager.html" />
+ <item name="Repositories" href="/repositories.html" />
+ <item name="The Mailet API" href="/mailet_api.html" />
+ </menu>
+
+ <menu name="How to...">
+ <item name="Build James" href="/build_instructions.html" />
+ <item name="Install James" href="/installation_instructions.html" />
+ </menu>
+
+ <menu name="Configuration">
+ <item name="DNS Server" href="/dns_configuration.html" />
+ <item name="POP3 Server" href="/pop3_configuration.html" />
+ <item name="SMTP Server" href="/smtp_configuration.html" />
+ <item name="NNTP Server" href="/nntp_configuration.html" />
+ <item name="FetchMail" href="/fetchmail_configuration.html" />
+ <item name="RemoteManager" href="/remotemanager_configuration.html" />
+ <!--
+ <item name="Repository" href="/repositories.html" />
+ -->
+ <item name="SpoolManager" href="/spoolmanager_configuration.html" />
+ <item name="Server-wide" href="/serverwide_configuration.html" />
+ <item name="Adding Users" href="/adding_users.html" />
+ <item name="Provided Matchers" href="/provided_matchers.html" />
+ <item name="Provided Mailets" href="/provided_mailets.html" />
+ </menu>
+
+ <menu name="Common Configurations">
+ <item name="Using SMTP AUTH" href="/smtp_auth.html" />
+ <item name="Using a Database with James" href="/using_database.html" />
+ <item name="Using TLS/SSL" href="/usingTLS.html" />
+ <item name="Creating Mailing Lists" href="/mailing_lists.html" />
+ </menu>
+
+ <menu name="Customization">
+ <item name="How to write a custom Matcher" href="/custom_matcher.html" />
+ <item name="How to write a custom Mailet" href="/custom_mailet.html" />
+ </menu>
+
+ <menu name="Project">
+ <item name="Changelog" href="/changelog.html" />
+ </menu>
+
+ </navbar>
+<!--
+ <navbar name="rhs">
+ <menu name="Project">
+ <item name="Bug Database " href="http://issues.apache.org/jira/browse/JAMES"/>
+ <item name="Source Code" href="http://svn.apache.org/"/>
+ <item name="Who We Are" href="/weare.html"/>
+ <item name="Contributing" href="/contribute.html"/>
+ <item name="Standards" href="/code-standards.html"/>
+ <item name="License" href="/license.html"/>
+ <item name="Changelog" href="/changelog.html"/>
+ <item name="TODO" href="/todo.html"/>
+ </menu>
+ <menu name="Translated">
+ <item name="Japanese (web)" href="http://james.terra-intl.com/"/>
+ </menu>
+ <menu name="Related Projects">
+ <item name="jSPF" href="http://james.apache.org/jspf/index.html"/>
+ <item name="Jakarta" href="http://jakarta.apache.org/index.html"/>
+ <item name="Ant" href="http://ant.apache.org/index.html"/>
+ <item name="Avalon" href="http://avalon.apache.org/index.html"/>
+ </menu>
+ <menu name="Useful Information">
+ <item name="Get Involved" href="http://jakarta.apache.org/site/getinvolved.html"/>
+ <item name="Reference Library" href="http://jakarta.apache.org/site/library.html"/>
+ <item name="Apache" href="http://apache.org/foundation/faq.html"/>
+ </menu>
+ </navbar>
+
+ -->
+ </body>
+</site>
Propchange: james/server/branches/v2.3/src/site/xdoc/stylesheets/project.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: james/server/branches/v2.3/src/site/xdoc/summary.xml
URL: http://svn.apache.org/viewvc/james/server/branches/v2.3/src/site/xdoc/summary.xml?view=auto&rev=494041
==============================================================================
--- james/server/branches/v2.3/src/site/xdoc/summary.xml (added)
+++ james/server/branches/v2.3/src/site/xdoc/summary.xml Mon Jan 8 04:20:55 2007
@@ -0,0 +1,116 @@
+<?xml version="1.0"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<document>
+
+ <properties>
+ <title>James 2.3 - Component Summary</title>
+ </properties>
+
+<body>
+
+<section name="The James Server">
+
+<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>
+
+</section>
+<section name="POP3 Service">
+
+<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>
+
+</section>
+<section name="SMTP Service">
+
+<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>
+
+</section>
+<section name="NNTP Service">
+
+<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>
+
+</section>
+<section name="FetchMail">
+
+<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>
+</section>
+<section name="The SpoolManager, Matchers, and Mailets">
+
+<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>
+
+</section>
+<section name="Repositories">
+
+<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>
+
+</section>
+<section name="RemoteManager">
+
+<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>
+
+</section>
+</body>
+</document>
Propchange: james/server/branches/v2.3/src/site/xdoc/summary.xml
------------------------------------------------------------------------------
svn:eol-style = native
Added: james/server/branches/v2.3/src/site/xdoc/usingTLS.xml
URL: http://svn.apache.org/viewvc/james/server/branches/v2.3/src/site/xdoc/usingTLS.xml?view=auto&rev=494041
==============================================================================
--- james/server/branches/v2.3/src/site/xdoc/usingTLS.xml (added)
+++ james/server/branches/v2.3/src/site/xdoc/usingTLS.xml Mon Jan 8 04:20:55 2007
@@ -0,0 +1,89 @@
+<?xml version="1.0"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<document>
+
+ <properties>
+ <title>James 2.3 - Using TLS</title>
+ </properties>
+
+<body>
+
+<section name="James 2.3 - Using TLS">
+
+<p>
+This document explains how to enable James 2.3 services to use Transport Layer Security (TLS) for encrypted client-server communication.</p>
+
+<subsection name="Making TLS/SSL Server Sockets Available Inside James">
+<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>
+</subsection>
+<subsection name="Certificate Keystores">
+<p>To use TLS/SSL inside James you will need a certificate keystore.</p>
+</subsection>
+<subsection name="Configuring the Server Socket Factory">
+<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>
+</subsection>
+<subsection name="Configuring a Service to Use TLS">
+<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>
+</subsection>
+<subsection name="Verifying a TLS-enabled James Service">
+<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>
+</subsection>
+</section>
+
+</body>
+</document>
Propchange: james/server/branches/v2.3/src/site/xdoc/usingTLS.xml
------------------------------------------------------------------------------
svn:eol-style = native
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org