Author: eric
Date: Fri Apr 8 14:31:17 2011
New Revision: 1090268
URL: http://svn.apache.org/viewvc?rev=1090268&view=rev
Log:
Comment configuration content coming from 2.3 and that still must still be
updated for 3.0 (JAMES-1219)
Removed:
james/server/trunk/src/site/xdoc/config-remotemanager.xml
Modified:
james/server/trunk/src/site/xdoc/config-antispam.xml
james/server/trunk/src/site/xdoc/config-dnsservice.xml
james/server/trunk/src/site/xdoc/config-imap4.xml
james/server/trunk/src/site/xdoc/config-mailetcontainer.xml
james/server/trunk/src/site/xdoc/config-mailrepositorystore.xml
james/server/trunk/src/site/xdoc/config-pop3.xml
james/server/trunk/src/site/xdoc/config-serverwide.xml
james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml
james/server/trunk/src/site/xdoc/config-ssl-tls.xml
james/server/trunk/src/site/xdoc/config-users.xml
Modified: james/server/trunk/src/site/xdoc/config-antispam.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-antispam.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-antispam.xml (original)
+++ james/server/trunk/src/site/xdoc/config-antispam.xml Fri Apr 8 14:31:17
2011
@@ -25,7 +25,9 @@
<body>
-<p></p>
+ <section name="Antispam Configuration">
+
+ </section>
</body>
Modified: james/server/trunk/src/site/xdoc/config-dnsservice.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-dnsservice.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-dnsservice.xml (original)
+++ james/server/trunk/src/site/xdoc/config-dnsservice.xml Fri Apr 8 14:31:17
2011
@@ -20,28 +20,17 @@
<document>
<properties>
- <title>Configuring DNS Service</title>
+ <title>DNS Service Configuration</title>
</properties>
<body>
-<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>
- <strong>This page still contains text related to James 2.3 and needs
to
- be updated for James 3.0</strong>
- </p>
- </div>
- </div>
-</p>
-
<section name="DNS Configuration">
<subsection name="dnsservice.xml">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/dnsservice.xml";>dnsservice.xml</a>
in SVN to get some examples and hints.</p>
-
+<!--
<p>DNS Transport services are controlled by a configuration block in
the dnsservice.xml. This block affects SMTP remote delivery.</p>
@@ -80,9 +69,10 @@
<p>This should always be <strong>false</strong> unless you
understand the implications.</p>
</li>
</ul>
-
+-->
</subsection>
- </section>
+
+ </section>
<!--
<section name="Sun JVM DNS Lookup Configuration.">
Modified: james/server/trunk/src/site/xdoc/config-imap4.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-imap4.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-imap4.xml (original)
+++ james/server/trunk/src/site/xdoc/config-imap4.xml Fri Apr 8 14:31:17 2011
@@ -20,28 +20,16 @@
<document>
<properties>
- <title>Configuring the IMAP4 Service</title>
+ <title>IMAP4 Configuration</title>
</properties>
<body>
-<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>
- <strong>This page still contains text related to James 2.3 and needs
to
- be updated for James 3.0</strong>
- </p>
- </div>
- </div>
-</p>
-
-
<section name="IMAP4 Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/imapserver.xml";>imapserver.xml</a>
in SVN to get some examples and hints.</p>
-
- <p>This block controls general connection management. There are two
elements.
+<!--
+ <p>This block controls general connection management. There are two
elements:</p>
<ul>
<li><strong>idle-timeout</strong> - the number of milliseconds that it
will take for idle
client connections managed by this connection manager to be marked
at timed out. If no
@@ -54,9 +42,8 @@
by the connection manager, although resource limitations imposed
by other components
(i.e. max # of threads) may serve to limit the number of open
connections.</li>
</ul>
- </p>
-
-</section>
+-->
+ </section>
</body>
Modified: james/server/trunk/src/site/xdoc/config-mailetcontainer.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-mailetcontainer.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-mailetcontainer.xml (original)
+++ james/server/trunk/src/site/xdoc/config-mailetcontainer.xml Fri Apr 8
14:31:17 2011
@@ -20,7 +20,7 @@
<document>
<properties>
- <title>Configuring the Mailet Container</title>
+ <title>Mailet Container Configuration</title>
</properties>
<body>
@@ -45,7 +45,7 @@
<mailet match="anyname" class="MailetX"/>
-->
</ul>
-
+<!--
<p>The SpoolManager is controlled by a single configuration block in the
mailetcontainer.xml.
The spoolmanager tag defines the boundaries of the configuration block.
The behavior of
the SpoolManager, most importantly the routing of mail messages through
the processor tree,
@@ -53,26 +53,26 @@
<p>The spoolmanager tag has only one children. It is:</p>
<ul>
- <li><strong>threads</strong> - This is a required positive integer
element. It specifies
- the number of threads the SpoolManager will use to process messages in the
spool. This
- parameter tends to substantially impact performance, so it is advisable to
tune it in production
- configurations.</li>
+ <li><strong>threads</strong> - This is a required positive integer
element. It specifies
+ the number of threads the SpoolManager will use to process messages
in the spool. This
+ parameter tends to substantially impact performance, so it is
advisable to tune it in production
+ configurations.</li>
</ul>
-
+
<p>Spoolmanager depends on mailet and matcher packages, configured by
these tags:</p>
<ul>
- <li><strong>mailetpackages</strong> - This is a required container tag.
It contains some number
- of <strong>mailetpackage</strong> children. The body of each of these
<strong>mailetpackage</strong>
- elements is a Java package name. It is these packages that contain the
classes to be instantiated
- as mailets.</li>
- <li><strong>matcherpackages</strong> - This is a required container tag.
It contains some number
- of <strong>matcherpackage</strong> children. The body of each of these
<strong>matcherpackage</strong>
- elements is a Java package name. It is these packages that contain the
classes to be instantiated
- as matchers.</li>
+ <li><strong>mailetpackages</strong> - This is a required container tag.
It contains some number
+ of <strong>mailetpackage</strong> children. The body of each of
these <strong>mailetpackage</strong>
+ elements is a Java package name. It is these packages that contain
the classes to be instantiated
+ as mailets.</li>
+ <li><strong>matcherpackages</strong> - This is a required container tag.
It contains some number
+ of <strong>matcherpackage</strong> children. The body of each of
these <strong>matcherpackage</strong>
+ elements is a Java package name. It is these packages that contain
the classes to be instantiated
+ as matchers.</li>
</ul>
-
+
<p>The remaining SpoolManager configuration elements are complex enough to
require a more in-depth
- discussion.</p>
+ discussion.</p>
<subsection name="Processor Configuration">
@@ -100,30 +100,38 @@
<p>The transport and spam processors are two useful, but optional,
processors that are included in the out of
the box configuration. These processors include logic for actual mail
delivery and spam handling respectively. More
information on these processors can be found in the default
mailetcontainer.xml.</p>
+
<p>Each processor element has zero or more <strong>mailet</strong> child
elements. Each of these elements describes a
matcher/mailet pair. The ordering of the <strong>mailet</strong>
children is crucial to the configuration, as
it is the order in which pairs will be traversed in the processor.</p>
+
<p>It is this <strong>mailet</strong> element that is at the core of the
SpoolManager configuration.</p>
</subsection>
-
+-->
<subsection name="The Mailet Tag">
<p>Consider the following simple <strong>mailet</strong> tag:</p>
<mailet match="RemoteAddrNotInNetwork=127.0.0.1"
class="ToProcessor"><br/>
<processor>spam</processor><br/>
</mailet><br/>
+
<p>The mailet tag has two required attributes, <strong>match</strong>
and <strong>class</strong>.</p>
+
<p>The <strong>match</strong> attribute is set to the value of the
specific Matcher class to be instantiated with a an
optional argument. If present, the argument is separated from the
Matcher class name by an '='. Semantic
interpretation of the argument is left to the particular mailet.</p>
+
<p>The <strong>class</strong> attribute is set to the value of the
Mailet class that is to be instantiated.</p>
+
<p>Finally, the children of the <strong>mailet</strong> tag define the
configuration that is passed to the Mailet. The
tags used in this section should have no attributes or children. The
names and bodies of the elements will be passed to
the mailet as (name, value) pairs.</p>
+
<p>So in the example above, a Matcher instance of RemoteAddrNotInNetwork
would be instantiated, and the value "127.0.0.1"
would be passed to the matcher. The Mailet of the pair will be an
instance of ToProcessor, and it will be passed the (name, value)
pair of ("processor", "spam").</p>
+
<p>James includes a number of pre-packaged Mailets and Matchers. A list
of provided Mailets may be found
<a href="provided-mailets.html">here</a>. A list of provided Matchers
may be found <a href="provided-matchers.html">here</a>.</p>
Modified: james/server/trunk/src/site/xdoc/config-mailrepositorystore.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-mailrepositorystore.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-mailrepositorystore.xml (original)
+++ james/server/trunk/src/site/xdoc/config-mailrepositorystore.xml Fri Apr 8
14:31:17 2011
@@ -20,12 +20,12 @@
<document>
<properties>
- <title>Mail Stores Configuration</title>
+ <title>Mail Repository Store Configuration</title>
</properties>
<body>
- <section name="Mail Stores Configuration">
+ <section name="Mail Repository Store Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/mailrepositorystore.xml";>mailrepositorystore.xml</a>
in SVN to get some examples and hints.</p>
Modified: james/server/trunk/src/site/xdoc/config-pop3.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-pop3.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-pop3.xml (original)
+++ james/server/trunk/src/site/xdoc/config-pop3.xml Fri Apr 8 14:31:17 2011
@@ -25,29 +25,18 @@
<body>
-<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>
- <strong>This page still contains text related to James 2.3 and needs
to
- be updated for James 3.0</strong>
- </p>
- </div>
- </div>
-</p>
-
-
<section name="POP3 Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/pop3server.xml";>pop3server.xml</a>
in SVN to get some examples and hints.</p>
-
+<!--
<p>The POP3 service is controlled by a configuration block in the
pop3server.xml.
- The pop3server tag defines the boundaries of the configuration block. It
encloses
- all the relevant configuration for the POP3 server. The behavior of the
POP service is
- controlled by the attributes and children of this tag.</p>
+ The pop3server tag defines the boundaries of the configuration block.
It encloses
+ all the relevant configuration for the POP3 server. The behavior of
the POP service is
+ controlled by the attributes and children of this tag.</p>
<p>This tag has an optional boolean attribute - <strong>enabled</strong> -
that defines whether the service is active or not. The value defaults to
"true" if
- not present.</p>
+ not present.</p>
+
<p>The standard children of the pop3server tag are:</p>
<ul>
<li><strong>port</strong> - This is an optional integer value. This
value is the port on which this POP3 server is configured
@@ -85,8 +74,9 @@
by the service, although resource limitations imposed by other
components
(i.e. max # of threads) may serve to limit the number of open
connections.</li>
</ul>
-
- </section>
+-->
+ </section>
</body>
+
</document>
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=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-serverwide.xml (original)
+++ james/server/trunk/src/site/xdoc/config-serverwide.xml Fri Apr 8 14:31:17
2011
@@ -25,17 +25,6 @@
<body>
-<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>
- <strong>This page still contains text related to James 2.3 and needs
to
- be updated for James 3.0</strong>
- </p>
- </div>
- </div>
-</p>
-
<section name="Server Wide Configuration">
<p>There are a number of global configuration blocks that do not fall into
any one
@@ -50,7 +39,7 @@
<p>This configuration block is defined by the
<strong>mailserver</strong> tag. All administrators
need to adjust this configuration block upon installation. It no
attributes, but several
children, all of which are required.</p>
-
+<!--
<p>The tag has these attributes:</p>
<dl>
<dt><strong>postmaster</strong></dt>
@@ -67,8 +56,8 @@
aliasing will be enabled. Finally, the value of the third
attribute determines whether forwarding
to potentially remote users will be enabled.</dd>
</dl>
-
- </subsection>
+-->
+ </subsection>
<subsection name="spring-beans.xml">
@@ -81,17 +70,19 @@
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/database.properties";>database.properties</a>
in SVN to get some examples and hints.</p>
<p>The database connection in database.properties</p>
-
+<!--
<p>James has the capacity to use a JDBC-compatible database for storage
of both message and user
data. This section explains how to configure James to utilize a
database for storage.</p>
<p>Using James with a database backend has certain requirements.
Database configuration is
- extremely vendor-specific, so we can only state the requirements in
general terms.</p>
+ extremely vendor-specific, so we can only state the requirements in
general terms.</p>
+
<p>There must be a database instance accessible from the James server.
An account with appropriate
privileges (select, insert, delete into tables, and on initial startup
creation of tables) and
with sufficient quota for the data to be inserted into the database must
be available. Also,
since James will use JDBC to access the database, an appropriate JDBC
driver must be
available for installation.</p>
+
<p>It is important to verify the functionality of the database before
attempting to configure
James to use it as a repository. This will help ensure that
configuration issues are properly
identified.</p>
@@ -170,8 +161,8 @@
by some users. These issues (and methods to resolve them) are recorded
on the
<a href="../FAQ.html">James FAQ</a> as they are reported. Please
consult the FAQ if you encounter any
difficulties.</p>
-
- </subsection>
+-->
+ </subsection>
<subsection name="META-INF/persistence.xml">
@@ -194,19 +185,19 @@
<p>Deprecated.</p>
<p>The precise SQL statements used by James to modify and view data
stored in the database are specified in
- an external configuration file. The sqlResources.xml file
- (which can be found in the apps/james/conf directory) is a sample
configuration file that contains the SQL
- statements used by James. The purpose of each of these statements, as
well as the repository with which
- they are associated, is documented in situ.</p>
+ an external configuration file. The sqlResources.xml file
+ (which can be found in the apps/james/conf directory) is a sample
configuration file that contains the SQL
+ statements used by James. The purpose of each of these statements,
as well as the repository with which
+ they are associated, is documented in situ.</p>
<p>If you are using a SQL database with unusual SQL commands or data
types, you may
- need to add special entries to this file. The James team
- does try to keep sqlResources.xml updated, so if you do run into a
- special case, please let us know.</p>
+ need to add special entries to this file. The James team
+ does try to keep sqlResources.xml updated, so if you do run into a
+ special case, please let us know.</p>
<p>Also, if the database tables are not created a priori, but rather are
to be created by James
- upon startup, special attention should be paid to the "create table"
statements in this file. Such
- statements tend to be both very database and very database instance
specific.</p>
+ upon startup, special attention should be paid to the "create table"
statements in this file. Such
+ statements tend to be both very database and very database instance
specific.</p>
</subsection>
Modified: james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml (original)
+++ james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml Fri Apr 8 14:31:17
2011
@@ -25,29 +25,17 @@
<body>
-<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>
- <strong>This page still contains text related to James 2.3 and needs
to
- be updated for James 3.0</strong>
- </p>
- </div>
- </div>
-</p>
-
-
<section name="SMTP Configuration">
- <p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/smtpserver.xml";>smtpserver.xml</a>
in SVN to get some examples and hints.</p>
-
+ <p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/smtpserver.xml";>smtpserver.xml</a>
in SVN to get some examples and hints.</p>
+<!--
<p>The SMTP service is controlled by a configuration block in the
smptserver.xml.
- The smtpserver tag defines the boundaries of the configuration block. It
encloses
- all the relevant configuration for the SMTP server. The behavior of the
SMTP service is
- controlled by the attributes and children of this tag.</p>
+ The smtpserver tag defines the boundaries of the configuration block.
It encloses
+ all the relevant configuration for the SMTP server. The behavior of
the SMTP service is
+ controlled by the attributes and children of this tag.</p>
<p>This tag has an optional boolean attribute - <strong>enabled</strong> -
that defines whether the service is active or not. The value defaults to
"true" if
- not present.</p>
+ not present.</p>
<p>The standard children of the smtpserver tag are:</p>
@@ -142,7 +130,7 @@
Eudora, Evolution).</p>
</subsection>
-
+-->
<subsection name="Configure multiple SMTP servers">
<p>Read <a
href="https://issues.apache.org/jira/browse/JAMES-1105";>https://issues.apache.org/jira/browse/JAMES-1105</a>
Modified: james/server/trunk/src/site/xdoc/config-ssl-tls.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-ssl-tls.xml?rev=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-ssl-tls.xml (original)
+++ james/server/trunk/src/site/xdoc/config-ssl-tls.xml Fri Apr 8 14:31:17 2011
@@ -25,22 +25,11 @@
<body>
-<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>
- <strong>This page still contains text related to James 2.3 and needs
to
- be updated for James 3.0</strong>
- </p>
- </div>
- </div>
-</p>
-
- <section name="TLS Configuration">
+ <section name="SSL / TLS Configuration">
<p>This document explains how to enable James 3.0 services to use
Transport Layer Security (TLS) for encrypted client-server communication.</p>
-
- <subsection name="Making TLS/SSL Server Sockets Available Inside Apache
James Server">
+<!--
+ <subsection name="Making SSL/TLS Server Sockets Available Inside Apache
James Server">
<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,
@@ -81,7 +70,7 @@
</subsection>
- <subsection name="Configuring a Service to Use TLS">
+ <subsection name="Configuring a Service to Use SSL/TLS">
<p>Each of the services - <a href="config-smtp-lmtp.html">SMTP</a>,
<a href="config-pop3.html">POP3</a>,
@@ -92,7 +81,7 @@
</subsection>
- <subsection name="Verifying a TLS-enabled James Service">
+ <subsection name="Verifying a SSL/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
@@ -106,14 +95,12 @@
service greeting should appear.</p>
</subsection>
-
+-->
</section>
- <section name="Simultaneous Support of TLS and non-TLS per Protocol">
+ <section name="Simultaneous Support of SSL/TLS and non-SSL/TLS per Protocol">
-<!--
-see smtp_ssl.xml in example
--->
+ <p>See smtp_ssl.xml in example folder.</p>
</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=1090268&r1=1090267&r2=1090268&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-users.xml (original)
+++ james/server/trunk/src/site/xdoc/config-users.xml Fri Apr 8 14:31:17 2011
@@ -25,18 +25,6 @@
<body>
-<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>
- <strong>This page still contains text related to James 2.3 and needs
to
- be updated for James 3.0</strong>
- </p>
- </div>
- </div>
-</p>
-
-
<section name="Users Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/container-spring/src/main/config/examples/usersrepository.xml";>usersrepository.xml</a>
in SVN to get some examples and hints.</p>
@@ -46,55 +34,48 @@
</subsection>
<subsection name="LDAP Users">
-
- <p>
- This document explains how to enable JAMES to use an LDAP directory as
a
- Users Repository.
- </p>
+<!--
+ <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
+ <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
+ directory schema.</p>
+
+ <p>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
+ mailserver and the mailserver, is called the LDAPRoot. (See
diagram)</p>
+
+ <p>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
+ not imply that this mailserver should handle mail for them.</p>
+
+ <p>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
+ of these objects. These nodes are child nodes of the mailserver.</p>
+
+ <p>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
+ first servername, e.g. apache.org).</p>
+
+ <p>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
+ the offered password.</p>
+
+ <p>This implementation does not set passwords in the directory. Use a
dummy
+ password when invoking adduser in RemoteManger.</p>
+
+ <p>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>
+ mailserver and what email lists am I subscribed to?</p>
<table cellspacing="0">
<tr>
@@ -179,6 +160,7 @@
<td> </td>
</tr>
</table>
+-->
<!--
<p>
Six entries in JAMES.conf.xml must be set for this to work:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
