<commit_before><?xml version="1.0"?>

<document>

 <properties>
  <title>Overview</title>
  <author email="<EMAIL>"><NAME></author>
  <author email="<EMAIL>"><NAME></author>
 </properties>

<body>
<section name="What is it?">
<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 solution based on currently available open protocols. </p>
<p>James is also a mail application platform. <br/>The James project hosts the Apache Mailet API, and James provides an implementation of this mail application platform API.  </p>
<p>James is based upon the Apache Avalon application framework. (For more information about Avalon, please go to <a href="http://jakarta.apache.org/avalon">http://jakarta.apache.org/avalon</a>)</p>
<p>James requires Java 2 (either JRE 1.3 or 1.4 as of 2.0a3). </p>
<subsection name="news">
<p><b>Find out how to use James with sendmail</b><br/>We've added a HOW TO document explaining how to configure sendmail to route all mail through James, read it <a href="james_and_sendmail.html">Here</a>.</p>
</subsection>
<subsection name="releases">
<p><b>Latest and Stable: james-2.1</b><br/>
James v2.1 is the current release.  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>

<p>This release has many enhancements and bug fixes over the previous
release.  See the <a
href="http://jakarta.apache.org/james/changelog.html">Change Log</a>
for a detailed list of changes.  Some of the earlier defects could
turn a James mail server into an Open Relay.  All users of James 2.0a3
and earlier are urged to upgrade to James v2.1 as soon as
possible.</p>

<p>For details see the <A
HREF="http://jakarta.apache.org/james/announcement_2_1.html">Official
Announcement</A>.</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>
</subsection>
</section><section name="Design Objectives">
<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.3 API.
  </p>
  <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
       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
       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
       systems. Examples of the services a Mailet might provide include: a
       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_2_1.html">documentation</a>).</p>
    <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
       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>
</section>
<section name="Feature Status">
    <table>
      <tr>
        <th>Item</th>
        <th>Status (v2.0a3)</th>
        <th>Since</th>
        <th>First released</th>
      </tr>
      <tr>
        <td>SMTP server</td>
        <td>Stable</td>
        <td>1.0</td>
        <td>0.95</td>
      </tr>
      <tr>
        <td>Mailet Engine</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>0.95</td>
      </tr>
      <tr>
        <td>FileSystem mailboxes/spool</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>1.0</td>
      </tr>
      <tr>
        <td>RDBMS mailboxes/spool</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>POP3 server</td>
        <td>Stable</td>
        <td>1.1</td>
        <td>1.0</td>
      </tr>
      <tr>
        <td>RDBMS - Users</td>
        <td>Stable</td>
        <td>1.2.1</td>
        <td>1.2.1</td>
      </tr>
      <tr>
        <td>LDAP Support - Users</td>
        <td>Experimental</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>TLS Support - POP3</td>
        <td>Experimental</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>Remote Manager</td>
        <td>Stable</td>
        <td>1.0</td>
        <td>1.0</td>
      </tr>
      <tr>
        <td>TLS Support - Remote Manager</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>NNTP server</td>
        <td>Experimental</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>FetchPOP</td>
        <td>Experimental</td>
        <td>2.1</td>
        <td>2.1</td>
      </tr>
    </table>
</section>

</body>
</document>
<commit_msg>Updated for TLP (site was changed without commit)<commit_after><?xml version="1.0"?>

<document>

 <properties>
  <title>Overview</title>
  <author email="<EMAIL>"><NAME></author>
  <author email="<EMAIL>"><NAME></author>
 </properties>

<body>
<section name="What is it?">
<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 solution based on currently available open protocols. </p>
<p>James is also a mail application platform. <br/>The James project hosts the Apache Mailet API, and James provides an implementation of this mail application platform API.  </p>
<p>James is based upon the Apache Avalon application framework. (For more information about Avalon, please go to <a href="http://jakarta.apache.org/avalon">http://jakarta.apache.org/avalon</a>)</p>
<p>James requires Java 2 (either JRE 1.3 or 1.4 as of 2.0a3). </p>
<subsection name="news">
<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>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>
</subsection>
<subsection name="releases">
<p><b>Latest and Stable: james-2.1</b><br/>
James v2.1 is the current release.  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>

<p>This release has many enhancements and bug fixes over the previous
release.  See the <a
href="http://jakarta.apache.org/james/changelog.html">Change Log</a>
for a detailed list of changes.  Some of the earlier defects could
turn a James mail server into an Open Relay.  All users of James 2.0a3
and earlier are urged to upgrade to James v2.1 as soon as
possible.</p>

<p>For details see the <A
HREF="http://jakarta.apache.org/james/announcement_2_1.html">Official
Announcement</A>.</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>
</subsection>
</section><section name="Design Objectives">
<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.3 API.
  </p>
  <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
       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
       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
       systems. Examples of the services a Mailet might provide include: a
       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_2_1.html">documentation</a>).</p>
    <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
       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>
</section>
<section name="Feature Status">
    <table>
      <tr>
        <th>Item</th>
        <th>Status (v2.0a3)</th>
        <th>Since</th>
        <th>First released</th>
      </tr>
      <tr>
        <td>SMTP server</td>
        <td>Stable</td>
        <td>1.0</td>
        <td>0.95</td>
      </tr>
      <tr>
        <td>Mailet Engine</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>0.95</td>
      </tr>
      <tr>
        <td>FileSystem mailboxes/spool</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>1.0</td>
      </tr>
      <tr>
        <td>RDBMS mailboxes/spool</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>POP3 server</td>
        <td>Stable</td>
        <td>1.1</td>
        <td>1.0</td>
      </tr>
      <tr>
        <td>RDBMS - Users</td>
        <td>Stable</td>
        <td>1.2.1</td>
        <td>1.2.1</td>
      </tr>
      <tr>
        <td>LDAP Support - Users</td>
        <td>Experimental</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>TLS Support - POP3</td>
        <td>Experimental</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>Remote Manager</td>
        <td>Stable</td>
        <td>1.0</td>
        <td>1.0</td>
      </tr>
      <tr>
        <td>TLS Support - Remote Manager</td>
        <td>Stable</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>NNTP server</td>
        <td>Experimental</td>
        <td>1.2</td>
        <td>1.2</td>
      </tr>
      <tr>
        <td>FetchPOP</td>
        <td>Experimental</td>
        <td>2.1</td>
        <td>2.1</td>
      </tr>
    </table>
</section>

</body>
</document>

{'fraction_non_alphanumeric': 0.13514953199908683, 'fraction_numerical': 0.013697587702610151, 'mean_word_length': 2.771018651362984, 'pattern_counts': {'":': 0, '<': 505, '<?xml version=': 2, '>': 505, 'https://': 0, 'lorem ipsum': 0, 'www.': 1, 'xml': 2}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '782968', 'n_tokens_mistral': 4317, 'n_tokens_neox': 4195, 'n_words': 1384}