You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by se...@apache.org on 2004/05/03 05:58:08 UTC
cvs commit: james-server/tools/etc changelog.xsl checkstyle-frames.xsl
serge 2004/05/02 20:58:08
Modified: lib Tag: branch_2_1_fcs readme.xml
src/conf Tag: branch_2_1_fcs james-config.xml
src/java/org/apache/james Tag: branch_2_1_fcs James.java
src/xdocs Tag: branch_2_1_fcs announcement_2_1.xml
build_instructions_2_1.xml changelog.xml
code-standards.xml contribute.xml
documentation_2_1.xml FAQ.xml index.xml install.xml
installation_instructions_2_1.xml weare.xml
src/xdocs/stylesheets Tag: branch_2_1_fcs project.xml
tools/etc Tag: branch_2_1_fcs changelog.xsl
checkstyle-frames.xsl
Log:
Correct references that were to legacy jakarta mailing lists, websites, and subprojects. [JAMES-278]
Revision Changes Path
No revision
No revision
1.2.4.2 +3 -3 james-server/lib/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/james-server/lib/readme.xml,v
retrieving revision 1.2.4.1
retrieving revision 1.2.4.2
diff -u -r1.2.4.1 -r1.2.4.2
--- readme.xml 8 Jan 2003 06:08:25 -0000 1.2.4.1
+++ readme.xml 3 May 2004 03:58:07 -0000 1.2.4.2
@@ -17,10 +17,10 @@
<library>
<filename>ant.jar</filename>
- <url>http://jakarta.apache.org/ant/index.html</url>
+ <url>http://ant.apache.org/</url>
<version>1.1</version>
<name>Ant is a Java based build tool</name>
- <desc>In theory it is kind of like make without makes wrinkles. Ant is part of the Jakarta Project</desc>
+ <desc>In theory it is kind of like make without makes wrinkles. Ant is a top level project of the Apache Software Foundation</desc>
</library>
<library>
No revision
No revision
1.40.2.23 +3 -3 james-server/src/conf/james-config.xml
Index: james-config.xml
===================================================================
RCS file: /home/cvs/james-server/src/conf/james-config.xml,v
retrieving revision 1.40.2.22
retrieving revision 1.40.2.23
diff -u -r1.40.2.22 -r1.40.2.23
--- james-config.xml 18 Apr 2004 23:11:41 -0000 1.40.2.22
+++ james-config.xml 3 May 2004 03:58:07 -0000 1.40.2.23
@@ -5,7 +5,7 @@
<!ENTITY fetchmailConfig SYSTEM "file:../apps/james/conf/james-fetchmail.xml">
]>
-<!-- Configuration file for the Apache Jakarta James server -->
+<!-- Configuration file for the ASF James server -->
<!-- This file contains important settings that control the behaviour -->
<!-- of all of the services and repositories. -->
@@ -126,7 +126,7 @@
<!-- Fetchmail is a functionally richer replacement for FetchPOP. -->
<!-- CHECKME: FetchMail is disabled by default, and must be configured to use. -->
<!-- Edit the file referred to by fetchmailConfig to enable and configure. -->
- &fetchmailConfig;
+ &fetchmailConfig;
<!-- The James Spool Manager block -->
<!-- -->
No revision
No revision
1.35.4.16 +5 -5 james-server/src/java/org/apache/james/James.java
Index: James.java
===================================================================
RCS file: /home/cvs/james-server/src/java/org/apache/james/James.java,v
retrieving revision 1.35.4.15
retrieving revision 1.35.4.16
diff -u -r1.35.4.15 -r1.35.4.16
--- James.java 20 Mar 2004 15:55:46 -0000 1.35.4.15
+++ James.java 3 May 2004 03:58:07 -0000 1.35.4.16
@@ -564,7 +564,7 @@
*
* <p>TODO: This needs to be made a more specific ordered subtype of Collection.</p>
*
- * @param host
+ * @param host
*/
public Collection getMailServers(String host) {
DNSServer dnsServer = null;
@@ -769,7 +769,7 @@
if (enableForwarding && user.getForwarding()) {
MailAddress forwardTo = user.getForwardingDestination();
if (forwardTo == null) {
- StringBuffer errorBuffer =
+ StringBuffer errorBuffer =
new StringBuffer(128)
.append("Forwarding was enabled for ")
.append(username)
@@ -838,7 +838,7 @@
}
/**
- * Check whether the mail domain in question is to be
+ * Check whether the mail domain in question is to be
* handled by this server.
*
* @param serverName the name of the server to check
@@ -854,7 +854,7 @@
* @return the type of the server
*/
public String getServerInfo() {
- return "Apache Jakarta JAMES";
+ return "Apache JAMES";
}
/**
No revision
No revision
1.2.4.1 +19 -19 james-server/src/xdocs/announcement_2_1.xml
Index: announcement_2_1.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/announcement_2_1.xml,v
retrieving revision 1.2
retrieving revision 1.2.4.1
diff -u -r1.2 -r1.2.4.1
--- announcement_2_1.xml 13 Dec 2002 08:28:32 -0000 1.2
+++ announcement_2_1.xml 3 May 2004 03:58:07 -0000 1.2.4.1
@@ -5,35 +5,35 @@
</properties>
<body>
<section name="Release Announcement">
-<p>The Java Apache Mail Enterprise Server (a.k.a. Apache James) Project is happy to announce the release
+<p>The Java Apache Mail Enterprise Server (a.k.a. Apache James) Project is happy to announce the release
of version 2.1 of the Apache James server.</p>
-<p>James is a 100% pure Java Mail and News server designed to be a complete and portable enterprise
-mail engine solution. James supports currently available IETF protocols, including SMTP and POP3
-(NNTP is experimental in v2.1, and it and IMAP are targeted for full functionality in v3). James
-is able to store user and message data either in a file-system or a JDBC-compatible database,
+<p>James is a 100% pure Java Mail and News server designed to be a complete and portable enterprise
+mail engine solution. James supports currently available IETF protocols, including SMTP and POP3
+(NNTP is experimental in v2.1, and it and IMAP are targeted for full functionality in v3). James
+is able to store user and message data either in a file-system or a JDBC-compatible database,
allowing fast, reliable, even real-time replicated storage.</p>
-<p>James provides a powerful, flexible mail application engine through support for the Apache Mailet
-API. With its Mailet pipeline architecture, James can be used not only to provide standard e-mail
+<p>James provides a powerful, flexible mail application engine through support for the Apache Mailet
+API. With its Mailet pipeline architecture, James can be used not only to provide standard e-mail
services, but also to implement custom e-mail applications.</p>
-<p>The James mail server is deployed in production environments and has proven itself to be a robust
-and high performance mail solution. Tests indicate that version 2.1 is able to maintain a constant
+<p>The James mail server is deployed in production environments and has proven itself to be a robust
+and high performance mail solution. Tests indicate that version 2.1 is able to maintain a constant
mail throughput rate of thousands of messages/minute for continuous periods.</p>
-<p>The James Community is also happy to announce the beginning of the design phase for James version
-3.0. Features tentatively slated for that version include enhancements to nearly every area of
-functionality, including full IMAP support, improved mailing list capabilities, and the next revision
-of the Mailet API. This is expected to be an exciting time in James development. We are actively
-looking for eager, capable developers to contribute to James. If you're interesting in contributing
+<p>The James Community is also happy to announce the beginning of the design phase for James version
+3.0. Features tentatively slated for that version include enhancements to nearly every area of
+functionality, including full IMAP support, improved mailing list capabilities, and the next revision
+of the Mailet API. This is expected to be an exciting time in James development. We are actively
+looking for eager, capable developers to contribute to James. If you're interesting in contributing
to the James project, please subscribe to the James developer mailing list.</p>
-<p>Information about James can be found at the <a href="http://jakarta.apache.org/james">James web site</a>
-at http://jakarta.apache.org/james. Users interested in subscribing to the James
-<a href="mailto:james-user-subscribe@jakarta.apache.org">user</a> and
-<a href="mailto:james-dev-subscribe@jakarta.apache.org">developer</a> mailings lists should send emails
-to subscribe-james-user@jakarta.apache.org and subscribe-james-dev@jakarta.apache.org, respectively</p>
+<p>Information about James can be found at the <a href="http://james.apache.org/">James web site</a>
+at http://james.apache.org/. Users interested in subscribing to the James
+<a href="mailto:server-user-subscribe@james.apache.org">user</a> and
+<a href="mailto:server-dev-subscribe@james.apache.org">developer</a> mailings lists should send emails
+to server-user-subscribe@james.apache.org and server-dev-subscribe@james.apache.org, respectively</p>
</section>
</body>
</document>
1.1.4.1 +20 -20 james-server/src/xdocs/build_instructions_2_1.xml
Index: build_instructions_2_1.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/build_instructions_2_1.xml,v
retrieving revision 1.1
retrieving revision 1.1.4.1
diff -u -r1.1 -r1.1.4.1
--- build_instructions_2_1.xml 1 Dec 2002 09:55:00 -0000 1.1
+++ build_instructions_2_1.xml 3 May 2004 03:58:07 -0000 1.1.4.1
@@ -6,38 +6,38 @@
<title>James 2.1 - Building James</title>
</properties>
<body>
-<p>This step is not necessary to use the standard out of the box version of James. A
-pre-built binary version of James is available from the James download directory. But
-if you wish to customize the James source code, it will be necessary for you to build the
+<p>This step is not necessary to use the standard out of the box version of James. A
+pre-built binary version of James is available from the James download directory. But
+if you wish to customize the James source code, it will be necessary for you to build the
distribution yourself.
</p>
<section name="Getting the Source Code">
<p>There are two ways to get the James source code.</p>
-<p>1. Download the source distribution - the source is available from the
-<a href="http://jakarta.apache.org/builds/jakarta-james/latest/">James download directory</a>.
-Simply choose the version of James you'd like to download, navigate into the src subdirectory
+<p>1. Download the source distribution - the source is available from the
+<a href="http://james.apache.org/download.cgi">James download directory</a>.
+Simply choose the version of James you'd like to download, navigate into the src subdirectory
for that version, and pick the source distribution appropriate for your platform.
</p>
-<p>2. Get the source code using CVS - this method gives you access to the cutting edge code
-base. Instructions on how to use CVS to get the James source code (the jakarta-james distribution)
+<p>2. Get the source code using CVS - this method gives you access to the cutting edge code
+base. Instructions on how to use CVS to get the James source code (the james-server distribution)
can be found <a href="http://jakarta.apache.org/site/cvsindex.html">here</a>.
</p>
</section>
<section name="Required Tools">
<p>To run the build you need two third-party tools.</p>
-<p>1. Java Development Kit - You must have a JDK of Java version 1.3 or higher installed to build the
+<p>1. Java Development Kit - You must have a JDK of Java version 1.3 or higher installed to build the
James distribution. The exact JDKs available depend on the platform. A JDK must be downloaded and
installed before the build can run.</p>
-<p>2. Ant - This is a Java-tailored, XML-configured, extensible build or make system. The James
-source tree includes Ant v1.5. You can get the latest version of Ant
-<a href="http://jakarta.apache.org/ant">here</a>. Since Ant is currently included in the source
+<p>2. Ant - This is a Java-tailored, XML-configured, extensible build or make system. The James
+source tree includes Ant v1.5. You can get the latest version of Ant
+<a href="http://ant.apache.org/">here</a>. Since Ant is currently included in the source
distribution, it is not necessary to download it separately.</p>
</section>
<section name="Building the Distribution">
-<p>In the top level directory of the source distribution James includes two helper scripts for running
-the build. The script build.bat should be used on Windows systems, while build.sh is appropriate for
+<p>In the top level directory of the source distribution James includes two helper scripts for running
+the build. The script build.bat should be used on Windows systems, while build.sh is appropriate for
Unix systems. Each script takes an optional set of arguments that tell the script exactly what to build. </p>
-<p>To use these scripts, simple set the environment variable JAVA_HOME to the base directory of the
+<p>To use these scripts, simple set the environment variable JAVA_HOME to the base directory of the
JDK. Then run the build script, optionally with any of the following command line arguments:
<ul>
<li>clean - deletes the build directory, making the system ready for a clean build.</li>
@@ -50,12 +50,12 @@
<li>xdocs - creates the documentaion for James.</li>
</ul>
</p>
-<p>All build products are output in the dist subdirectory of the James source distribution directory. There
-is also a build subdirectory of the James source distribution directory that is created during the build process. Both
+<p>All build products are output in the dist subdirectory of the James source distribution directory. There
+is also a build subdirectory of the James source distribution directory that is created during the build process. Both
of these directories will be deleted if you run build with the clean argument.</p>
-<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 config.xml
-or other files, we recommend you backup and then change the copies in src to
+<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 config.xml
+or other files, we recommend you backup and then change the copies in src to
avoid losing work. </p>
</section>
1.11.4.14 +2 -2 james-server/src/xdocs/changelog.xml
Index: changelog.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/changelog.xml,v
retrieving revision 1.11.4.13
retrieving revision 1.11.4.14
diff -u -r1.11.4.13 -r1.11.4.14
--- changelog.xml 24 Jun 2003 19:41:30 -0000 1.11.4.13
+++ changelog.xml 3 May 2004 03:58:07 -0000 1.11.4.14
@@ -4,7 +4,7 @@
<properties>
<title>ChangeLog</title>
- <author email="james-dev@jakarta.apache.org">James Project</author>
+ <author email="server-dev@james.apache.org">James Project</author>
</properties>
<body>
@@ -12,7 +12,7 @@
<p>This is a living document that records what was done between releases. As always, thank you to everyone who contributed code, documentation, bug reports, and feedback.
</p>
<section name="Version 2.2.0">
-<p>Expected release June 2003</p>
+<p>Expected release May 2004</p>
<li>[NjB,MT,VGP] (code) Added Quota Matcher framework and fixed storage matcher</li>
<li>[NjB] (code) Fixed LocalDelivery.LocalMimeMessage to prevent re-rendering</li>
1.3.4.1 +1 -1 james-server/src/xdocs/code-standards.xml
Index: code-standards.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/code-standards.xml,v
retrieving revision 1.3
retrieving revision 1.3.4.1
diff -u -r1.3 -r1.3.4.1
--- code-standards.xml 21 Apr 2002 01:38:26 -0000 1.3
+++ code-standards.xml 3 May 2004 03:58:08 -0000 1.3.4.1
@@ -70,7 +70,7 @@
</p>
<p>
-5. The Jakarta Apache/James License <strong>MUST</strong> be placed
+5. The Apache Software Foundation License <strong>MUST</strong> be placed
at the top of every file.
</p>
1.5.4.1 +29 -29 james-server/src/xdocs/contribute.xml
Index: contribute.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/contribute.xml,v
retrieving revision 1.5
retrieving revision 1.5.4.1
diff -u -r1.5 -r1.5.4.1
--- contribute.xml 7 Dec 2002 20:16:54 -0000 1.5
+++ contribute.xml 3 May 2004 03:58:08 -0000 1.5.4.1
@@ -8,8 +8,8 @@
<section name="Introduction">
<p>
<b>Anyone can contribute</b><br/>
- That's right, we always want to hear from people with contributions to the code,
- the documentation, the website, and bug reports.<br/>
+ That's right, we always want to hear from people with contributions to the code,
+ the documentation, the website, and bug reports.<br/>
The rest of this document outlines the way to go about these to maximum effect.<br/>
</p>
<p>
@@ -19,69 +19,69 @@
<a href="http://jakarta.apache.org/site/contributing.html">Craig R. McClanahan's advice how to get involved</a><br/>
<a href="http://jakarta.apache.org/site/guidelines.html">How Jakarta projects run</a><br/>
</p>
-
+
</section>
<section name="Code Patches">
<p>
Patches should be submitted to the developers mailing list.<br/>
<b>Always</b> use diff -u to generate patches, make sure you are patching the latest cvs (the HEAD).<br/>
- Make your patch from the jakarta-james directory and make sure it conforms
- to the code standards, otherwise it may be ignored. It is OK to make a single patch covering several
+ Make your patch from the james-server directory and make sure it conforms
+ to the code standards, otherwise it may be ignored. It is OK to make a single patch covering several
files, but please only one issue at a time.<br/>
Prefix the mail subject with [PATCH]<br/>
- Briefly outline the reason for your patch,
- the solution your patch implements, why a patch is
+ Briefly outline the reason for your patch,
+ the solution your patch implements, why a patch is
needed and why your code will solve the problem. Note any bug numbers your patch addresses.
</p>
<p>
- The reason for these is so that the commiters can easily see what you are trying to achieve,
- it is their resonsibility to manage the code and review submissions,
- if you make it easy for them to see what you are doing your patch is more likely to
+ The reason for these is so that the commiters can easily see what you are trying to achieve,
+ it is their resonsibility to manage the code and review submissions,
+ if you make it easy for them to see what you are doing your patch is more likely to
be commited quickly (or at all).<br/>
</p>
</section>
-
+
<section name="Adding New Code">
<p>
- Like the principles for patch submission, mark your mail [PATCH] and ensure
- your submission conforms to the code standards. Provide a Brief outline of
- your intentions, as above, so that your code can be reviewed easily, and a
+ Like the principles for patch submission, mark your mail [PATCH] and ensure
+ your submission conforms to the code standards. Provide a Brief outline of
+ your intentions, as above, so that your code can be reviewed easily, and a
note of any relevant bug numbers.<br/>
New files must contain a reference to the Apache licence, copy the header from an existing file.<br/>
- It also helps if you send your files in an archive (tar, zip) which preserves directories, make it from the jakarta-james directory so we can un-tar your files into the right place.
+ It also helps if you send your files in an archive (tar, zip) which preserves directories, make it from the james-server directory so we can un-tar your files into the right place.
</p>
</section>
-
+
<section name="Reporting and Fixing Bugs">
<p>
- Many improvements come as a direct result of bug
- reports, and contributed fixes, often by the same person. It is sometimes said that Apache
- projects evolve because users become so fed-up waiting for bugs to be addressed that they
+ Many improvements come as a direct result of bug
+ reports, and contributed fixes, often by the same person. It is sometimes said that Apache
+ projects evolve because users become so fed-up waiting for bugs to be addressed that they
fix them themselves. :)<br/>
- If you report a bug, <a href="http://jakarta.apache.org/site/bugs.html">here</a> we'd appreciate it if you could send a mail to the users or developers
- mailing lists, so that we can discuss it with you, bugzilla isn't a great way for mediating
+ If you report a bug, <a href="http://issues.apache.org/jira/browse/JAMES">here</a> we'd appreciate it if you could send a mail to the users or developers
+ mailing lists, so that we can discuss it with you, bugzilla isn't a great way for mediating
communication.<br/>
- If you want to fix a bug, please contribute your changes according to the guidelines above,
- in the Code Patches section. It is much simpler to deal with submissions if they all come
+ If you want to fix a bug, please contribute your changes according to the guidelines above,
+ in the Code Patches section. It is much simpler to deal with submissions if they all come
through the same channel. If you still really want to attach patches to bug submissions, please do send us a mail tagged [PATCH] too, so that we notice your patch.
</p>
</section>
-
+
<section name="Documentation">
<p>
- While we are glad to accept contributions to documentation
- from anyone, in almost any format, because its much better than none, please consider these
+ While we are glad to accept contributions to documentation
+ from anyone, in almost any format, because its much better than none, please consider these
guidelines to help us to assimilate your contribution.<br/>
- To edit an existing document try to edit the xml version in src/xdocs (check it out from cvs)
+ To edit an existing document try to edit the xml version in src/xdocs (check it out from cvs)
and if you can, submit a patch as for Code Patches.<br/>
If you want to contribute new files please try to use the simple xml format we use.<br/>
- If this means nothing to you please try to contribute HTML or plain text documents without
+ If this means nothing to you please try to contribute HTML or plain text documents without
any styling, so that we can get at the words and easily convert them into our xml format.<br/>
If all this seems like unnecessary nonsense, send us whatever you like, we'd still be
happy to receive good documentation.
</p>
</section>
-
+
</body>
</document>
1.7.4.2 +10 -10 james-server/src/xdocs/documentation_2_1.xml
Index: documentation_2_1.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/documentation_2_1.xml,v
retrieving revision 1.7.4.1
retrieving revision 1.7.4.2
diff -u -r1.7.4.1 -r1.7.4.2
--- documentation_2_1.xml 21 Sep 2003 20:03:36 -0000 1.7.4.1
+++ documentation_2_1.xml 3 May 2004 03:58:08 -0000 1.7.4.2
@@ -9,25 +9,25 @@
<body>
<section name="James 2.1">
<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
+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
solution. James is based on currently available open protocols.
</p>
<p>
-The James server also serves as a mail application platform. The James project hosts the Apache Mailet API,
-and the James server is a Mailet container. This feature makes it easy to design, write, and deploy
-custom applications for mail processing. This modularity and ease of customization is one of James'
+The James server also serves as a mail application platform. The James project hosts the Apache Mailet API,
+and the James server is a Mailet container. This feature makes it easy to design, write, and deploy
+custom applications for mail processing. This modularity and ease of customization is one of James'
strengths, and can allow administrators to produce powerful applications surprisingly easily.
</p>
<p>
-James is built on top of version 4.1.3 of the <a href="http://jakarta.apache.org/avalon">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 version 4.0.1 of the
-<a href="http://jakarta.apache.org/avalon/phoenix">Phoenix Avalon Framework container</a>. This stable
+James is built on top of version 4.1.3 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 version 4.0.1 of the
+<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
+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>
<subsection name="Table of Contents">
1.24.4.2 +1 -1 james-server/src/xdocs/FAQ.xml
Index: FAQ.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/FAQ.xml,v
retrieving revision 1.24.4.1
retrieving revision 1.24.4.2
diff -u -r1.24.4.1 -r1.24.4.2
--- FAQ.xml 6 Feb 2003 05:26:37 -0000 1.24.4.1
+++ FAQ.xml 3 May 2004 03:58:08 -0000 1.24.4.2
@@ -2,7 +2,7 @@
<document>
<properties>
<title>Frequently Asked Questions</title>
- <author email="james-dev@jakarta.apache.org">James Mail Server Project</author>
+ <author email="server-dev@james.apache.org">James Mail Server Project</author>
</properties>
<body>
<section name="This FAQ">
1.23.2.8 +11 -5 james-server/src/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/index.xml,v
retrieving revision 1.23.2.7
retrieving revision 1.23.2.8
diff -u -r1.23.2.7 -r1.23.2.8
--- index.xml 4 Jun 2003 23:00:18 -0000 1.23.2.7
+++ index.xml 3 May 2004 03:58:08 -0000 1.23.2.8
@@ -4,7 +4,7 @@
<properties>
<title>Overview</title>
- <author email="james-dev@jakarta.apache.org">James Project</author>
+ <author email="server-dev@james.apache.org">James Project</author>
</properties>
<body>
@@ -16,21 +16,21 @@
</section>
<section name="news">
<p><b>James v2.1.3</b><br/><a href="#releases">James v2.1.3</a> is released.</p>
-<p><b>James Comes Of Age</b><br/>We're proud to announce that Jakarta James has been promoted from being a Jakarta sub-project to Apache James, a top-level project of the Apache Software Foundation (ASF). James now has its own Project Management Committee, and reports directly to the <a href="http://www.apache.org/foundation">ASF</a>.</p>
+<p><b>James Comes Of Age</b><br/>We're proud to announce that James has been promoted from being a Jakarta sub-project to Apache James, a top-level project of the Apache Software Foundation (ASF). James now has its own Project Management Committee, and reports directly to the <a href="http://www.apache.org/foundation">ASF</a>.</p>
<p>We also have a brand new domain name: <b>http://james.apache.org</b> and are in the process of moving our infrastructure over to the new domain, so please forgive any confusion that might occur.</p>
<p><i>At this time we would especially appreciate hearing about broken links or out of date references on this site.</i></p>
</section>
<section name="releases">
<p><b>Latest and Stable: James v2.1.3</b><br/>
James v2.1.3 is the current release, and the latest in the <A HREF="announcement_2_1.html">James v2.1 series</A>.
-Both <a href="http://jakarta.apache.org/site/binindex.cgi">binary</a> and <a href="http://jakarta.apache.org/site/sourceindex.cgi">source</a> distributions are available.</p>
+Both <a href="http://james.apache.org/download.cgi">binary</a> and <a href="http://james.apache.org/download.cgi">source</a> distributions are available.</p>
<p>James v2.1.3 fixes several important defects, and contains functional improvements.
See the <a href="changelog.html">Change Log</a> for a detailed list of changes. <b>All
users are urged to upgrade to v2.1.3 as soon as possible</b>.</p>
<p>Any bugs found in James are dealt with promptly. Please provide feedback on the james-user and james-dev mailing lists.</p>
-<p><b>Get your hands on the latest versions..</b><br/>We put significant milestones, and potential release candidates in the <a href="http://jakarta.apache.org/builds/jakarta-james/latest">download area.</a><br/>Whilst the quality of these versions cannot be guaranteed they may contain important bug fixes and cool new features.<br/></p>
+<p><b>Get your hands on the latest versions..</b><br/>We put significant milestones, and potential release candidates in the <a href="http://cvs.apache.org/builds/james-server/test-build/">download area.</a><br/>Whilst the quality of these versions cannot be guaranteed they may contain important bug fixes and cool new features.<br/></p>
</section>
<section name="Feature Status">
@@ -109,9 +109,15 @@
</tr>
<tr>
<td>FetchPOP</td>
- <td>Experimental</td>
+ <td>Deprecated</td>
<td>2.1</td>
<td>2.1</td>
+ </tr>
+ <tr>
+ <td>FetchMail</td>
+ <td>Experimental</td>
+ <td>2.2</td>
+ <td>2.2</td>
</tr>
</table>
</section>
1.5.4.1 +30 -30 james-server/src/xdocs/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/install.xml,v
retrieving revision 1.5
retrieving revision 1.5.4.1
diff -u -r1.5 -r1.5.4.1
--- install.xml 7 Dec 2002 20:16:54 -0000 1.5
+++ install.xml 3 May 2004 03:58:08 -0000 1.5.4.1
@@ -4,31 +4,31 @@
<properties>
<title>Installation</title>
-<author email="sergek@lokitech.com">Serge Knystautas</author> </properties> <body>
-<section name="Step 0: Building. (only necessary for daily snapshots)">
-<p> If you have downloaded a binary distribution, you do not need to build James.
+<author email="sergek@lokitech.com">Serge Knystautas</author> </properties> <body>
+<section name="Step 0: Building. (only necessary for daily snapshots)">
+<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://jakarta.apache.org/ant/">Ant</a>.
- This is a Java-tailored, XML-configured, extensible build or make system. We
+<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.
- James includes Ant to compile and package its distribution. Extract the snapshot
- to your favorite directory, cd to that directory and run the build by calling "build"
- or "./build.sh" which will create an unpacked binary distribution
+<p> If you have downloaded a daily snapshot, you need to build a distribution.
+ James includes Ant to compile and package its distribution. Extract the snapshot
+ to your favorite directory, cd to that directory and run the build by calling "build"
+ or "./build.sh" which will create an unpacked binary distribution
in the dist directory, but no archives.</p>
-<p>This "./dist" directory is the distribution directory used in Step 1 and beyond.
- You may either cd to ./dist, or you may copy and rename the dist directory to your
+<p>This "./dist" directory is the distribution directory used in Step 1 and beyond.
+ You may either cd to ./dist, or you may copy and rename the dist directory to your
installation directory.</p>
-<p>If you prefer you can run build with the "dist" task "build dist"
- (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
+<p>If you prefer you can run build with the "dist" task "build dist"
+ (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
- 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
+<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>
-</section> <section name="Step 1: Installation.">
-<p> Download distibution. Extract or copy all the files in the archive or dist
+</section> <section name="Step 1: Installation.">
+<p> Download distibution. Extract or copy all the files in the archive or dist
directory intto your installation directory. </p>
</section>
@@ -40,10 +40,10 @@
<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
+
+<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>
@@ -53,13 +53,13 @@
would then need to reconfigure your clients. This may not be an option if
you want to receive mail from external mailservers.)
</p>
-
-<p> The Avalon framework will unpack the necessary configuration files you will
- need to start the server. Wait until it is running, stop it again (ctrl-c), and
- edit the configuration (thereafter *nix users can run the server in the background
- using ./run.sh &). For basic use, you only need to set two items in the
- JAMES.conf.xml file: a root password for the remote administration facility
- and the IP address of a DNS server. Once you have edited the configuration files,
+
+<p> The Avalon framework will unpack the necessary configuration files you will
+ need to start the server. Wait until it is running, stop it again (ctrl-c), and
+ edit the configuration (thereafter *nix users can run the server in the background
+ using ./run.sh &). For basic use, you only need to set two items in the
+ JAMES.conf.xml file: a root password for the remote administration facility
+ and the IP address of a DNS server. Once you have edited the configuration files,
press 'Enter' on the terminal where Avalon is waiting. </p>
</section>
1.2.4.1 +32 -32 james-server/src/xdocs/installation_instructions_2_1.xml
Index: installation_instructions_2_1.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/installation_instructions_2_1.xml,v
retrieving revision 1.2
retrieving revision 1.2.4.1
diff -u -r1.2 -r1.2.4.1
--- installation_instructions_2_1.xml 11 Dec 2002 09:39:18 -0000 1.2
+++ installation_instructions_2_1.xml 3 May 2004 03:58:08 -0000 1.2.4.1
@@ -7,48 +7,48 @@
</properties>
<body>
<section name="Requirements">
-<p>James requires a Java Runtime Environment of Java version 1.3 or higher installed to run the
+<p>James requires a Java Runtime Environment of Java version 1.3 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
the JRE home directory before running James.</p>
<p>
-<strong>Warning!</strong> - Issues have been observed when using Sun's Java 1.3.0 on older Linux
-distributions. It is recommended that users of these platforms run James using a more recent
+<strong>Warning!</strong> - Issues have been observed when using Sun's Java 1.3.0 on older Linux
+distributions. It is recommended that users of these platforms run James using a more recent
Sun JRE or a JRE produced by an alternate vendor.
</p>
<p>
-On Unix platforms, root access will be required to run James. On these platforms, access to ports
-below 1024 is generally restricted to the root user. As SMTP, POP3, and NNTP all need to open
+On Unix platforms, root access will be required to run James. On these platforms, access to ports
+below 1024 is generally restricted to the root user. As SMTP, POP3, and NNTP all need to open
server sockets on such ports in standard configurations, James requires root access.
</p>
<p>
-Obviously James also requires sufficient disk space, processor power, and network bandwidth. But,
+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>
</section>
<section name="Installation Comments">
-<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
+<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>
-<p>It is important to realize that the James configuration files are not unpacked from the James
-distribution until the first time James is started. This is a consequence of the design of the
-Avalon Phoenix container used to run James. Once James has been started, the distribution will
+<p>It is important to realize that the James configuration files are not unpacked from the James
+distribution until the first time James is started. This is a consequence of the design of the
+Avalon Phoenix container used to run James. Once James has been started, the distribution will
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>
</section>
<section name="Installing the Binary">
<subsection name="Installing a Stand-alone James Server">
-<p>Obtain the full James binary distribution from the <a href="http://jakarta.apache.org/builds/jakarta-james/">James
-download directory</a>. It can be found in the bin subdirectory of the distribution directory for the particular
-build you are downloading. Unpack the archive into your James installation directory. Go to the bin subdirectory of the
+<p>Obtain the full James binary distribution from the <a href="http://james.apache.org/download.cgi">James
+download directory</a>. It can be found in the bin subdirectory of the distribution directory for the particular
+build you are downloading. 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>
</subsection>
<subsection name="Deploying a James Server in a Pre-Existing Phoenix Container">
-<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
+<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://jakarta.apache.org/builds/jakarta-james/">James download directory</a>. It can be found in the bin
+<p>Deploying James in Phoenix is fairly easy. Obtain the james.sar file from the
+<a href="http://james.apache.org/download.cgi">James download directory</a>. It can be found in the bin
subdirectory of the distribution directory for the particular build you are downloading. 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>
@@ -57,22 +57,22 @@
<section name="Initial Configuration">
<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
+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
found in the apps/james/SAR-INF subdirectory of the installation directory.</p>
-<p>The out of the box configuration makes certain assumptions and has some default values that are unlikely to
+<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
+<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_2_1.html">here</a>.</li>
-<li>DNS Servers - James needs to have access to a DNS server for domain resolution. The out of the box
-configuration assumes that there is a DNS server on localhost. In general administrators will have to change
-the configuration to point to a valid DNS server. This can be done by adjusting the dnsserver configuration
+<li>DNS Servers - James needs to have access to a DNS server for domain resolution. The out of the box
+configuration assumes that there is a DNS server on localhost. In general administrators will have to change
+the configuration to point to a valid DNS server. This can be done by adjusting the dnsserver configuration
block in the config.xml. More information can be found <a href="serverwide_configuration_2_1.html">here</a>.</li>
-<li>Managed Domain Names/IP Addresses - Out of the box, James only handles mail that is sent to recipients at
-localhost. It will attempt to deliver all other email to remote SMTP servers. To allow James to handle email
-for your domain or IP address, you simply need to add the appropriate domain name or IP address to the servernames
+<li>Managed Domain Names/IP Addresses - Out of the box, James only handles mail that is sent to recipients at
+localhost. It will attempt to deliver all other email to remote SMTP servers. To allow James to handle email
+for your domain or IP address, you simply need to add the appropriate domain name or IP address to the servernames
section of the config.xml. More information can be found <a href="serverwide_configuration_2_1.html">here</a>.</li>
<li>Postmaster Address - More information can be found <a href="serverwide_configuration_2_1.html">here</a>.</li>
</ul>
@@ -81,12 +81,12 @@
be found <a href="documentation_2_1.html">here</a>.</p>
</section>
<section name="Starting James with Your Configuration">
-<p>Once you have edited the configuration file you will need to restart James so that the changes take
-effect. When James starts, a list of the James services and the ports on which they are listening should
-be displayed on the console. Additional information about the system configuration is printed in the James log files
+<p>Once you have edited the configuration file you will need to restart James so that the changes take
+effect. When James starts, a list of the James services and the ports on which they are listening should
+be displayed on the console. Additional information about the system configuration is printed in the James log files
upon startup.</p>
-<p>Finally, after configuration is complete, it will be necessary to create user accounts before the James server
-will be fully operational. Instructions on creating user accounts can be found
+<p>Finally, after 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_2_1.html">here</a>.</p>
</section>
1.12.4.12 +1 -1 james-server/src/xdocs/weare.xml
Index: weare.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/weare.xml,v
retrieving revision 1.12.4.11
retrieving revision 1.12.4.12
diff -u -r1.12.4.11 -r1.12.4.12
--- weare.xml 24 Jun 2003 19:41:30 -0000 1.12.4.11
+++ weare.xml 3 May 2004 03:58:08 -0000 1.12.4.12
@@ -4,7 +4,7 @@
<properties>
<title>Who We Are</title>
- <author email="james-dev@jakarta.apache.org">James Team</author>
+ <author email="server-dev@james.apache.org">James Team</author>
</properties>
<body>
No revision
No revision
1.20.2.3 +3 -3 james-server/src/xdocs/stylesheets/project.xml
Index: project.xml
===================================================================
RCS file: /home/cvs/james-server/src/xdocs/stylesheets/project.xml,v
retrieving revision 1.20.2.2
retrieving revision 1.20.2.3
diff -u -r1.20.2.2 -r1.20.2.3
--- project.xml 6 May 2003 17:47:40 -0000 1.20.2.2
+++ project.xml 3 May 2004 03:58:08 -0000 1.20.2.3
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="ISO-8859-1"?>
<project name="James"
- href="http://jakarta.apache.org/james">
+ href="http://james.apache.org/">
<title>Java Mail and News server, SMTP POP3 NNTP</title>
<logo href="/images/james-logo.jpg">James - Java Apache Mail Enterprise Server</logo>
@@ -10,7 +10,7 @@
<item name="Overview" href="/index.html"/>
<item name="James FAQ" href="/FAQ.html"/>
</menu>
-
+
<menu name="Translated">
<item name="Japanese (web)" href="http://james.terra-intl.com/"/>
</menu>
@@ -32,7 +32,7 @@
<menu name="Older Documentation">
<item name="James Document Archive" href="/document_archive.html"/>
</menu>
-
+
<menu name="Project">
<item name="Bug Database " href="/site/bugs.html"/>
<item name="How Can I Contribute?" href="/contribute.html"/>
No revision
No revision
1.1.2.1 +1 -1 james-server/tools/etc/changelog.xsl
Index: changelog.xsl
===================================================================
RCS file: /home/cvs/james-server/tools/etc/changelog.xsl,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- changelog.xsl 26 Sep 2002 22:05:12 -0000 1.1
+++ changelog.xsl 3 May 2004 03:58:08 -0000 1.1.2.1
@@ -101,7 +101,7 @@
<h1>
<a name="top"><xsl:value-of select="$title"/></a>
</h1>
- <p align="right">Designed for use with <a href="http://jakarta.apache.org">Ant</a>.</p>
+ <p align="right">Designed for use with <a href="http://ant.apache.org">Ant</a>.</p>
<hr size="2"/>
<TABLE BORDER="0" WIDTH="100%" CELLPADDING="3" CELLSPACING="1">
1.1.2.1 +1 -1 james-server/tools/etc/checkstyle-frames.xsl
Index: checkstyle-frames.xsl
===================================================================
RCS file: /home/cvs/james-server/tools/etc/checkstyle-frames.xsl,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- checkstyle-frames.xsl 26 Sep 2002 22:05:12 -0000 1.1
+++ checkstyle-frames.xsl 3 May 2004 03:58:08 -0000 1.1.2.1
@@ -111,7 +111,7 @@
<td class="text-align:right"><h2>CheckStyle Audit</h2></td>
</tr>
<tr>
- <td class="text-align:right">Designed for use with <a href='http://checkstyle.sourceforge.net/'>CheckStyle</a> and <a href='http://jakarta.apache.org'>Ant</a>.</td>
+ <td class="text-align:right">Designed for use with <a href='http://checkstyle.sourceforge.net/'>CheckStyle</a> and <a href='http://ant.apache.org'>Ant</a>.</td>
</tr>
</table>
<hr size="1"/>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org