Author: eric
Date: Thu Apr 14 06:21:14 2011
New Revision: 1092015
URL: http://svn.apache.org/viewvc?rev=1092015&view=rev
Log:
fix typos and menus - detail smpt/imap4/pop3 configuration (JAMES-1219)
Modified:
james/server/trunk/src/site/site.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-smtp-lmtp.xml
james/server/trunk/src/site/xdoc/config.xml
james/server/trunk/src/site/xdoc/feature-persistence.xml
Modified: james/server/trunk/src/site/site.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/site.xml?rev=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/site.xml (original)
+++ james/server/trunk/src/site/site.xml Thu Apr 14 06:21:14 2011
@@ -17,7 +17,7 @@
specific language governing permissions and limitations
under the License.
-->
-<project name="Apache James Server">
+<project name="Apache James Server 3.0">
<skin>
<groupId>org.apache.james</groupId>
@@ -26,7 +26,7 @@
</skin>
<bannerLeft>
- <name>James Server</name>
+ <name>Apache James Server 3.0</name>
<src>images/logos/james-server-logo.gif</src>
<href>http://james.apache.org/server/index.html</href>
<alt>james-server-logo.gif</alt>
@@ -67,9 +67,9 @@
<item name="Mailbox" href="/config-mailbox.html" />
<item name="Mail Repository Stores"
href="/config-mailrepositorystore.html" />
<item name="DNS Service" href="/config-dnsservice.html" />
- <item name="IMAP4" href="/config-imap4.html" />
- <item name="POP3" href="/config-pop3.html" />
<item name="SMTP LMTP" href="/config-smtp-lmtp.html" />
+ <item name="POP3" href="/config-pop3.html" />
+ <item name="IMAP4" href="/config-imap4.html" />
<item name="Mailet Container" href="/config-mailetcontainer.html" />
<item name="FetchMail" href="/config-fetchmail.html" />
<!--
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=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-dnsservice.xml (original)
+++ james/server/trunk/src/site/xdoc/config-dnsservice.xml Thu Apr 14 06:21:14
2011
@@ -57,13 +57,15 @@
<dt><strong>authoritative</strong></dt>
<dd><strong>true/false</strong> - This tag specifies whether or not
to require authoritative (non-cached) DNS records; to only accept
DNS responses that are
- authoritative for the domain. It is primarily useful in an
intranet/extranet environment.
- <p>This should always be <strong>false</strong> unless you
understand the implications.</dd>
+ authoritative for the domain. It is primarily useful in an
intranet/extranet environment.
+ This should always be <strong>false</strong> unless you understand
the implications.</dd>
<dt><strong>maxcachesize</strong></dt>
- <dd> Maximum number of entries to maintain in the DNS cache
(typically 50000)</dd>
+ <dd>Maximum number of entries to maintain in the DNS cache (typically
50000)</dd>
<dt><strong>singleIPperMX</strong></dt>
<dd>true or false (default) - Sepcifies if Apache James Server must
try a single server for each multihomed mx host</dd>
</dl>
+
+ </subsection>
</section>
<!--
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=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-imap4.xml (original)
+++ james/server/trunk/src/site/xdoc/config-imap4.xml Thu Apr 14 06:21:14 2011
@@ -28,22 +28,55 @@
<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>
- <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
- value is specified, the value defaults to 5 minutes, 300000
milliseconds. A value of 0
- means that client sockets will not timeout.</li>
- <li><strong>max-connections</strong> - The max-connections parameter
specifies the default
- maximum number of client connections that this connection manager
will allow per managed
- server socket. This value can be overridden by each individual
service. If no value is
- specified, the value defaults to 30. A value of 0 means that
there is no limit imposed
- 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>
--->
- </section>
+
+ <p>The IMAP4 service is controlled by a configuration block in the
imap4server.xml.
+ The imap4server tag defines the boundaries of the configuration block.
It encloses
+ all the relevant configuration for the IMAP4 server. The behavior of
the IMAP4 service is
+ controlled by the attributes and children of this tag.</p>
+
+ <p>This tag has an optional boolean attribute - <strong>enabled</strong> -
that defines whether the service is active or not. The value defaults to
"true" if
+ not present.</p>
+
+ <p>The standard children of the imapserver tag are:</p>
+
+ <dl>
+ <dt><strong>bind</strong></dt>
+ <dd>Configure this to bind to a specific inetaddress. This is an
optional integer value. This value is the port on which this IMAP4 server is
configured
+ to listen. If the tag or value is absent then the service
+ will bind to all network interfaces for the machine If the tag or value
is omitted, the value will default to the standard IMAP4 port
+ port 143 is the well-known/IANA registered port for IMAP
+ port 993 is the well-known/IANA registered port for IMAPS ie over
SSL/TLS</dd>
+ <dt><strong>connectionBacklog</strong></dt>
+ <dd></dd>
+ <dt><strong>compress</strong></dt>
+ <dd>true or false - Use or don't use COMPRESS extension.</dd>
+ <dt><strong>maxLineLength</strong></dt>
+ <dd>Maximal allowed line-length before a BAD response will get
returned to the client
+ This should be set with caution as a to high value can make the
server a target for DOS (Denial of Service)!</dd>
+ <dt><strong>inMemorySizeLimit</strong></dt>
+ <dd>10MB size limit before we will start to stream to a temporary
file</dd>
+ <dt><strong>tls</strong></dt>
+ <dd>Set to true to support STARTTLS or SSL for the Socket.
+ To use this you need to copy sunjce_provider.jar to /path/james/lib
directory. To create a new keystore execute:
+ keytool -genkey -alias james -keyalg RSA -keystore
/path/to/james/conf/keystore</dd>
+ <dt><strong>handler.helloName</strong></dt>
+ <dd>This is the name used by the server to identify itself in the
IMAP4
+ protocol. If autodetect is TRUE, the server will discover its
+ own host name and use that in the protocol. If discovery fails,
+ the value of 'localhost' is used. If autodetect is FALSE, James
+ will use the specified value.</dd>
+ <dt><strong>handler.connectiontimeout</strong></dt>
+ <dd>Connection timeout in secconds</dd>
+ <dt><strong>handler.connectionLimit</strong></dt>
+ <dd>Set the maximum simultaneous incoming connections for this
service</dd>
+ <dt><strong>handler.connectionLimitPerIP</strong></dt>
+ <dd>Set the maximum simultaneous incoming connections per IP for this
service</dd>
+ <dt><strong>handler.handlerchain</strong></dt>
+ <dd>This loads the core CommandHandlers. Only remove this if you
really
+ know what you are doing</dd>
+ </dl>
+
+</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=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-mailetcontainer.xml (original)
+++ james/server/trunk/src/site/xdoc/config-mailetcontainer.xml Thu Apr 14
06:21:14 2011
@@ -49,7 +49,7 @@
need to adjust the <strong>mailserver</strong> block upon
installation.</p>
<dl>
- <dt><strong>postmaster</strong></dt>
+ <dt><strong>context.postmaster</strong></dt>
<dd>The body of this element is the address that the server
will consider its postmaster address. This address will be listed
as the sender address
of all error messages that originate from James. Also, all
messages addressed to
@@ -58,14 +58,8 @@
Set this to the appropriate email address for error reports
If this is set to a non-local email address, the mail server
will still function, but will generate a warning on startup.</dd>
- <dt><strong>enableVirtualHosting</strong></dt>
- <dd>Set to true to support virtualHosting. If virtualHosting support
- is enabled the server will accept thread every user independ on
domain level.</dd>
- <dt><strong>key</strong></dt>
- <dd>value.</dd>
- <dt><strong>defaultDomain</strong></dt>
- <dd>Set the default domain which will be used if an email is send to a
recipient without a domain part.
- If not defaultdomain is set the first domain of the DomainList get
used.</dd>
+ <dt><strong>spooler.threads</strong></dt>
+ <dd>Number of simultaneous threads used to spool the mails.</dd>
</dl>
<!--
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=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-mailrepositorystore.xml (original)
+++ james/server/trunk/src/site/xdoc/config-mailrepositorystore.xml Thu Apr 14
06:21:14 2011
@@ -29,7 +29,7 @@
<subsection name="Introduction">
- <p>Read <a href="feature-persistence.html" for a description of the Mail
Repository Store functionality.</p>
+ <p>Read <a href="feature-persistence.html">documentation about
persistence</a> for a description of the Mail Repository Store
functionality.</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/mailrepositorystore.xml";>mailrepositorystore.xml</a>
in SVN to get some examples and hints.</p>
@@ -89,7 +89,7 @@
<subsection name="MBox Repositories">
- <p>The MBox file format repository.<.p>
+ <p>The MBox file format repository.</p>
</subsection>
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=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-pop3.xml (original)
+++ james/server/trunk/src/site/xdoc/config-pop3.xml Thu Apr 14 06:21:14 2011
@@ -28,7 +28,7 @@
<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
@@ -38,45 +38,40 @@
not present.</p>
<p>The standard children of the pop3server tag are:</p>
- <ul>
- <li><strong>port</strong> - This is an optional integer value. This
value is the port on which this POP3 server is configured
- to listen.If the tag or value is omitted, the value will default to the
standard POP3 port, 110.</li>
- <li><strong>bind</strong> - This is an optional value. If present, this
value is a string describing
- the IP address to which this service should be bound. If the tag or
value is absent then the service
- will bind to all network interfaces for the machine.</li>
- <li><strong>useTLS</strong> - This is an optional boolean value. If
this value is true, then the "ssl"
- server socket factory is used to generate the server socket for this
service. If it is false, the
- "plain" server socket factory is used. In either case this behavior is
overridden by the serverSocketType
- tag which is described under the expert configuration options.</li>
- <li><strong>handler</strong> - This is an artifact preserved for
backwards compatibility. This tag
- was used to group related parameters. It should disappear in future
versions.</li>
- <ul>
- <li><strong>helloName</strong> - This is a required tag with an
optional body that defines the server name
- used in the initial service greeting. The tag may have an optional
attribute - <strong>autodetect</strong>. If
- the autodetect attribute is present and true, the service will use the
local hostname
- returned by the Java libraries. If autodetect is absent or false, the
body of the tag will be used. In
- this case, if no body is present, the value "localhost" will be
used.</li>
- <li><strong>connectionTimeout</strong> - This is an optional tag with
an integer body. </li>
- </ul>
- </ul>
- <p>There are a few additional children of the pop3server tag that are
appropriate for advanced
- configurations. These should only be used by expert administrators. All
tags in this group are optional.</p>
- <ul>
- <li><strong>serverSocketFactory</strong> - This is an optional tag with
a string body. If the tag is present,
- the body must be the name of one of the server socket factories
specified in the socket manager block. Any other
- value will result in an error. If present, this tag overrides the
useTLS tag.</li>
- <li><strong>threadGroup</strong> - This is an optional tag with a string
body. If the tag is present,
- the body must be the name of one of the thread groups specified in the
thread manager block. Any other
- value will result in an error. This tag is best used to fine tune
thread allocation between the services.</li>
- <li><strong>connectionLimit</strong> - The connectionLimit parameter
specifies the maximum number of client
- connections that this service will allow. If no value is specified, the
value defaults to that specified in
- the connectionmanager block. A value of 0 means that there is no limit
imposed
- by the service, although resource limitations imposed by other
components
- (i.e. max # of threads) may serve to limit the number of open
connections.</li>
- </ul>
--->
- </section>
+
+ <dl>
+ <dt><strong>bind</strong></dt>
+ <dd>Configure this to bind to a specific inetaddress. This is an
optional integer value. This value is the port on which this POP3 server is
configured
+ to listen. If the tag or value is absent then the service
+ will bind to all network interfaces for the machine If the tag or value
is omitted, the value will default to the standard POP3 port, 11
+ port 995 is the well-known/IANA registered port for POP3S ie over SSL/TLS
+ port 110 is the well-known/IANA registered port for Standard POP3</dd>
+ <dt><strong>connectionBacklog</strong></dt>
+ <dd></dd>
+ <dt><strong>tls</strong></dt>
+ <dd>Set to true to support STARTTLS or SSL for the Socket.
+ To use this you need to copy sunjce_provider.jar to /path/james/lib
directory. To create a new keystore execute:
+ keytool -genkey -alias james -keyalg RSA -keystore
/path/to/james/conf/keystore</dd>
+ <dt><strong>handler.helloName</strong></dt>
+ <dd>This is the name used by the server to identify itself in the POP3
+ protocol. If autodetect is TRUE, the server will discover its
+ own host name and use that in the protocol. If discovery fails,
+ the value of 'localhost' is used. If autodetect is FALSE, James
+ will use the specified value.</dd>
+ <dt><strong>handler.connectiontimeout</strong></dt>
+ <dd>Connection timeout in secconds</dd>
+ <dt><strong>handler.connectionLimit</strong></dt>
+ <dd>Set the maximum simultaneous incoming connections for this
service</dd>
+ <dt><strong>handler.connectionLimitPerIP</strong></dt>
+ <dd>Set the maximum simultaneous incoming connections per IP for this
service</dd>
+ <dt><strong>handler.handlerchain</strong></dt>
+ <dd>This loads the core CommandHandlers. Only remove this if you
really
+ know what you are doing</dd>
+ </dl>
+
+ </section>
</body>
</document>
+
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=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml (original)
+++ james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml Thu Apr 14 06:21:14
2011
@@ -28,7 +28,7 @@
<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>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
@@ -39,103 +39,148 @@
<p>The standard children of the smtpserver tag are:</p>
- <ul>
- <li><strong>port</strong> - This is an optional integer value. This
value is the port on which this SMTP server is configured
- to listen.If the tag or value is omitted, the value will default to the
standard SMTP port, 25.</li>
- <li><strong>bind</strong> - This is an optional value. If present, this
value is a string describing
+ <dl>
+ <dt><strong>bind</strong></dt>
+ <dd>A list of address:port - This is an optional value. If present,
this value is a string describing
the IP address to which this service should be bound. If the tag or
value is absent then the service
- will bind to all network interfaces for the machine.</li>
- <li><strong>useTLS</strong> - This is an optional boolean value. If
this value is true, then the "ssl"
- server socket factory is used to generate the server socket for this
service. If it is false, the
- "plain" server socket factory is used. In either case this behavior is
overridden by the serverSocketType
- tag which is described under the expert configuration options.</li>
- <li><strong>handler</strong> - This is an artifact preserved for
backwards compatibility. This tag
- was used to group related parameters. It should disappear in future
versions.</li>
- <ul>
- <li><strong>helloName</strong> - This is a required tag with an optional
body that defines the server name
+ will bind to all network interfaces for the machine on port 25. Port 25
is the well-known/IANA registered port for SMTP.
+ Port 465 is the well-known/IANA registered port for SMTP over
TLS.</dd>
+ <dt><strong>connectBacklog</strong></dt>
+ <dd></dd>
+ <dt><strong>tls</strong></dt>
+ <dd>Set to true to support STARTTLS or SSL for the Socket.
+ To use this you need to copy sunjce_provider.jar to /path/james/lib
directory. To create a new keystore execute:
+ keytool -genkey -alias james -keyalg RSA -keystore
/path/to/james/conf/keystore. The algorithm is optional and only needs to be
specified when using something other
+ than the Sun JCE provider - You could use IbmX509 with IBM Java
runtime.</dd>
+ <dt><strong>handler.helloName</strong></dt>
+ <dd>This is a required tag with an optional body that defines the server
name
used in the initial service greeting. The tag may have an optional
attribute - <strong>autodetect</strong>. If
the autodetect attribute is present and true, the service will use the
local hostname
returned by the Java libraries. If autodetect is absent or false, the
body of the tag will be used. In
- this case, if no body is present, the value "localhost" will be
used.</li>
- <li><strong>connectionTimeout</strong> - This is an optional tag with a
non-negative integer body. </li>
- <li><strong>authRequired</strong> - This is an optional tag with a
boolean body. If true, then the server will
+ this case, if no body is present, the value "localhost" will be
used.</dd>
+ <dt><strong>handler.connectionTimeout</strong></dt>
+ <dd>This is an optional tag with a non-negative integer body. Connection
timeout in secconds.</dd>
+ <dt><strong>handler.connectionLimit</strong></dt>
+ <dd>Set the maximum simultaneous incoming connections for this
service.</dd>
+ <dt><strong>handler.connectionLimitPerIP</strong></dt>
+ <dd>Set the maximum simultaneous incoming connections per IP for this
service.</dd>
+ <dt><strong>handler.authRequired</strong></dt>
+ <dd>This is an optional tag with a boolean body. If true, then the
server will
require authentication before delivering mail to non-local email
addresses. If this tag is absent, or the value
is false then the client will not be prompted for authentication. Only
simple user/password authentication is
- supported at this time.</li>
- <li><strong>verifyIdentity</strong> - This is an optional tag with a
boolean body. This option can only be used
+ supported at this time. supported values:
+ true: required but announced only to not authorizedAddresses
+ false: don't use AUTH
+ announce: like true, but always announce AUTH capability to
clients
+
+ The correct behaviour per RFC value would be false or announce
+ but we still support true for backward compatibility and because
+ some webmail client fails when AUTH is announced but no
authentication
+ information has been provided</dd>
+ <dt><strong>handler.authorizedAddresses</strong></dt>
+ <dd>Authorize specific addresses/networks.
+ If you use SMTP AUTH, addresses that match those specified here
will
+ be permitted to relay without SMTP AUTH. If you do not use SMTP
+ AUTH, and you specify addreses here, then only addresses that
match
+ those specified will be permitted to relay.
+
+ Addresses may be specified as a an IP address or domain name,
with an
+ optional netmask, e.g.,
+
+ 127.*, 127.0.0.0/8, 127.0.0.0/255.0.0.0, and localhost/8 are
all the same
+
+ See also the RemoteAddrNotInNetwork matcher in the transport
processor.
+ You would generally use one OR the other approach.</dd>
+ <dt><strong>handler.verifyIdentity</strong></dt>
+ <dd>This is an optional tag with a boolean body. This option can only
be used
if SMTP authentication is required. If the parameter is set to true
then the sender address for the submitted message
- will be verified against the authenticated subject.</li>
- <li><strong>maxmessagesize</strong> - This is an optional tag with a
non-negative integer body. It specifies the maximum
+ will be verified against the authenticated subject. Verify sender
addresses, ensuring that
+ the sender address matches the user who has authenticated.
+ This prevents a user of your mail server from acting as someone else
+ If unspecified, default value is true.</dd>
+ <dt><strong>handler.maxmessagesize</strong></dt>
+ <dd>This is an optional tag with a non-negative integer body. It
specifies the maximum
size, in kbytes, of any message that will be transmitted by this SMTP
server. It is a service-wide, as opposed to
a per user, limit. If the value is zero then there is no limit. If the
tag isn't specified, the service will
- default to an unlimited message size.</li>
- </ul>
- </ul>
- <p>There are a few additional children of the smtpserver tag that are
appropriate for advanced
- configurations. These should only be used by expert administrators.
All tags in this group are optional.</p>
- <ul>
- <li><strong>serverSocketFactory</strong> - This is an optional tag with
a string body. If the tag is present,
- the body must be the name of one of the server socket factories
specified in the socket manager block. Any other
- value will result in an error. If present, this tag overrides the
useTLS tag.</li>
- <li><strong>threadGroup</strong> - This is an optional tag with a string
body. If the tag is present,
- the body must be the name of one of the thread groups specified in the
thread manager block. Any other
- value will result in an error. This tag is best used to fine tune
thread allocation between the services.</li>
- <li><strong>connectionLimit</strong> - The connectionLimit parameter
specifies the maximum number of client
- connections that this service will allow. If no value is specified, the
value defaults to that specified in
- the connectionmanager block. A value of 0 means that there is no limit
imposed
- by the service, although resource limitations imposed by other
components
- (i.e. max # of threads) may serve to limit the number of open
connections.</li>
- </ul>
-
+ default to an unlimited message size.</dd>
+ <dt><strong>handler.heloEhloEnforcement</strong></dt>
+ <dd>This sets wether to enforce the use of HELO/EHLO salutation before a
+ MAIL command is accepted. If unspecified, the value defaults to
true.</dd>
+ <dt><strong>handler.addressBracketsEnforcement</strong></dt>
+ <dd>WARNING: This is Non-RFC compliant (default value: true)
+ See: http://wiki.apache.org/james/StandardsComplianceStatement</dd>
+ <dt><strong>handler.smtpGreeting</strong></dt>
+ <dd>This sets the SMTPGreeting which will be used when connect to the
smtpserver
+ If none is specified a default is generated</dd>
+ <dt><strong>handler.handlerchain</strong></dt>
+ <dd></dd>
+ <dt><strong>handler.handlerchain</strong></dt>
+ <dd>The configuration handler chain</dd>
+ </dl>
+
<subsection name="Configure Authenticated SMTP (SMTP AUTH)">
-
+
<p>Authenticated SMTP is a method of securing your SMTP server. With
SMTP AUTH enabled senders who wish to
- relay mail through the SMTP server (that is, send mail that is
eventually to be delivered to another SMTP
- server) must authenticate themselves to James before sending their
message. Mail that is to be delivered
- locally does not require authentication. This method ensures that
spammers cannot use your SMTP server
- to send unauthorized mail, while still enabling users who may not have
fixed IP addresses to send their
- messages.</p>
+ relay mail through the SMTP server (that is, send mail that is
eventually to be delivered to another SMTP
+ server) must authenticate themselves to Apache James Server before
sending their message. Mail that is to be delivered
+ locally does not require authentication. This method ensures that
spammers cannot use your SMTP server
+ to send unauthorized mail, while still enabling users who may not have
fixed IP addresses to send their
+ messages.</p>
<p>Mail servers that allow spammers to send unauthorized email are known
as open relays. So SMTP AUTH
- is a mechanism for ensuring that your server is not an open relay .</p>
- <p>At this time James only supports simple user name / password
authentication.</p>
+ is a mechanism for ensuring that your server is not an open relay .</p>
+
+ <p>At this time Apache James Server only supports simple user name /
password authentication.</p>
- <p>Configuring James for Authentication SMTP is a multi-step process.
It requires several adjustments of
- the smtpserver.xml. To enable SMTP AUTH, do the following:</p>
- <p>First, as mentioned above, SMTP AUTH requires that James be able to
distinguish between mail intended
- for local delivery and mail intended for remote delivery. James makes
this determination by matching the
- domain to which the mail was sent against the <servernames>
element of the James configuration block. Any
- local domains should be explicitly listed as <servername> elements
in this section.</p>
- <p>Second, James is configured out of the box so as to not serve as an
open relay for spammers. This is done
+ <p>Configuring Apache James Server for Authentication SMTP is a
multi-step process. It requires several adjustments of
+ the smtpserver.xml. To enable SMTP AUTH, do the following:</p>
+
+ <ol>
+
+ <li>As mentioned above, SMTP AUTH requires that Apache James Server be
able to distinguish between mail intended
+ for local delivery and mail intended for remote delivery. Apache
James Server makes this determination by matching the
+ domain to which the mail was sent against the <servernames>
element of the Apache James Server configuration block. Any
+ local domains should be explicitly listed as <servername>
elements in this section.</li>
+<!--
+Correct this.
+ <li>Apache James Server is configured out of the box so as to not serve
as an open relay for spammers. This is done
by restricting the IP addresses from which mail will be accepted using
the RemoteAddrNotInNetwork mailet. This
restriction must be lifted before users can send from arbitrary clients.
To do this, comment out or remove the
mailet tag containing the class attribute "RemoteAddrNotInNetwork".
This tag can be found in the spoolmanager
- configuration block, in the root processor configuration.</p>
- <p>Third, set the authRequired element of the smtpserver configuration
block to "true".</p>
- <p>Fourth, if you wish to ensure that authenticated users can only send
email from their own account, you may
- optionally set the verifyIdentity element of the smtpserver
configuration block to "true".</p>
- <p>Fifth, restart James. This will pull in all of your configuration
changes.</p>
+ configuration block, in the root processor configuration.</li>
+-->
+ <li>set the authRequired element of the smtpserver configuration block
to "true".</li>
+
+ <li>if you wish to ensure that authenticated users can only send email
from their own account, you may
+ optionally set the verifyIdentity element of the smtpserver
configuration block to "true".</li>
+
+ <li>Restart Apache James Server. This will pull in all of your
configuration changes.</li>
+
+ </ol>
<p>Finally, you need to verify that your configuration was done
correctly. This step is
- <strong>important</strong> and should not be skipped.</p>
+ <strong>important</strong> and should not be skipped.</p>
+
<p>Verify that you have not inadvertantly configured your server as an
open relay. This is most easily
- accomplished by using the service provided at <a
href="http://www.ordb.org";>ORDB.org</a>. ORDB.org will
- check your mail server and inform you if it is an open relay.</p>
+ accomplished by using the service provided at <a
href="http://www.abuse.net/relay.html";>abuse.net</a>. abuse.net will
+ check your mail server and inform you if it is an open relay.</p>
+
<p>It is extremely important that your server not be configured as an
open relay. Aside from potential
- costs associated with usage by spammers, connections from servers that
are determined to be open relays
- are routinely rejected by SMTP servers. This can severely impede the
ability of your mail server to
- send mail.</p>
- <p>Of course it is also necessary to confirm that users and log in and
send
- mail through your server. This can be accomplished using any standard
mail client (i.e. Outlook,
- Eudora, Evolution).</p>
+ costs associated with usage by spammers, connections from servers
that are determined to be open relays
+ are routinely rejected by SMTP servers. This can severely impede the
ability of your mail server to
+ send mail.</p>
+ <p>Of course it is also necessary to confirm that users and log in and
send
+ mail through your server. This can be accomplished using any
standard mail client (i.e. Thunderbird, Outlook,
+ 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>
for ideas to have multiple SMTP port open.</p>
-
+-->
</subsection>
</section>
@@ -143,9 +188,14 @@
<section name="LMTP 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/lmtpserver.xml";>lmtpserver.xml</a>
in SVN to get some examples and hints.</p>
+
+ <p>The configuration is the same of for SMTP.</p>
+
+ <p>By default, it is desactivated. You can activate it with SMTP and bind
for example on port 24.</p>
</section>
</body>
</document>
+
Modified: james/server/trunk/src/site/xdoc/config.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config.xml?rev=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config.xml (original)
+++ james/server/trunk/src/site/xdoc/config.xml Thu Apr 14 06:21:14 2011
@@ -105,23 +105,23 @@
<td></td>
</tr>
<tr>
- <td><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></td>
- <td><a href="config-imap4.html">IMAP4 Configuration</a></td>
+ <td><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></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/tags/james-server-3.0-M3/container-spring/src/main/config/examples/pop3server.xml";>pop3server.xml</a></td>
- <td><a href="config-pop3.html">POP3 Configuration</a></td>
+ <td><a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M3/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/tags/james-server-3.0-M3/container-spring/src/main/config/examples/smtpserver.xml";>smtpserver.xml</a></td>
- <td><a href="config-smtp-lmtp.html">SMTP Configuration</a></td>
+ <td><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></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/tags/james-server-3.0-M3/container-spring/src/main/config/examples/lmtpserver.xml";>lmtpserver.xml</a></td>
- <td><a href="config-smtp-lmtp.html">LMTP Configuration</a></td>
+ <td><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></td>
+ <td><a href="config-imap4.html">IMAP4 Configuration</a></td>
<td></td>
</tr>
<tr>
Modified: james/server/trunk/src/site/xdoc/feature-persistence.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-persistence.xml?rev=1092015&r1=1092014&r2=1092015&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-persistence.xml (original)
+++ james/server/trunk/src/site/xdoc/feature-persistence.xml Thu Apr 14
06:21:14 2011
@@ -25,14 +25,13 @@
<body>
- <section name="Mail Persistence: Mailbox and Mail Repository Store">
+ <section name="Mailbox and Mail Repository Store for Mail Persistence">
<subsection name="Introduction">
- <p>The <u><b>Mailbox</b> persists users' Inbox, Sent Items, Trash...
folders</u> with their mails.</p>
+ <p>The <b>Mailbox</b> persists users' Inbox, Sent Items, Trash...
folders with their mails.</p>
- <p>The <u><b>Mail Repository Store</b> persists spam, error,... mails,
so nothing to do with users visible mails</u>.
- The Mail Respos</p>
+ <p>The <b>Mail Repository Store</b> persists spam, error,... mails, so
nothing to do with users visible mails.</p>
<p>In case of database access, both Mailbox and Mail Repository Store
use database connection defined via database.properties.</p>
@@ -58,7 +57,7 @@
to define where to store spam,... mails (example:
file://var/mail/error/).</p>
<p>More information about the mailstores configuration can be
- found <a href="config-mailrepositorystores.html">here</a>.</p>
+ found <a href="config-mailrepositorystore.html">here</a>.</p>
<p>Mail Repository Stores are distinguished by how they store data.
There are five types of
storage: File, Database, DBFile, MBox and JCR.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
