You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-dev@james.apache.org by rd...@apache.org on 2009/08/03 19:36:34 UTC
svn commit: r800474 [18/26] - in /james/site/trunk/www/server: 2.3.2/
2.3.2/apidocs/ 2.3.2/apidocs/org/apache/james/
2.3.2/apidocs/org/apache/james/class-use/
2.3.2/apidocs/org/apache/james/context/
2.3.2/apidocs/org/apache/james/context/class-use/ 2.3...
Modified: james/site/trunk/www/server/2.3.2/design_objectives.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/design_objectives.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/design_objectives.html (original)
+++ james/site/trunk/www/server/2.3.2/design_objectives.html Mon Aug 3 17:36:07 2009
@@ -11,19 +11,21 @@
<html>
<head>
- <title>James Server - Design Objectives</title>
+ <title>James Server -
+ Design Objectives</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="author" content="James Project Web Team" />
+ <meta name="author" content="
+ James Project Web Team" />
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -46,21 +48,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -304,11 +306,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -329,21 +331,37 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2><a name="Design_Objectives"></a>Design Objectives</h2>
-<div class="section"><h3><a name="features"></a>features</h3>
-<p>These are some of the currently implemented features:</p>
-<p><i><b>Complete portability</b></i> Apache James is be a 100% pure Java application
+
+
+
+ <a name="Design Objectives"></a><div class="section"><h2>Design Objectives</h2>
+
+ <a name="features"></a><div class="section"><h3>features</h3>
+ <p>These are some of the currently implemented features:</p>
+ <p>
+ <i>
+ <b>Complete portability</b>
+ </i> Apache James is be a 100% pure Java application
based on the Java 2 platform and the JavaMail 1.4 API.
</p>
-<p><i><b>Protocol abstraction</b></i> Unlike other mail engines, protocols are seen only
+ <p>
+ <i>
+ <b>Protocol abstraction</b>
+ </i> Unlike other mail engines, protocols are seen only
like "communication languages" ruling comunications between clients and
the server. Apache James is not be tied to any particular protocol but
follow an abstracted server design (like JavaMail did on the
client side)</p>
-<p><i><b>Complete solution</b></i> the mail system is able to handle both mail
+ <p>
+ <i>
+ <b>Complete solution</b>
+ </i> the mail system is able to handle both mail
transport and storage in a single server application. Apache James
works alone without the need for any other server or solution.</p>
-<p><i><b>Mailet support</b></i> Apache James supports the Apache Mailet API. A Mailet
+ <p>
+ <i>
+ <b>Mailet support</b>
+ </i> Apache James supports the Apache Mailet API. A Mailet
is a discrete piece of mail-processing logic which is incorporated into
a Mailet-compliant mail-server's processing. This easy-to-write,
easy-to-use pattern allows developers to build powerful customized mail
@@ -351,29 +369,32 @@
mail-to-fax or mail-to-phone transformer, a filter, a language translator, a mailing
list manager, etc. Several Mailets are included in the JAMES
distribution (see <a href="documentation.html">documentation</a>).</p>
-<p><i><b>Resource abstraction</b></i> Like protocols, resources are abstracted and,
+ <p>
+ <i>
+ <b>Resource abstraction</b>
+ </i> Like protocols, resources are abstracted and,
accessed through defined interfaces (JavaMail for transport, JDBC for
spool storage or user accounts in RDBMS's, Apache Mailet API). The server is
highly modular and reuse solutions from other projects.</p>
-<p><i><b>Secure and multi-threaded design</b></i> Based on the technology developed
+ <p>
+ <i>
+ <b>Secure and multi-threaded design</b>
+ </i> Based on the technology developed
for the Apache JServ servlet engine, Apache James has a careful,
security-oriented, full multi-threaded design, to allow performance,
scalability and mission-critical use.</p>
-<p>Anything else you may want if you help us write it :-)</p>
-</div>
-<div class="section"><h3><a name="standards_compliance"></a>standards compliance</h3>
-<p>It is the existence of published "open" standards which
+ <p>Anything else you may want if you help us write it :-)</p>
+ </div>
+ <a name="standards compliance"></a><div class="section"><h3>standards compliance</h3>
+ <p>It is the existence of published "open" standards which
allows independant teams to develop interoperable software.
-<br />
-James attempts to support a number of these standards most of which are
+<br></br>James attempts to support a number of these standards most of which are
IETF RFC's and in the areas covered by these standards the published standard
is our requirements document.
-<br />
-This sometimes leads to confusion where behaviour is not
+<br></br>This sometimes leads to confusion where behaviour is not
the subject of a relevant standard, or conflict where common
(de-facto) behaviour is actually at odds with a supported standard.
-<br />
-We believe that it is our responsibility to adhere to the published standard.
+<br></br>We believe that it is our responsibility to adhere to the published standard.
If we allow our implementation to deviate it means that we are tacitly encouraging
the situation whereby interoperability is no longer guarenteed by standards
compliance alone, but also requires access to undocumented and possibly
@@ -381,16 +402,16 @@
newcomer to aquire these secrets, and interoperabilty
becomes something only available to the elite.
</p>
-<p>The James policy for issues of non-compliance tries to tread the fine line
+ <p>The James policy for issues of non-compliance tries to tread the fine line
between a pragmatic acceptance of other people's misinterpretation of the
RFC's and an evangelical defence of open standards as the key to freedom of interoperation.
</p>
-<p>
+ <p>
In practice this policy is that certain well argued of cases of
non-compliance which can be *safely* worked around, will be tolerated by
James.
</p>
-<p>
+ <p>
In cases (like jira issue JAMES-344 ) where variance from a published standard is
required it is desirable that this functionality is disabled in James by default,
it must be prominently and clearly documented that this causes James
@@ -398,7 +419,7 @@
configuration, making its use a conscious decision of the user rather
than an decision taken by the James team.
</p>
-<p>
+ <p>
In cases where the required behaviour is not within the scope of any standard which
James claims to support (such as behaviour which is a de-facto standard or
an <i>internet draft</i> RFC but not yet subject of a <i>standards track</i> RFC) it is
@@ -406,8 +427,9 @@
documented (for instance by refrence to an <i>internet draft</i> or
other public document) and users can be clear about what to expect from James.
</p>
-</div>
-</div>
+ </div>
+ </div>
+
</div>
</div>
Modified: james/site/trunk/www/server/2.3.2/dns_configuration.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/dns_configuration.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/dns_configuration.html (original)
+++ james/site/trunk/www/server/2.3.2/dns_configuration.html Mon Aug 3 17:36:07 2009
@@ -11,7 +11,8 @@
<html>
<head>
- <title>James Server - James 2.3 - Configuring DNS Services</title>
+ <title>James Server -
+ James 2.3 - Configuring DNS Services</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@@ -22,7 +23,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -45,21 +46,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -303,11 +304,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -328,15 +329,25 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2><a name="DNS_Configuration"></a>DNS Configuration</h2>
+
+
+
+
+
+<a name="DNS Configuration"></a><div class="section"><h2>DNS Configuration</h2>
+
+
<p>DNS Transport services are controlled by a configuration block in
the config.xml. This block affects SMTP remote delivery.</p>
+
<p>The dnsserver tag defines the boundaries of the configuration
block. It encloses all the relevant configuration for the DNS server.
The behavior of the DNS service is controlled by the attributes and
-children of this tag.</p>
+children of this tag.</p>
+
<p>The standard children of the dnsserver tag are:</p>
-<ul><li><strong>servers</strong> - This is a list of DNS Servers to be used by James and are
+<ul>
+<li><strong>servers</strong> - This is a list of DNS Servers to be used by James and are
specified by one, or more <strong><i>server</i></strong> elements, which are child elements.
Each server element is the IP address of a single DNS server.
<div class="source"><pre>
@@ -344,26 +355,26 @@
<server>127.0.0.1</server>
<server>166.181.194.205</server>
</servers>
-</pre>
-</div>
+</pre></div>
</li>
+
<li><strong>authoritative</strong> - (<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.
-This should always be <strong>false</strong> unless you understand the implications.</li>
+This should always be <strong>false</strong> unless you understand the implications.
+</li>
</ul>
</div>
-<div class="section"><h2><a name="Sun_JVM_DNS_Lookup_Configuration."></a>Sun JVM DNS Lookup Configuration.</h2>
-<p>Sun's JVM Internet address lookup uses a cache which is unbounded and doesn't time out.<br />
-
-This is obviously not great for a long running process like a mail server so we have introduced a system property <strong>networkaddress.cache.ttl</strong> that is used by the distributed phoenix start-up scripts, at startup, to override the java 1.4 <strong>Security.setProperty("networkaddress.cache.ttl")</strong>.<br />
- By default this is set to <strong>300</strong> seconds.</p>
+<a name="Sun JVM DNS Lookup Configuration."></a><div class="section"><h2>Sun JVM DNS Lookup Configuration.</h2>
+Sun's JVM Internet address lookup uses a cache which is unbounded and doesn't time out.<br></br>
+This is obviously not great for a long running process like a mail server so we have introduced a system property <strong>networkaddress.cache.ttl</strong> that is used by the distributed phoenix start-up scripts, at startup, to override the java 1.4 <strong>Security.setProperty("networkaddress.cache.ttl")</strong>.<br></br> By default this is set to <strong>300</strong> seconds.
<p>This workaround will only be present if you use James as distributed. If you use James in any other container, including different versions of Phoenix, you will need to ensure that you make a similar configuration change to allow the internet address cache to perform acceptably.</p>
<p>James 2.3 has this workaround and it requires it to operate acceptably. Future versions of James will continue to have the workaround in place but will *not* require it. This will provide continued support for any mailets which you may deploy from other sources which might continue to use Sun's InetAddress class for DNS resolution.</p>
<p>We are not currently aware of the behaviour of this cache in other JVM implementations, nor of the effect, if any, which this change might have on them</p>
-<p>For more on this read defect report <a href="http://issues.apache.org/jira/browse/JAMES-592" class="externalLink">JAMES-592</a> and related defects.</p>
+<p>For more on this read defect report <a href="http://issues.apache.org/jira/browse/JAMES-592">JAMES-592</a> and related defects.</p>
</div>
+
</div>
</div>
<div class="clear">
Modified: james/site/trunk/www/server/2.3.2/fetchmail_configuration.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/fetchmail_configuration.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/fetchmail_configuration.html (original)
+++ james/site/trunk/www/server/2.3.2/fetchmail_configuration.html Mon Aug 3 17:36:07 2009
@@ -11,7 +11,8 @@
<html>
<head>
- <title>James Server - James 2.3 - fetchmail Configuration</title>
+ <title>James Server -
+ James 2.3 - fetchmail Configuration</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@@ -22,7 +23,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -45,21 +46,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -303,11 +304,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -328,27 +329,38 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2><a name="fetchmail"></a>fetchmail</h2>
+
+
+
+
+<a name="fetchmail"></a><div class="section"><h2>fetchmail</h2>
<p>fetchmail acts as a gateway between an external message store such as an IMAP
or POP3 server and James. Mail is fetched from the external message store and
injected into the James input spool.</p>
+
<p>fetchmail is useful when delivery via standard SMTP is not an option, as a
means of consolidating mail delivered to several external accounts into a single
James account, or to apply the mail processing capabilities of James to mail
stored in an external message store.</p>
+
<p>fetchmail has several configuration options that control the fetching and
filtering of mail injected into the James input spool. Once there, James'
flexible mail processing engine can be used to further process the mail, just as
if it had been delivered via standard SMTP.</p>
-<p><a href="#How fetchmail Works">How fetchmail Works</a><br />
-<a href="#fetchmail Configuration Parameters">fetchmail Configuration Parameters</a><br />
-<a href="#fetchmail Examples">fetchmail Examples</a><br />
-<a href="#fetchmail Caveats">fetchmail Caveats</a></p>
+
+<p>
+<a href="#How fetchmail Works">How fetchmail Works</a><br></br>
+<a href="#fetchmail Configuration Parameters">fetchmail Configuration Parameters</a><br></br>
+<a href="#fetchmail Examples">fetchmail Examples</a><br></br>
+<a href="#fetchmail Caveats">fetchmail Caveats</a>
+</p>
</div>
-<div class="section"><h2><a name="How_fetchmail_Works"></a>How fetchmail Works</h2>
+
+<a name="How fetchmail Works"></a><div class="section"><h2>How fetchmail Works</h2>
<p>Mail is delivered by periodically running fetch tasks that read messages from
an external message store and injects them into the James input spool. Fetch
tasks run concurrently.</p>
+
<p>A set of filters applies to each fetch task. Each filter provides the ability
to reject a message that matches the filter criteria. Rejected messages are not
injected into the James input spool; they are either marked as seen or deleted.
@@ -356,21 +368,26 @@
messages are marked with a MailAttribute. This MailAttribute can be detected
within the James matcher/mailet chain, allowing further processing as
required.</p>
+
<p>Each fetch task is associated with a single host server. Accounts are defined
to the fetch task for each mailbox on the server from which mail is to be
fetched. Accounts run consecutively.</p>
+
<p>Optionally, the fetch task can be configured with an <alllocal> Account that
generates an Account entry for each user defined in the James user repository.
This removes the requirement to manually add or remove Account entries to the
fetchmail configuration each time a James user is added or removed. Currently
this is only useful if the server supports virtual mailboxes that allow the same
password to apply to all users within a domain.</p>
+
<p>Accounts can be configured to deliver all mail for an Account to a specified
recipient or to deduce the intended recipient from the mail headers.</p>
+
<p>Accounts are normally configured to deliver all mail for an Account to a
specified recipient, ignoring the recipient in the mail headers. This works well
in the majority of cases where a mailbox is guaranteed to contain mail for a sole
mailbox recipient.</p>
+
<p>Accounts are configured to deduce the intended recipient from the mail headers
when a mailbox contains mail for several users, typically all users in a domain.
Used alone, this is not foolproof as there are circumstances when a single unique
@@ -378,44 +395,57 @@
an appropriately configured <alllocal> account, it is always possible to deduce
the intended recipient when the recipient is a James user.</p>
</div>
-<div class="section"><h2><a name="fetchmail_Configuration_Parameters"></a>fetchmail Configuration Parameters</h2>
+
+<a name="fetchmail Configuration Parameters"></a><div class="section"><h2>fetchmail Configuration Parameters</h2>
<p>The fetchmail configuration parameters are part of the James configuration,
whose base file is <code>config.xml</code>. For clarity and flexibility, the
fetchmail configuration parameters are stored in the file
<code>james-fetchmail.xml</code>, which is referenced within
<code>config.xml</code>.</p>
+
<p>The configuration parameters are described below.</p>
-<div class="section"><h3><a name="fetchmail"></a>fetchmail</h3>
+
+<a name="fetchmail"></a><div class="section"><h3>fetchmail</h3>
<p>The configuration block delimited by the <strong>fetchmail</strong> tag
controls fetchmail.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>enabled</strong></dt>
+<dl>
+<dt><strong>enabled</strong></dt>
<dd>A boolean. If "true", the fetch tasks will be run periodically. If "false",
no fetch tasks will be run. The default is "false".</dd>
</dl>
</p>
+
<p>The tag has these child tags (minimum cardinality, maximum cardinality):
-<ul><li><strong><a href="#fetch">fetch</a></strong> (0, *)</li>
+<ul>
+<li><strong><a href="#fetch">fetch</a></strong> (0, *)</li>
</ul>
-</p>
-<p><div class="source"><pre>
+
+
+<p>
+<div class="source"><pre>
<fetchmail enabled="true">
...
</fetchmail>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="fetch"></a>fetch</h3>
+
+<a name="fetch"></a><div class="section"><h3>fetch</h3>
<p>The <strong>fetch</strong> tag defines a fetch task to be run
periodically. Fetch tasks run concurrently.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>name</strong></dt>
+<dl>
+<dt><strong>name</strong></dt>
<dd>A string uniquely identifying the fetch task.</dd>
</dl>
</p>
+
<p>The tag has these child tags (minimum cardinality, maximum cardinality):
-<ul><li><strong><a href="#accounts">accounts</a></strong> (1, 1)</li>
+<ul>
+<li><strong><a href="#accounts">accounts</a></strong> (1, 1)</li>
<li><strong><a href="#blacklist">blacklist</a></strong> (1, 1)</li>
<li><strong><a href="#defaultdomain">defaultdomain</a></strong> (0, 1)</li>
<li><strong><a href="#fetchall">fetchall</a></strong> (1, 1)</li>
@@ -433,38 +463,47 @@
<li><strong><a href="#undeliverable">undeliverable</a></strong> (1, 1)</li>
<li><strong><a href="#userundefined">userundefined</a></strong> (1, 1)</li>
</ul>
-</p>
-<p><div class="source"><pre>
+
+
+
+<div class="source"><pre>
<fetch name="mydomain.com">
...
</fetch>
-</pre>
-</div>
-</p>
+</pre></div>
+
</div>
-<div class="section"><h3><a name="accounts"></a>accounts</h3>
-<p>The <strong>accounts</strong> tag declares the accounts from which mail will
-be fetched by the fetch task. Accounts run concurrently.</p>
-<p>The tag has these child tags (minimum cardinality, maximum cardinality):
-<ul><li><strong><a href="#account">account</a></strong> (0, *)</li>
+
+<a name="accounts"></a><div class="section"><h3>accounts</h3>
+The <strong>accounts</strong> tag declares the accounts from which mail will
+be fetched by the fetch task. Accounts run concurrently.
+
+The tag has these child tags (minimum cardinality, maximum cardinality):
+<ul>
+<li><strong><a href="#account">account</a></strong> (0, *)</li>
<li><strong><a href="#alllocal">alllocal</a></strong> (0, 1)</li>
</ul>
-</p>
-<p><div class="source"><pre>
+
+
+
+<div class="source"><pre>
<accounts>
...
</accounts>
-</pre>
-</div>
-</p>
+</pre></div>
+
</div>
-<div class="section"><h3><a name="blacklist"></a>blacklist</h3>
-<p>The <strong>blacklist</strong> tag declares a list of recipient addresses
-for whom mail will be rejected and what happens to the rejected mail.</p>
-<p>The tag value is a tab, comma or space delimited list of recipient
-addresses, eg: <code>wibble@mydomain.com, flobble@mydomain.com</code>.</p>
-<p>The tag has these attributes:
-<dl><dt><strong>reject</strong></dt>
+
+<a name="blacklist"></a><div class="section"><h3>blacklist</h3>
+The <strong>blacklist</strong> tag declares a list of recipient addresses
+for whom mail will be rejected and what happens to the rejected mail.
+
+The tag value is a tab, comma or space delimited list of recipient
+addresses, eg: <code>wibble@mydomain.com, flobble@mydomain.com</code>.
+
+The tag has these attributes:
+<dl>
+<dt><strong>reject</strong></dt>
<dd>A boolean. If "true", mail for recipients in the blacklist will
not be injected into the James input spool. If "false", mail for
recipients in the blacklist will be injected into the James input spool with the
@@ -479,51 +518,62 @@
marked as seen on the server. If "false", mail for recipients in the blacklist
will not be marked as seen.</dd>
</dl>
-</p>
-<p><div class="source"><pre>
+
+
+
+<div class="source"><pre>
<blacklist
reject="true"
leaveonserver="true"
markseen="true">
wibble@mydomain.com, flobble@mydomain.com
</blacklist>
-</pre>
-</div>
-</p>
+</pre></div>
+
</div>
-<div class="section"><h3><a name="defaultdomain"></a>defaultdomain</h3>
-<p>The <strong>defaultdomain</strong> tag declares the domain name to be
+
+<a name="defaultdomain"></a><div class="section"><h3>defaultdomain</h3>
+The <strong>defaultdomain</strong> tag declares the domain name to be
appended to the <code>From:</code> header of a mail that has a valid user part
-but is missing the domain part.</p>
-<p>If not specified, the default behaviour is to append the canonical host name
-of the James server.</p>
-<p>The tag value is the name of the server to append. The name must be a server
+but is missing the domain part.
+
+If not specified, the default behaviour is to append the canonical host name
+of the James server.
+
+The tag value is the name of the server to append. The name must be a server
declared in the <strong>servernames</strong> tag of the <strong>James</strong>
-block in the configuration or the name <code>localhost</code>.</p>
-<p><div class="source"><pre>
+block in the configuration or the name <code>localhost</code>.
+
+
+<div class="source"><pre>
<defaultdomain>
mydomain.com
</defaultdomain>
-</pre>
-</div>
-</p>
+</pre></div>
+
</div>
-<div class="section"><h3><a name="fetchall"></a>fetchall</h3>
-<p>The <strong>fetchall</strong> tag declares if all mail should be fetched from
-the server, or just unseen mail.</p>
-<p>The tag value is a boolean. If true, all mail is fetched. If false, only
-unseen mail is fetched.</p>
-<p><div class="source"><pre>
+
+<a name="fetchall"></a><div class="section"><h3>fetchall</h3>
+The <strong>fetchall</strong> tag declares if all mail should be fetched from
+the server, or just unseen mail.
+
+The tag value is a boolean. If true, all mail is fetched. If false, only
+unseen mail is fetched.
+
+
+<div class="source"><pre>
<fetchall>false</fetchall>
-</pre>
-</div>
-</p>
+</pre></div>
+
</div>
-<div class="section"><h3><a name="fetched"></a>fetched</h3>
-<p>The <strong>fetched</strong> tag declares what will happen to mail on the
-external server that is successfully injected into the James input spool.</p>
-<p>The tag has these attributes:
-<dl><dt><strong>leaveonserver</strong></dt>
+
+<a name="fetched"></a><div class="section"><h3>fetched</h3>
+The <strong>fetched</strong> tag declares what will happen to mail on the
+external server that is successfully injected into the James input spool.
+
+The tag has these attributes:
+<dl>
+<dt><strong>leaveonserver</strong></dt>
<dd>A boolean. If "true", mail injected into the James input spool
will be left on the server. If "false", mail injected into the James
input spool will be marked for deletion.</dd>
@@ -532,97 +582,120 @@
will be marked as seen on the server. If "false", mail injected into
the James input spool will not be marked as seen.</dd>
</dl>
-</p>
-<p><div class="source"><pre>
+
+
+
+<div class="source"><pre>
<fetched leaveonserver="true" markseen="true"/>
-</pre>
-</div>
-</p>
+</pre></div>
+
</div>
-<div class="section"><h3><a name="host"></a>host</h3>
+
+<a name="host"></a><div class="section"><h3>host</h3>
<p>The <strong>host</strong> tag declares the IP address of the external
server from which mail is fetched.</p>
+
<p>The tag value is the DNS name or IP address literal of the external
server.</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<host>pop3.server.com</host>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="interval"></a>interval</h3>
+
+<a name="interval"></a><div class="section"><h3>interval</h3>
<p>The <strong>interval</strong> tag declares the period between invocations of
the fetch tasks. If a fetch task is still active from a previous invocation
when the period expires, the new invocation is skipped over.</p>
+
<p>The tag value is an integer representing the number of milliseconds to elapse
between invocations of the fetch tasks.</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<interval>60000</interval>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="javaMailFolderName"></a>javaMailFolderName</h3>
+
+<a name="javaMailFolderName"></a><div class="section"><h3>javaMailFolderName</h3>
<p>The <strong>javaMailFolderName</strong> tag declares the name of the root
folder on the external server from which mail is fetched.</p>
+
<p>The tag value is the cAsE-sEnSiTiVe name of the root folder on the external
server from which mail is fetched. For POP3 servers this is always
<code>INBOX</code>.</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<javaMailFolderName>INBOX</javaMailFolderName>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="javaMailProperties"></a>javaMailProperties</h3>
+
+<a name="javaMailProperties"></a><div class="section"><h3>javaMailProperties</h3>
<p>The <strong>javaMailProperties</strong> tag declares the properties to be
applied to the JavaMail Session used by the fetch task. These override the
properties answered by <code>System.getProperties()</code>. Many JavaMail
properties are specific to the JavaMail Provider selected by the
<a href="#javaMailProviderName">javaMailProviderName</a> tag.</p>
+
<p><strong>Relying on the default values selected by the Provider can be
inappropriate.</strong> For instance, the default connection and I/O timeout
values of infinite for the default IMAP and POP3 Providers is rarely what is
required. Consult the documentation of the Provider for details and options.</p>
+
<p>Documentation for the default Provider for IMAP is located
-<a href="http://java.sun.com/products/javamail/javadocs/com/sun/mail/imap/package-summary.html" class="externalLink">
+<a href="http://java.sun.com/products/javamail/javadocs/com/sun/mail/imap/package-summary.html">
here</a>.</p>
+
<p>Documentation for the default Provider for POP3 is located
-<a href="http://java.sun.com/products/javamail/javadocs/com/sun/mail/pop3/package-summary.html" class="externalLink">
+<a href="http://java.sun.com/products/javamail/javadocs/com/sun/mail/pop3/package-summary.html">
here</a>.</p>
+
<p>Details of how to change a Provider are located
-<a href="http://java.sun.com/products/javamail/javadocs/javax/mail/Session.html" class="externalLink">
+<a href="http://java.sun.com/products/javamail/javadocs/javax/mail/Session.html">
here</a>.</p>
+
<p>The tag has these child tags (minimum cardinality, maximum cardinality):
-<ul><li><strong><a href="#property">property</a></strong> (0, *)</li>
+<ul>
+<li><strong><a href="#property">property</a></strong> (0, *)</li>
</ul>
-</p>
-<p><div class="source"><pre>
+
+
+<p>
+<div class="source"><pre>
<javaMailProperties>
...
</javaMailProperties>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="javaMailProviderName"></a>javaMailProviderName</h3>
+
+<a name="javaMailProviderName"></a><div class="section"><h3>javaMailProviderName</h3>
<p>The <strong>javaMailProviderName</strong> tag selects the JavaMail protocol
Provider used to interact with the external server.</p>
+
<p>The tag value is the name of a JavaMail supported protocol, such as
<code>pop3</code> or <code>imap</code>. The name is used to select the default
Provider for the protocol.</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<javaMailProviderName>pop3</javaMailProviderName>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="maxmessagesize"></a>maxmessagesize</h3>
+
+<a name="maxmessagesize"></a><div class="section"><h3>maxmessagesize</h3>
<p>The <strong>maxmessagesize</strong> tag declares the maximum permitted message
size for messages injected into the James input spool and what happens to fetched
messages that exceed this size.</p>
<p>The tag has these attributes:
-<dl><dt><strong>limit</strong></dt>
+<dl>
+<dt><strong>limit</strong></dt>
<dd>An integer. The maximum message size expressed in Kilobytes. If 0, there is
no limit.</dd>
<dt><strong>reject</strong></dt>
@@ -643,30 +716,36 @@
seen.</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<maxmessagesize
limit="4096"
reject="false"
leaveonserver="false"
markseen="false"/>
-</pre>
-</div>
+</pre></div>
</p>
+
<p>An example configuration using James mailet processing to bounce fetched
messages that exceed the maximum permitted size can be found in the file
<code>$PHOENIX_HOME/apps/james/conf/samples/fetchmail/maxMessageSize.xml</code>.
</p>
</div>
-<div class="section"><h3><a name="recipientnotfound"></a>recipientnotfound</h3>
+
+<a name="recipientnotfound"></a><div class="section"><h3>recipientnotfound</h3>
<p>The <strong>recipientnotfound</strong> tag declares what happens to mail for
which a sole intended recipient cannot be found when attempting to determine
the recipient from the mail headers.</p>
+
<p>In configurations with more than one account per fetch task, processing of
matched mail can be deferred to the next run of the fetch task. This gives
other accounts that may be able to determine a sole intended recipient an
opportunity to do so before recipientnotfound processing is invoked.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>defer</strong></dt>
+<dl>
+<dt><strong>defer</strong></dt>
<dd>A boolean. If "true", mail for which a sole intended recipient
cannot be determined is left unprocessed until the next run of the fetch task.
If "false", mail for which a sole intended recipient cannot be
@@ -691,43 +770,51 @@
as seen.</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<recipientnotfound
defer="true"
reject="true"
leaveonserver="true"
markseen="true"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="recursesubfolders"></a>recursesubfolders</h3>
+
+<a name="recursesubfolders"></a><div class="section"><h3>recursesubfolders</h3>
<p>The <strong>recursesubfolders</strong> tag declares if mail should be fetched
from sub-folders of the root folder, or just the root folder.</p>
+
<p>The tag value is a boolean. If true, mail is fetched from the root folder and
its subfolders. If false, mail is fetched from just the root folder.</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<recursesubfolders>false</recursesubfolders>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="remoteReceivedHeader"></a>remoteReceivedHeader</h3>
+
+<a name="remoteReceivedHeader"></a><div class="section"><h3>remoteReceivedHeader</h3>
<p>The <strong>remoteReceivedHeader</strong> tag declares the zero based
index of the RFC2822 compliant RECEIVED header used to determine the address and
host name of the remote MTA that sent a fetched message and what happens to
messages when the specified header is invalid.</p>
+
<p>Typically, the first (index = 0) RECEIVED header is for the local MTA that
delivered the message to the message store and the second (index = 1) RECEIVED
header is for the remote MTA that delivered the message to the local MTA. When
this configuration applies, the <strong>remoteReceivedHeaderIndex</strong> should
be set to <strong>1</strong>.
</p>
+
<p>To verify the correct setting, examine the RECEIVED headers for messages
delivered to the configured message store and locate the first one containing a
remote domain in the'from' field. Remembering that zero based indexing is used,
if this the second header, use an index of 1, if this is the third header, use an
index of 2, and so forth.</p>
+
<p>Matchers such as InSpammerBlacklist use the remote address and/or remote host
name to identify illegitimate remote MTAs. If you do not use such matchers, the
<strong>remoteReceivedHeaderIndex</strong> tag may be omitted or the default
@@ -735,8 +822,10 @@
<code>127.0.0.1</code> and the remote host name to be set to
<code>localhost</code>. Matchers almost always considered these values to be
legitimate.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>index</strong></dt>
+<dl>
+<dt><strong>index</strong></dt>
<dd>An integer whose meaning is described above.
</dd>
<dt><strong>reject</strong></dt>
@@ -757,27 +846,32 @@
recieved header is invalid will not be marked as seen.</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<remoteReceivedHeader
index="1"
reject="true"
leaveonserver="true"
markseen="true"/>
-</pre>
-</div>
+</pre></div>
</p>
+
<p>An example configuration using James mailet processing to notify the postmaster
of fetched messages that contain an invalid Received header can be found in the file
<code>$PHOENIX_HOME/apps/james/conf/samples/fetchmail/remoteReceivedHeader.xml</code>.
</p>
</div>
-<div class="section"><h3><a name="remoterecipient"></a>remoterecipient</h3>
+
+<a name="remoterecipient"></a><div class="section"><h3>remoterecipient</h3>
<p>The <strong>remoterecipient</strong> tag declares what happens to mail for
which the domain part of the recipient is remote. A domain is remote if it is
not a server declared in the <strong>servernames</strong> tag of the
<strong>James</strong> block in the configuration.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>reject</strong></dt>
+<dl>
+<dt><strong>reject</strong></dt>
<dd>A boolean. If "true", mail for remote recipients will not be
injected into the James input spool. If "false", mail for remote
recipients will be injected into the James input spool with the Mail Attribute
@@ -793,20 +887,24 @@
marked as seen.</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<remoterecipient
reject="true"
leaveonserver="true"
markseen="true"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="undeliverable"></a>undeliverable</h3>
+
+<a name="undeliverable"></a><div class="section"><h3>undeliverable</h3>
<p>The <strong>undeliverable</strong> tag declares what happens to mail that
cannot be delivered.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>leaveonserver</strong></dt>
+<dl>
+<dt><strong>leaveonserver</strong></dt>
<dd>A boolean. If "true", mail that cannot be delivered will be left
on the server. If "false", mail that cannot be delivered will be
marked for deletion.</dd>
@@ -816,19 +914,23 @@
delivered will not be marked as seen.</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<undeliverable
leaveonserver="true"
markseen="true"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="userundefined"></a>userundefined</h3>
+
+<a name="userundefined"></a><div class="section"><h3>userundefined</h3>
<p>The <strong>userundefined</strong> tag declares what happens to mail for
which the recipient is not defined as a James user.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>reject</strong></dt>
+<dl>
+<dt><strong>reject</strong></dt>
<dd>A boolean. If "true", mail for recipients who are not defined as
James users will not be injected into the James input spool. If
"false", mail for recipients who are not defined as James users will
@@ -846,20 +948,24 @@
</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<userundefined
reject="true"
leaveonserver="true"
markseen="true"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="account"></a>account</h3>
+
+<a name="account"></a><div class="section"><h3>account</h3>
<p>The <strong>account</strong> tag declares an account on the external server
from which mail should be fetched.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>user</strong></dt>
+<dl>
+<dt><strong>user</strong></dt>
<dd>The string to be passed as the user when connecting to the external server.
</dd>
<dt><strong>password</strong></dt>
@@ -876,23 +982,27 @@
</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<account
user="myaccount"
password="mypassword"
recipient="user@localhost"
ignorercpt-header="true"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="alllocal"></a>alllocal</h3>
+
+<a name="alllocal"></a><div class="section"><h3>alllocal</h3>
<p>The <strong>alllocal</strong> tag declares the parameters to be applied to
dynamic accounts. The set of dynamic accounts is refreshed each time the fetch
task runs by combining the <strong>alllocal</strong> tag attributes with each of
the currently defined James users to create an account for every James user.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>userprefix</strong></dt>
+<dl>
+<dt><strong>userprefix</strong></dt>
<dd>The string to be added before the James user when constructing the string
passed as the user when connecting to the external server.
</dd>
@@ -920,7 +1030,9 @@
</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<alllocal
userprefix=""
usersuffix="@external.domain.com"
@@ -928,38 +1040,46 @@
recipientprefix=""
recipientsuffix="@mydomain.com"
ignorercpt-header="true"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="property"></a>property</h3>
+
+<a name="property"></a><div class="section"><h3>property</h3>
<p>The <strong>property</strong> tag declares a name/value pair.</p>
+
<p>The tag has these attributes:
-<dl><dt><strong>name</strong></dt>
+<dl>
+<dt><strong>name</strong></dt>
<dd>The name of the property.
</dd>
<dt><strong>value</strong></dt>
<dd>The value of the property.</dd>
</dl>
</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<property
name="mail.pop3.connectiontimeout"
value="180000"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
+
</div>
-<div class="section"><h2><a name="fetchmail_Examples"></a>fetchmail Examples</h2>
+
+<a name="fetchmail Examples"></a><div class="section"><h2>fetchmail Examples</h2>
<p>Full sources to the examples discussed below can be found in the directory
<code>$PHOENIX_HOME/apps/james/conf/samples/fetchmail</code>.</p>
-<div class="section"><h3><a name="One_Account_One_User"></a>One Account, One User</h3>
+
+<a name="One Account, One User"></a><div class="section"><h3>One Account, One User</h3>
<p>When all mail for an account is to be delivered to a single user,
configure each account to ignore the recipient in the mail headers and deliver
to the specified recipient. The <strong>accounts</strong> block looks like
this:</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<accounts>
<account
user="user1@external.domain.com"
@@ -979,15 +1099,17 @@
recipient="user3@localhost"
ignorercpt-header="true"/>
</accounts>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="One_Account_Many_Users"></a>One Account, Many Users</h3>
+
+<a name="One Account, Many Users"></a><div class="section"><h3>One Account, Many Users</h3>
<p>When an account contains mail to be delivered to many users, configure each
account to determine the recipient from the mail headers and deliver to that
user. The <strong>accounts</strong> block looks like this:</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<accounts>
<account
user="global@external.domain.com"
@@ -995,37 +1117,43 @@
recipient="fetchmail@localhost"
ignorercpt-header="false"/>
</accounts>
-</pre>
-</div>
+</pre></div>
</p>
+
<p>The <strong>recipientnotfound</strong> tag is used to declare what happens
when the recipient cannot be determined from the mail headers. In the example
below, mail is injected into the spool using the recipient declared in the
<strong>account</strong> tag:</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<recipientnotfound
defer="false"
reject="false"
leaveonserver="false"
markseen="false"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="One_Account_One_User_-_Dynamic"></a>One Account, One User - Dynamic</h3>
+
+<a name="One Account, One User - Dynamic"></a><div class="section"><h3>One Account, One User - Dynamic</h3>
<p>When an external server supports virtual mailboxes, fetchmail's dynamic
account facility can be used. This greatly simplifies user configuration as
the fetchmail accounts for users are automatically synchronized with those
defined in the James user repository. This guarantees that mail for all local
users will be fetched and delivered.</p>
+
<p>Currently, there is a limitation that all virtual accounts and the global
account must share the same password.</p>
+
<p>The <strong>alllocal</strong> tag declares the parameters for the dynamic
accounts. The <strong>accounts</strong> block below will deliver mail for
<code>user1@external.domain.com</code> to <code>user1@localhost</code>,
<code>user2@external.domain.com</code> to <code>user2@localhost</code>,
<code>userZ@external.domain.com</code> to <code>userZ@localhost</code> etc.:</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<accounts>
<alllocal
userprefix=""
@@ -1035,11 +1163,11 @@
recipientsuffix="@localhost"
ignorercpt-header="true"/>
</accounts>
-</pre>
-</div>
+</pre></div>
</p>
</div>
-<div class="section"><h3><a name="One_Account_Many_Users_-_Dynamic"></a>One Account, Many Users - Dynamic</h3>
+
+<a name="One Account, Many Users - Dynamic"></a><div class="section"><h3>One Account, Many Users - Dynamic</h3>
<p>The
<a href="#One Account, One User - Dynamic">One Account, One User - Dynamic</a>
example guarantees delivery of mail for all local users, but leaves other mail
@@ -1048,9 +1176,11 @@
processes all mail on the external server, but cannot guarantee delivery to the
intended recipient. By combining the two, it is possible to guarantee the
delivery of mail for all local users and process all mail.</p>
+
<p>In the snippet below, the <strong>alllocal</strong> tag declares dynamic
accounts for all local users and the <strong>account</strong> tag configures an
account to fetch all mail.</p>
+
<p>The <strong>recipientnotfound</strong> tag rejects mail for which a recipient
cannot be determined. By the time this processing is activated, the dynamic
accounts will have processed mail for all local users, so the mail can
@@ -1059,11 +1189,14 @@
dealt with by the dynamic accounts. The next time the dynamic accounts run any
newly arrived mail for local users will be processed. The remainder will be for
non-local users and can now be safely dealt with.</p>
+
<p>The <code><recipientnotfound defer="true"</code> attribute
enables deferal of the processing of messages for which the recipient cannot be
determined to the next iteration of the fetch task, and is used here. The
relevant tags are:</p>
-<p><div class="source"><pre>
+
+<p>
+<div class="source"><pre>
<accounts>
<alllocal
userprefix=""
@@ -1085,24 +1218,28 @@
reject="true"
leaveonserver="true"
markseen="true"/>
-</pre>
-</div>
+</pre></div>
</p>
</div>
+
</div>
-<div class="section"><h2><a name="fetchmail_Caveats"></a>fetchmail Caveats</h2>
+
+<a name="fetchmail Caveats"></a><div class="section"><h2>fetchmail Caveats</h2>
<p>These are some things to be aware of when using fetchmail:
-<ul><li>As noted in the
+<ul>
+<li>As noted in the
<a href="#One Account, One User - Dynamic">One Account, One User - Dynamic</a>
example, all virtual accounts and the global account must share the same
password. A future version might associate each James user to a set of account
credentials.
</li>
+
<li>When using dynamic accounts, an account is generated and an attempt made to
fetch mail for all James users defined to James even if there is no such mailbox
on the server. This is inefficient but not fatal. The solution is the same as
described above.
</li>
+
<li>When using dynamic accounts, as described in the
<a href="#One Account, Many Users - Dynamic">One Account, Many Users - Dynamic</a>
example, the user name used to fetch the mail for all accounts must not be
@@ -1110,6 +1247,7 @@
and fetch all the mail before the account declared to process mail for all users
has an opportunity to run!
</li>
+
<li>The now deprecated fetchPOP interacted with the <code>FetchedFrom</code>
matcher to detect mail injected by fetchPOP. This will not work with fetchmail.
Compared to fetchPOP, there are far fewer occasions when mail injected by
@@ -1121,6 +1259,7 @@
attribute value. The attribute value is the name of the fetch task that
injected the mail.
</li>
+
<li>The POP3 protocol does not enforce support of any of the Flags associated
with messages other than DELETED. This means that
<code>markseen="true"</code> will most likely have no effect and
@@ -1128,12 +1267,18 @@
situation, the only way to avoid repeatedly fetching the same mail is to delete
it from the server using <code>leaveonserver="false"/></code>.
</li>
+
<li>If using a Exchange 2000 or Exchange 2003 server get sure you fix the CLRF bug.
-See <a href="http://support.microsoft.com/kb/816896/en-us" class="externalLink"> Bug description and fix</a></li>
+See <a href="http://support.microsoft.com/kb/816896/en-us"> Bug description and fix</a>
+</li>
</ul>
-</p>
+
</div>
+
+
+
+
</div>
</div>
<div class="clear">
Modified: james/site/trunk/www/server/2.3.2/index.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/index.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/index.html (original)
+++ james/site/trunk/www/server/2.3.2/index.html Mon Aug 3 17:36:07 2009
@@ -11,7 +11,8 @@
<html>
<head>
- <title>James Server - James 2.3 - Table of Contents</title>
+ <title>James Server -
+ James 2.3 - Table of Contents</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@@ -22,7 +23,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -45,21 +46,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -303,11 +304,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -328,7 +329,12 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2><a name="James_2.3"></a>James 2.3</h2>
+
+
+
+
+
+<a name="James 2.3"></a><div class="section"><h2>James 2.3</h2>
<p>
The Java Apache Mail Enterprise Server (a.k.a. Apache James) is a 100% pure Java SMTP and POP3 Mail
server and NNTP News server designed to be a complete and portable enterprise mail engine
@@ -341,35 +347,36 @@
strengths, and can allow administrators to produce powerful applications surprisingly easily.
</p>
<p>
-James is built on top of trunk version of the <a href="http://avalon.apache.org/" class="externalLink">Avalon Application Framework</a>. This
+James is built on top of trunk version of the <a href="http://avalon.apache.org/">Avalon Application Framework</a>. This
framework encourages a set of good development practices such as Component Oriented Programming and
Inversion of Control. The standard distribution of James includes
-<a href="http://avalon.apache.org/phoenix" class="externalLink">Phoenix Avalon Framework container</a>. This stable
+<a href="http://avalon.apache.org/phoenix">Phoenix Avalon Framework container</a>. This stable
and robust container provides a strong foundation for the James server.
</p>
<p>
This documentation is intended to be an introduction to the concepts behind the James implementation, as well
as a guide to installing, configuring, (and for developers) building the James server.
</p>
-<div class="section"><h3><a name="Table_of_Contents"></a>Table of Contents</h3>
+<a name="Table of Contents"></a><div class="section"><h3>Table of Contents</h3>
<p>
I. James Concepts
-<ul><li><a href="summary.html">Summary</a></li>
+<ul>
+<li><a href="summary.html">Summary</a></li>
<li><a href="spoolmanager.html">SpoolManager</a></li>
<li><a href="repositories.html">Repositories</a></li>
<li><a href="mailet_api.html">The Mailet API</a></li>
</ul>
-
II. How To Build James
-<ul><li><a href="build_instructions.html">Building James</a></li>
+<ul>
+<li><a href="build_instructions.html">Building James</a></li>
</ul>
-
III. How To Install James
-<ul><li><a href="installation_instructions.html">Installing James</a></li>
+<ul>
+<li><a href="installation_instructions.html">Installing James</a></li>
</ul>
-
IV. Configuring James
-<ul><li><a href="dns_configuration.html">DNS Server Configuration</a></li>
+<ul>
+<li><a href="dns_configuration.html">DNS Server Configuration</a></li>
<li><a href="pop3_configuration.html">POP3 Server Configuration</a></li>
<li><a href="smtp_configuration.html">SMTP Server Configuration</a></li>
<li><a href="nntp_configuration.html">NNTP Server Configuration</a></li>
@@ -382,26 +389,27 @@
<li><a href="provided_matchers.html">Provided Matchers</a></li>
<li><a href="provided_mailets.html">Provided Mailets</a></li>
</ul>
-
V. Common Configurations
-<ul><li><a href="smtp_auth.html">Using SMTP AUTH</a></li>
+<ul>
+<li><a href="smtp_auth.html">Using SMTP AUTH</a></li>
<li><a href="using_database.html">Using a Database with James</a></li>
<li><a href="usingTLS.html">Using TLS/SSL</a></li>
<li><a href="mailing_lists.html">Creating Mailing Lists</a></li>
</ul>
-
VI. Customizing James
-<ul><li><a href="custom_matcher.html">How to write a custom Matcher</a></li>
+<ul>
+<li><a href="custom_matcher.html">How to write a custom Matcher</a></li>
<li><a href="custom_mailet.html">How to write a custom Mailet</a></li>
</ul>
-
V. Other Information
-<ul><li><a href="upgrade_instructions.html">Upgrade James</a></li>
+<ul>
+<li><a href="upgrade_instructions.html">Upgrade James</a></li>
</ul>
-</p>
+
</div>
</div>
+
</div>
</div>
<div class="clear">
Modified: james/site/trunk/www/server/2.3.2/install.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/install.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/install.html (original)
+++ james/site/trunk/www/server/2.3.2/install.html Mon Aug 3 17:36:07 2009
@@ -11,19 +11,21 @@
<html>
<head>
- <title>James Server - Installation</title>
+ <title>James Server -
+ Installation</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="author" content="Serge Knystautas" />
+ <meta name="author" content="
+Serge Knystautas" />
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -46,21 +48,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -304,11 +306,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -329,10 +331,13 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2><a name="Step_0:_Building._only_necessary_for_daily_snapshots"></a>Step 0: Building. (only necessary for daily snapshots)</h2>
+
+
+
+<a name="Step 0: Building. (only necessary for daily snapshots)"></a><div class="section"><h2>Step 0: Building. (only necessary for daily snapshots)</h2>
<p> If you have downloaded a binary distribution, you do not need to build James.
Proceed directory to Step 1. </p>
-<p> To compile James from the source code you need <a href="http://ant.apache.org/" class="externalLink">Ant</a>.
+<p> To compile James from the source code you need <a href="http://ant.apache.org/">Ant</a>.
This is a Java-tailored, XML-configured, extensible build or make system. We
are currently using Ant 1.4, which is included in the source distribution.</p>
<p> If you have downloaded a daily snapshot, you need to build a distribution.
@@ -347,34 +352,37 @@
(or "./build.sh dist"). This will create the distribution in the "./dist"
directory as well as create .tgz and .zip copies of this directory, however it may
require other resources to build the documentation. </p>
-<p><strong>Warning!</strong> Any changes you've made in the 'dist' directory
+<p> <strong>Warning!</strong> Any changes you've made in the 'dist' directory
will be lost after a recompilation. If you are making changes to the conf.xml
or other files, we recommend you backup and then change the copies in src to
avoid losing work. </p>
-</div>
-<div class="section"><h2><a name="Step_1:_Installation."></a>Step 1: Installation.</h2>
+</div> <a name="Step 1: Installation."></a><div class="section"><h2>Step 1: Installation.</h2>
<p> Download distibution. Extract or copy all the files in the archive or dist
directory intto your installation directory. </p>
</div>
-<div class="section"><h2><a name="Step_2:_Configuration."></a>Step 2: Configuration.</h2>
-<p>
+
+<a name="Step 2: Configuration."></a><div class="section"><h2>Step 2: Configuration.</h2>
+ <p>
Read the short and snappy documentation at docs/index.html for a proper
overview of configuring the system.
</p>
-<p><b>Summary</b> (for impatient people)
+ <p>
+ <b>Summary</b> (for impatient people)
</p>
+
<p> M$ users should just run /bin/run.bat. Unix users will find run.sh under the
same directory. A JVM must be present and its location specified in the JAVA_HOME
environment variable. Set this on windows at the command prompt with something
similar to "set JAVA_HOME=\jdk1.3\bin" on *nix with JAVA_HOME=/jdk1.3/</p>
<p> Running [run* --help] will provide a simple command line help. </p>
-<p>
+ <p>
Most UNIX systems require superuser privileges to open sockets below 1024,
which includes the IANA-standard SMTP (on port 25) and POP3 (on port 110).
These default ports can be changed in the conf.xml file. (Obviously, you
would then need to reconfigure your clients. This may not be an option if
you want to receive mail from external mailservers.)
</p>
+
<p> The Avalon framework will unpack the necessary configuration files you will
need to start the server. Wait until it is running, stop it again (ctrl-c), and
edit the configuration (thereafter *nix users can run the server in the background
@@ -383,8 +391,9 @@
and the IP address of a DNS server. Once you have edited the configuration files,
press 'Enter' on the terminal where Avalon is waiting. </p>
</div>
-<div class="section"><h2><a name="Step_4:_Kickstart."></a>Step 4: Kickstart.</h2>
-<p>
+
+<a name="Step 4: Kickstart."></a><div class="section"><h2>Step 4: Kickstart.</h2>
+ <p>
Once started you'll see a message saying Avalon is running. This means that
Avalon has loaded JAMES and every other needed Block (see /logs/avalon.log)
and is now waiting for a socket request.
@@ -396,7 +405,7 @@
administrator tool". It is really a basic set but should allow you to test
installation.
</p>
-<p>
+ <p>
Once you have some local users registered, try sending mail to one of them
@localhost with SMTP (port 25) (assuming you have not changed the default
server names in the conf.xml file). You'll see the mail appear under
@@ -407,11 +416,13 @@
the mailet pipe line (/conf/JAMES.conf.xml). Look at it if you want to
understand what's happening.
</p>
-<p>
+ <p>
Good luck :)
</p>
</div>
+
+
</div>
</div>
<div class="clear">
Modified: james/site/trunk/www/server/2.3.2/installation_instructions.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/installation_instructions.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/installation_instructions.html (original)
+++ james/site/trunk/www/server/2.3.2/installation_instructions.html Mon Aug 3 17:36:07 2009
@@ -11,7 +11,8 @@
<html>
<head>
- <title>James Server - James 2.3 - Installation</title>
+ <title>James Server -
+ James 2.3 - Installation</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@import url("./css/maven-theme.css");
@@ -22,7 +23,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -45,21 +46,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -303,11 +304,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -328,7 +329,11 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2><a name="Requirements"></a>Requirements</h2>
+
+
+
+
+<a name="Requirements"></a><div class="section"><h2>Requirements</h2>
<p>James requires a Java Runtime Environment of Java version 1.4 or higher installed to run the
James application. The exact JREs available depend on the platform. A JRE must be downloaded and
installed before James can run. In addition, the environment variable JAVA_HOME must be set to
@@ -342,7 +347,7 @@
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>
</div>
-<div class="section"><h2><a name="Installation_Comments"></a>Installation Comments</h2>
+<a name="Installation Comments"></a><div class="section"><h2>Installation Comments</h2>
<p>James installation involves a number of steps, each of which is described in some detail in the
following sections. But as this sequence of steps has confused some users in the past, additional
comments seem warranted.</p>
@@ -352,25 +357,26 @@
be unpacked. The server should be stopped, the configuration files edited, and the server restarted.</p>
<p>So the installation sequence is: <b>1) Start, 2) Stop, 3) Edit, 4) Restart</b>.</p>
</div>
-<div class="section"><h2><a name="Installing_the_Binary"></a>Installing the Binary</h2>
-<div class="section"><h3><a name="Installing_a_Stand-alone_James_Server"></a>Installing a Stand-alone James Server</h3>
-<p>Obtain the full James binary distribution from the <a href="http://james.apache.org/download.cgi" class="externalLink">James
+<a name="Installing the Binary"></a><div class="section"><h2>Installing the Binary</h2>
+<a name="Installing a Stand-alone James Server"></a><div class="section"><h3>Installing a Stand-alone James Server</h3>
+<p>Obtain the full James binary distribution from the <a href="http://james.apache.org/download.cgi">James
release mirrors</a>. Unpack the archive into your James installation directory. Go to the bin subdirectory of the
installation directory and run the "run" script (either run.sh or run.bat, depending on your platform). The configuration
file is now unpacked and available for editing.</p>
</div>
-<div class="section"><h3><a name="Deploying_a_James_Server_in_a_Pre-Existing_Phoenix_Container"></a>Deploying a James Server in a Pre-Existing Phoenix Container</h3>
+<a name="Deploying a James Server in a Pre-Existing Phoenix Container"></a><div class="section"><h3>Deploying a James Server in a Pre-Existing Phoenix Container</h3>
<p><strong>Warning!</strong> - James requires Phoenix version 4.0.x to run. There is a known issue with logging in Phoenix 4.0, so version
4.0.1 or higher is strongly recommended. Before attempting to deploy James in a Phoenix container, please make sure
it meets these version criteria.</p>
-<p>Deploying James in Phoenix is fairly easy. Obtain the james.sar file from the <a href="http://james.apache.org/download.cgi" class="externalLink">James
+<p>Deploying James in Phoenix is fairly easy. Obtain the james.sar file from the <a href="http://james.apache.org/download.cgi">James
release mirrors</a>. It can be found in the "Other Binaries"
area of the distribution directory. After downloading the james.sar,
simply place it in the apps subdirectory of your Phoenix installation. Restart Phoenix, and the james.sar should unpack and you
will be ready to configure your James installation.</p>
</div>
</div>
-<div class="section"><h2><a name="Initial_Configuration"></a>Initial Configuration</h2>
+
+<a name="Initial Configuration"></a><div class="section"><h2>Initial Configuration</h2>
<p>
After installing the binary, the next step is to adjust the initial configuration. The server should be stopped, and then
configuration can proceed. The most essential configuration is set in the config.xml file. This file can be
@@ -378,7 +384,8 @@
<p>The out of the box configuration makes certain assumptions and has some default values that are unlikely to
be appropriate for real-world servers. There are a few issues that should be addressed immediately upon installation:
</p>
-<ul><li>RemoteManager Administrator Account - Before the RemoteManager service can be used to add users to this server
+<ul>
+<li>RemoteManager Administrator Account - Before the RemoteManager service can be used to add users to this server
installation an administrator account must be created. More information can be found <a href="remotemanager_configuration.html">here</a>.</li>
<li>DNS Servers - James needs to have access to a DNS server for domain resolution. The out of the box
configuration assumes that there is a DNS server on localhost. In general administrators will have to change
@@ -390,20 +397,22 @@
section of the config.xml. More information can be found <a href="serverwide_configuration.html">here</a>.</li>
<li>Postmaster Address - More information can be found <a href="serverwide_configuration.html">here</a>.</li>
</ul>
-<p>In addition to adjusting these parameters, you may wish to consult the documentation for a discussion of
+In addition to adjusting these parameters, you may wish to consult the documentation for a discussion of
common configurations. A list of such configurations, as well as the steps necessary to configure them, can
-be found <a href="index.html">here</a>.</p>
+be found <a href="index.html">here</a>.
</div>
-<div class="section"><h2><a name="Starting_James_with_Your_Configuration"></a>Starting James with Your Configuration</h2>
-<p>Once you have edited the configuration file you will need to restart James so that the changes take
+<a name="Starting James with Your Configuration"></a><div class="section"><h2>Starting James with Your Configuration</h2>
+Once you have edited the configuration file you will need to restart James so that the changes take
effect. When James starts, a list of the James services and the ports on which they are listening should
be displayed on the console. Additional information about the system configuration is printed in the James log files
-upon startup.</p>
-<p>Finally, after configuration is complete, it will be necessary to create user accounts before the James server
+upon startup.
+Finally, after configuration is complete, it will be necessary to create user accounts before the James server
will be fully operational. Instructions on creating user accounts can be found
-<a href="adding_users.html">here</a>.</p>
+<a href="adding_users.html">here</a>.
</div>
+
+
</div>
</div>
<div class="clear">
Modified: james/site/trunk/www/server/2.3.2/integration.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/integration.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/integration.html (original)
+++ james/site/trunk/www/server/2.3.2/integration.html Mon Aug 3 17:36:07 2009
@@ -22,7 +22,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -45,21 +45,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -345,11 +345,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -370,24 +370,7 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Overview</h2>
-This project uses <a class="externalLink" href="http://maven.apache.org/continuum/">Continuum</a>.</div>
-<div class="section"><h2>Access</h2>
-<p>No url to the continuous integration system is defined.</p>
-</div>
-<div class="section"><h2>Notifiers</h2>
-<p>Configuration for notifying developers/users when a build is unsuccessful, including user information and notification mode.</p>
-<table class="bodyTable"><tr class="a"><th>Type</th>
-<th>Address</th>
-<th>Configuration</th>
-</tr>
-<tr class="b"><td>mail</td>
-<td><a class="externalLink" href="mailto:server-dev@james.apache.org">server-dev@james.apache.org</a></td>
-<td>-</td>
-</tr>
-</table>
-</div>
-
+ <div class="section"><h2>Overview</h2>This project uses <a href="http://maven.apache.org/continuum/">Continuum</a>.</div><div class="section"><h2>Access</h2><p>No url to the continuous integration system is defined.</p></div><div class="section"><h2>Notifiers</h2><p>Configuration for notifying developers/users when a build is unsuccessful, including user information and notification mode.</p><table class="bodyTable"><tr class="a"><th>Type</th><th>Address</th><th>Configuration</th></tr><tr class="b"><td>mail</td><td><a href="mailto:server-dev@james.apache.org">server-dev@james.apache.org</a></td><td>-</td></tr></table></div>
</div>
</div>
<div class="clear">
Modified: james/site/trunk/www/server/2.3.2/issue-tracking.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/issue-tracking.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/issue-tracking.html (original)
+++ james/site/trunk/www/server/2.3.2/issue-tracking.html Mon Aug 3 17:36:07 2009
@@ -22,7 +22,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -45,21 +45,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -345,11 +345,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -370,14 +370,7 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Overview</h2>
-This project uses <a class="externalLink" href="http://www.atlassian.com/software/jira">JIRA</a> a J2EE-based, issue tracking and project management application.</div>
-<div class="section"><h2>Issue Tracking</h2>
-<p>Issues, bugs, and feature requests should be submitted to the following issue tracking system for this project.</p>
-<div class="source"><pre><a class="externalLink" href="http://issues.apache.org/jira/browse/JAMES">http://issues.apache.org/jira/browse/JAMES</a></pre>
-</div>
-</div>
-
+ <div class="section"><h2>Overview</h2>This project uses <a href="http://www.atlassian.com/software/jira">JIRA</a> a J2EE-based, issue tracking and project management application.</div><div class="section"><h2>Issue Tracking</h2><p>Issues, bugs, and feature requests should be submitted to the following issue tracking system for this project.</p><div class="source"><pre><a href="http://issues.apache.org/jira/browse/JAMES">http://issues.apache.org/jira/browse/JAMES</a></pre></div></div>
</div>
</div>
<div class="clear">
Modified: james/site/trunk/www/server/2.3.2/jxr.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/server/2.3.2/jxr.html?rev=800474&r1=800473&r2=800474&view=diff
==============================================================================
--- james/site/trunk/www/server/2.3.2/jxr.html (original)
+++ james/site/trunk/www/server/2.3.2/jxr.html Mon Aug 3 17:36:07 2009
@@ -22,7 +22,7 @@
</head>
<body class="composite">
<div id="banner">
- <a href="../../index.html" id="bannerLeft">
+ <a href="http://james.apache.org/index.html" id="bannerLeft">
<img src="images/james-server-logo.gif" alt="" />
@@ -45,21 +45,21 @@
<div class="xleft">
- Last Published: 05/23/2009
+ Last Published: 08/03/2009
</div>
- <div class="xright"> <a href="../../index.html">JAMES Project</a>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
|
- <a href="../index.html">Server</a>
+ <a href="http://james.apache.org/server/index.html">Server</a>
|
- <a href="../../mailet/index.html">Mailet API</a>
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
|
- <a href="../../jspf/index.html">jSPF</a>
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
|
- <a href="../../mime4j/index.html">Mime4J</a>
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
|
- <a href="../../jsieve/index.html">JSieve</a>
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
|
- <a href="../../postage/index.html">Postage</a>
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
@@ -325,11 +325,11 @@
<ul>
<li class="none">
- <a href="../../download.cgi">Stable releases</a>
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
</li>
<li class="none">
- <a href="../../downloadunstable.cgi">Unstable releases</a>
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
</li>
<li class="none">
@@ -350,16 +350,7 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Cross-reference Java source code</h2>
-<p>This report includes a cross-reference of the project's sources. Each source entry is also linked with its corresponding Javadoc (if Javadoc was generated).</p>
-<div class="section"><h3>Project sources</h3>
-<p>The cross-reference project sources can be found here: <a href="xref/index.html">xref/index.html</a></p>
-</div>
-<div class="section"><h3>Test sources</h3>
-<p>The cross-reference test sources can be found here: <a href="xref-test/index.html">xref-test/index.html</a></p>
-</div>
-</div>
-
+ <div class="section"><h2>Cross-reference Java source code</h2><p>This report includes a cross-reference of the project's sources. Each source entry is also linked with its corresponding Javadoc (if Javadoc was generated).</p><div class="section"><h3>Project sources</h3><p>The cross-reference project sources can be found here: <a href="xref/index.html">xref/index.html</a></p></div><div class="section"><h3>Test sources</h3><p>The cross-reference test sources can be found here: <a href="xref-test/index.html">xref-test/index.html</a></p></div></div>
</div>
</div>
<div class="clear">