Author: eric
Date: Sun Nov 14 07:06:46 2010
New Revision: 1034944
URL: http://svn.apache.org/viewvc?rev=1034944&view=rev
Log:
James Server 3.0 web site update further to M1 release.
Added:
james/server/trunk/src/site/xdoc/feature-persistence.xml
- copied, changed from r1033409,
james/server/trunk/src/site/xdoc/feature-stores.xml
james/server/trunk/src/site/xdoc/feature-servers.xml
- copied, changed from r1034937,
james/server/trunk/src/site/xdoc/feature-summary.xml
james/server/trunk/src/site/xdoc/feature-smtp-hooks.xml
Removed:
james/server/trunk/src/site/xdoc/feature-stores.xml
james/server/trunk/src/site/xdoc/feature-summary.xml
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-mailstores.xml
james/server/trunk/src/site/xdoc/config-pop3.xml
james/server/trunk/src/site/xdoc/config-remotemanager.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-tls.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-extend-smtp-hook.xml
james/server/trunk/src/site/xdoc/feature-mailetcontainer.xml
james/server/trunk/src/site/xdoc/feature-perfomance.xml
james/server/trunk/src/site/xdoc/install.xml
james/server/trunk/src/site/xdoc/quick-start.xml
Modified: james/server/trunk/src/site/site.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/site.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/site.xml (original)
+++ james/server/trunk/src/site/site.xml Sun Nov 14 07:06:46 2010
@@ -46,9 +46,10 @@
</menu>
<menu name="Features">
- <item name="Summary" href="/feature-summary.html" />
+ <item name="Servers" href="/feature-servers.html" />
+ <item name="Persistence" href="/feature-persistence.html" />
<item name="Mailet Container" href="/feature-mailetcontainer.html" />
- <item name="Stores" href="/feature-stores.html" />
+ <item name="SMTP Hooks" href="/feature-smtp-hooks.html" />
<item name="Queue Priority" href="/feature-queue-priority.html" />
<item name="Performance" href="/feature-perfomance.html" />
<item name="Security" href="/feature-security.html" />
@@ -92,7 +93,7 @@
<item name="Develop Extensions" href="/dev-extend.html" collapse="true" >
<item name="Mailet" href="/dev-extend-mailet.html" />
<item name="Matcher" href="/dev-extend-matcher.html" />
- <item name="Hook SMTP" href="/dev-extend-smtp-hook.html" />
+ <item name="SMTP Hook" href="/dev-extend-smtp-hook.html" />
</item>
<item name="Provided Extensions" href="/dev-provided.html"
collapse="true" >
<item name="Mailets" href="/dev-provided-mailets.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=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-dnsservice.xml (original)
+++ james/server/trunk/src/site/xdoc/config-dnsservice.xml Sun Nov 14 07:06:46
2010
@@ -25,6 +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="DNS Configuration">
<subsection name="dnsservice.xml">
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=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-imap4.xml (original)
+++ james/server/trunk/src/site/xdoc/config-imap4.xml Sun Nov 14 07:06:46 2010
@@ -25,6 +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="IMAP4 Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/container-spring/src/main/config/examples/imapserver.xml";>imapserver.xml</a>
in SVN to get some examples and hints.</p>
Modified: james/server/trunk/src/site/xdoc/config-mailstores.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-mailstores.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-mailstores.xml (original)
+++ james/server/trunk/src/site/xdoc/config-mailstores.xml Sun Nov 14 07:06:46
2010
@@ -31,12 +31,6 @@
</section>
- <section name="JCR Repository Configuration">
-
- <p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/container-spring/src/main/config/examples/jcr-repository.xml";>jcr-repository.xml</a>
in SVN to get some examples and hints.</p>
-
- </section>
-
</body>
</document>
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=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-pop3.xml (original)
+++ james/server/trunk/src/site/xdoc/config-pop3.xml Sun Nov 14 07:06:46 2010
@@ -25,6 +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-M2/container-spring/src/main/config/examples/pop3server.xml";>pop3server.xml</a>
in SVN to get some examples and hints.</p>
Modified: james/server/trunk/src/site/xdoc/config-remotemanager.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-remotemanager.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-remotemanager.xml (original)
+++ james/server/trunk/src/site/xdoc/config-remotemanager.xml Sun Nov 14
07:06:46 2010
@@ -25,6 +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="RemoteManager Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/container-spring/src/main/config/examples/remotemanager.xml";>remotemanager.xml</a>
in SVN to get some examples and hints.</p>
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=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-serverwide.xml (original)
+++ james/server/trunk/src/site/xdoc/config-serverwide.xml Sun Nov 14 07:06:46
2010
@@ -25,6 +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="Server Wide Configuration">
<p>There are a number of global configuration blocks that do not fall into
any one
@@ -199,6 +210,12 @@
</subsection>
+ <subsection name="JCR Repository Configuration">
+
+ <p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/container-spring/src/main/config/examples/jcr-repository.xml";>jcr-repository.xml</a>
in SVN to get some examples and hints.</p>
+
+ </subsection>
+
</section>
</body>
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=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml (original)
+++ james/server/trunk/src/site/xdoc/config-smtp-lmtp.xml Sun Nov 14 07:06:46
2010
@@ -25,6 +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="SMTP Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/container-spring/src/main/config/examples/smtpserver.xml";>smtpserver.xml</a>
in SVN to get some examples and hints.</p>
Modified: james/server/trunk/src/site/xdoc/config-tls.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config-tls.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-tls.xml (original)
+++ james/server/trunk/src/site/xdoc/config-tls.xml Sun Nov 14 07:06:46 2010
@@ -25,6 +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="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>
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=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config-users.xml (original)
+++ james/server/trunk/src/site/xdoc/config-users.xml Sun Nov 14 07:06:46 2010
@@ -25,6 +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="Users Configuration">
<p>Consult <a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/container-spring/src/main/config/examples/usersrepository.xml";>usersrepository.xml</a>
in SVN to get some examples and hints.</p>
Modified: james/server/trunk/src/site/xdoc/config.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/config.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/config.xml (original)
+++ james/server/trunk/src/site/xdoc/config.xml Sun Nov 14 07:06:46 2010
@@ -75,6 +75,11 @@
<td>Deprecated</td>
</tr>
<tr>
+ <td><a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/container-spring/src/main/config/examples/jcr-repository.xml";>jcr-repository.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/tags/james-server-3.0-M2/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>
@@ -95,11 +100,6 @@
<td></td>
</tr>
<tr>
- <td><a
href="https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-M2/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/tags/james-server-3.0-M2/container-spring/src/main/config/examples/dnsservice.xml";>dnsservice.xml</a></td>
<td><a href="config-dnsservice.html">DNS Service Configuration</a></td>
<td></td>
Modified: james/server/trunk/src/site/xdoc/dev-extend-smtp-hook.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/dev-extend-smtp-hook.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/dev-extend-smtp-hook.xml (original)
+++ james/server/trunk/src/site/xdoc/dev-extend-smtp-hook.xml Sun Nov 14
07:06:46 2010
@@ -20,44 +20,22 @@
<document>
<properties>
- <title>James - SMTP Hooks</title>
+ <title>James - Extend James - SMTP Hooks</title>
</properties>
<body>
- <section name="Introduction to SMTP Hooks">
-
- <p>The James SMTP Server Component allows to easy write your own code
which will get executed
- in the SMTP-Transaction. Thats a bit different then using a Mailet
a.k.a Mailet-API.</p>
-
- <p>The James SMTP Server comes with a few interfaces which helps you to
"hook-in" a
- specific SMTP Command. That means your class which implements the given
interface(s) will get
- called after the SMTP-Command was parsed and depending on your
implementation it will handle it.</p>
-
- <p>As your code will get executed before the mail was even accepted. This
can help you in many ways,
- most times its used for rejecting SPAM/Junk within the SMTP-Dialog. But
it can be used for
- other things too.</p>
-
- <p>Its up to you and your use case.</p>
-
- <p>But be aware as your code needs to get executed during the
SMTP-Transaction it should not
- take to long to execute. As it will need to fit in before the timeout
was hit which can be
- different on every mailserver. But as a general rule as long as your
code can get executed
- within 30 seconds it should be fine.</p>
-
- </section>
-
- <section name="Custom Hooks Implementations">
+ <section name="Custom SMTP Hooks Implementations">
- <subsection name="Why a Custom Hook">
+ <subsection name="Why a Custom SMTP Hook">
<p>What to do if the Hook API is not enough for you ? You want for
example
to write a code which handles a new command like "YOURCOOLCOMMAND:
whate...@example".</p>
<p>For this kind of needs you should implement the CommandHandler
interface.
This gives you a lower-level API to handle this kind of tasks. If you
want
- to support a custom Hook in your CommandHandler its the best
- to just extend AbstractHookableCmdHandler.</p>
+ to support a custom Hook in your <code>CommandHandler</code> its the
best
+ to just extend <code>AbstractHookableCmdHandler</code>.</p>
</subsection>
@@ -65,10 +43,11 @@
<p>Be aware that your implementation needs to be thread-safe as it will
get used as singleton.
If you need to store temporary informations within the SMTP
Transaction/Session you should
- use the SMTPSession.getState().put(...) and
SMTPSession.getConnectionState().put(...) methods.</p>
+ use the <code>SMTPSession.getState().put(...)</code>
+ and <code>SMTPSession.getConnectionState().put(...)</code>
methods.</p>
- <p>For a more explanation see the <a
href="http://james.apache.org/protocols/apidocs/index.html";>apidocs</a> for the
protocols library which
- is used by James SMTP Server.</p>
+ <p>For a more explanation see the <a
href="http://james.apache.org/protocols/apidocs/index.html";>apidocs</a>
+ for the protocols library which is used by James SMTP Server.</p>
</subsection>
Modified: james/server/trunk/src/site/xdoc/feature-mailetcontainer.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-mailetcontainer.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-mailetcontainer.xml (original)
+++ james/server/trunk/src/site/xdoc/feature-mailetcontainer.xml Sun Nov 14
07:06:46 2010
@@ -25,12 +25,18 @@
<body>
- <section name="MailetContainer for Matchers and Mailets, Processors and
SpoolManager">
+ <section name="MailetContainer">
- <p>James separates the services that deliver mail to James (i.e. SMTP,
FetchMail)
- from the engine that processes mail after it is received by James. The
- SpoolManager component is James' mail processing engine. James'
SpoolManager component
- is a Mailet container. It is these mailets and matchers that actually
carry out mail processing.</p>
+ <subsection name="Introduction">
+
+ <p>James separates the services that deliver mail to James (i.e. SMTP,
FetchMail)
+ from the engine that processes mail after it is received by James.
The
+ SpoolManager component is James' mail processing engine. James'
SpoolManager component
+ is also called the Mailet container. It is these mailets and matchers
that actually carry out mail processing.</p>
+
+ <p>More on the configuration of the SpoolManager and the Mailet API can
be found <a href="config-mailetcontainer.html">here</a>.</p>
+
+ </subsection>
<subsection name="Matchers and Mailets">
@@ -91,51 +97,51 @@
</subsection>
- </section>
-
- <section name="Mailet API">
-
- <p>The Mailet API is a simple API used to build mail processing
applications. James is a Mailet
- container, allowing administrators to deploy Mailets (both custom and
pre-made) to carry out a
- variety of complex mail processing tasks. In the default configuration
James uses Mailets to carry
- out a number of tasks that are carried out deep in the source code of
other mail servers (i.e. list
- processing, remote and local delivery).</p>
-
- <p>As it stands today, the Mailet API defines interfaces for both Matchers
and Mailets.</p>
-
- <ul>
- <li>Matchers, as their name would suggest, match mail messages against
certain conditions. They
- return some subset (possibly the entire set) of the original
recipients of the message if there
- is a match. An inherent part of the Matcher contract is that a
Matcher should not induce any changes
- in a message under evaluation.</li>
- <li>Mailets are responsible for actually processing the message. They
may alter the message in any fashion,
- or pass the message to an external API or component. This can
include delivering a message to its destination
- repository or SMTP server.</li>
- </ul>
-
- <p>The Mailet API is currently in its second revision. Although, the
Mailet API is expected to undergo substantial changes in the near future, it is
our aim that existing Mailets that abided purely by the prior Mailet API
interfaces will continue to run with the revised specification.</p>
-
- <p>The Javadoc for the Mailet API can be found <a
href="http://james.apache.org/mailet/api/apidocs/";>here</a>.</p>
-
- <p>James bundles a number of Matchers and Mailets in its distribution.
Descriptions of provided matchers
- can be found <a href="dev-provided-matchers.html">here</a>, while
descriptions of provided mailets can be found
- <a href="dev-provided-mailets.html">here</a>.</p>
-
- <p>You can read more on mailets on following web sites:</p>
-
- <ul>
- <li><a href="http://james.apache.org/mailet/index.html";>Mailet
Site</a></li>
- <li><a href="http://james.apache.org/mailet/api/index.html";>Mailet
API</a></li>
- <li><a href="http://james.apache.org/mailet/base/index.html";>Mailet
Toolkit</a></li>
- <li><a href="http://james.apache.org/mailet/crypto/index.html";>Mailet
Crypto</a></li>
- <li><a href="http://james.apache.org/mailet/standard/index.html";>Mailet
Sieve</a></li>
- <li><a href="http://james.apache.org/mailet/standard/index.html";>Mailet
Standard</a></li>
- <li><a
href="http://james.apache.org/mailet/maven-mailetdocs-plugin/index.html";>Mailet
Docs</a></li>
- <li><a href="/james-server-mailets-function/mailet-report.html">Server
Mailets</a></li>
- </ul>
+ <subsection name="Mailet API">
+
+ <p>The Mailet API is a simple API used to build mail processing
applications. James is a Mailet
+ container, allowing administrators to deploy Mailets (both custom and
pre-made) to carry out a
+ variety of complex mail processing tasks. In the default
configuration James uses Mailets to carry
+ out a number of tasks that are carried out deep in the source code of
other mail servers (i.e. list
+ processing, remote and local delivery).</p>
+
+ <p>As it stands today, the Mailet API defines interfaces for both
Matchers and Mailets.</p>
+
+ <ul>
+ <li>Matchers, as their name would suggest, match mail messages
against certain conditions. They
+ return some subset (possibly the entire set) of the original
recipients of the message if there
+ is a match. An inherent part of the Matcher contract is that a
Matcher should not induce any changes
+ in a message under evaluation.</li>
+ <li>Mailets are responsible for actually processing the message.
They may alter the message in any fashion,
+ or pass the message to an external API or component. This can
include delivering a message to its destination
+ repository or SMTP server.</li>
+ </ul>
+
+ <p>The Mailet API is currently in its second revision. Although, the
Mailet API is expected to undergo substantial changes in the near future, it is
our aim that existing Mailets that abided purely by the prior Mailet API
interfaces will continue to run with the revised specification.</p>
+
+ <p>The Javadoc for the Mailet API can be found <a
href="http://james.apache.org/mailet/api/apidocs/";>here</a>.</p>
+
+ <p>James bundles a number of Matchers and Mailets in its distribution.
Descriptions of provided matchers
+ can be found <a href="dev-provided-matchers.html">here</a>, while
descriptions of provided mailets can be found
+ <a href="dev-provided-mailets.html">here</a>.</p>
+
+ <p>You can read more on mailets on following web sites:</p>
+
+ <ul>
+ <li><a href="http://james.apache.org/mailet/index.html";>Mailet
Site</a></li>
+ <li><a href="http://james.apache.org/mailet/api/index.html";>Mailet
API</a></li>
+ <li><a href="http://james.apache.org/mailet/base/index.html";>Mailet
Toolkit</a></li>
+ <li><a
href="http://james.apache.org/mailet/crypto/index.html";>Mailet Crypto</a></li>
+ <li><a
href="http://james.apache.org/mailet/standard/index.html";>Mailet Sieve</a></li>
+ <li><a
href="http://james.apache.org/mailet/standard/index.html";>Mailet
Standard</a></li>
+ <li><a
href="http://james.apache.org/mailet/maven-mailetdocs-plugin/index.html";>Mailet
Docs</a></li>
+ <li><a
href="/james-server-mailets-function/mailet-report.html">Server Mailets</a></li>
+ </ul>
+
+ </subsection>
</section>
-
+
</body>
</document>
Modified: james/server/trunk/src/site/xdoc/feature-perfomance.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-perfomance.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-perfomance.xml (original)
+++ james/server/trunk/src/site/xdoc/feature-perfomance.xml Sun Nov 14 07:06:46
2010
@@ -34,12 +34,16 @@
<source>time smtp-source -A -C1500 -l 100 -m 100000 -s 500 -d -c -f
[email protected] -t te localhost:25 100000</source>
<p>The result was:</p>
- <ol>
+ <ol>
<li>The queuing of the 100.000 emails took 8 minutes.</li>
- <li>The dequeue of the 100.000 emails took 16 minutes.</li>
+ <li>The dequeueing of the 100.000 emails took 16 minutes.</li>
</ol>
- <p>We thus have a troughput of more than <b>100 mails/second</b>.</p>
+ <p>We thus have a throughput of more than <b>100 mails/second</b>.</p>
+
+ <p>These numbers are obtained with the out-of-the-box configuration (not
optimized).
+ I you run for example (depends on JVM) with <code>-XX:+UseParallelGC
-XX:+AggressiveOpts -XX:+UseFastAccessorMethods</code>,
+ you may have 10.000 mails enqueued in 38 seconds, which represents
<b>263 mails per second</b>.</p>
</section>
Copied: james/server/trunk/src/site/xdoc/feature-persistence.xml (from
r1033409, james/server/trunk/src/site/xdoc/feature-stores.xml)
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-persistence.xml?p2=james/server/trunk/src/site/xdoc/feature-persistence.xml&p1=james/server/trunk/src/site/xdoc/feature-stores.xml&r1=1033409&r2=1034944&rev=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-stores.xml (original)
+++ james/server/trunk/src/site/xdoc/feature-persistence.xml Sun Nov 14
07:06:46 2010
@@ -20,89 +20,113 @@
<document>
<properties>
- <title>Repositories</title>
+ <title>Persistence</title>
</properties>
<body>
-<section name="Mailbox Store">
-
-<p>James Server uses the <a href="http://james.apache.org/mailbox";>mailbox</a>
storage system
-to store the users mailboxes.</p>
-
-<p>The mailbox library supports different persistence mecanisms: MailDir,
Database (via JPA) and JCR.</p>
-
-</section>
-
-<section name="Repositories">
-
-<p>James uses also a number of different repositories to both store message
data (non mailbox emails, news messages in V2) and
-user information. User repositories store user information, including user
names, authentication
-information, and aliases. Mail repositories store messages that have been
delivered locally. Spool
-repositories store messages that are still being processed. Finally, news
repositories are used to
-store news messages.</p>
-
-<p>Aside from the type of data they store, repositories are distinguished by
-where they store data. There are three types of storage - File, Database, and
DBFile.</p>
-
-<subsection name="File Repositories">
-
-<p>File-based repositories store all data in the file system. In general,
these repositories are extremely
-simple to configure, but may compare poorly in terms of performance when
compared to other repository
-types. File repositories are not recommended for large or
performance-critical configurations. In the
-default configuration, all repositories are file repositories.</p>
-
-<p>File repository paths typically begin with the prefix "file". Paths are
relative to the application
-base directory, unless the path begins with a slash. As an example, assume
that James is running in
-/usr/james/phoenix/apps/james. Then "file://var/mail/spool/" would refer to
the directory /usr/james/phoenix/apps/james/var/mail/spool.
-And "file:///var/mail/spool/" (note the extra '/') would refer to the
directory /var/mail/spool.</p>
-
-<p>All repository types (mail, spool, user, and news) have file-based
implementations. No special configuration is required to enable file-based
repositories</p>
-
-</subsection>
-
-<subsection name="Database (JPA) Repositories">
-
-</subsection>
-
-<subsection name="Database (JDBC) Repositories">
-
-<p>Database repositories store all data in an administrator-supplied database.
Configuration is somewhat
-more complex, requiring that the administrator adjust the data-connections
section. Detailed directions
-are included in the sample configuration file. The administrator will need to
know the JDBC driver class,
-the appropriate URL for use with his database, and a valid username/password
for the database.</p>
-
-<p>If the administrator wants to configure a database other than MySQL, it
will be necessary to add the jar
-or zip file containing the JDBC driver classes to the lib subdirectory of the
installation directory. This
-will allow Phoenix to properly load the driver when it is initializing the
database repository. The MySQL
-driver is pre-packaged with James.</p>
-
-<p>Database repository paths typically begin with the prefix "db". The format
is "db://<data-source>/<table>"
-where <data-source> is the name of the data-source defined in the
data-connections section. And <table> is
-the particular table associated with the repository.</p>
-
-<p>Mail, spool, and user repositories have JDBC-based implementations.</p>
-
-</subsection>
-
-<subsection name="DBFile Repositories">
-
-<p>This is a special repository type used only for mail repositories. DBFile
repositories store the body of
-a mail message in the file system, while headers are stored in the database.
This allows the administrator
-to minimize the size of data stored in the database, while conserving most of
the performance of the
-database repository.</p>
-
-<p>Only mail repositories have dbfile-based implementations.</p>
-
-</subsection>
-
-<subsection name="JCR Repositories">
-
-<p>Only user repositories have jcr-based implementations.</p>
-
-</subsection>
-
-</section>
+ <section name="Mailbox and Mailstore">
+
+ <p><b>Mailbox</b> is for users' Inbox, Sent Items, Trash... folders.</p>
+
+ <p><b>Mailstore</b> is for spam, error,... mails, so nothing to do with
users visible mails.</p>
+
+ <p>Both mailbox and mailstore use database connection defined via
database.properties
+ in case of database access.</p>
+
+ </section>
+
+ <section name="Mailbox Persistence">
+
+ <p>James Server uses the <a
href="http://james.apache.org/mailbox";>mailbox</a> storage system
+ to store the users mailboxes.</p>
+
+ <p>The mailbox library supports different persistence mecanisms: MailDir,
Database (via JPA) and JCR.</p>
+
+ <p>Mailbox persistence is configured in spring-beans.xml (by default JPA,
+ you set the database connection properties in database.properties - can
also be
+ MailDir, JCR).</p>
+
+ </section>
+
+ <section name="Mailstore Persistence">
+
+ <subsection name="Repositories">
+
+ <p>Available mailstore persistence (aka repository) are defined in
mailstore.xml.
+ Each has an URL prefix (file, db, dbfile,...) that can be used in
mailetcontainer.xml
+ 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-mailstores.html">here</a>.</p>
+
+ <p>Mailstores are distinguished by where they store data. There are
three types of
+ storage - File, Database, and DBFile.</p>
+
+ </subsection>
+
+ <subsection name="File Repositories">
+
+ <p>File-based repositories store all data in the file system. In
general, these repositories are extremely
+ simple to configure, but may compare poorly in terms of performance when
compared to other repository
+ types. File repositories are not recommended for large or
performance-critical configurations. In the
+ default configuration, all repositories are file repositories.</p>
+
+ <p>File repository paths typically begin with the prefix "file". Paths
are relative to the application
+ base directory, unless the path begins with a slash. As an example,
assume that James is running in
+ /usr/james/phoenix/apps/james. Then "file://var/mail/spool/" would
refer to the directory /usr/james/phoenix/apps/james/var/mail/spool.
+ And "file:///var/mail/spool/" (note the extra '/') would refer to the
directory /var/mail/spool.</p>
+
+ <p>All repository types (mail, spool, user, and news) have file-based
implementations. No special configuration is required to enable file-based
repositories</p>
+
+ </subsection>
+
+ <subsection name="Database (JDBC) Repositories">
+
+ <p>Database repositories store all data in an administrator-supplied
database. Configuration is somewhat
+ more complex, requiring that the administrator adjust the
data-connections section. Detailed directions
+ are included in the sample configuration file. The administrator will
need to know the JDBC driver class,
+ the appropriate URL for use with his database, and a valid
username/password for the database.</p>
+
+ <p>If the administrator wants to configure a database other than MySQL,
it will be necessary to add the jar
+ or zip file containing the JDBC driver classes to the lib subdirectory
of the installation directory. This
+ will allow Phoenix to properly load the driver when it is initializing
the database repository. The MySQL
+ driver is pre-packaged with James.</p>
+
+ <p>Database repository paths typically begin with the prefix "db". The
format is "db://<data-source>/<table>"
+ where <data-source> is the name of the data-source defined in the
data-connections section. And <table> is
+ the particular table associated with the repository.</p>
+
+ <p>Mail, spool, and user repositories have JDBC-based
implementations.</p>
+
+ </subsection>
+
+ <subsection name="DBFile Repositories">
+
+ <p>This is a special repository type used only for mail repositories.
DBFile repositories store the body of
+ a mail message in the file system, while headers are stored in the
database. This allows the administrator
+ to minimize the size of data stored in the database, while conserving
most of the performance of the
+ database repository.</p>
+
+ <p>Only mail repositories have dbfile-based implementations.</p>
+
+ </subsection>
+
+ <subsection name="JCR Repositories">
+
+ <p>Only user repositories have jcr-based implementations.</p>
+
+ </subsection>
+
+ </section>
+
+ <section name="Domain Persistence">
+
+ </section>
+
+ <section name="User Persistence">
+
+ </section>
</body>
Copied: james/server/trunk/src/site/xdoc/feature-servers.xml (from r1034937,
james/server/trunk/src/site/xdoc/feature-summary.xml)
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-servers.xml?p2=james/server/trunk/src/site/xdoc/feature-servers.xml&p1=james/server/trunk/src/site/xdoc/feature-summary.xml&r1=1034937&r2=1034944&rev=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-summary.xml (original)
+++ james/server/trunk/src/site/xdoc/feature-servers.xml Sun Nov 14 07:06:46
2010
@@ -20,25 +20,29 @@
<document>
<properties>
- <title>James 3.0 - Features Summary</title>
+ <title>James 3.0 - Feature - Servers</title>
</properties>
<body>
- <section name="The James Server">
+ <section name="Servers">
- <p>James is an open source project intended to produce a robust, flexible,
and powerful
- enterprise class server that provides email and email-related services.
It is also designed to
- be highly customizable, allowing administrators to configure James to
process email in a
- nearly endless variety of fashions.</p>
-
- <p>The standard James distribution deploys inside the Spring dependency
injection container.
- In addition to providing a robust server architecture for James, the use
of Spring allows James administrators
- to deploy their own applications inside the container. These applications
can then be accessed during
- mail processing.</p>
+ <subsection name="Introduction">
- <p>The James server is implemented as a complete collection of servers and
related components that, taken together,
- provide an email solution. These components are described below.</p>
+ <p>James is an open source project intended to produce a robust,
flexible, and powerful
+ enterprise class server that provides email and email-related services.
It is also designed to
+ be highly customizable, allowing administrators to configure James to
process email in a
+ nearly endless variety of fashions.</p>
+
+ <p>The standard James distribution deploys inside the Spring dependency
injection container.
+ In addition to providing a robust server architecture for James, the use
of Spring allows James administrators
+ to deploy their own applications inside the container. These
applications can then be accessed during
+ mail processing.</p>
+
+ <p>The James server is implemented as a complete collection of servers
and related components that, taken together,
+ provide an email solution. These components are described below.</p>
+
+ </subsection>
<subsection name="SMTP Protocol">
@@ -51,31 +55,31 @@
</subsection>
- <subsection name="POP3 Protocol">
+ <subsection name="IMAP4 Protocol">
- <p>The POP3 protocol allows users to retrieve email messages. It is the
method
+ <p>The IMAP4 protocol allows users to retrieve email messages. It is
the method
most commonly used by email clients to download and manage email
messages.</p>
- <p>The James version of the POP3 service is a simple and straightforward
implementation that
+ <p>The James version of the IMAP4 service is a simple and
straightforward implementation that
provides full compliance with the specification and maximum
compatibility with common
- POP3 clients. In addition, James can be configured to require SSL/TLS
connections for
- POP3 client connecting to the server.</p>
+ IMAP4 clients. In addition, James can be configured to require SSL/TLS
connections for
+ IMAP4 client connecting to the server.</p>
- <p>More information on configuring the POP3 service can be found <a
href="config-pop3.html">here</a>.</p>
+ <p>More information on configuring the IMAP4 service can be found <a
href="config-imap4.html">here</a>.</p>
</subsection>
- <subsection name="IMAP4 Protocol">
+ <subsection name="POP3 Protocol">
- <p>The IMAP4 protocol allows users to retrieve email messages. It is
the method
+ <p>The POP3 protocol allows users to retrieve email messages. It is the
method
most commonly used by email clients to download and manage email
messages.</p>
- <p>The James version of the IMAP4 service is a simple and
straightforward implementation that
+ <p>The James version of the POP3 service is a simple and straightforward
implementation that
provides full compliance with the specification and maximum
compatibility with common
- IMAP4 clients. In addition, James can be configured to require SSL/TLS
connections for
- IMAP4 client connecting to the server.</p>
+ POP3 clients. In addition, James can be configured to require SSL/TLS
connections for
+ POP3 client connecting to the server.</p>
- <p>More information on configuring the IMAP4 service can be found <a
href="config-imap4.html">here</a>.</p>
+ <p>More information on configuring the POP3 service can be found <a
href="config-pop3.html">here</a>.</p>
</subsection>
@@ -90,29 +94,6 @@
</subsection>
- <subsection name="SpoolManager, Matchers and Mailets">
-
- <p>James separates the services that deliver mail to James (i.e. SMTP,
FetchMail)
- from the engine that processes mail after it is received by James. The
- SpoolManager component is James' mail processing engine. James'
SpoolManager component
- is also called the Mailet container. It is these mailets and matchers
that actually carry out mail processing.</p>
-
- <p>More on the structure of the SpoolManager and the Mailet API can be
found <a href="config-mailetcontainer.html">here</a>.</p>
-
- </subsection>
-
- <subsection name="Stores">
-
- <p>James uses a number of different stores/repositories to both store
message data (email, news messages) and
- user information. User stores/repositories contain user information,
including user names, authentication
- information, and aliases. Mail stores/repositories contain messages
that have been delivered locally. Spool
- Stores/repositories contain messages that are still being processed.
Aside from what type of data they store,
- repositories are distinguished by where they store data. There are
three types of storage - File, Database, and DBFile.</p>
-
- <p>More information the stores can be found <a
href="config-mailstores.html">here</a>.</p>
-
- </subsection>
-
<subsection name="RemoteManager">
<p>James provides a simple telnet-based interface for control. Through
this interface you can add
Added: james/server/trunk/src/site/xdoc/feature-smtp-hooks.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/feature-smtp-hooks.xml?rev=1034944&view=auto
==============================================================================
--- james/server/trunk/src/site/xdoc/feature-smtp-hooks.xml (added)
+++ james/server/trunk/src/site/xdoc/feature-smtp-hooks.xml Sun Nov 14 07:06:46
2010
@@ -0,0 +1,64 @@
+<?xml version="1.0"?>
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+<document>
+
+ <properties>
+ <title>James - Features - SMTP Hooks</title>
+ </properties>
+
+<body>
+
+ <section name="SMTP Hooks">
+
+ <p>The James SMTP Server Component allows to easy write your own code
which will get executed
+ in the SMTP-Transaction. Thats a bit different then using a Mailet
a.k.a Mailet-API.</p>
+
+ <p>The James SMTP Server comes with a few interfaces which helps you to
"hook-in" a
+ specific SMTP Command. That means your class which implements the given
interface(s) will get
+ called after the SMTP-Command was parsed and depending on your
implementation it will handle it.</p>
+
+ <p>As your code will get executed before the mail was even accepted. This
can help you in many ways,
+ most times its used for rejecting SPAM/Junk within the SMTP-Dialog. But
it can be used for
+ other things too.</p>
+
+ <p>Its up to you and your use case.</p>
+
+ <p>But be aware as your code needs to get executed during the
SMTP-Transaction it should not
+ take to long to execute. As it will need to fit in before the timeout
was hit which can be
+ different on every mailserver. But as a general rule as long as your
code can get executed
+ within 30 seconds it should be fine.</p>
+
+ </section>
+
+ <section name="Provided SMTP Hooks">
+
+ Read more on the <a href="dev-provided-smtp-hooks.html">provided SMTP
Hooks</a>.
+
+ </section>
+
+ <section name="Create your own SMTP Hooks">
+
+ Read more on how to create your <a href="dev-extend-smtp-hook.html">own
SMTP Hook</a>.
+
+ </section>
+
+</body>
+
+</document>
Modified: james/server/trunk/src/site/xdoc/install.xml
URL:
http://svn.apache.org/viewvc/james/server/trunk/src/site/xdoc/install.xml?rev=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/install.xml (original)
+++ james/server/trunk/src/site/xdoc/install.xml Sun Nov 14 07:06:46 2010
@@ -60,7 +60,12 @@
<p>Obviously James also requires sufficient disk space, processor power,
and network bandwidth. But,
other than what's been discussed here, it has no additional special
requirements.</p>
- <p>James is configured to run with 512 MB RAM available, but may need more
or less depending on the load.</p>
+ <p>James is configured to run with 512 MB RAM (-Xmx512M in the bat/sh)
available, but may need more or
+ less depending on the load. With the default configuraiton, JVM can use
until 512M (It does not mean it will do).
+ It really depends on your traffic, and also which mailbox you will use
(you can save much memory
+ if you don't use the default embedded derby database but an external
database of your choice).
+ Work is still done to minimize the needed memory.
+ </p>
</subsection>
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=1034944&r1=1034943&r2=1034944&view=diff
==============================================================================
--- james/server/trunk/src/site/xdoc/quick-start.xml (original)
+++ james/server/trunk/src/site/xdoc/quick-start.xml Sun Nov 14 07:06:46 2010
@@ -37,7 +37,7 @@ Step 0: Requirements
* JRE 1.5+
* root (linux/unix) or Administrator (Windows)
* libc6 (linux)
- * 512MB RAM
+ * 512MB RAM (launches with -Xmx512M - can use less, can need more, depending
on load)
Step 1: Download
#################
@@ -52,52 +52,62 @@ Step 2: Deploy
$ unzip james-server-container-spring-3.0-M2-bin.tar.gz
$ cd james-server-container-spring-3.0-M2
-$ ls -l
-drwxrwxrwx. 2 root root 4096 2010-11-06 09:24 bin
--rw-r--r--. 1 root root 495 2010-11-06 08:56 BUILD.txt
-drwxrwxrwx. 4 root root 4096 2010-11-06 14:43 conf
-drwxrwxrwx. 2 root root 12288 2010-11-06 09:01 lib
--rw-r--r--. 1 root root 12082 2010-11-01 17:23 LICENSE.txt
-drwxrwxrwx. 2 root root 4096 2010-11-06 09:24 log
--rw-r--r--. 1 root root 1579 2010-11-01 17:23 NOTICE.txt
--rw-r--r--. 1 root root 1545 2010-11-06 08:55 README.txt
-drwxrwxrwx. 6 root root 4096 2010-11-06 09:25 var
+$ ls (linux) / dir (windows)
+bin
+BUILD.txt
+conf
+lib
+LICENSE.txt
+log
+NOTICE.txt
+README.txt
+var
+
+Step 3: Understand James Features
+#################################
+
+Persistence
+- Mailbox is for users' Inbox, Sent Items, Trash... folders - Mailbox
persistence is configured in spring-beans.xml (by default jpa, you set the
database connection properties in database.properties - can also be
maildir=file, jcr). We think to move this config out-of spring-beans.xml.
+- Mailstore is for spam, error,... mails, so nothing to do with users visible
mails. Available mailstore persistence are defined in mailstore.xml. Each has
an URL prefix (file, db, dbfile,...) that can be used in mailetcontainer.xml to
define where to store spam,... mails (exemple: file://var/mail/error/).
+- Domain persistence is configured in domainlist.xml
+- Users persistence is configured in usersrepository.xml
+- All database connection use the database.properties in case of database
access.
+Mailet Container - http://james.apache.org/server/3/feature-mailetcontainer.xml
-Step 3: Configure
+SMTP Hooks - http://james.apache.org/server/3/feature-smtp-hooks.xml
+
+Step 4: Configure
#################
* All configuration files reside in the conf folder.
-$ cd conf
-$ ls -l
--rw-------. 1 root root 1414 2010-11-05 16:01 database.properties
--rw-------. 1 root root 2749 2010-10-21 14:07 dnsservice.xml
--rw-------. 1 root root 2802 2010-11-06 09:22 domainlist.xml
--rw-------. 1 root root 18599 2010-10-21 14:07 fetchmail.xml
--rw-------. 1 root root 3201 2010-10-21 14:07 imapserver.xml
--rw-------. 1 root root 2850 2010-11-04 08:10 james-listmanager.xml
--rw-------. 1 root root 5821 2010-10-21 14:07 jcr-repository.xml
--rw-------. 1 root root 0 2010-11-05 16:01 jmx.access
--rw-------. 1 root root 0 2010-11-05 16:01 jmx.password
--rw-------. 1 root root 961 2010-11-06 08:42 jmx.properties
-drwxrwxrwx. 2 root root 4096 2010-10-21 14:07 lib
--rw-------. 1 root root 3129 2010-10-21 14:07 lmtpserver.xml
--rw-------. 1 root root 7463 2010-11-05 15:54 log4j.properties
--rw-------. 1 root root 31478 2010-11-06 09:22 mailetcontainer.xml
--rw-------. 1 root root 2473 2010-11-06 09:22 mailserver.xml
--rw-------. 1 root root 5234 2010-10-21 14:54 mailstore.xml
-drwxrwxrwx. 2 root root 4096 2010-10-21 14:07 META-INF
--rw-------. 1 root root 8038 2010-10-21 14:07 miResources.xml
--rw-------. 1 root root 3327 2010-10-21 14:07 pop3server.xml
--rw-------. 1 root root 3369 2010-10-21 14:07 remotemanager.xml
--rw-------. 1 root root 15837 2010-11-05 15:54 smtpserver.xml
--rw-------. 1 root root 21941 2010-11-05 16:01 spring-beans.xml
--rw-------. 1 root root 48523 2010-10-21 14:07 sqlResources.xml
--rw-------. 1 root root 4301 2010-10-29 15:48 usersrepository.xml
--rw-------. 1 root root 2465 2010-10-21 14:07 virtualusertable.xml
--rw-------. 1 root root 13680 2010-11-06 09:01 wrapper.conf
-
+database.properties
+META-INF/persistence.xml
+dnsservice.xml
+domainlist.xml
+fetchmail.xml
+imapserver.xml
+james-listmanager.xml
+jcr-repository.xml
+jmx.access
+jmx.password
+jmx.properties
+lmtpserver.xml
+log4j.properties
+mailetcontainer.xml
+mailserver.xml
+mailstore.xml
+miResources.xml
+pop3server.xml
+remotemanager.xml
+smtpserver.xml
+spring-beans.xml
+sqlResources.xml
+usersrepository.xml
+virtualusertable.xml
+wrapper.conf
+lib folder
James is packaged with virtual hosting disabled, XML domain list, JPA (Derby
database) storage for the mails and SMTP Auth.
You can for example edit the following files to change the behaviour:
@@ -118,19 +128,23 @@ You can for example edit the following f
* Add the needed JDBC driver jar in the ./conf/lib folder according to your
database.
-Step 4: Start
+Step 5: Start
#############
$ cd bin
$ ./james start
- * !! you need libc6 installed on Linux - sudo apt-get install libc6-i386
libc6-dev-i386 on ubuntu
+ * !! you need libc6 installed on Linux !! - sudo apt-get install libc6-i386
libc6-dev-i386 on ubuntu
* You can see log result in the log/james-server.log file.
-Step 5: Create Domains and Users
+Step 6: Create Domains and Users
################################
+Time to add domains and users.
+We wil show how to via the remote manager (telnet).
+You also can achieve it via JMX.
+
$ telnet localhost 4555
Trying 127.0.0.1...
Connected to localhost.
@@ -153,7 +167,7 @@ Connection closed by foreign host.
* For example, YOUR_DOMAIN=localhost.net, YOUR_NAME=test, so you will have a
[email protected] user.
* The username to use in you mail client will be [email protected].
-Step 6: Test
+Step 7: Test
############
$ telnet 127.0.0.1 25
@@ -180,10 +194,10 @@ this is a test
quit
Connection closed by foreign host.
-Step 7: Manage
+Step 8: Manage
##############
-7.1. Manage via telnet
+8.1. Manage via telnet
$ telnet localhost 4555
Trying 127.0.0.1...
@@ -220,11 +234,11 @@ unsetforwarding [username] removes
user [repositoryname] change to another user repository
verify [username] verify if specified user exist
-7.2. Manage via JMX
+8.2. Manage via JMX
* Launch jconsole (or any other JMX client) and connect on
URL=service:jmx:rmi:///jndi/rmi://localhost:9999/jmxrmi
-Step 8: Monitor
+Step 9: Monitor
###############
* Monitor the ./log/james-server.log log file.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
