Author: bago
Date: Wed Nov 15 04:36:10 2006
New Revision: 475217
URL: http://svn.apache.org/viewvc?view=rev&rev=475217
Log:
Fixed few more broken links on the new website (JAMES-691)
Added:
james/server/trunk/src/site/xdoc/usingTLS.xml (with props)
Modified:
james/server/trunk/src/site/xdoc/changelog.xml
james/server/trunk/src/site/xdoc/installation_instructions.xml
james/server/trunk/src/site/xdoc/provided_mailets.xml
james/server/trunk/src/site/xdoc/summary.xml
james/server/trunk/src/site/xdoc/using_database.xml
Modified: james/server/trunk/src/site/xdoc/changelog.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/changelog.xml?view=diff&rev=475217&r1=475216&r2=475217
==============================================================================
--- james/server/trunk/src/site/xdoc/changelog.xml (original)
+++ james/server/trunk/src/site/xdoc/changelog.xml Wed Nov 15 04:36:10 2006
@@ -28,6 +28,40 @@
<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>
@@ -50,6 +84,7 @@
<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>
Modified: james/server/trunk/src/site/xdoc/installation_instructions.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/installation_instructions.xml?view=diff&rev=475217&r1=475216&r2=475217
==============================================================================
--- james/server/trunk/src/site/xdoc/installation_instructions.xml (original)
+++ james/server/trunk/src/site/xdoc/installation_instructions.xml Wed Nov 15
04:36:10 2006
@@ -89,7 +89,7 @@
</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="documentation.html">here</a>.</p>
+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
Modified: james/server/trunk/src/site/xdoc/provided_mailets.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/provided_mailets.xml?view=diff&rev=475217&r1=475216&r2=475217
==============================================================================
--- james/server/trunk/src/site/xdoc/provided_mailets.xml (original)
+++ james/server/trunk/src/site/xdoc/provided_mailets.xml Wed Nov 15 04:36:10
2006
@@ -368,7 +368,7 @@
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="javadocs/org/apache/james/transport/mailets/Redirect.html">here</a>.</p>
+ <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
Modified: james/server/trunk/src/site/xdoc/summary.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/summary.xml?view=diff&rev=475217&r1=475216&r2=475217
==============================================================================
--- james/server/trunk/src/site/xdoc/summary.xml (original)
+++ james/server/trunk/src/site/xdoc/summary.xml Wed Nov 15 04:36:10 2006
@@ -82,7 +82,7 @@
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="fetchpop_configuration.html">here</a>.</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">
Added: james/server/trunk/src/site/xdoc/usingTLS.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/usingTLS.xml?view=auto&rev=475217
==============================================================================
--- james/server/trunk/src/site/xdoc/usingTLS.xml (added)
+++ james/server/trunk/src/site/xdoc/usingTLS.xml Wed Nov 15 04:36:10 2006
@@ -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/trunk/src/site/xdoc/usingTLS.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: james/server/trunk/src/site/xdoc/using_database.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/using_database.xml?view=diff&rev=475217&r1=475216&r2=475217
==============================================================================
--- james/server/trunk/src/site/xdoc/using_database.xml (original)
+++ james/server/trunk/src/site/xdoc/using_database.xml Wed Nov 15 04:36:10 2006
@@ -135,7 +135,7 @@
<subsection name="Known Issues">
<p>There are some vendor-specific subtleties in using databases with James
that have been observed
by some users. These issues (and methods to resolve them) are recorded on the
-<a href="FAQ.html">James FAQ</a> as they are reported. Please consult the FAQ
if you encounter any
+<a href="../FAQ.html">James FAQ</a> as they are reported. Please consult the
FAQ if you encounter any
difficulties.</p>
</subsection>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
