james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pgoldst...@apache.org
Subject cvs commit: jakarta-james/src/xdocs/stylesheets project.xml
Date Sat, 07 Dec 2002 20:16:55 GMT
pgoldstein    2002/12/07 12:16:55

  Modified:    src/xdocs FAQ.xml configuration_v2_0.xml contribute.xml
                        install.xml james_and_sendmail.xml
                        usingJDBC_v2.0.xml usingLDAP_v1_2.xml
                        usingTLS_v1_2.xml architecture_v2_0.xml
               src/xdocs/stylesheets project.xml
  Log:
  Fixing some line feeds, tabs, grammar/spelling issues.
  
  Revision  Changes    Path
  1.21      +13 -13    jakarta-james/src/xdocs/FAQ.xml
  
  Index: FAQ.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/FAQ.xml,v
  retrieving revision 1.20
  retrieving revision 1.21
  diff -u -r1.20 -r1.21
  --- FAQ.xml	24 Nov 2002 21:15:43 -0000	1.20
  +++ FAQ.xml	7 Dec 2002 20:16:54 -0000	1.21
  @@ -284,19 +284,19 @@
             <a name="16"/>
             <subsection name="I am using James with a MySQL database and I keep getting
a &quot;Packet is larger than max_allowed_packet&quot; when receiving large messages
despite the fact that my max packet size is configured to be larger than my max message size.
 What's going on?">
               <p>When a user tries to send a large message that is close to but not
quite at the max message limit the send fails and an exception similar to the following appears
in the log:</p>
  -            <p>Sent: 451 Error processing message:<br/>
  -            Exception spooling message: Exception caught while storing mail Container:<br/>
  -            java.lang.IllegalArgumentException: Packet is larger than max_allowed_packet<br/>
  -            from server configuration of 4193280 bytes;<br/>
  -              nested exception is:<br/>
  -                    java.lang.RuntimeException: Exception caught while storing mail<br/>
  -            Container: java.lang.IllegalArgumentException: Packet is larger than<br/>
  -            max_allowed_packet from server configuration of 4193280 bytes<br/></p>
  -            <p>Because of how the JDBC driver is written, a 25%
  -            factor is necessary between the maximum message size and the max_packet_size
  -            to prevent the driver from throwing an exception.  So if you want a 4MB
  -            maximum message size, you need a 5MB max_packet size.  Or a 4MB
  -            max_packet_size allows only a 3.2MB max message.
  +            <p>Sent: 451 Error processing message:<br/>
  +            Exception spooling message: Exception caught while storing mail Container:<br/>
  +            java.lang.IllegalArgumentException: Packet is larger than max_allowed_packet<br/>
  +            from server configuration of 4193280 bytes;<br/>
  +              nested exception is:<br/>
  +                    java.lang.RuntimeException: Exception caught while storing mail<br/>
  +            Container: java.lang.IllegalArgumentException: Packet is larger than<br/>
  +            max_allowed_packet from server configuration of 4193280 bytes<br/></p>
  +            <p>Because of how the JDBC driver is written, a 25%
  +            factor is necessary between the maximum message size and the max_packet_size
  +            to prevent the driver from throwing an exception.  So if you want a 4MB
  +            maximum message size, you need a 5MB max_packet size.  Or a 4MB
  +            max_packet_size allows only a 3.2MB max message.
               </p><p>Noel Bergman</p>
             </subsection>
         </section>
  
  
  
  1.4       +14 -14    jakarta-james/src/xdocs/configuration_v2_0.xml
  
  Index: configuration_v2_0.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/configuration_v2_0.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- configuration_v2_0.xml	21 Nov 2002 15:10:45 -0000	1.3
  +++ configuration_v2_0.xml	7 Dec 2002 20:16:54 -0000	1.4
  @@ -41,15 +41,15 @@
               <td> Is the source of error replies and the email users will mail to
for any problem.  You
               should change this to an address that can receive incoming messages.</td>
           </tr>
  -	<tr>
  +    <tr>
               <td> helloName</td>
               <td> attribute autodetect=TRUE and value of 'myMailServer'  </td>
               <td> The name by which James will identify itself in SMTP and POP3
  -	     greetings. If autodetect is TRUE James will attempt to detect
  +            greetings. If autodetect is TRUE James will attempt to detect
               automatically the name, failing which it will use 'localhost'. If
  -	    autodetect is not TRUE, James will use the specified name or
  -	    'localhost' if none is specified. Look in jamesinfo.log for
  -	     lines like "[...] Local host is: [servername] and [...] Hello Name is: [machine name]"</td>
  +            autodetect is not TRUE, James will use the specified name or
  +            'localhost' if none is specified. Look in jamesinfo.log for
  +            lines like "[...] Local host is: [servername] and [...] Hello Name is: [machine
name]"</td>
           </tr>
           <tr>
               <td> servernames/servername</td>
  @@ -310,12 +310,12 @@
               (see &lt;servername&gt;). </td>
               <td> match="HostIsLocal" </td>
           </tr>
  -       	<tr>
  -       		<td> InSpammerBlacklist </td>
  -       		<td> DNS zone with blacklist </td>
  -       		<td> match all recipients if mail received from an IP address on the blacklist.
</td>
  -       		<td> match="InSpammerBlacklist=blackholes.mail-abuse.org" </td>
  -       	</tr>
  +        <tr>
  +            <td> InSpammerBlacklist </td>
  +            <td> DNS zone with blacklist </td>
  +            <td> match all recipients if mail received from an IP address on the
blacklist. </td>
  +            <td> match="InSpammerBlacklist=blackholes.mail-abuse.org" </td>
  +        </tr>
           <tr>
               <td> IsSingleRecipient </td>
               <td> none </td>
  @@ -442,7 +442,7 @@
       </blockquote>
       <b>debug.Identity</b>
       <blockquote>
  -         Leave any incoming mail untoched. A debug mailet
  +         Leave any incoming mail untouched. A debug mailet
            (not really useful).
            No configuration needed.
               <br>
  @@ -451,7 +451,7 @@
       </blockquote>
       <b>Forward</b>
       <blockquote>
  -    		<br>
  +            <br>
               Replace the recipient list with recipient specified in
               configurations.</br>
               <br>
  @@ -522,7 +522,7 @@
   
       <b>RemoteDelivery</b>
       
  - Relay mails to remote hosts. "delayTime" is the time in mills the 
  + Relays mails to remote hosts. "delayTime" is the time in mills the 
     mailet will wait before retrying sending a mail which fail at first time. "maxRetries"

     is the number of retries before sending back to sender the mail. <br>
             &lt;mailet match="!RecipientIsLocal" class="RemoteDelivery"&gt;
  
  
  
  1.5       +80 -80    jakarta-james/src/xdocs/contribute.xml
  
  Index: contribute.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/contribute.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- contribute.xml	26 Sep 2002 18:40:09 -0000	1.4
  +++ contribute.xml	7 Dec 2002 20:16:54 -0000	1.5
  @@ -5,83 +5,83 @@
         <author email="danny@thought.co.uk">Danny Angus</author>
      </properties>
      <body>
  -	   <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/> 
  -		   The rest of this document outlines the way to go about these to maximum effect.<br/>
  -	   </p>
  -	   <p>
  -		   If you are new to this you may be interested in some of these resources.<br/>
  -		   <a href="http://jakarta.apache.org/site/guides.html">A good, full, summary of
links to guidelines</a><br/>
  -		   Subscribe to the relevant mailing lists (link on the left).<br/>
  -		   <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 
  -			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 
  -			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

  -			be commited quickly (or at all).<br/>
  -		</p>
  -		</section>
  -	
  -		<section name="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 
  -			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.
  -		</p>
  -		</section>
  -	
  -		<section name="Bug reporting and fixing">
  -		<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 
  -			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

  -			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 
  -			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 
  -			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) 
  -			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

  -			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>
  \ No newline at end of file
  +       <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/> 
  +           The rest of this document outlines the way to go about these to maximum effect.<br/>
  +       </p>
  +       <p>
  +           If you are new to this you may be interested in some of these resources.<br/>
  +           <a href="http://jakarta.apache.org/site/guides.html">A good, full, summary
of links to guidelines</a><br/>
  +           Subscribe to the relevant mailing lists (link on the left).<br/>
  +           <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 
  +            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 
  +            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 
  +            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

  +            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.
  +        </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 
  +            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 
  +            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 
  +            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 
  +            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) 
  +            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 
  +            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.5       +6 -6      jakarta-james/src/xdocs/install.xml
  
  Index: install.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/install.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- install.xml	9 Jan 2002 21:50:20 -0000	1.4
  +++ install.xml	7 Dec 2002 20:16:54 -0000	1.5
  @@ -8,7 +8,7 @@
   <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 sources you need <a href="http://jakarta.apache.org/ant/">Ant</a>.

  +<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 
     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. 
  @@ -24,7 +24,7 @@
     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 config.xml 
  +  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."> 
  @@ -54,8 +54,8 @@
       you want to receive mail from external mailservers.)
     </p>
     
  -<p> The Avalon framework will unpack the neccessay configuration files you will 
  -  need to start the server, wait until it is running stop it again (ctrl-c) and 
  +<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 &amp;). For basic use, you only need to set two items in the 
     JAMES.conf.xml file: a root password for the remote administration facility 
  @@ -83,8 +83,8 @@
       ../var/mail/localinbox/[user].
       Try now to retrieve that mail using POP3 (port 110).
       Trace out JAMES actions in /logs/*info.log.
  -    Action that will be taken by JAMES on incoming mail are configurated in
  -    the mailet pipe line (/conf/james.conf.xml). Look at it if you want to
  +    Actions that will be taken by JAMES on incoming mail are configured in
  +    the mailet pipe line (/conf/JAMES.conf.xml). Look at it if you want to
       understand what's happening.
     </p>
     <p>
  
  
  
  1.3       +6 -6      jakarta-james/src/xdocs/james_and_sendmail.xml
  
  Index: james_and_sendmail.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/james_and_sendmail.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- james_and_sendmail.xml	21 Nov 2002 15:10:45 -0000	1.2
  +++ james_and_sendmail.xml	7 Dec 2002 20:16:54 -0000	1.3
  @@ -49,15 +49,15 @@
   But we *want* to relay mail to localhost, and because sendmail isn't receiving our mail,
James is, we won't be creating a loop. (make sure you've followed step one though).<br/>
   So open <b>/etc/sendmail.cf</b> again and go to the bottom of the file, start
scrolling upwards until you see the declaration of the esmtp mailer it'll look something like
this
   <source>
  -Mesmtp,		P=[IPC], F=mDFMuXa, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990,
  -		T=DNS/RFC822/SMTP,
  -		A=TCP $h
  +Mesmtp,     P=[IPC], F=mDFMuXa, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990,
  +        T=DNS/RFC822/SMTP,
  +        A=TCP $h
   </source>
   You need to change it so its more like this:  :-D
   <source>
  -Mesmtp,		P=[IPC], F=kmDFMuXa, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990,
  -		T=DNS/RFC822/SMTP,
  -		A=TCP $h
  +Mesmtp,     P=[IPC], F=kmDFMuXa, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP, E=\r\n, L=990,
  +        T=DNS/RFC822/SMTP,
  +        A=TCP $h
   </source>
   But seriously, we've added a <b>k</b> to the "F=" list <b>F=mDFMuXa</b>
becomes <b>F=kmDFMuXa</b><br/>
   And again, thats it, sendmail will now skip the loopback test on mail leaving through the
esmtp mailer.
  
  
  
  1.3       +1 -1      jakarta-james/src/xdocs/usingJDBC_v2.0.xml
  
  Index: usingJDBC_v2.0.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/usingJDBC_v2.0.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- usingJDBC_v2.0.xml	21 Nov 2002 15:10:45 -0000	1.2
  +++ usingJDBC_v2.0.xml	7 Dec 2002 20:16:54 -0000	1.3
  @@ -138,7 +138,7 @@
   I've made a simple modification to "RemoteManagerHandler", to allow testing. The
   "use [userRepositoryName]" command will switch the Remote manager to manage the
   named repository. This isn't really intended for production, makes for easier testing.
  -The "james-config.xml" included in the proposal sets up 4 jdbc repositories: 
  +The "james-config.xml" included in the proposal sets up 4 JDBC repositories: 
       <ul>
           <li> "localUsers" - a JamesUsersJdbcRepository.</li>
           <li> "list-james" - a ListUsersJdbcRepository, used by the ListServ mailet.</li>
  
  
  
  1.3       +9 -9      jakarta-james/src/xdocs/usingLDAP_v1_2.xml
  
  Index: usingLDAP_v1_2.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/usingLDAP_v1_2.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- usingLDAP_v1_2.xml	21 Nov 2002 15:10:45 -0000	1.2
  +++ usingLDAP_v1_2.xml	7 Dec 2002 20:16:54 -0000	1.3
  @@ -126,17 +126,17 @@
             <tr>
               <td>
                 <table cellspace="0">
  -	        <tr>
  -	          <td align="center" valign="top"> |
  -                    <br>LocalUsers</br>
  -                    <br>member=Arthur</br>
  -                  </td>
  -	          <td align="center" valign="top"> |
  +            <tr>
  +              <td align="center" valign="top"> |
  +                <br>LocalUsers</br>
  +                <br>member=Arthur</br>
  +              </td>
  +              <td align="center" valign="top"> |
                       <br>list-james</br>
                       <br>member=Arthur</br>
                     </td>
  -	        </tr>
  -	      </table>
  +            </tr>
  +          </table>
               </td>
               <td> </td>
               <td> </td>
  @@ -152,7 +152,7 @@
   <section name="Installation">
   
     <p>
  -    Six  entries in JAMES.conf.xml must be set for this to work: 
  +    Six entries in JAMES.conf.xml must be set for this to work: 
       <ul>
         <li>change usersManager - type to ldap.</li>
         <li>Set the ldapServer element to point to the correct host and port</li>
  
  
  
  1.3       +1 -1      jakarta-james/src/xdocs/usingTLS_v1_2.xml
  
  Index: usingTLS_v1_2.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/usingTLS_v1_2.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- usingTLS_v1_2.xml	21 Nov 2002 15:10:45 -0000	1.2
  +++ usingTLS_v1_2.xml	7 Dec 2002 20:16:54 -0000	1.3
  @@ -70,7 +70,7 @@
    </p>
     <p>
      (Negative Test) telnet to port 4555 (ie without SSL). This should hang the
  -   telnet client. It should also lock port 4555 until the connection timesout,
  +   telnet client. It should also lock port 4555 until the connection times out,
      I think.
     </p>
   </section>
  
  
  
  1.4       +2 -2      jakarta-james/src/xdocs/architecture_v2_0.xml
  
  Index: architecture_v2_0.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/architecture_v2_0.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- architecture_v2_0.xml	21 Nov 2002 15:10:45 -0000	1.3
  +++ architecture_v2_0.xml	7 Dec 2002 20:16:54 -0000	1.4
  @@ -12,7 +12,7 @@
   <section name="Architecture">
   
     <p>
  -    JAMES is a multi-protocol message processing and storage engine. JAMES
  +    James is a multi-protocol message processing and storage engine. James
       currently consists of:
       <ul>
         <li> two mail prototcol servers (SMTP and POP3),</li>
  @@ -27,7 +27,7 @@
     </p>
   
     <p>
  -    JAMES is built on top of Avalon, the Java Apache Server Framework.
  +    James is built on top of Avalon, the Java Apache Server Framework.
       Versions 2.0 of James use a date-snapshot of Avalon code as of November 2001.
       The <code>lib</code> directory includes date-stamped jars of the various
Avalon libraries.
       We intend to stay current with new versions of Avalon as they are released.</p>
  
  
  
  1.17      +68 -68    jakarta-james/src/xdocs/stylesheets/project.xml
  
  Index: project.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-james/src/xdocs/stylesheets/project.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -r1.16 -r1.17
  --- project.xml	2 Dec 2002 11:42:14 -0000	1.16
  +++ project.xml	7 Dec 2002 20:16:55 -0000	1.17
  @@ -1,68 +1,68 @@
  -<?xml version="1.0" encoding="ISO-8859-1"?>
  -<project name="James"
  -        href="http://jakarta.apache.org/james/">
  -
  -    <title>Java Mail and News server, SMTP POP3 NNTP</title>
  -    <logo href="/images/james-logo.jpg">James - Java Apache Mail Enterprise Server</logo>
  -
  -    <body>
  -    <menu name="James">
  -        <item name="Overview"          href="/index.html"/>
  -        <item name="James FAQ"      href="/FAQ.html"/>
  -    </menu>
  -    
  -    <menu name="Translated">
  -        <item name="Japanese (web)" href="http://www.terra-intl.com/jakarta/james/"/>
  -    </menu>
  -
  -    <menu name="Downloads">
  -        <item name="Binaries"              href="/site/binindex.html"/>
  -        <item name="Source Code"           href="/site/sourceindex.html"/>
  -    </menu>
  -
  -    <menu name="Current Documentation">
  -        <item name="James 2.1 Documentation"           href="/documentation_2_1.html"/>
  -        <item name="James Javadocs"      href="/javadocs/index.html"/>
  -        <item name="Mailet API"     href="/mailet/index.html"/>
  -        <item name="James and sendmail"     href="/james_and_sendmail.html"/>
  -
  -    </menu>
  -
  -    <menu name="Older Documentation">
  -        <item name="Architecture (version 2.0)"      href="/architecture_v2_0.html"/>
  -        <item name="Install (version 2.0)"           href="/install.html"/>
  -        <item name="Configuration (version 2.0)"     href="/configuration_v2_0.html"/>
  -        <item name="Using JDBC (version 2.0)"     href="/usingJDBC_v2.0.html"/>
  -        <item name="Using LDAP (version 1.2)"     href="/usingLDAP_v1_2.html"/>
  -        <item name="Using TLS (version 1.2)"     href="/usingTLS_v1_2.html"/>
  -
  -        <item name="Useful RFCs (web)"   href="http://jakarta.apache.org/james/rfclist"/>
  -    </menu>
  -    
  -    <menu name="Project">
  -        <item name="Bug Database "     href="/site/bugs.html"/>
  -        <item name="How Can I Contribute?" href="/contribute.html"/>
  -        <item name="Coding Standards"  href="/code-standards.html"/>
  -        <item name="License"           href="/license.html"/>
  -        <item name="TODO"              href="/todo.html"/>
  -        <item name="Changelog"         href="/changelog.html"/>
  -        <item name="Who We Are"        href="/weare.html"/>
  -    </menu>
  -
  -    <menu name="Jakarta Information (web)">
  -        <item name="Front Page"            href="http://jakarta.apache.org/index.html"/>
  -        <item name="News &amp; Status"     href="http://jakarta.apache.org/site/news.html"/>
  -        <item name="Mailing Lists"         href="http://jakarta.apache.org/site/mail.html"/>
  -        <item name="Get Involved"          href="http://jakarta.apache.org/site/getinvolved.html"/>
  -        <item name="CVS Repositories"      href="http://jakarta.apache.org/site/cvsindex.html"/>
  -        <item name="Reference Library"     href="http://jakarta.apache.org/site/library.html"/>
  -        <item name="FAQs"                  href="http://jakarta.apache.org/site/faqs.html"/>
  -    </menu>
  -
  -    <menu name="Related Projects (web)">
  -        <item name="Ant"                   href="http://jakarta.apache.org/ant/index.html"/>
  -        <item name="Avalon"                href="http://jakarta.apache.org/avalon/index.html"/>
  -    </menu>
  -
  -    </body>
  -</project>
  +<?xml version="1.0" encoding="ISO-8859-1"?>
  +<project name="James"
  +        href="http://jakarta.apache.org/james/">
  +
  +    <title>Java Mail and News server, SMTP POP3 NNTP</title>
  +    <logo href="/images/james-logo.jpg">James - Java Apache Mail Enterprise Server</logo>
  +
  +    <body>
  +    <menu name="James">
  +        <item name="Overview"          href="/index.html"/>
  +        <item name="James FAQ"      href="/FAQ.html"/>
  +    </menu>
  +    
  +    <menu name="Translated">
  +        <item name="Japanese (web)" href="http://www.terra-intl.com/jakarta/james/"/>
  +    </menu>
  +
  +    <menu name="Downloads">
  +        <item name="Binaries"              href="/site/binindex.html"/>
  +        <item name="Source Code"           href="/site/sourceindex.html"/>
  +    </menu>
  +
  +    <menu name="Current Documentation">
  +        <item name="James 2.1 Documentation"           href="/documentation_2_1.html"/>
  +        <item name="James Javadocs"      href="/javadocs/index.html"/>
  +        <item name="Mailet API"     href="/mailet/index.html"/>
  +        <item name="James and sendmail"     href="/james_and_sendmail.html"/>
  +
  +    </menu>
  +
  +    <menu name="Older Documentation">
  +        <item name="Architecture (version 2.0)"      href="/architecture_v2_0.html"/>
  +        <item name="Install (version 2.0)"           href="/install.html"/>
  +        <item name="Configuration (version 2.0)"     href="/configuration_v2_0.html"/>
  +        <item name="Using JDBC (version 2.0)"     href="/usingJDBC_v2.0.html"/>
  +        <item name="Using LDAP (version 1.2)"     href="/usingLDAP_v1_2.html"/>
  +        <item name="Using TLS (version 1.2)"     href="/usingTLS_v1_2.html"/>
  +
  +        <item name="Useful RFCs (web)"   href="http://jakarta.apache.org/james/rfclist"/>
  +    </menu>
  +    
  +    <menu name="Project">
  +        <item name="Bug Database "     href="/site/bugs.html"/>
  +        <item name="How Can I Contribute?" href="/contribute.html"/>
  +        <item name="Coding Standards"  href="/code-standards.html"/>
  +        <item name="License"           href="/license.html"/>
  +        <item name="TODO"              href="/todo.html"/>
  +        <item name="Changelog"         href="/changelog.html"/>
  +        <item name="Who We Are"        href="/weare.html"/>
  +    </menu>
  +
  +    <menu name="Jakarta Information (web)">
  +        <item name="Front Page"            href="http://jakarta.apache.org/index.html"/>
  +        <item name="News &amp; Status"     href="http://jakarta.apache.org/site/news.html"/>
  +        <item name="Mailing Lists"         href="http://jakarta.apache.org/site/mail.html"/>
  +        <item name="Get Involved"          href="http://jakarta.apache.org/site/getinvolved.html"/>
  +        <item name="CVS Repositories"      href="http://jakarta.apache.org/site/cvsindex.html"/>
  +        <item name="Reference Library"     href="http://jakarta.apache.org/site/library.html"/>
  +        <item name="FAQs"                  href="http://jakarta.apache.org/site/faqs.html"/>
  +    </menu>
  +
  +    <menu name="Related Projects (web)">
  +        <item name="Ant"                   href="http://jakarta.apache.org/ant/index.html"/>
  +        <item name="Avalon"                href="http://jakarta.apache.org/avalon/index.html"/>
  +    </menu>
  +
  +    </body>
  +</project>
  
  
  

--
To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>


Mime
View raw message