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 er...@apache.org on 2010/11/07 09:15:36 UTC

svn commit: r1032225 - in /james/server/trunk/src/site: ./ resources/images/jmx-management/ resources/images/jmx-monitoring/ xdoc/

Author: eric
Date: Sun Nov  7 08:15:36 2010
New Revision: 1032225

URL: http://svn.apache.org/viewvc?rev=1032225&view=rev
Log:
Server V3 user manual is up-to-date for install, monitor, manage sections - enhancements for config section

Modified:
    james/server/trunk/src/site/resources/images/jmx-management/jmx-domainlist.png
    james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-current-connections.png
    james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-gc.png
    james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-memory.png
    james/server/trunk/src/site/site.xml
    james/server/trunk/src/site/xdoc/config-serverwide.xml
    james/server/trunk/src/site/xdoc/config-sieve.xml
    james/server/trunk/src/site/xdoc/config-users.xml
    james/server/trunk/src/site/xdoc/config.xml
    james/server/trunk/src/site/xdoc/dev.xml
    james/server/trunk/src/site/xdoc/install.xml
    james/server/trunk/src/site/xdoc/manage-domains.xml
    james/server/trunk/src/site/xdoc/manage-users.xml
    james/server/trunk/src/site/xdoc/manage-virtualusers.xml
    james/server/trunk/src/site/xdoc/manage.xml
    james/server/trunk/src/site/xdoc/monitor-jmx.xml
    james/server/trunk/src/site/xdoc/monitor-logging.xml
    james/server/trunk/src/site/xdoc/monitor.xml
    james/server/trunk/src/site/xdoc/quick-start.xml
    james/server/trunk/src/site/xdoc/upgrade-2.3.xml

Modified: james/server/trunk/src/site/resources/images/jmx-management/jmx-domainlist.png
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/resources/images/jmx-management/jmx-domainlist.png?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
Binary files - no diff available.

Modified: james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-current-connections.png
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-current-connections.png?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
Binary files - no diff available.

Modified: james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-gc.png
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-gc.png?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
Binary files - no diff available.

Modified: james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-memory.png
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/resources/images/jmx-monitoring/jmx-memory.png?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
Binary files - no diff available.

Modified: james/server/trunk/src/site/site.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/site.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/site.xml (original)
+++ james/server/trunk/src/site/site.xml Sun Nov  7 08:15:36 2010
@@ -82,7 +82,7 @@
         <item name="Logging" href="/monitor-logging.html" />
         <item name="JMX" href="/monitor-jmx.html" />
       </item>
-      <item name="5. Upgrade from James 2.3" href="/upgrade-2.3.html" />
+      <item name="6. Upgrade from James 2.3" href="/upgrade-2.3.html" />
     </menu>
 
     <menu name="Developers Corner">

Modified: james/server/trunk/src/site/xdoc/config-serverwide.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-serverwide.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-serverwide.xml (original)
+++ james/server/trunk/src/site/xdoc/config-serverwide.xml Sun Nov  7 08:15:36 2010
@@ -20,12 +20,12 @@
 <document>
 
  <properties>
-  <title>James 3.0 - Global Server Configuration</title>
+  <title>James 3.0 - Sever Wide Configuration</title>
  </properties>
 
 <body>
 
-  <section name="Global Server Configuration">
+  <section name="Server Wide Configuration">
   
     <p>There are a number of global configuration blocks that do not fall into any one 
       component.  They have effects that are global in scope across the server.  Some of 

Modified: james/server/trunk/src/site/xdoc/config-sieve.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-sieve.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-sieve.xml (original)
+++ james/server/trunk/src/site/xdoc/config-sieve.xml Sun Nov  7 08:15:36 2010
@@ -25,7 +25,7 @@
 
 <body>
 
-  <section name="Configure Sieve">
+  <section name="Sieve Configuration">
   
   </section>
 

Modified: james/server/trunk/src/site/xdoc/config-users.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-users.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-users.xml (original)
+++ james/server/trunk/src/site/xdoc/config-users.xml Sun Nov  7 08:15:36 2010
@@ -27,10 +27,159 @@
 
   <section name="Users Configuration">
 
-  </section>
+    <subsection name="JPA Users">
+  
+    </subsection>
 
-  <section name="Use LDAP to Store Users">
+    <subsection name="LDAP Users">
   
+      <p>
+        This document explains how to enable JAMES to use an LDAP directory as a
+        Users Repository.
+      </p>
+    
+      <p>
+        We have tried to make the LDAP implementation of UsersRepository as
+        flexible a possible, recognising that each installation will have a unique
+        directory schema.
+        <br>We assume that all users that a James Mailserver will handle fall
+          within one single-rooted tree. The root of this tree, ie the lowest node
+          in the directory which is an ancestor for all users served by this
+          mailserver and the mailserver, is called the LDAPRoot. (See diagram)
+        </br>
+        <br>It is entirely possible that an organization may have more than one
+          mail server. Consequently, the fact that a user is in the Directory does
+          not imply that this mailserver should handle mail for them.
+        </br>
+        <br>This implementation of UsersRepository creates one node (object) for
+          each set of mail users. The set called 'LocalUsers' is the set of users
+          whose mail is handled by this server. Other sets include any mail-lists
+          handled by the server. Each member of a set is recorded as an attribute
+          of these objects. These nodes are child nodes of the mailserver.
+        </br>
+        <br>The mailserver will accept mail for local delivery if the user part of
+          the email address matches a member of LocalUsers and if the domain/host
+          part of the email address matches the first servername .
+          (Set servernames autodetect to false and enter the domain served as the
+          first servername, e.g. apache.org).
+        </br>
+        <br>For POP3 authentication, the mailserver first finds the user entry in
+          the directory, underLDAPRoot, whose attribute, specified as
+          MailAttribute in conf, matches user@domain. The mailserver authenticates
+          the POP3 user if it can bind to the directory as that user entry with
+          the offered password.
+        </br>
+        <br>
+          This implementation does not set passwords in the directory. Use a dummy
+          password when invoking adduser in RemoteManger.
+        </br>
+        <br>
+          If ManageGroupAttribute is set to TRUE (as it is by default), then the
+          RemoteManger will add/remove the full DN of the email group to/from the
+          user entry. This facilty allows users to ask the directory what is my
+          mailserver and what email lists am I subscribed to?
+        </br>
+    
+      </p>
+    
+      <table cellspacing="0">
+        <tr>
+          <td> </td>
+          <td align="center">Root of Directory
+            <br>Example: dc=org</br>
+            <br>May not be referenced in conf.xml</br>
+            <br>|</br>
+            <br>|</br>
+          </td>
+          <td> </td>
+        </tr>
+        <tr>
+          <td colspan="3" align="center">-------------------------------------------------------------------------------------------------</td>
+    
+        </tr>
+        <tr>
+          <td align="center" valign="top">|
+            <br>Subtree not served by James</br>
+            <br> e.g.: dc=w3c, dc=org</br>
+           </td>
+          <td align="center" valign="top">|
+            <br>Subtree served by James</br>
+            <br> e.g.: dc=apache, dc=org </br>
+            <br>"LDAPRoot"</br>
+            <br>|</br>
+          </td>
+          <td align="center" valign="top">|
+            <br>Subtree not served by James</br>
+            <br> e.g.: dc=xml, dc=org</br>
+          </td>
+        </tr>
+        <tr>
+          <td> </td>
+          <td>
+            <table cellspace="0">
+              <tr>
+                <td colspan="4" align="center">----------------------------------------------------</td>
+              </tr>
+              <tr>
+                <td align="center" valign="top">|
+                  <br>This mailserver </br>
+                  <br>cn=mailserver.apache.org</br>
+                  <br>|</br>
+                  <br>---------------</br>
+                </td>
+                <td align="center" valign="top">|
+                  <br>A user </br>
+                  <br>cn=King Arthur</br>
+                  <br> memberOfGroup=</br>
+                  <br>cn=LocalUsers etc</br>
+                </td>
+                <td align="center" valign="top">|
+                  <br>A user </br>
+                  <br>cn=Morgan LeFay </br>
+                </td>
+                <td align="center" valign="top">|
+                 <br>Another mailserver </br>
+                 <br>cn=oldmail.apache.org</br>
+                </td>
+              </tr>
+              <tr>
+                <td>
+                  <table cellspace="0">
+                <tr>
+                  <td align="center" valign="top"> |
+                    <br>LocalUsers</br>
+                    <br>member=Arthur</br>
+                  </td>
+                  <td align="center" valign="top"> |
+                        <br>list-james</br>
+                        <br>member=Arthur</br>
+                      </td>
+                </tr>
+              </table>
+                </td>
+                <td> </td>
+                <td> </td>
+                <td> </td>
+              </tr>
+            </table>
+          </td>
+          <td> </td>
+        </tr>
+      </table>
+<!-- 
+      <p>
+        Six entries in JAMES.conf.xml must be set for this to work: 
+        <ul>
+          <li>change usersManager - type to ldap.</li>
+          <li>Set the ldapServer element to point to the correct host and port</li>
+          <li>Set LDAPRoot and ThsServerRDN.</li>
+          <li>Set the direcory FDN and password that should be used to write to the directory.</li>
+          <li>Unless all your users have email addresses of the form, name@the-machine-running-James, set servernames-autodetect to false and apecify the your email domain as the first servername.</li>
+        </ul>
+      </p>
+-->    
+     </subsection>
+
   </section>
 
 </body>

Modified: james/server/trunk/src/site/xdoc/config.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config.xml (original)
+++ james/server/trunk/src/site/xdoc/config.xml Sun Nov  7 08:15:36 2010
@@ -27,24 +27,138 @@
 
   <section name="Configure James Server">
   
-    <p>All configuration files resides in the ./conf/ and ./conf/META-INF/ directories.
+    <p>All configuration files resides in the ./conf and ./conf/META-INF folder.
       You can/must configure James for the following:</p>
     
-    <ul>
-        <li><a href="config-serverwide.html">Server-wide Configuration</a></li>
-        <li><a href="config-domainlist.html">Domain List Configuration</a></li>
-        <li><a href="config-users.html">Users Configuration</a></li>
-        <li><a href="config-mailstores.html">Mail Stores Configuration</a></li>
-        <li><a href="config-dns.html">DNS Configuration</a></li>
-        <li><a href="config-imap4.html">IMAP4 Configuration</a></li>
-        <li><a href="config-pop3.html">POP3 Configuration</a></li>
-        <li><a href="config-smtp-lmtp.html">SMTP LMTP Configuration</a></li>
-        <li><a href="config-mailetcontainer.html">Mailet Container Configuration</a></li>
-        <li><a href="config-fetchmail.html">FetchMail Configuration</a></li>
-        <li><a href="config-remotemanager.html">Remote Manager Configuration</a></li>
-        <li><a href="config-listmanager.html">List Manager Configuration</a></li>
-        <li><a href="config-common.html">Common Configuration</a></li>
-    </ul>
+    <table>
+
+      <tr>
+        <th>Config File Sample</th>
+        <th>Config Area</th>
+        <th>Config Comment</th>
+      </tr>
+    
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/mailserver.xml">mailserver.xml</a></td>
+        <td><a href="config-serverwide.html">Server-wide Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/spring-beans.xml">spring-beans.xml</a></td>
+        <td><a href="config-serverwide.html">Server-wide Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/database.properties">database.properties</a></td>
+        <td><a href="config-serverwide.html">Server-wide Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td>
+          <a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/jmx.properties">jmx.properties</a><br/>
+          <a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/jmx.access">jmx.access</a><br/>
+          <a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/jmx.password">jmx.password</a><br/>
+        </td>
+        <td><a href="config-serverwide.html">Server-wide Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/sqlResources.xml">sqlResources.xml</a></td>
+        <td><a href="config-serverwide.html">Server-wide Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/domainlist.xml">domainlist.xml</a></td>
+        <td><a href="config-domainlist.html">Domain List Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/usersrepository.xml">usersrepository.xml</a></td>
+        <td><a href="config-users.html">Users Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/virtualusertable.xml">virtualusertable.xml</a></td>
+        <td><a href="config-users.html">Users Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/mailstore.xml">mailstore.xml</a></td>
+        <td><a href="config-mailstores.html">Mail Stores Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/miResources.xml">miResources.xml</a></td>
+        <td><a href="config-mailstores.html">Mail Stores Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/jcr-repository.xml">jcr-repository.xml</a></td>
+        <td><a href="config-mailstores.html">Mail Stores Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/dnsservice.xml">dnsservice.xml</a></td>
+        <td><a href="config-dns.html">DNS Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/imapserver.xml">imapserver.xml</a></td>
+        <td><a href="config-imap4.html">IMAP4 Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/pop3server.xml">pop3server.xml</a></td>
+        <td><a href="config-pop3.html">POP3 Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/smtpserver.xml">smtpserver.xml</a></td>
+        <td><a href="config-smtp-lmtp.html">SMTP Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/lmtpserver.xml">lmtpserver.xml</a></td>
+        <td><a href="config-smtp-lmtp.html">LMTP Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/mailetcontainer.xml">mailetcontainer.xml</a></td>
+        <td><a href="config-mailetcontainer.html">Mailet Container Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/fetchmail.xml">fetchmail.xml</a></td>
+        <td><a href="config-fetchmail.html">FetchMail Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/remotemanager.xml">remotemanager.xml</a></td>
+        <td><a href="config-remotemanager.html">Remote Manager Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/james-listmanager.xml">james-listmanager.xml</a></td>
+        <td><a href="config-listmanager.html">List Manager Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td></td>
+        <td><a href="config-tls.html">TLS Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td></td>
+        <td><a href="config-sieve.html">Sieve Configuration</a></td>
+        <td></td>
+      </tr>
+      <tr>
+        <td><a href="https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/log4j.properties">log4j.properties</a></td>
+        <td>See <a href="monitor-logging.html">monitoring with log4j</a> section.</td>
+        <td></td>
+      </tr>
+
+    </table>
 
   </section>
 

Modified: james/server/trunk/src/site/xdoc/dev.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/dev.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/dev.xml (original)
+++ james/server/trunk/src/site/xdoc/dev.xml Sun Nov  7 08:15:36 2010
@@ -32,13 +32,13 @@
       currently consists of:
       <ul>
         <li>Four mail protocol servers: SMTP, POP3, IMAP4 and LMTP.</li>
+        <li>Support for SMTP Auth.</li>
         <li>A remote administration server.</li>
   <!--      <li>an NNTP server,</li>-->
+        <li>Support for TLS (SSL) for mail protocols and remote administration.</li>
         <li>A mail processing engine that supports the Mailet API.</li>
         <li>File-system message storage and a message storage interface to RDBMS's.</li>
         <li>File-system user record storage and an experimental interface to LDAP directories.</li>
-        <li>Support for TLS (SSL) for POP3 and remote administration.</li>
-        <li>Support for SMTP auth.</li>
       </ul>
     </p>
   

Modified: james/server/trunk/src/site/xdoc/install.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/install.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/install.xml (original)
+++ james/server/trunk/src/site/xdoc/install.xml Sun Nov  7 08:15:36 2010
@@ -30,9 +30,7 @@
   <subsection name="Java Virtual Machine">
   
     <p>James requires a Java Runtime Environment. Java version 1.5 or higher is required to run the 
-       James application.</p>
-       
-    <p>The exact JREs available depend on the platform. In addition, the environment variable JAVA_HOME should be set to
+       James application. The exact JREs available depend on the platform. In addition, the environment variable JAVA_HOME should be set to
        the JRE home directory before running James.</p>
     
     <p>James 3.0 has been successfully tested on OpenJDK, Sun JDK and IBM JDK</p>
@@ -68,7 +66,7 @@
   
   </section>
   
-  <section name="Details">
+  <section name="Install Step by Step">
   
   <subsection name="Step 1: Download James"> 
   
@@ -106,99 +104,68 @@
       </div>
   -->
     <p>After unpacking the binary, the next step is to adjust the initial configuration.  
-       The most configuration files reside in the ./conf directory.</p>
+       The configuration files reside in the ./conf and ./conf/META-INF folders.</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="config-remotemanager.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="config-serverwide.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="config-serverwide.html">here</a>.</li>
-        <li>Postmaster Address - More information can be found <a href="config-serverwide.html">here</a>.</li>
+            installation an administrator account must be created - <a href="config-remotemanager.html">read more</a>.</li>
+        <li>Virtual Hosting - Out of the box, James is not configure to manage more than one domain
+            If you need James to server multiple domains, you need to enable virtual hosting
+             - <a href="config-remotemanager.html">read more</a>. If you want to configure you domains
+             in a database rather that in a static XML file, you need to use the JPADomainList
+              - <a href="config-domainlist.html">read more</a></li>
+        <li>Postmaster Address - Change according to your need - <a href="config-serverwide.html">read more</a>.</li>
+        <li>Most UNIX systems require superuser privileges to open sockets below 1024,
+            which includes the IANA-standard SMTP (on port 25), POP3 (on port 110) and IMAP4 (on port 143).
+            These default ports can be changed in the conf file 
+            (read for <a href="config-pop3.html">pop3</a>, <a href="config-smtp.html">smtp</a> 
+            and <a href="config-imap4.html">imap4</a>. Obviously, you
+            would then need to reconfigure your clients. This may not be an option if
+            you want to receive mail from external mailservers.</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>
+       all other configurations.  A list of such configurations, as well as the steps necessary to configure them, can
+       be found <a href="config.html">here</a>.</p>
     
-    <p>Read the short and snappy documentation at docs/index.html for a proper
-        overview of configuring the system.</p>
-  
-    <p>M$ users should just run /bin/run.bat. Unix users will find run.sh under the 
-      same directory. A JVM must be present and its location specified in the JAVA-HOME 
-      environment variable. Set this on windows at the command prompt with something 
-      similar to &quot;set JAVA-HOME=\jdk1.3\bin&quot; on *nix with JAVA-HOME=/jdk1.3/</p>
-      
   </subsection>
   
   <subsection name="Step 4: Start James">
   
-    <p>Go to the bin subdirectory of the installation directory and run "./james start".</p>
+    <p>Go to the bin subdirectory of the installation directory and run <code>$ ./james start</code>.</p>
       
-    <p>Running [run* --help] will provide a simple command line help. </p>
+    <p>Running <code>$ ./james help</code> help will provide the list of commands you can invoke. </p>
     
-    <p>Most UNIX systems require superuser privileges to open sockets below 1024,
-        which includes the IANA-standard SMTP (on port 25) and POP3 (on port 110).
-        These default ports can be changed in the conf.xml file. (Obviously, you
-        would then need to reconfigure your clients. This may not be an option if
-        you want to receive mail from external mailservers.)</p>
-      
-    <p>The Avalon framework will unpack the necessary configuration files you will 
-       need to start the server.  Wait until it is running, stop it again (ctrl-c), and 
-       edit the configuration (thereafter *nix users can run the server in the background 
-       using ./run.sh &amp;). For basic use, you only need to set two items in the 
-       JAMES.conf.xml file: a root password for the remote administration facility 
-       and the IP address of a DNS server. Once you have edited the configuration files, 
-       press 'Enter' on the terminal where Avalon is waiting. </p>
-  
-    <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>Once started, you'll see in the log file (./logs/james-server.log) that 
+       James is running. This means that Spring has loaded James and is now waiting for a request.</p>
+  
   </subsection>
     
   <subsection name="Step 5: Create Domains and Users">
   
-    <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 
+    <p>Finally, after launch, 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="manage-users.html">here</a>.</p>
     
-    <p>Once started you'll see a message saying Avalon is running. This means that
-       Avalon has loaded JAMES and every other needed Block (see /logs/avalon.log)
-       and is now waiting for a socket request.</p>
-  
     <p>Since at the beginning James is empty, it will not have any local users
        registered.</p>
        
     <p>To register a local user open a telnet session with localhost on port 4555,
-       log in as root ("root[enter]  &lt;password-you-set-in-conf.xml&gt;[enter]") and
+       log in as root ("root[enter]  &lt;password-you-set-in-remotemanager.xml&gt;[enter]") and
        type "help" for a list of available commands in the "JAMES remote
        administrator tool". It is really a basic set but should allow you to test
        installation.</p>
         
-    <p>Once you have some local users registered, try sending mail to one of them
-        @localhost with SMTP (port 25) (assuming you have not changed the default
-        server names in the conf.xml file). You'll see the mail appear under
-        ../var/mail/localinbox/[user].
-        Try now to retrieve that mail using POP3 (port 110).
-        Trace out JAMES actions in /logs/*info.log.
-        Actions that will be taken by JAMES on incoming mail are configured in
-        the mailet pipe line (/conf/JAMES.conf.xml). Look at it if you want to
-        understand what's happening.</p>
-  
   </subsection>
   
   <subsection name="Step 6: Test James">
 
+    <p>Once you have some local users registered, try sending mail to one of them
+        with SMTP (port 25).</p>
+  
 <source>
 $ telnet 127.0.0.1 25
 Trying 127.0.0.1...
@@ -224,6 +191,14 @@ this is a test
 quit
 Connection closed by foreign host.
 </source>
+
+    <p>Try now to retrieve that mail using POP3 (port 110) or IMAP (port 143).</p>
+    
+    <p>Trace out James actions in ./logs/james-server.log.</p>
+    
+    <p>Actions that will be taken by James on incoming mail are configured in
+       the mailet pipe line (./conf/mailetcontainer.xml). Look at it if you want to
+       understand what's happening.</p>
     
   </subsection>
 

Modified: james/server/trunk/src/site/xdoc/manage-domains.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage-domains.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage-domains.xml (original)
+++ james/server/trunk/src/site/xdoc/manage-domains.xml Sun Nov  7 08:15:36 2010
@@ -25,13 +25,18 @@
 
 <body>
 
-  <section name="Manage Domains">
+  <section name="Manage Domains via Telnet">
   
     <p>Domain accounts are shared across services.  A common Domain repository is shared across James 
-    services.  That is, once you've created a POP3 mail and set a password, that same 
-    is available for authenticated SMTP and NNTP.</p>
+       services.  That is, once you've created a POP3 mail and set a password, that same 
+      is available for authenticated SMTP and NNTP.</p>
     
-    <p>Once James is up and listening, adding a Domain is simple:</p>
+    <p>If you have XMLDomainList (default setup), you can only list the available domains. To add a domain,
+       you must add it in the domainlist.xml file.</p>
+
+    <p>If you have JPADomainList for example, you can add, delete and list the domains.</p>
+
+    <p>Once James is up and listening, with JPADomainList, adding a Domain is simple:</p>
 
     <p><ol>
 
@@ -40,19 +45,34 @@
       hostname and &lt;port&gt; is the RemoteManager port specified in the James config.xml.</li>
   
       <li>You will be prompted for your administrator userid and password.  Enter the values you specified 
-      in the James config.xml.</li>
+      in the James remotemanager.xml.</li>
       
       <li>After logging in, type "adddomain &lt;domain&gt;" where &lt;domain&gt; is the domain name 
       of the domain you wish to create.</li>
       
-      <li>Repeat step 3 for all user accounts you wish to create.</li>
+      <li>Repeat step 3 for all domains you wish to create.</li>
     
     </ol></p>
     
-    <p>That's it.  Your Domain are now created and can be used by all James services.</p>
+    <p>That's it.  Your domains are now created and can be used by all James services.</p>
     
   </section>
 
+  <section name="Manage Domains via JMX">
+  
+    <p>Use and JMX client to access the DomainList management function.</p>
+  
+    <p>The managed objects are exposed from localhost only (for security reasons) on the following URL:</p>
+      
+    <p><code>service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi</code></p>
+      
+    <p>If you want a remote access, you can install a web application management tool such as jmanage. 
+       You will get screens such as the following one.</p>
+         
+    <p><img src="images/jmx-management/jmx-domainlist.png"/></p>
+
+  </section>
+  
 </body>
 
 </document>

Modified: james/server/trunk/src/site/xdoc/manage-users.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage-users.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage-users.xml (original)
+++ james/server/trunk/src/site/xdoc/manage-users.xml Sun Nov  7 08:15:36 2010
@@ -25,7 +25,7 @@
 
 <body>
 
-  <section name="Manage Users">
+  <section name="Manage Users via Telnet">
   
     <p>User accounts are shared across services.  A common user repository is shared across James 
     services.  That is, once you've created a POP3 mail account and set a password, that same 
@@ -40,22 +40,37 @@
       hostname and &lt;port&gt; is the RemoteManager port specified in the James config.xml.</li>
   
       <li>You will be prompted for your administrator userid and password.  Enter the values you specified 
-      in the James config.xml.</li>
+      in the James remotemanager.xml.</li>
       
       <li>After logging in, type "adduser &lt;user&gt; &lt;password&gt;" where &lt;user&gt; is the user name 
       and &lt;password&gt; is the password of the account you wish to create.  Please note that the user name 
-      should NOT be a complete email address.  Rather, all email addresses of the form &lt;user&gt;@&lt;domain&gt; 
-      (where &lt;domain&gt; is any of the values specified in the &lt;servernames&gt; block) will be delivered to 
-      this account by default.  Mailet configuration can change this default behavior.</li>
+      MUST be a complete email address of the form &lt;user&gt;@&lt;domain&gt; 
+      (where &lt;domain&gt; is any of the values specified in the &lt;servernames&gt; block of XMLDomainList or
+      a domain defined via the <a href="manage-domains.html">domain management</a>).</li>
       
       <li>Repeat step 3 for all user accounts you wish to create.</li>
     
     </ol></p>
     
-    <p>That's it.  Your user accounts are now created and can be used by all James services.</p>
+    <p>That's it.  Your users are now created and can be used by all James services.</p>
     
   </section>
 
+  <section name="Manage Users via JMX">
+  
+    <p>Use and JMX client to access the Users management function.</p>
+  
+    <p>The managed objects are exposed from localhost only (for security reasons) on the following URL:</p>
+      
+    <p><code>service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi</code></p>
+     
+    <p>If you want a remote access, you can install a web application management tool such as jmanage. 
+       You will get screens such as the following one.</p>
+         
+    <p><img src="images/jmx-management/jmx-user.png"/></p>
+
+  </section>
+  
 </body>
 
 </document>

Modified: james/server/trunk/src/site/xdoc/manage-virtualusers.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage-virtualusers.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage-virtualusers.xml (original)
+++ james/server/trunk/src/site/xdoc/manage-virtualusers.xml Sun Nov  7 08:15:36 2010
@@ -25,8 +25,58 @@
 
 <body>
 
-  <section name="Manage Virtual Users">
+  <section name="Introduction to Virtual Users">
+
+    <p>The only way to manage the virtual users is called "mapping" 
+       (the previous "alias" and "forwarding" functions are 
+       deprecated and you should not use them anymore.</p>
+  
+<source>
+addmapping [toUser@toDomain] [fromMapping] add mapping for the given email addres
+listallmappings list all mappings
+listmapping [user@domain] list all mappings for the given emailaddress
+removemapping [toUser@toDomain] [fromMapping] remove mapping for the given emailaddress
+</source>
+
+    <p>You will add mapping from an existing user to a virtual user. So read "addmapping toVirtual fromExisting".</p>
+
+    <p>You can also use wildcards (*) and regular expressions in the fromExisting.</p>
+
+  </section>
+
+  <section name="Manage Virtual Users via Telnet">
+  
+    <p>Once James is up and listening, adding a user is simple:</p>
+    
+    <p><ol>
+
+      <li>Telnet to the host and port on which the RemoteManager is listening.  For command-line telnet clients 
+      this is generally done by typing "telnet &lt;host&gt; &lt;port&gt;" where &lt;host&gt; is the James 
+      hostname and &lt;port&gt; is the RemoteManager port specified in the James config.xml.</li>
+  
+      <li>You will be prompted for your administrator userid and password.  Enter the values you specified 
+      in the James remotemanager.xml.</li>
+      
+      <li>After logging in, type "addmapping &lt;to&gt; &lt;from&gt;" where &lt;to&gt; is the new user name 
+         and &lt;from&gt; is the existing username you wish to map.  Please note that the user name 
+         MUST be a complete email address.</li>
+      
+      <li>Repeat step 3 for all mapping you wish to create.</li>
+    
+    </ol></p>
+    
+    <p>That's it.  Your mappings are now created and can be used by all James services.</p>
+    
+  </section>
+
+  <section name="Manage Virtual Users via JMX">
+  
+    <p>Use and JMX client to access the Virtual User management function.</p>
   
+    <p>The managed objects are exposed from localhost only (for security reasons) on the following URL:</p>
+      
+    <p><code>service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi</code></p>
+      
   </section>
 
 </body>

Modified: james/server/trunk/src/site/xdoc/manage.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/manage.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/manage.xml (original)
+++ james/server/trunk/src/site/xdoc/manage.xml Sun Nov  7 08:15:36 2010
@@ -27,26 +27,48 @@
 
   <section name="Manage James Server">
   
-    <p>You can manage James via:</p>
-    
-    <ol>
-      <li>JMX</li>
-      <li>Remote Manager</li>
-    </ol>
-    
     <p>You need to make sure that your user/domain/mail repository configuration is correct before managing.  If 
     you change your user/domain/mail repository type (i.e. file to database) or the configuration of your user repository 
     (i.e. the file or database URL) after you have added user/domain/mail, you may lose your user/domain/mail data.  Please change these 
     values with care.</p>
   
-    <p>After you've done this, restart James to ensure that any changes you've made in the configuration are incorporated into 
-    the running system.  You are now ready to create users/domains.</p>
+    <p>After you've done this, restart James to ensure that any changes you've made in 
+       the configuration are incorporated into the running system.</p>
+       
+     <p>You are now ready to manage <a href="manage-domains.html">domains</a>, 
+       <a href="manage-users.html">users</a> and <a href="manage-virtualusers.html">virtual users</a>.</p>
 
-    <subsection name="Manage via JMX">
+    <p>You can manage James via:</p>
+    
+    <ol>
+      <li><a href="Manage_via_Telnet">Telnet (Remote Manager)</a></li>
+      <li><a href="Manage_via_JMX">JMX</a></li>
+    </ol>
     
-      <p>James can be managed via JMX. Simply launch jconsole to access 
-        the exposed attributes and methods.</p>
+    <subsection name="Manage via Telnet">
+  
+      <p>Once James is up and listening, manage via telnet is simple:</p>
+      <ul>
+        <li>Telnet to the host and port on which the RemoteManager is listening.  For command-line telnet clients 
+            this is generally done by typing "telnet &lt;host&gt; &lt;port&gt;" where &lt;host&gt; is the James 
+            hostname and &lt;port&gt; is the RemoteManager port specified in the James remotemanager.xml config file.</li>
+        <li>You will be prompted for your administrator userid and password.  Enter the values you specified 
+            in the James remotemanager.xml.</li>
+        <li>type help to get a list of available commands.</li>
+      </ul>
   
+    </subsection>
+    
+    <subsection name="Manage via JMX">
+    
+      <p>James can be managed via JMX.</p>
+      
+      <p>The managed objects are exposed from localhost only (for security reasons) on the following URL:</p>
+      
+      <p><code>service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi</code></p>
+      
+      <p>Simply launch jconsole to access the exposed attributes and methods.</p>
+<!-- 
       <div class="ui-widget">
         <div class="ui-state-error ui-corner-all" style="padding: 0 .7em;"> 
           <p><span class="ui-icon ui-icon-alert" style="float: left; margin-right: .3em;"></span> 
@@ -58,22 +80,14 @@
         </p>
         </div>
       </div>
-  
+-->
+      <p>If you want a remote access, you can install a web application management tool such as jmanage. 
+         You will get screens such as the following one.</p>
+         
+       <p><img src="images/jmx-management/jmx-domainlist.png"/></p>
+
     </subsection>
   
-    <subsection name="Manage via Telnet">
-  
-      <p>Once James is up and listening, manage via telnet is simple:</p>
-      <ul>
-        <li>Telnet to the host and port on which the RemoteManager is listening.  For command-line telnet clients 
-            this is generally done by typing "telnet &lt;host&gt; &lt;port&gt;" where &lt;host&gt; is the James 
-            hostname and &lt;port&gt; is the RemoteManager port specified in the James config.xml.</li>
-        <li>You will be prompted for your administrator userid and password.  Enter the values you specified 
-            in the James remotemanager.xml.</li>
-      </ul>
-  
-    </subsection>
-    
   </section>
 
 </body>

Modified: james/server/trunk/src/site/xdoc/monitor-jmx.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/monitor-jmx.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/monitor-jmx.xml (original)
+++ james/server/trunk/src/site/xdoc/monitor-jmx.xml Sun Nov  7 08:15:36 2010
@@ -25,22 +25,36 @@
 
 <body>
 
-  <section name="JMX Monitoring">
+  <section name="Montiro via JMX">
   
     <p>You can monitor James Server via JMX.</p>
 
+    <p>The managed objects are exposed from localhost only (for security reasons) on the following URL:</p>
+      
+    <p><code>service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi</code></p>
+      
+    <p>Simply launch jconsole to access the exposed attributes and methods.
+       Active Connections active per component, limits,... can be displayed and following services can 
+       be monitored:</p>
+
     <ul>
-      <li>smtp</li>
-      <li>imap</li>
-      <li>lmtp</li>
-      <li>pop3</li>
-      <li>remotemanager</li>
-      <li>dnsservice</li>
-      <li>domainlist</li>
-      <li>queues</li>
+      <li>IMAP</li>
+      <li>POP3</li>
+      <li>SMTP</li>
+      <li>LMTP</li>
+      <li>RemoteManager</li>
+      <li>DNSService</li>
+      <li>Queues</li>
     </ul>
 
-    <p>Connections are active per component, limits,... are displayed.</p>
+    <p>If you want a remote access, you can install a web application management tool such as jmanage. 
+       You will get screens such as the following one.</p>
+         
+    <p><img src="images/jmx-monitoring/jmx-current-connections.png"/></p>
+
+    <p><img src="images/jmx-monitoring/jmx-memory.png"/></p>
+
+    <p><img src="images/jmx-monitoring/jmx-gc.png"/></p>
 
   </section>
 

Modified: james/server/trunk/src/site/xdoc/monitor-logging.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/monitor-logging.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/monitor-logging.xml (original)
+++ james/server/trunk/src/site/xdoc/monitor-logging.xml Sun Nov  7 08:15:36 2010
@@ -28,6 +28,199 @@
   <section name="Monitor via Logging">
   
     <p>Use the well-known log4j system.</p>
+    
+    <p>The log4j.properties reside in the ./conf folder. You can edit it to change the 
+       logging level, per component.</p>
+       
+    <p>All log files are written in the ./log folder. The ./log/james-sever.log gathers all the other logs.
+      Log file rotation is also available.</p>
+    
+<source>
+[root@srv001 log]# ls -alp
+total 2892
+drwxrwxrwx. 2 root root   4096 2010-11-07 07:58 ./
+drwxrwxrwx. 7 root root   4096 2010-11-06 09:01 ../
+-rw-r--r--. 1 root root      0 2010-11-06 09:24 dnsserver.log
+-rw-r--r--. 1 root root    811 2010-11-06 17:37 domainlist.log
+-rwxrwxrwx. 1 root root      0 2010-10-21 14:07 .dummy
+-rw-r--r--. 1 root root     58 2010-11-06 09:24 fetchmail.log
+-rw-r--r--. 1 root root    552 2010-11-07 08:27 imapserver.log
+-rw-r--r--. 1 root root    959 2010-11-06 18:50 imapserver.log.2010-11-06
+-rw-r--r--. 1 root root 677090 2010-11-07 08:29 james-server.log
+-rw-r--r--. 1 root root 761987 2010-11-06 23:59 james-server.log.2010-11-06
+-rw-r--r--. 1 root root   1941 2010-11-06 09:24 lmtpserver.log
+-rw-r--r--. 1 root root      0 2010-11-06 09:24 mailboxmanager.log
+-rw-r--r--. 1 root root   7935 2010-11-06 09:24 mailetcontainer.log
+-rw-r--r--. 1 root root  61129 2010-11-07 08:26 mailet.log
+-rw-r--r--. 1 root root  23393 2010-11-06 23:57 mailet.log.2010-11-06
+-rw-r--r--. 1 root root    325 2010-11-06 09:24 mailserver.log
+-rw-r--r--. 1 root root   5008 2010-11-06 09:24 mailstore.log
+-rw-r--r--. 1 root root      0 2010-11-06 09:24 objectstore.log
+-rw-r--r--. 1 root root   2001 2010-11-06 09:24 pop3server.log
+-rw-r--r--. 1 root root    138 2010-11-07 08:18 remotemanager.log
+-rw-r--r--. 1 root root    746 2010-11-06 17:57 remotemanager.log.2010-11-06
+-rw-r--r--. 1 root root 615271 2010-11-07 08:29 smtpserver.log
+-rw-r--r--. 1 root root 717888 2010-11-06 23:59 smtpserver.log.2010-11-06
+-rw-r--r--. 1 root root     71 2010-11-06 09:24 usersrepository.log
+</source>    
+       
+    <p>The default log4j.properties is taken hereafter for information.</p>
+
+<source>
+#  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.
+
+# See http://james.apache.org/server/3/config.html for usage
+
+log4j.rootLogger=DEBUG
+
+log4j.appender.CONS=org.apache.log4j.ConsoleAppender
+log4j.appender.CONS.layout=org.apache.log4j.PatternLayout
+log4j.appender.CONS.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.FILE=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.FILE.File=../log/james-server.log
+log4j.appender.FILE.layout=org.apache.log4j.PatternLayout
+log4j.appender.FILE.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.MAILBOXMANAGER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.MAILBOXMANAGER.File=../log/mailboxmanager.log
+log4j.appender.MAILBOXMANAGER.DatePattern='.'yyyy-MM-dd
+log4j.appender.MAILBOXMANAGER.layout=org.apache.log4j.PatternLayout
+log4j.appender.MAILBOXMANAGER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+
+log4j.appender.IMAPSERVER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.IMAPSERVER.File=../log/imapserver.log
+log4j.appender.IMAPSERVER.DatePattern='.'yyyy-MM-dd
+log4j.appender.IMAPSERVER.layout=org.apache.log4j.PatternLayout
+log4j.appender.IMAPSERVER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.MAILSERVER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.MAILSERVER.File=../log/mailserver.log
+log4j.appender.MAILSERVER.DatePattern='.'yyyy-MM-dd
+log4j.appender.MAILSERVER.layout=org.apache.log4j.PatternLayout
+log4j.appender.MAILSERVER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.MAILET=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.MAILET.File=../log/mailet.log
+log4j.appender.MAILET.DatePattern='.'yyyy-MM-dd
+log4j.appender.MAILET.layout=org.apache.log4j.PatternLayout
+log4j.appender.MAILET.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+
+log4j.appender.MAILETCONTAINER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.MAILETCONTAINER.File=../log/mailetcontainer.log
+log4j.appender.MAILETCONTAINER.DatePattern='.'yyyy-MM-dd
+log4j.appender.MAILETCONTAINER.layout=org.apache.log4j.PatternLayout
+log4j.appender.MAILETCONTAINER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+
+log4j.appender.DNSSERVER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.DNSSERVER.File=../log/dnsserver.log
+log4j.appender.DNSSERVER.DatePattern='.'yyyy-MM-dd
+log4j.appender.DNSSERVER.layout=org.apache.log4j.PatternLayout
+log4j.appender.DNSSERVER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.REMOTEMANAGER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.REMOTEMANAGER.File=../log/remotemanager.log
+log4j.appender.REMOTEMANAGER.DatePattern='.'yyyy-MM-dd
+log4j.appender.REMOTEMANAGER.layout=org.apache.log4j.PatternLayout
+log4j.appender.REMOTEMANAGER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.POP3SERVER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.POP3SERVER.File=../log/pop3server.log
+log4j.appender.POP3SERVER.DatePattern='.'yyyy-MM-dd
+log4j.appender.POP3SERVER.layout=org.apache.log4j.PatternLayout
+log4j.appender.POP3SERVER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.SMTPSERVER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.SMTPSERVER.File=../log/smtpserver.log
+log4j.appender.SMTPSERVER.DatePattern='.'yyyy-MM-dd
+log4j.appender.SMTPSERVER.layout=org.apache.log4j.PatternLayout
+log4j.appender.SMTPSERVER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.LMTPSERVER=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.LMTPSERVER.File=../log/lmtpserver.log
+log4j.appender.LMTPSERVER.DatePattern='.'yyyy-MM-dd
+log4j.appender.LMTPSERVER.layout=org.apache.log4j.PatternLayout
+log4j.appender.LMTPSERVER.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.MAILSTORE=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.MAILSTORE.File=../log/mailstore.log
+log4j.appender.MAILSTORE.DatePattern='.'yyyy-MM-dd
+log4j.appender.MAILSTORE.layout=org.apache.log4j.PatternLayout
+log4j.appender.MAILSTORE.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.USERSREPOSITORY=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.USERSREPOSITORY.File=../log/usersrepository.log
+log4j.appender.USERSREPOSITORY.DatePattern='.'yyyy-MM-dd
+log4j.appender.USERSREPOSITORY.layout=org.apache.log4j.PatternLayout
+log4j.appender.USERSREPOSITORY.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.OBJECTSTORAGE=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.OBJECTSTORAGE.File=../log/objectstore.log
+log4j.appender.OBJECTSTORAGE.DatePattern='.'yyyy-MM-dd
+log4j.appender.OBJECTSTORAGE.layout=org.apache.log4j.PatternLayout
+log4j.appender.OBJECTSTORAGE.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.FETCHMAIL=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.FETCHMAIL.File=../log/fetchmail.log
+log4j.appender.FETCHMAIL.DatePattern='.'yyyy-MM-dd
+log4j.appender.FETCHMAIL.layout=org.apache.log4j.PatternLayout
+log4j.appender.FETCHMAIL.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+log4j.appender.DOMAINLIST=org.apache.log4j.DailyRollingFileAppender
+log4j.appender.DOMAINLIST.File=../log/domainlist.log
+log4j.appender.DOMAINLIST.DatePattern='.'yyyy-MM-dd
+log4j.appender.DOMAINLIST.layout=org.apache.log4j.PatternLayout
+log4j.appender.DOMAINLIST.layout.ConversionPattern=%-5p %d{HH:mm:ss,SSS} | %c | %m%n
+
+# logger for jackrabbit
+log4j.logger.org.apache.jackrabbit=ERROR, CONS, FILE
+
+# logger for activemq
+log4j.logger.org.apache.xbean.spring=WARN, CONS, FILE
+log4j.logger.org.apache.activemq=WARN, CONS, FILE
+
+# logger for camel
+log4j.logger.org.apache.camel=WARN, CONS, FILE
+log4j.logger.org.springframework=WARN, CONS, FILE
+log4j.logger.org.apache.james=INFO, CONS, FILE
+#log4j.logger.james: set from default value WARN to INFO or even DEBUG to see (even) more logging
+log4j.logger.james=WARN, CONS, FILE
+log4j.logger=DEBUG, CONS, FILE
+
+log4j.logger.james.mailboxmanager=INFO, MAILBOXMANAGER
+log4j.logger.james.imapserver=INFO, IMAPSERVER
+log4j.logger.james.mailserver=INFO, MAILSERVER
+log4j.logger.james.mailetcontext=INFO, MAILET
+log4j.logger.james.mailetcontainer=INFO, MAILETCONTAINER
+log4j.logger.james.dnsserver=INFO, DNSSERVER
+log4j.logger.james.remotemanager=INFO, REMOTEMANAGER
+log4j.logger.james.pop3server=INFO, POP3SERVER
+log4j.logger.james.smtpserver=INFO, SMTPSERVER
+log4j.logger.james.lmtpserver=INFO, LMTPSERVER
+log4j.logger.james.mailstore=INFO, MAILSTORE
+log4j.logger.james.usersrepository=INFO, USERSREPOSITORY
+log4j.logger.james.objectstorage=INFO, OBJECTSTORAGE
+log4j.logger.james.fetchmail=INFO, FETCHMAIL
+log4j.logger.james.domainlist=INFO, DOMAINLIST
+</source>
   
   </section>
 

Modified: james/server/trunk/src/site/xdoc/monitor.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/monitor.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/monitor.xml (original)
+++ james/server/trunk/src/site/xdoc/monitor.xml Sun Nov  7 08:15:36 2010
@@ -27,9 +27,18 @@
 
   <section name="Monitor James Server">
   
-    <p>You can monitor James Server via <a href="monitor-logging.html">logging</a>
-       and via <a href="monitor-jmx.html">JMX</a>.</p>
+    <subsection name="Montior James Server via Loging">
   
+      <p>You can monitor James Server via logging - <a href="monitor-logging.html">read more</a>.</p>
+  
+    </subsection>
+
+    <subsection name="Montior James Server via JMX">
+  
+      <p>You can monitor James Server via JMX - <a href="monitor-jmx.html">read more</a>.</p>
+  
+    </subsection>
+
   </section>
   
 </body>

Modified: james/server/trunk/src/site/xdoc/quick-start.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/quick-start.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/quick-start.xml (original)
+++ james/server/trunk/src/site/xdoc/quick-start.xml Sun Nov  7 08:15:36 2010
@@ -109,7 +109,7 @@ You can edit the following files to chan
   &lt;/domainlist&gt;
 
 - Edit the database.properties and change the values according to your database.
-- If you don't forget to add the needed jdbc driver jar in the ./conf/lib folder.
+- Don't forget to add the needed JDBC driver jar in the ./conf/lib folder.
   
 Step 4: Start
 #############
@@ -140,6 +140,9 @@ quit
 Bye
 Connection closed by foreign host.
 
+For example, YOUR_DOMAIN=localhost.net, YOUR_NAME=test, so you will have a test@localhost.net user.
+The username to use in you mail client will be test@localhost.net.
+
 Step 6: Test
 ############
 

Modified: james/server/trunk/src/site/xdoc/upgrade-2.3.xml
URL: http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/upgrade-2.3.xml?rev=1032225&r1=1032224&r2=1032225&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/upgrade-2.3.xml (original)
+++ james/server/trunk/src/site/xdoc/upgrade-2.3.xml Sun Nov  7 08:15:36 2010
@@ -20,19 +20,28 @@
 <document>
 
  <properties>
-  <title>James 3.0 - Upgrading</title>
+  <title>James 3.0 - Upgrading from 2.3</title>
  </properties>
  
 <body>
 
-  <section name="Migration Tool">
+  <section name="Migrate from Server 2.3 to Server 3.0">
+  
+    <subsection name="Migrate Users from Server 2.3 to Server 3.0">
+
+      <p>We are also working on a tool that will migrate 2.3 user repositories to 3 user repository. 
+         See <a href="https://issues.apache.org/jira/browse/JAMES-1090">https://issues.apache.org/jira/browse/JAMES-1090</a>
+         to follow progress on this</p>
+         
+    </subsection>
 
-    <p>We are working on a tool that will migrate 2.3 mail and user
-      repositories to 3.0 mailbox store and user repository.</p>
+    <subsection name="Migrate Mails from Server 2.3 to Server 3.0">
 
-    <p>See <a href="https://issues.apache.org/jira/browse/JAMES-1052">https://issues.apache.org/jira/browse/JAMES-1052</a>
-       and <a href="https://issues.apache.org/jira/browse/JAMES-1090">https://issues.apache.org/jira/browse/JAMES-1090</a>
-       to follow progress on this.</p>
+      <p>We are working on a tool that will migrate 2.3 mail repositories to 3.0 mailbox store. 
+         See <a href="https://issues.apache.org/jira/browse/JAMES-1052">https://issues.apache.org/jira/browse/JAMES-1052</a>
+         to follow progress on this</p>
+       
+    </subsection>
 
   </section>
 <!-- 



---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org