You are viewing a plain text version of this content. The canonical link for it is here.
Posted to site-dev@james.apache.org by rd...@apache.org on 2009/07/02 12:18:19 UTC
svn commit: r790538 [25/36] - in /james/site/trunk/www/mpt/1.0: ./
apache-james-mpt-antlib/ apache-james-mpt-antlib/css/
apache-james-mpt-antlib/emma/ apache-james-mpt-antlib/images/
apache-james-mpt-app/ apache-james-mpt-app/css/ apache-james-mpt-app/...
Added: james/site/trunk/www/mpt/1.0/rat-report.html
URL: http://svn.apache.org/viewvc/james/site/trunk/www/mpt/1.0/rat-report.html?rev=790538&view=auto
==============================================================================
--- james/site/trunk/www/mpt/1.0/rat-report.html (added)
+++ james/site/trunk/www/mpt/1.0/rat-report.html Thu Jul 2 10:18:09 2009
@@ -0,0 +1,10527 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+<html>
+ <head>
+ <title>JAMES Mail Protocol Tester (MPT) - RAT (Release Audit Tool) results</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://james.apache.org/mpt/index.html" id="bannerLeft">
+
+ <img src="images/james-mpt-logo.gif" alt="" />
+
+ </a>
+ <a href="http://www.apache.org/index.html" id="bannerRight">
+
+ <img src="images/asf-logo-reduced.gif" alt="" />
+
+ </a>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 07/02/2009
+ </div>
+ <div class="xright"> <a href="http://james.apache.org/index.html">JAMES Project</a>
+ |
+ <a href="http://james.apache.org/server/index.html">Server</a>
+ |
+ <a href="http://james.apache.org/mailet/index.html">Mailets</a>
+ |
+ <a href="http://james.apache.org/jspf/index.html">jSPF</a>
+ |
+ <a href="http://james.apache.org/mime4j/index.html">Mime4J</a>
+ |
+ <a href="http://james.apache.org/jsieve/index.html">JSieve</a>
+ |
+ <a href="http://james.apache.org/postage/index.html">Postage</a>
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+ <h5>Mail Protocol Tester</h5>
+ <ul>
+
+ <li class="none">
+ <a href="http://james.apache.org/mpt/index.html">Overview</a>
+ </li>
+
+ <li class="none">
+ <a href="release-notes.html">Release Notes</a>
+ </li>
+
+ <li class="none">
+ <a href="http://james.apache.org/mpt/main">Main Library</a>
+ </li>
+
+ <li class="none">
+ <a href="http://james.apache.org/mpt/antlib">AntLib</a>
+ </li>
+
+ <li class="none">
+ <a href="http://james.apache.org/mpt/app">Application</a>
+ </li>
+ </ul>
+ <h5>The Apache Software Foundation</h5>
+ <ul>
+
+ <li class="none">
+ <a href="http://jakarta.apache.org/site/getinvolved.html">Get Involved</a>
+ </li>
+
+ <li class="none">
+ <a href="http://apache.org/foundation/faq.html">FAQ</a>
+ </li>
+
+ <li class="none">
+ <a href="http://apache.org/foundation/sponsorship.html">Sponsorship</a>
+ </li>
+
+ <li class="none">
+ <a href="http://apache.org/foundation/contributing.html">Donations</a>
+ </li>
+
+ <li class="none">
+ <a href="http://apache.org/foundation/thanks.html">Thanks</a>
+ </li>
+ </ul>
+ <h5>Downloads</h5>
+ <ul>
+
+ <li class="none">
+ <a href="http://james.apache.org/download.cgi">Stable releases</a>
+ </li>
+
+ <li class="none">
+ <a href="http://james.apache.org/downloadunstable.cgi">Unstable releases</a>
+ </li>
+
+ <li class="none">
+ <a href="http://people.apache.org/builds/james/nightly/">Nightly builds</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" id="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <div class="section"><h2>RAT (Release Audit Tool) results</h2><p>The following document contains the results of <a href="http://code.google.com/p/arat/">RAT (Release Audit Tool)</a>.</p><p><div class="source"><pre>
+*****************************************************
+Summary
+-------
+Notes: 3
+Binaries: 91
+Archives: 2
+Standards: 464
+
+Apache Licensed: 150
+Generated Documents: 108
+
+JavaDocs are generated and so license header is optional
+Generated files do not required license headers
+
+206 Unknown Licenses
+
+*******************************
+
+Archives (+ indicates readable, $ unreadable):
+
+ + james-project/stage/org.apache.maven.skins/jars/maven-default-skin-1.0.jar
+ + james-project/maven-skin/stage/org.apache/jars/apache-jar-resource-bundle-1.2.jar
+
+*****************************************************
+ Files with AL headers will be marked L
+ Binary files (which do not require AL headers) will be marked B
+ Compressed archives will be marked A
+ Notices, licenses etc will be marked N
+ AL pom.xml
+ AL james-project/pom.xml
+ !????? james-project/HOWTO.txt
+ A james-project/stage/org.apache.maven.skins/jars/maven-default-skin-1.0.jar
+ AL james-project/stage/org.apache.maven.skins/poms/maven-default-skin-1.0.pom
+ AL james-project/src/site/site.xml
+ AL james-project/maven-skin/pom.xml
+ N james-project/maven-skin/README.txt
+ A james-project/maven-skin/stage/org.apache/jars/apache-jar-resource-bundle-1.2.jar
+ B james-project/maven-skin/src/main/resources/images/newwindow.png
+ B james-project/maven-skin/src/main/resources/images/icon_error_sml.gif
+ B james-project/maven-skin/src/main/resources/images/button-bottom.gif
+ B james-project/maven-skin/src/main/resources/images/icon_success_sml.gif
+ B james-project/maven-skin/src/main/resources/images/icon_info_sml.gif
+ B james-project/maven-skin/src/main/resources/images/h2feather.gif
+ B james-project/maven-skin/src/main/resources/images/icon_warning_sml.gif
+ B james-project/maven-skin/src/main/resources/images/button-top.gif
+ B james-project/maven-skin/src/main/resources/images/expanded.gif
+ B james-project/maven-skin/src/main/resources/images/external.png
+ B james-project/maven-skin/src/main/resources/images/void.gif
+ B james-project/maven-skin/src/main/resources/images/collapsed.gif
+ B james-project/maven-skin/src/main/resources/images/h4.jpg
+ !????? james-project/maven-skin/src/main/resources/css/print.css
+ !????? james-project/maven-skin/src/main/resources/css/maven-base.css
+ AL james-project/maven-skin/src/main/resources/css/maven-theme.css
+ !????? james-project/maven-skin/src/main/resources/META-INF/maven/site.vm
+ !????? james-project/HOWTO_RELEASE.txt
+ AL james-project/project/pom.xml
+ B james-project/project/src/site/resources/images/asf-logo-reduced.gif
+ B james-project/project/src/site/resources/images/james-project-logo.gif
+ !????? james-project/project/src/site/resources/download.cgi
+ !????? james-project/project/src/site/resources/css/site.css
+ B james-project/project/src/site/resources/favicon.ico
+ !????? james-project/project/src/site/resources/downloadunstable.cgi
+ !????? james-project/project/src/site/resources/robots.txt
+ AL james-project/project/src/site/xdoc/mail.xml
+ AL james-project/project/src/site/xdoc/weare.xml
+ !????? james-project/project/src/site/xdoc/newsarchive.xml
+ AL james-project/project/src/site/xdoc/download.xml
+ AL james-project/project/src/site/xdoc/code-standards.xml
+ AL james-project/project/src/site/xdoc/guidelines.xml
+ !????? james-project/project/src/site/xdoc/index.xml
+ AL james-project/project/src/site/xdoc/contribute.xml
+ !????? james-project/project/src/site/xdoc/license.xml
+ AL james-project/project/src/site/xdoc/downloadunstable.xml
+ AL james-project/project/src/site/site.xml
+ AL james-project/project/server/pom.xml
+ B james-project/project/server/src/site/resources/images/james_config_load_balance.png
+ B james-project/project/server/src/site/resources/images/james_config_secondary.png
+ B james-project/project/server/src/site/resources/images/james-server-logo.gif
+ B james-project/project/server/src/site/resources/images/asf-logo-reduced.gif
+ B james-project/project/server/src/site/resources/images/james_config_smart_host.png
+ AL james-project/project/server/src/site/resources/css/site.css
+ !????? james-project/project/server/src/site/resources/rfclist/pop3/rfc1939.txt
+ !????? james-project/project/server/src/site/resources/rfclist/pop3/rfc1734.txt
+ !????? james-project/project/server/src/site/resources/rfclist/pop3/rfc1725.txt
+ !????? james-project/project/server/src/site/resources/rfclist/basic/rfc0822.txt
+ !????? james-project/project/server/src/site/resources/rfclist/basic/rfc2046.txt
+ !????? james-project/project/server/src/site/resources/rfclist/basic/rfc2822.txt
+ !????? james-project/project/server/src/site/resources/rfclist/basic/rfc2045.txt
+ !????? james-project/project/server/src/site/resources/rfclist/basic/rfc1123.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2595.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2359.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2060.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2221.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2195.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2086.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2177.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2088.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2180.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2342.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2683.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2192.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2193.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc1731.txt
+ !????? james-project/project/server/src/site/resources/rfclist/imap4/rfc2087.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc1830.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc1869.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc2142.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc0821.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc1870.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc0974.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc2034.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc1652.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc1893.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc1985.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc1891.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc2197.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc2554.txt
+ !????? james-project/project/server/src/site/resources/rfclist/smtp/rfc2821.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2252.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2829.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2255.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2251.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2256.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc3377.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2253.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2254.txt
+ !????? james-project/project/server/src/site/resources/rfclist/ldap/rfc2830.txt
+ !????? james-project/project/server/src/site/resources/rfclist/nntp/draft-ietf-nntpext-base-13.txt
+ !????? james-project/project/server/src/site/resources/rfclist/nntp/rfc2980.txt
+ !????? james-project/project/server/src/site/resources/rfclist/nntp/rfc0977.txt
+ !????? james-project/project/server/src/site/resources/rfclist/nntp/rfc1036.txt
+ AL james-project/project/server/src/site/xdoc/todo.xml
+ AL james-project/project/server/src/site/xdoc/design_objectives.xml
+ AL james-project/project/server/src/site/xdoc/index.xml
+ AL james-project/project/server/src/site/xdoc/archive/usingTLS_v1_2.xml
+ AL james-project/project/server/src/site/xdoc/archive/architecture_v1_2.xml
+ AL james-project/project/server/src/site/xdoc/archive/configuration_v2_0.xml
+ AL james-project/project/server/src/site/xdoc/archive/usingJDBC_v2.0.xml
+ AL james-project/project/server/src/site/xdoc/archive/announcement_2_1.xml
+ AL james-project/project/server/src/site/xdoc/archive/usingLDAP_v1_2.xml
+ AL james-project/project/server/src/site/xdoc/archive/document_archive.xml
+ AL james-project/project/server/src/site/xdoc/archive/architecture_v2_0.xml
+ AL james-project/project/server/src/site/xdoc/archive/install.xml
+ AL james-project/project/server/src/site/xdoc/rfclist.xml
+ AL james-project/project/server/src/site/xdoc/james_and_sendmail.xml
+ AL james-project/project/server/src/site/xdoc/FAQ.xml
+ AL james-project/project/server/src/site/site.xml
+ AL james-project/project/server/2.2.0/pom.xml
+ B james-project/project/server/2.2.0/src/site/resources/images/james-server-logo.gif
+ B james-project/project/server/2.2.0/src/site/resources/images/asf-logo-reduced.gif
+ AL james-project/project/server/2.2.0/src/site/xdoc/fetchpop_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/repositories.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/provided_matchers.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/spoolmanager_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/smtp_auth.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/build_instructions.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/adding_users.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/custom_mailet.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/spoolmanager.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/pop3_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/provided_mailets.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/summary.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/mailing_lists.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/installation_instructions.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/fetchmail_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/index.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/serverwide_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/dns_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/using_database.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/usingTLS.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/nntp_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/changelog.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/smtp_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/remotemanager_configuration.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/custom_matcher.xml
+ AL james-project/project/server/2.2.0/src/site/xdoc/mailet_api.xml
+ !????? james-project/project/server/2.2.0/src/site/site.xml
+ !????? site/plugins.html
+ B site/images/newwindow.png
+ B site/images/icon_error_sml.gif
+ B site/images/james-mpt-logo.gif
+ B site/images/close.gif
+ B site/images/button-bottom.gif
+ B site/images/icon_success_sml.gif
+ B site/images/asf-logo-reduced.gif
+ B site/images/icon_info_sml.gif
+ B site/images/h2feather.gif
+ B site/images/icon_warning_sml.gif
+ B site/images/button-top.gif
+ B site/images/expanded.gif
+ B site/images/external.png
+ B site/images/void.gif
+ B site/images/collapsed.gif
+ B site/images/h4.jpg
+ !????? site/index.html
+ !????? site/xref/index.html
+ !????? site/xref/allclasses-frame.html
+ !????? site/xref/overview-frame.html
+ GEN site/xref/stylesheet.css
+ !????? site/xref/overview-summary.html
+ AL site/xref/org/apache/james/mpt/AbstractSimpleScriptedTestProtocol.html
+ AL site/xref/org/apache/james/mpt/SystemLoggingMonitor.html
+ AL site/xref/org/apache/james/mpt/Runner.html
+ AL site/xref/org/apache/james/mpt/ExternalSession.html
+ AL site/xref/org/apache/james/mpt/AbstractProtocolTestFramework.html
+ AL site/xref/org/apache/james/mpt/ScriptedUserAdder.html
+ AL site/xref/org/apache/james/mpt/ant/MailProtocolTestTask.html
+ !????? site/xref/org/apache/james/mpt/ant/package-frame.html
+ !????? site/xref/org/apache/james/mpt/ant/package-summary.html
+ AL site/xref/org/apache/james/mpt/ProtocolSession.html
+ AL site/xref/org/apache/james/mpt/HostSystem.html
+ AL site/xref/org/apache/james/mpt/Session.html
+ AL site/xref/org/apache/james/mpt/ProtocolInteractor.html
+ AL site/xref/org/apache/james/mpt/InvalidServerResponseException.html
+ AL site/xref/org/apache/james/mpt/ProtocolSessionBuilder.html
+ !????? site/xref/org/apache/james/mpt/package-frame.html
+ AL site/xref/org/apache/james/mpt/SessionFactory.html
+ !????? site/xref/org/apache/james/mpt/package-summary.html
+ AL site/xref/org/apache/james/mpt/ExternalHostSystem.html
+ AL site/xref/org/apache/james/mpt/UserAdder.html
+ AL site/xref/org/apache/james/mpt/ExternalSessionFactory.html
+ AL site/xref/org/apache/james/mpt/NullMonitor.html
+ AL site/xref/org/apache/james/mpt/Monitor.html
+ AL site/xref/org/apache/james/mpt/app/RunScript.html
+ !????? site/xref/org/apache/james/mpt/app/package-frame.html
+ !????? site/xref/org/apache/james/mpt/app/package-summary.html
+ AL site/xref/org/apache/james/mpt/app/Main.html
+ !????? site/dependency-convergence.html
+ AL site/license.html
+ !????? site/xref-test/index.html
+ !????? site/xref-test/allclasses-frame.html
+ !????? site/xref-test/overview-frame.html
+ GEN site/xref-test/stylesheet.css
+ !????? site/xref-test/overview-summary.html
+ AL site/xref-test/org/apache/james/mpt/TestExternalHostSystem.html
+ AL site/xref-test/org/apache/james/mpt/TestDiscardProtocol.html
+ AL site/xref-test/org/apache/james/mpt/TestFileProtocolSessionBuilder.html
+ AL site/xref-test/org/apache/james/mpt/ant/TestRunScripts.html
+ !????? site/xref-test/org/apache/james/mpt/ant/package-frame.html
+ !????? site/xref-test/org/apache/james/mpt/ant/package-summary.html
+ AL site/xref-test/org/apache/james/mpt/ant/TestAddUser.html
+ !????? site/xref-test/org/apache/james/mpt/package-frame.html
+ !????? site/xref-test/org/apache/james/mpt/package-summary.html
+ AL site/xref-test/org/apache/james/mpt/DiscardProtocol.html
+ AL site/xref-test/org/apache/james/mpt/TestScriptedUserAdder.html
+ !????? site/main/plugins.html
+ B site/main/images/newwindow.png
+ B site/main/images/icon_error_sml.gif
+ B site/main/images/james-mpt-logo.gif
+ B site/main/images/close.gif
+ B site/main/images/button-bottom.gif
+ B site/main/images/icon_success_sml.gif
+ B site/main/images/asf-logo-reduced.gif
+ B site/main/images/icon_info_sml.gif
+ B site/main/images/h2feather.gif
+ B site/main/images/icon_warning_sml.gif
+ B site/main/images/button-top.gif
+ B site/main/images/expanded.gif
+ B site/main/images/external.png
+ B site/main/images/void.gif
+ B site/main/images/collapsed.gif
+ B site/main/images/h4.jpg
+ !????? site/main/index.html
+ !????? site/main/xref/index.html
+ !????? site/main/xref/allclasses-frame.html
+ !????? site/main/xref/overview-frame.html
+ GEN site/main/xref/stylesheet.css
+ !????? site/main/xref/overview-summary.html
+ AL site/main/xref/org/apache/james/mpt/AbstractSimpleScriptedTestProtocol.html
+ AL site/main/xref/org/apache/james/mpt/SystemLoggingMonitor.html
+ AL site/main/xref/org/apache/james/mpt/Runner.html
+ AL site/main/xref/org/apache/james/mpt/ExternalSession.html
+ AL site/main/xref/org/apache/james/mpt/AbstractProtocolTestFramework.html
+ AL site/main/xref/org/apache/james/mpt/ScriptedUserAdder.html
+ AL site/main/xref/org/apache/james/mpt/ProtocolSession.html
+ AL site/main/xref/org/apache/james/mpt/HostSystem.html
+ AL site/main/xref/org/apache/james/mpt/Session.html
+ AL site/main/xref/org/apache/james/mpt/ProtocolInteractor.html
+ AL site/main/xref/org/apache/james/mpt/InvalidServerResponseException.html
+ AL site/main/xref/org/apache/james/mpt/ProtocolSessionBuilder.html
+ !????? site/main/xref/org/apache/james/mpt/package-frame.html
+ AL site/main/xref/org/apache/james/mpt/SessionFactory.html
+ !????? site/main/xref/org/apache/james/mpt/package-summary.html
+ AL site/main/xref/org/apache/james/mpt/ExternalHostSystem.html
+ AL site/main/xref/org/apache/james/mpt/UserAdder.html
+ AL site/main/xref/org/apache/james/mpt/ExternalSessionFactory.html
+ AL site/main/xref/org/apache/james/mpt/NullMonitor.html
+ AL site/main/xref/org/apache/james/mpt/Monitor.html
+ !????? site/main/dependency-convergence.html
+ AL site/main/license.html
+ !????? site/main/xref-test/index.html
+ !????? site/main/xref-test/allclasses-frame.html
+ !????? site/main/xref-test/overview-frame.html
+ GEN site/main/xref-test/stylesheet.css
+ !????? site/main/xref-test/overview-summary.html
+ AL site/main/xref-test/org/apache/james/mpt/TestExternalHostSystem.html
+ AL site/main/xref-test/org/apache/james/mpt/TestDiscardProtocol.html
+ AL site/main/xref-test/org/apache/james/mpt/TestFileProtocolSessionBuilder.html
+ !????? site/main/xref-test/org/apache/james/mpt/package-frame.html
+ !????? site/main/xref-test/org/apache/james/mpt/package-summary.html
+ AL site/main/xref-test/org/apache/james/mpt/DiscardProtocol.html
+ AL site/main/xref-test/org/apache/james/mpt/TestScriptedUserAdder.html
+ !????? site/main/integration.html
+ !????? site/main/project-summary.html
+ !????? site/main/project-info.html
+ AL site/main/doap_apache-james-mpt-main.rdf
+ !????? site/main/issue-tracking.html
+ !????? site/main/surefire-report.html
+ !????? site/main/jxr.html
+ !????? site/main/plugin-management.html
+ AL site/main/doap_apache-james-mtp.rdf
+ !????? site/main/project-reports.html
+ !????? site/main/taglist.html
+ AL site/main/dependencies.html
+ !????? site/main/emma/index.html
+ !????? site/main/emma/coverage.xml
+ AL site/main/emma/_files/b.html
+ AL site/main/emma/_files/c.html
+ !????? site/main/emma/_files/0.html
+ AL site/main/emma/_files/7.html
+ AL site/main/emma/_files/3.html
+ AL site/main/emma/_files/4.html
+ AL site/main/emma/_files/5.html
+ AL site/main/emma/_files/1.html
+ AL site/main/emma/_files/a.html
+ AL site/main/emma/_files/6.html
+ AL site/main/emma/_files/9.html
+ AL site/main/emma/_files/8.html
+ AL site/main/emma/_files/2.html
+ !????? site/main/mail-lists.html
+ !????? site/main/jira-report.html
+ !????? site/main/css/print.css
+ !????? site/main/css/maven-base.css
+ AL site/main/css/maven-theme.css
+ !????? site/main/rat-report.html
+ !????? site/main/source-repository.html
+ !????? site/main/team-list.html
+ !????? site/main/dependency-management.html
+ !????? site/integration.html
+ !????? site/project-summary.html
+ !????? site/antlib/plugins.html
+ B site/antlib/images/newwindow.png
+ B site/antlib/images/icon_error_sml.gif
+ B site/antlib/images/james-mpt-logo.gif
+ B site/antlib/images/close.gif
+ B site/antlib/images/button-bottom.gif
+ B site/antlib/images/icon_success_sml.gif
+ B site/antlib/images/asf-logo-reduced.gif
+ B site/antlib/images/icon_info_sml.gif
+ B site/antlib/images/h2feather.gif
+ B site/antlib/images/icon_warning_sml.gif
+ B site/antlib/images/button-top.gif
+ B site/antlib/images/expanded.gif
+ B site/antlib/images/external.png
+ B site/antlib/images/void.gif
+ B site/antlib/images/collapsed.gif
+ B site/antlib/images/h4.jpg
+ !????? site/antlib/index.html
+ !????? site/antlib/xref/index.html
+ !????? site/antlib/xref/allclasses-frame.html
+ !????? site/antlib/xref/overview-frame.html
+ GEN site/antlib/xref/stylesheet.css
+ !????? site/antlib/xref/overview-summary.html
+ AL site/antlib/xref/org/apache/james/mpt/ant/MailProtocolTestTask.html
+ !????? site/antlib/xref/org/apache/james/mpt/ant/package-frame.html
+ !????? site/antlib/xref/org/apache/james/mpt/ant/package-summary.html
+ !????? site/antlib/dependency-convergence.html
+ AL site/antlib/license.html
+ !????? site/antlib/xref-test/index.html
+ !????? site/antlib/xref-test/allclasses-frame.html
+ !????? site/antlib/xref-test/overview-frame.html
+ GEN site/antlib/xref-test/stylesheet.css
+ !????? site/antlib/xref-test/overview-summary.html
+ AL site/antlib/xref-test/org/apache/james/mpt/ant/TestRunScripts.html
+ !????? site/antlib/xref-test/org/apache/james/mpt/ant/package-frame.html
+ !????? site/antlib/xref-test/org/apache/james/mpt/ant/package-summary.html
+ AL site/antlib/xref-test/org/apache/james/mpt/ant/TestAddUser.html
+ !????? site/antlib/integration.html
+ !????? site/antlib/project-summary.html
+ AL site/antlib/doap_apache-james-mtp-antlib.rdf
+ !????? site/antlib/project-info.html
+ !????? site/antlib/issue-tracking.html
+ AL site/antlib/doap_apache-james-mpt-antlib.rdf
+ !????? site/antlib/surefire-report.html
+ !????? site/antlib/jxr.html
+ !????? site/antlib/plugin-management.html
+ !????? site/antlib/project-reports.html
+ !????? site/antlib/taglist.html
+ AL site/antlib/dependencies.html
+ !????? site/antlib/emma/index.html
+ !????? site/antlib/emma/coverage.xml
+ !????? site/antlib/emma/_files/0.html
+ AL site/antlib/emma/_files/1.html
+ !????? site/antlib/mail-lists.html
+ !????? site/antlib/jira-report.html
+ !????? site/antlib/css/print.css
+ !????? site/antlib/css/maven-base.css
+ AL site/antlib/css/maven-theme.css
+ !????? site/antlib/rat-report.html
+ !????? site/antlib/source-repository.html
+ !????? site/antlib/team-list.html
+ !????? site/antlib/dependency-management.html
+ !????? site/project-info.html
+ !????? site/issue-tracking.html
+ GEN site/testapidocs/index.html
+ GEN site/testapidocs/constant-values.html
+ GEN site/testapidocs/index-all.html
+ GEN site/testapidocs/allclasses-frame.html
+ !????? site/testapidocs/package-list
+ GEN site/testapidocs/overview-frame.html
+ GEN site/testapidocs/allclasses-noframe.html
+ GEN site/testapidocs/stylesheet.css
+ B site/testapidocs/resources/inherit.gif
+ GEN site/testapidocs/overview-summary.html
+ GEN site/testapidocs/overview-tree.html
+ GEN site/testapidocs/help-doc.html
+ GEN site/testapidocs/org/apache/james/mpt/TestExternalHostSystem.html
+ GEN site/testapidocs/org/apache/james/mpt/package-use.html
+ GEN site/testapidocs/org/apache/james/mpt/package-tree.html
+ GEN site/testapidocs/org/apache/james/mpt/TestDiscardProtocol.html
+ GEN site/testapidocs/org/apache/james/mpt/DiscardProtocol.Record.html
+ GEN site/testapidocs/org/apache/james/mpt/TestFileProtocolSessionBuilder.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/package-use.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/package-tree.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/TestRunScripts.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/package-frame.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/package-summary.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/TestAddUser.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/class-use/TestRunScripts.html
+ GEN site/testapidocs/org/apache/james/mpt/ant/class-use/TestAddUser.html
+ GEN site/testapidocs/org/apache/james/mpt/package-frame.html
+ GEN site/testapidocs/org/apache/james/mpt/package-summary.html
+ GEN site/testapidocs/org/apache/james/mpt/DiscardProtocol.html
+ GEN site/testapidocs/org/apache/james/mpt/class-use/TestExternalHostSystem.html
+ GEN site/testapidocs/org/apache/james/mpt/class-use/TestDiscardProtocol.html
+ GEN site/testapidocs/org/apache/james/mpt/class-use/DiscardProtocol.Record.html
+ GEN site/testapidocs/org/apache/james/mpt/class-use/TestFileProtocolSessionBuilder.html
+ GEN site/testapidocs/org/apache/james/mpt/class-use/DiscardProtocol.html
+ GEN site/testapidocs/org/apache/james/mpt/class-use/TestScriptedUserAdder.html
+ GEN site/testapidocs/org/apache/james/mpt/TestScriptedUserAdder.html
+ GEN site/testapidocs/deprecated-list.html
+ !????? site/surefire-report.html
+ !????? site/cpd.xml
+ !????? site/jxr.html
+ !????? site/plugin-management.html
+ !????? site/project-reports.html
+ !????? site/dependencies.html
+ !????? site/mail-lists.html
+ !????? site/pmd.xml
+ !????? site/jira-report.html
+ !????? site/pmd.html
+ GEN site/apidocs/serialized-form.html
+ GEN site/apidocs/index.html
+ GEN site/apidocs/constant-values.html
+ GEN site/apidocs/index-all.html
+ GEN site/apidocs/allclasses-frame.html
+ !????? site/apidocs/package-list
+ GEN site/apidocs/overview-frame.html
+ GEN site/apidocs/allclasses-noframe.html
+ GEN site/apidocs/stylesheet.css
+ B site/apidocs/resources/inherit.gif
+ GEN site/apidocs/overview-summary.html
+ GEN site/apidocs/overview-tree.html
+ GEN site/apidocs/help-doc.html
+ GEN site/apidocs/org/apache/james/mpt/AbstractSimpleScriptedTestProtocol.html
+ GEN site/apidocs/org/apache/james/mpt/SystemLoggingMonitor.html
+ GEN site/apidocs/org/apache/james/mpt/Runner.html
+ GEN site/apidocs/org/apache/james/mpt/package-use.html
+ GEN site/apidocs/org/apache/james/mpt/AbstractProtocolTestFramework.html
+ GEN site/apidocs/org/apache/james/mpt/package-tree.html
+ GEN site/apidocs/org/apache/james/mpt/ScriptedUserAdder.html
+ GEN site/apidocs/org/apache/james/mpt/ant/MailProtocolTestTask.html
+ GEN site/apidocs/org/apache/james/mpt/ant/package-use.html
+ GEN site/apidocs/org/apache/james/mpt/ant/package-tree.html
+ GEN site/apidocs/org/apache/james/mpt/ant/MailProtocolTestTask.AddUser.html
+ GEN site/apidocs/org/apache/james/mpt/ant/package-frame.html
+ GEN site/apidocs/org/apache/james/mpt/ant/package-summary.html
+ GEN site/apidocs/org/apache/james/mpt/ant/class-use/MailProtocolTestTask.html
+ GEN site/apidocs/org/apache/james/mpt/ant/class-use/MailProtocolTestTask.AddUser.html
+ GEN site/apidocs/org/apache/james/mpt/ProtocolSession.html
+ GEN site/apidocs/org/apache/james/mpt/HostSystem.html
+ GEN site/apidocs/org/apache/james/mpt/Session.html
+ GEN site/apidocs/org/apache/james/mpt/ProtocolInteractor.html
+ GEN site/apidocs/org/apache/james/mpt/InvalidServerResponseException.html
+ GEN site/apidocs/org/apache/james/mpt/ProtocolSessionBuilder.html
+ GEN site/apidocs/org/apache/james/mpt/package-frame.html
+ GEN site/apidocs/org/apache/james/mpt/SessionFactory.html
+ GEN site/apidocs/org/apache/james/mpt/package-summary.html
+ GEN site/apidocs/org/apache/james/mpt/ExternalHostSystem.html
+ GEN site/apidocs/org/apache/james/mpt/HostSystem.Continuation.html
+ GEN site/apidocs/org/apache/james/mpt/UserAdder.html
+ GEN site/apidocs/org/apache/james/mpt/ExternalSessionFactory.html
+ GEN site/apidocs/org/apache/james/mpt/NullMonitor.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/AbstractSimpleScriptedTestProtocol.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/SystemLoggingMonitor.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/Runner.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/AbstractProtocolTestFramework.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/ScriptedUserAdder.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/ProtocolSession.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/HostSystem.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/Session.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/ProtocolInteractor.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/InvalidServerResponseException.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/ProtocolSessionBuilder.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/SessionFactory.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/ExternalHostSystem.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/HostSystem.Continuation.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/UserAdder.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/ExternalSessionFactory.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/NullMonitor.html
+ GEN site/apidocs/org/apache/james/mpt/class-use/Monitor.html
+ GEN site/apidocs/org/apache/james/mpt/Monitor.html
+ GEN site/apidocs/org/apache/james/mpt/app/package-use.html
+ GEN site/apidocs/org/apache/james/mpt/app/package-tree.html
+ GEN site/apidocs/org/apache/james/mpt/app/package-frame.html
+ GEN site/apidocs/org/apache/james/mpt/app/package-summary.html
+ GEN site/apidocs/org/apache/james/mpt/app/Main.html
+ GEN site/apidocs/org/apache/james/mpt/app/class-use/Main.html
+ GEN site/apidocs/deprecated-list.html
+ !????? site/css/print.css
+ !????? site/css/maven-base.css
+ AL site/css/maven-theme.css
+ !????? site/rat-report.html
+ !????? site/release-notes.html
+ !????? site/source-repository.html
+ !????? site/team-list.html
+ AL site/doap_apache-james-mpt-project.rdf
+ !????? site/dependency-management.html
+ !????? site/app/plugins.html
+ B site/app/images/newwindow.png
+ B site/app/images/icon_error_sml.gif
+ B site/app/images/james-mpt-logo.gif
+ B site/app/images/close.gif
+ B site/app/images/button-bottom.gif
+ B site/app/images/icon_success_sml.gif
+ B site/app/images/asf-logo-reduced.gif
+ B site/app/images/icon_info_sml.gif
+ B site/app/images/h2feather.gif
+ B site/app/images/icon_warning_sml.gif
+ B site/app/images/button-top.gif
+ B site/app/images/expanded.gif
+ B site/app/images/external.png
+ B site/app/images/void.gif
+ B site/app/images/collapsed.gif
+ B site/app/images/h4.jpg
+ !????? site/app/index.html
+ !????? site/app/xref/index.html
+ !????? site/app/xref/allclasses-frame.html
+ !????? site/app/xref/overview-frame.html
+ GEN site/app/xref/stylesheet.css
+ !????? site/app/xref/overview-summary.html
+ AL site/app/xref/org/apache/james/mpt/app/RunScript.html
+ !????? site/app/xref/org/apache/james/mpt/app/package-frame.html
+ !????? site/app/xref/org/apache/james/mpt/app/package-summary.html
+ AL site/app/xref/org/apache/james/mpt/app/Main.html
+ !????? site/app/dependency-convergence.html
+ AL site/app/license.html
+ !????? site/app/integration.html
+ !????? site/app/project-summary.html
+ !????? site/app/project-info.html
+ !????? site/app/issue-tracking.html
+ !????? site/app/surefire-report.html
+ !????? site/app/jxr.html
+ !????? site/app/plugin-management.html
+ !????? site/app/project-reports.html
+ !????? site/app/taglist.html
+ AL site/app/dependencies.html
+ !????? site/app/emma/index.html
+ !????? site/app/mail-lists.html
+ AL site/app/doap_apache-james-mpt-app.rdf
+ !????? site/app/jira-report.html
+ AL site/app/doap_apache-james-mtp-app.rdf
+ !????? site/app/css/print.css
+ !????? site/app/css/maven-base.css
+ AL site/app/css/maven-theme.css
+ !????? site/app/rat-report.html
+ !????? site/app/source-repository.html
+ !????? site/app/team-list.html
+ !????? site/app/dependency-management.html
+ !????? site/cpd.html
+ B src/site/resources/images/james-mpt-logo.gif
+ B src/site/resources/images/asf-logo-reduced.gif
+ AL src/site/xdoc/index.xml
+ AL src/site/site.xml
+ AL src/site/apt/release-notes.apt
+ N RELEASE_NOTES.txt
+ !????? LICENSE.apache
+ N BUILDING.txt
+
+ *****************************************************
+ Printing headers for files without AL header...
+
+
+ =======================================================================
+ ==james-project/HOWTO.txt
+ =======================================================================
+ How to build and publish the website:
+
+ 1. Install Apache Maven 2.0.6+ and make its binary 'mvn' available on your PATH.
+ 2. run "mvn -U -Plocal,parent clean install site:stage -DstagingDirectory={path}".
+ - the -U will force mvn to update plugins (check new installed skin when building
+ the project site.
+ - the -Plocal will force mvn to not lookup remote maven repositories for standard
+ dependencies.
+ - the -Pparent will add the local "stage" repository to the build (this is needed
+ so that the site generation for the parent folder will find the default maven
+ skin (this is only a workaround: the default skin is not used).
+ - install is needed because the site generated in the project module will search
+ for an installed skin.
+ 3. Test the built site in your browser from the {path} folder
+ 4. If everything looks OK, copy the {path} folder to the checkout of james/site/trunk/www
+ folder.
+ 5. If you are on windows make sure endlines are LF only
+ hint: running "ant" from james/site/trunk/ will do this (this will take a lot).
+ 6. Commit changes to SVN
+ 7. Review generated pages on svn.apache.org/repos/asf/james/site/trunk/www
+ 8. svn-up on minotaur
+ 9. Wait for the changes to replicate to the Apache web server or setup 140.211.11.10:80 as
+ a proxy to review the changes (described here: http://www.apache.org/dev/project-site.html)
+
+The logical tree of the poms is the following
+
+james-parent (parent/pom.xml) is the main parent.
+|- maven-skin (maven-skin/pom.xml) is our skin
+'- james-project (pom.xml)
+ '- james-server-root (server/pom.xml) is the parent pom for JAMES server.
+ '- james-server-2.2.0 (server/2.2.0/pom.xml) is the static website for old 2.2.0 documentation.
+
+The "james-parent" artifact is needed because "james-project" uses the maven-skin but they needed
+to share some common data so they cannot depend on each-other but on a third "parent" pom.
+
+ =======================================================================
+ ==james-project/maven-skin/src/main/resources/css/print.css
+ =======================================================================
+ #banner, #footer, #leftcol, #breadcrumbs, .docs #toc, .docs .courtesylinks, #leftColumn, #navColumn {
+ display: none !important;
+}
+#bodyColumn, body.docs div.docs {
+ margin: 0 !important;
+ border: none !important
+}
+
+ =======================================================================
+ ==james-project/maven-skin/src/main/resources/css/maven-base.css
+ =======================================================================
+ body {
+ margin: 0px;
+ padding: 0px;
+}
+img {
+ border:none;
+}
+table {
+ padding:0px;
+ width: 100%;
+ margin-left: -2px;
+ margin-right: -2px;
+}
+acronym {
+ cursor: help;
+ border-bottom: 1px dotted #feb;
+}
+table.bodyTable th, table.bodyTable td {
+ padding: 2px 4px 2px 4px;
+ vertical-align: top;
+}
+div.clear{
+ clear:both;
+ visibility: hidden;
+}
+div.clear hr{
+ display: none;
+}
+#bannerLeft, #bannerRight {
+ font-size: xx-large;
+ font-weight: bold;
+}
+#bannerLeft img, #bannerRight img {
+ margin: 0px;
+}
+.xleft, #bannerLeft img {
+ float:left;
+ text-shadow: #7CFC00;
+}
+.xright, #bannerRight img {
+ float:right;
+ text-shadow: #7CFC00;
+}
+#banner {
+ padding: 0px;
+}
+#banner img {
+ border: none;
+}
+#breadcrumbs {
+
+ =======================================================================
+ ==james-project/maven-skin/src/main/resources/META-INF/maven/site.vm
+ =======================================================================
+ <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+#macro ( banner $banner $id )
+ #if ( $banner )
+ #if( $banner.href )
+ <a href="$banner.href" id="$id">
+ #else
+ <span id="$id">
+ #end
+
+ #if( $banner.src )
+ #set ( $src = $banner.src )
+ #if ( ! ( $src.toLowerCase().startsWith("http") || $src.toLowerCase().startsWith("https") ) )
+ #set ( $src = $PathTool.calculateLink( $src, . ) )
+ #set ( $src = $src.replaceAll( "\\", "/" ) )
+ #end
+ #if ( $banner.alt )
+ #set ( $alt = $banner.alt )
+ #else
+ #set ( $alt = "" )
+ #end
+ <img src="$src" alt="$alt" />
+ #else
+ $banner.name
+ #end
+
+ #if( $banner.href )
+ </a>
+ #else
+ </span>
+ #end
+ #end
+#end
+
+#macro ( links $links )
+ #set ( $counter = 0 )
+ #foreach( $item in $links )
+ #set ( $counter = $counter + 1 )
+ #set ( $currentItemHref = $PathTool.calculateLink( $item.href, . ) )
+ #set ( $currentItemHref = $currentItemHref.replaceAll( "\\", "/" ) )
+ <a href="$currentItemHref">$item.name</a>
+ #if ( $links.size() > $counter )
+ |
+ #end
+ #end
+#end
+
+#macro ( breadcrumbs $breadcrumbs )
+ #set ( $counter = 0 )
+ #foreach( $item in $breadcrumbs )
+
+ =======================================================================
+ ==james-project/HOWTO_RELEASE.txt
+ =======================================================================
+ Howto release via maven release plugin:
+
+ 1 One time setup steps:
+ Windows:
+ 1 Create and install a SSH key
+ 1 Install PuTTY
+ 2 Use PuttyGen to create a SSH key and export the key as openssh key
+ 3 Use PuTTY to ssh to people.apache.org
+ 4 Create a ~/.ssh folder
+ 5 Use pscp your SSH public key to ~/authorized_keys
+ 6 Configure putty to use your private key and save the session
+ 7 Check you can login people.apache.org with your key
+
+ 2 Install cygwin
+ 1 Install CygWin
+ 2 Use ssh to login to people.apache.org . This is needed to get the correct entry in your known_hosts file
+ 3 Copy the known_hosts file to your $(homedir)/.ssh/
+
+ Linux / Unix:
+ 1 Create and install a SSH key
+ 1 Install ssh ( this should be installed by default on must linux / unix systems)
+ 2 Use "ssh-keygen -t dsa" to generate a new private/public key
+ 3 Use ssh to login people.apache.org and add the content of "~/.ssh/id_dsa.pub" (local) to "~/.ssh/authorized_keys" (people.apache.org)
+ 4 Check you can login people.apache.org via your private key
+
+ 2 Some linux version (e.g: kubuntu 7) uses an hashed version of the known_hosts file.
+ This file is not understood by maven. So the easiest thing is to run an interactive maven command
+ using the ssh access to people.apache.org.
+ mvn deploy:deploy-file
+ \ -Durl=scp://people.apache.org/home/$(YOURHOME)/public_html/a-random-repository
+ \ -DrepositoryId=a_random.id
+ \ -Dfile=path_to_a_local_file.jar
+ \ -DgroupId=org.some.group
+ \ -DartifactId=your-artifact
+ \ -Dversion=1.0
+ \ -Dpackaging=jar
+ This will try connecting via ssh to people.apache.org and interactively will ask you to accept the new
+ host key.
+ Run this a second time and it HAVE TO work without asking anything. If it keep asking to accept
+ the key for an unknown host you will not be able to make the release.
+
+
+
+ General:
+ 1 Install Apache Maven 2.0.6+ and make its binary 'mvn' available on your PATH.
+
+ 2 Create a settings.xml in your .m2 directory with the following content:
+
+ <settings xmlns="http://maven.apache.org/POM/4.0.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+
+ =======================================================================
+ ==james-project/project/src/site/resources/download.cgi
+ =======================================================================
+ #!/bin/sh
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+# python includes correctly)
+cd /www/www.apache.org/dyn/mirrors
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*
+
+ =======================================================================
+ ==james-project/project/src/site/resources/css/site.css
+ =======================================================================
+ #newsbox {
+ margin: 20px 0px 0px 20px;
+ padding: 10px;
+ border: 1px solid #ccc;
+ background-color: white;
+ background-image: url(../images/button-top.gif);
+ background-repeat: repeat-x;
+ width: 260px;
+}
+#newsboxspacer {
+ float: right;
+ margin: 0px 0px 10px 10px;
+ background-color: white;
+}
+
+#newsbox ul {
+ padding-left: 15px;
+}
+
+#newsbox div {
+ margin-left: 0px;
+}
+
+#newsbox li {
+ margin-bottom: 5px;
+}
+
+#apacheconbox {
+ margin: 20px 0px 0px 20px;
+ padding: 10px;
+ border: 1px solid #ccc;
+ background-color: white;
+ background-image: url(../images/button-top.gif);
+ background-repeat: repeat-x;
+}
+#apacheconspacer {
+ float: right;
+ margin: 0px 0px 10px 10px;
+ background-color: white;
+}
+
+ =======================================================================
+ ==james-project/project/src/site/resources/downloadunstable.cgi
+ =======================================================================
+ #!/bin/sh
+# Wrapper script around mirrors.cgi script
+# (we must change to that directory in order for python to pick up the
+# python includes correctly)
+cd /www/www.apache.org/dyn/mirrors
+/www/www.apache.org/dyn/mirrors/mirrors.cgi $*
+
+ =======================================================================
+ ==james-project/project/src/site/resources/robots.txt
+ =======================================================================
+ # /robots.txt file for http://james.apache.org
+
+User-agent: *
+Disallow: /CVS
+Disallow: /images
+
+ =======================================================================
+ ==james-project/project/src/site/xdoc/newsarchive.xml
+ =======================================================================
+ <?xml version="1.0"?>
+<document>
+ <properties>
+ <title>News Archive</title>
+ <author email="site-dev@james.apache.org">JAMES Project Web Team</author>
+ </properties>
+ <body>
+ <section name="News">
+ <div id="apacheconspacer">
+ <div id="apacheconbox">
+ <iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no" width="250" height="150"></iframe>
+ </div>
+ </div>
+ <subsection name="2008">
+ <a name="10162008"><h4>October/2008 - Mime4j 0.5 released</h4></a>
+ <p>We are proud to announce the <a href="../download.cgi">availability</a> of APACHE Mime4j-0.5. This release addresses a number of important issues discovered since 0.4. In particular, it improves Mime4j ability to deal with malformed data streams including those intentionally crafted to cause excessive CPU and memory utilization that can lead to DoS condition</p>
+ <p>This release also fixes a serious bug that can prevent Mime4j from correctly processing binary content</p>
+ <a name="08262008"><h4>Aug/2008 - Apache JSieve 0.2 released</h4></a>
+ <p>The Apache JAMES Project is pleased to announce the first public release of
+ <a href='http://james.apache.org/jsieve'>Apache JSieve</a> an implementation
+ of <a href='http://www.faqs.org/rfcs/rfc3028.html'>RFC3028 - Sieve: A Mail Filtering Language</a>
+ for Java.
+ </p>
+ <a name="08222008"><h4>Aug/2008 - Mime4j 0.4 released</h4></a>
+ <p>We are proud to announce the <a href="../download.cgi">availability</a> of APACHE Mime4j-0.4. This release brings a number of significant improvements in terms of supported capabilities, flexibility and performance:</p>
+ <ul>
+ <li>Revised and improved public API with support for pull parsing</li>
+ <li>Support for parsing of 'headless' messages transmitted using non SMTP transports such as HTTP</li>
+ <li>Reduced external dependencies. Mime4j is no longer directly dependent on log4j and commons-io</li>
+ <li>Improved parsing performance (up to 10x for large messages)</li>
+ <li>More comprehensive header parsing including support for RFC1864, RFC2045, RFC2183, RFC2557 and RFC3066</li>
+ <li>Revised packaging and exception hierarchy. MimeException now extends IOException</li>
+ </ul>
+ <a name="04082008"><h4>Apr/2008 - jSPF-0.9.6 released</h4></a>
+ <p>We are proud to announce the <a href="../download.cgi">availability</a> release of APACHE jSPF-0.9.6. This release fix two possible NullPointerExceptions and handle the "exp=" modifier correctly.</p>
+
+ <a name="03192008"><h4>Mar/2008 - James publishes project ideas for Google Summer of Code '08</h4></a>
+ <p>The James Team are delighted to announce that we're proposing two project ideas for <a href="http://code.google.com/soc/2008/">Google Summer of Code (GSOC) 2008</a>. The project Ideas are set out on the Apache GSOC wiki <a href="http://wiki.apache.org/general/SummerOfCode2008#james">here</a>.</p>
+ <p>In brief they are:<br/>
+ 1) Develop a VERP Mailet to allow James to write VERP modified return addresses on outbound messages, and an inbound mailet/matcher to identify VERP bounces and invoke configurable "do something" code.
+ <br/>
+ And <br/>
+ 2) James' provided mailing list manager is fine for small closed groups, but lacks the functionality of a more robust MLM, the project is to add some all or more of the following features subscriber and message moderation, double opt-in and bounce handling.</p>
+ </subsection>
+
+ <subsection name="2007">
+ <a name="09252007"><h4>Sept/2007 - jSPF-0.9.5 released</h4></a>
+ <p>We are proud to announce the <a href="downloadunstable.cgi">availability</a> of APACHE jSPF-0.9.5. This release brings initial support for asynchronous processing and is fully RFC4408 compliant.</p>
+ <a name="05302007"><h4>May/2007 - Apache Mime4J 0.3 Final Released</h4></a>
+ <p>After almost 2 years the Apache JAMES team is proud to announce the <a href="download.cgi">availability</a> of Apache Mime4J 0.3. This is the first release under the ASF umbrella.</p>
+
+ =======================================================================
+ ==james-project/project/src/site/xdoc/index.xml
+ =======================================================================
+ <?xml version="1.0"?>
+<document>
+ <properties>
+ <title>Overview</title>
+ <author email="site-dev@james.apache.org">JAMES Project Web Team</author>
+ </properties>
+ <body>
+ <div id="newsboxspacer">
+ <div id="newsbox">
+ <subsection name="News">
+ <ul>
+ <li>Aug/2008 - <ul>
+ <li><a href="newsarchive.html#08262008"><strong>Apache JSieve 0.2</strong> released</a></li>
+ <li><a href="newsarchive.html#08222008"><strong>Mime4j 0.4</strong> released</a></li>
+ </ul>
+ </li>
+ <li>Apr/2008 - <a href="newsarchive.html#04082008"><strong>jSPF 0.9.6</strong> released</a></li>
+ <li>Mar/2008 - <a href="newsarchive.html#03192008">Project ideas for Google Summer of Code '08</a></li>
+ </ul>
+ <i>Read all the news in full in the <a href="newsarchive.html">News Archive</a></i><br/>
+ </subsection>
+ <br />
+ <iframe src="http://www.apache.org/ads/bannerbar.html" style="border-width:0;" frameborder="0" scrolling="no" width="250" height="150"></iframe>
+ </div>
+ </div>
+ <section name="What is JAMES?">
+ <p>
+The Apache JAMES Project delivers a rich set of open source solutions, written in Java, related to internet mail and news.
+ </p>
+ <subsection name='Get Involved'>
+<p>
+<a href='http://projects.apache.org'>Apache projects</a> are developed in an
+<a href='http://www.apache.org/foundation/how-it-works.html#meritocracy'>open</a>
+<a href='http://www.apache.org/foundation/how-it-works.html#management'>collaborative manner</a>. All
+are welcome.
+</p><p>
+We recommend that
+</p>
+<ul>
+<li>Users subscribe to the JAMES user <a href='http://james.apache.org/mail.html'>mailing list</a></li>
+<li>Developers subscribe to the appropriate development <a href='http://james.apache.org/mail.html'>mailing list</a></li>
+</ul>
+ </subsection>
+</section>
+ <section name='Products'>
+ <p>
+The JAMES project contains many products, classified by subproject:
+ </p>
+<ul>
+<li><a href='http://james.apache.org/server'>JAMES Server</a> is an advanced fully functioned
+
+ =======================================================================
+ ==james-project/project/src/site/xdoc/license.xml
+ =======================================================================
+ <?xml version="1.0"?>
+
+<document>
+
+ <properties>
+ <title>Apache Software License</title>
+ <author email="sergek@lokitech.com">Serge Knystautas</author>
+ </properties>
+
+<body>
+<section name="Apache Software License">
+<p>
+ James is released under the Apache Software License
+ listed below:
+</p>
+
+<source><![CDATA[
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/pop3/rfc1939.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group J. Myers
+Request for Comments: 1939 Carnegie Mellon
+STD: 53 M. Rose
+Obsoletes: 1725 Dover Beach Consulting, Inc.
+Category: Standards Track May 1996
+
+
+ Post Office Protocol - Version 3
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Table of Contents
+
+ 1. Introduction ................................................ 2
+ 2. A Short Digression .......................................... 2
+ 3. Basic Operation ............................................. 3
+ 4. The AUTHORIZATION State ..................................... 4
+ QUIT Command ................................................ 5
+ 5. The TRANSACTION State ....................................... 5
+ STAT Command ................................................ 6
+ LIST Command ................................................ 6
+ RETR Command ................................................ 8
+ DELE Command ................................................ 8
+ NOOP Command ................................................ 9
+ RSET Command ................................................ 9
+ 6. The UPDATE State ............................................ 10
+ QUIT Command ................................................ 10
+ 7. Optional POP3 Commands ...................................... 11
+ TOP Command ................................................. 11
+ UIDL Command ................................................ 12
+ USER Command ................................................ 13
+ PASS Command ................................................ 14
+ APOP Command ................................................ 15
+ 8. Scaling and Operational Considerations ...................... 16
+ 9. POP3 Command Summary ........................................ 18
+ 10. Example POP3 Session ....................................... 19
+ 11. Message Format ............................................. 19
+ 12. References ................................................. 20
+ 13. Security Considerations .................................... 20
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/pop3/rfc1734.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group J. Myers
+Request for Comments: 1734 Carnegie Mellon
+Category: Standards Track December 1994
+
+
+ POP3 AUTHentication command
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+
+1. Introduction
+
+ This document describes the optional AUTH command, for indicating an
+ authentication mechanism to the server, performing an authentication
+ protocol exchange, and optionally negotiating a protection mechanism
+ for subsequent protocol interactions. The authentication and
+ protection mechanisms used by the POP3 AUTH command are those used by
+ IMAP4.
+
+
+2. The AUTH command
+
+ AUTH mechanism
+
+ Arguments:
+ a string identifying an IMAP4 authentication mechanism,
+ such as defined by [IMAP4-AUTH]. Any use of the string
+ "imap" used in a server authentication identity in the
+ definition of an authentication mechanism is replaced with
+ the string "pop".
+
+ Restrictions:
+ may only be given in the AUTHORIZATION state
+
+ Discussion:
+ The AUTH command indicates an authentication mechanism to
+ the server. If the server supports the requested
+ authentication mechanism, it performs an authentication
+ protocol exchange to authenticate and identify the user.
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/pop3/rfc1725.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group J. Myers
+Request for Comments: 1725 Carnegie Mellon
+Obsoletes: 1460 M. Rose
+Category: Standards Track Dover Beach Consulting, Inc.
+ November 1994
+
+
+ Post Office Protocol - Version 3
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Overview
+
+ This memo is a revision to RFC 1460, a Draft Standard. It makes the
+ following changes from that document:
+
+ - removed text regarding "split-UA model", which didn't add
+ anything to the understanding of POP
+
+ - clarified syntax of commands, keywords, and arguments
+
+ - clarified behavior on broken connection
+
+ - explicitly permitted an inactivity autologout timer
+
+ - clarified the requirements of the "exclusive-access lock"
+
+ - removed implementation-specific wording regarding the parsing of
+ the maildrop
+
+ - allowed servers to close the connection after a failed
+ authentication command
+
+ - removed the LAST command
+
+ - fixed typo in example of TOP command
+
+ - clarified that the second argument to the TOP command is non-
+ negative
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/basic/rfc0822.txt
+ =======================================================================
+
+
+
+
+
+ RFC # 822
+
+ Obsoletes: RFC #733 (NIC #41952)
+
+
+
+
+
+
+
+
+
+
+
+
+ STANDARD FOR THE FORMAT OF
+
+ ARPA INTERNET TEXT MESSAGES
+
+
+
+
+
+
+ August 13, 1982
+
+
+
+
+
+
+ Revised by
+
+ David H. Crocker
+
+
+ Dept. of Electrical Engineering
+ University of Delaware, Newark, DE 19711
+ Network: DCrocker @ UDel-Relay
+
+
+
+
+
+
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/basic/rfc2046.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group N. Freed
+Request for Comments: 2046 Innosoft
+Obsoletes: 1521, 1522, 1590 N. Borenstein
+Category: Standards Track First Virtual
+ November 1996
+
+
+ Multipurpose Internet Mail Extensions
+ (MIME) Part Two:
+ Media Types
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Abstract
+
+ STD 11, RFC 822 defines a message representation protocol specifying
+ considerable detail about US-ASCII message headers, but which leaves
+ the message content, or message body, as flat US-ASCII text. This
+ set of documents, collectively called the Multipurpose Internet Mail
+ Extensions, or MIME, redefines the format of messages to allow for
+
+ (1) textual message bodies in character sets other than
+ US-ASCII,
+
+ (2) an extensible set of different formats for non-textual
+ message bodies,
+
+ (3) multi-part message bodies, and
+
+ (4) textual header information in character sets other than
+ US-ASCII.
+
+ These documents are based on earlier work documented in RFC 934, STD
+ 11, and RFC 1049, but extends and revises them. Because RFC 822 said
+ so little about message bodies, these documents are largely
+ orthogonal to (rather than a revision of) RFC 822.
+
+ The initial document in this set, RFC 2045, specifies the various
+ headers used to describe the structure of MIME messages. This second
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/basic/rfc2822.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group P. Resnick, Editor
+Request for Comments: 2822 QUALCOMM Incorporated
+Obsoletes: 822 April 2001
+Category: Standards Track
+
+
+ Internet Message Format
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Copyright Notice
+
+ Copyright (C) The Internet Society (2001). All Rights Reserved.
+
+Abstract
+
+ This standard specifies a syntax for text messages that are sent
+ between computer users, within the framework of "electronic mail"
+ messages. This standard supersedes the one specified in Request For
+ Comments (RFC) 822, "Standard for the Format of ARPA Internet Text
+ Messages", updating it to reflect current practice and incorporating
+ incremental changes that were specified in other RFCs.
+
+Table of Contents
+
+ 1. Introduction ............................................... 3
+ 1.1. Scope .................................................... 3
+ 1.2. Notational conventions ................................... 4
+ 1.2.1. Requirements notation .................................. 4
+ 1.2.2. Syntactic notation ..................................... 4
+ 1.3. Structure of this document ............................... 4
+ 2. Lexical Analysis of Messages ............................... 5
+ 2.1. General Description ...................................... 5
+ 2.1.1. Line Length Limits ..................................... 6
+ 2.2. Header Fields ............................................ 7
+ 2.2.1. Unstructured Header Field Bodies ....................... 7
+ 2.2.2. Structured Header Field Bodies ......................... 7
+ 2.2.3. Long Header Fields ..................................... 7
+ 2.3. Body ..................................................... 8
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/basic/rfc2045.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group N. Freed
+Request for Comments: 2045 Innosoft
+Obsoletes: 1521, 1522, 1590 N. Borenstein
+Category: Standards Track First Virtual
+ November 1996
+
+
+ Multipurpose Internet Mail Extensions
+ (MIME) Part One:
+ Format of Internet Message Bodies
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Abstract
+
+ STD 11, RFC 822, defines a message representation protocol specifying
+ considerable detail about US-ASCII message headers, and leaves the
+ message content, or message body, as flat US-ASCII text. This set of
+ documents, collectively called the Multipurpose Internet Mail
+ Extensions, or MIME, redefines the format of messages to allow for
+
+ (1) textual message bodies in character sets other than
+ US-ASCII,
+
+ (2) an extensible set of different formats for non-textual
+ message bodies,
+
+ (3) multi-part message bodies, and
+
+ (4) textual header information in character sets other than
+ US-ASCII.
+
+ These documents are based on earlier work documented in RFC 934, STD
+ 11, and RFC 1049, but extends and revises them. Because RFC 822 said
+ so little about message bodies, these documents are largely
+ orthogonal to (rather than a revision of) RFC 822.
+
+ This initial document specifies the various headers used to describe
+ the structure of MIME messages. The second document, RFC 2046,
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/basic/rfc1123.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group Internet Engineering Task Force
+Request for Comments: 1123 R. Braden, Editor
+ October 1989
+
+
+ Requirements for Internet Hosts -- Application and Support
+
+Status of This Memo
+
+ This RFC is an official specification for the Internet community. It
+ incorporates by reference, amends, corrects, and supplements the
+ primary protocol standards documents relating to hosts. Distribution
+ of this document is unlimited.
+
+Summary
+
+ This RFC is one of a pair that defines and discusses the requirements
+ for Internet host software. This RFC covers the application and
+ support protocols; its companion RFC-1122 covers the communication
+ protocol layers: link layer, IP layer, and transport layer.
+
+
+
+ Table of Contents
+
+
+
+
+ 1. INTRODUCTION ............................................... 5
+ 1.1 The Internet Architecture .............................. 6
+ 1.2 General Considerations ................................. 6
+ 1.2.1 Continuing Internet Evolution ..................... 6
+ 1.2.2 Robustness Principle .............................. 7
+ 1.2.3 Error Logging ..................................... 8
+ 1.2.4 Configuration ..................................... 8
+ 1.3 Reading this Document .................................. 10
+ 1.3.1 Organization ...................................... 10
+ 1.3.2 Requirements ...................................... 10
+ 1.3.3 Terminology ....................................... 11
+ 1.4 Acknowledgments ........................................ 12
+
+ 2. GENERAL ISSUES ............................................. 13
+ 2.1 Host Names and Numbers ................................. 13
+ 2.2 Using Domain Name Service .............................. 13
+ 2.3 Applications on Multihomed hosts ....................... 14
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/imap4/rfc2595.txt
+ =======================================================================
+
+
+
+
+
+
+Network Working Group C. Newman
+Request for Comments: 2595 Innosoft
+Category: Standards Track June 1999
+
+
+ Using TLS with IMAP, POP3 and ACAP
+
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Copyright Notice
+
+ Copyright (C) The Internet Society (1999). All Rights Reserved.
+
+1. Motivation
+
+ The TLS protocol (formerly known as SSL) provides a way to secure an
+ application protocol from tampering and eavesdropping. The option of
+ using such security is desirable for IMAP, POP and ACAP due to common
+ connection eavesdropping and hijacking attacks [AUTH]. Although
+ advanced SASL authentication mechanisms can provide a lightweight
+ version of this service, TLS is complimentary to simple
+ authentication-only SASL mechanisms or deployed clear-text password
+ login commands.
+
+ Many sites have a high investment in authentication infrastructure
+ (e.g., a large database of a one-way-function applied to user
+ passwords), so a privacy layer which is not tightly bound to user
+ authentication can protect against network eavesdropping attacks
+ without requiring a new authentication infrastructure and/or forcing
+ all users to change their password. Recognizing that such sites will
+ desire simple password authentication in combination with TLS
+ encryption, this specification defines the PLAIN SASL mechanism for
+ use with protocols which lack a simple password authentication
+ command such as ACAP and SMTP. (Note there is a separate RFC for the
+ STARTTLS command in SMTP [SMTPTLS].)
+
+ There is a strong desire in the IETF to eliminate the transmission of
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/imap4/rfc2359.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group J. Myers
+Request for Comments: 2359 Netscape Communications
+Category: Standards Track June 1998
+
+
+ IMAP4 UIDPLUS extension
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Copyright Notice
+
+ Copyright (C) The Internet Society (1998). All Rights Reserved.
+
+IESG NOTE
+
+ The IMAP extension described here assumes a particular means of using
+ IMAP to support disconnected operation. However, this means of
+ supporting disconnected operation is not yet documented. Also, there
+ are multiple theories about how best to do disconnected operation in
+ IMAP, and as yet, there is no consensus on which one should be
+ adopted as a standard.
+
+ This document is being approved as a Proposed Standard because it
+ does not appear to have technical flaws in itelf. However, approval
+ of this document as a Proposed Standard should not be considered an
+ IETF endorsement of any particular means of doing disconnected
+ operation in IMAP.
+
+Table of Contents
+
+ 1. Abstract .............................................. 2
+ 2. Conventions Used in this Document ..................... 2
+ 3. Introduction and Overview ............................. 2
+ 4. Features .............................................. 2
+ 4.1. UID EXPUNGE Command ................................... 2
+ 4.2. APPENDUID response code ............................... 3
+ 4.3. COPYUID response code ................................. 4
+ 5. Formal Syntax ......................................... 4
+ 6. References ............................................ 4
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/imap4/rfc2060.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group M. Crispin
+Request for Comments: 2060 University of Washington
+Obsoletes: 1730 December 1996
+Category: Standards Track
+
+
+ INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Abstract
+
+ The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)
+ allows a client to access and manipulate electronic mail messages on
+ a server. IMAP4rev1 permits manipulation of remote message folders,
+ called "mailboxes", in a way that is functionally equivalent to local
+ mailboxes. IMAP4rev1 also provides the capability for an offline
+ client to resynchronize with the server (see also [IMAP-DISC]).
+
+ IMAP4rev1 includes operations for creating, deleting, and renaming
+ mailboxes; checking for new messages; permanently removing messages;
+ setting and clearing flags; [RFC-822] and [MIME-IMB] parsing;
+ searching; and selective fetching of message attributes, texts, and
+ portions thereof. Messages in IMAP4rev1 are accessed by the use of
+ numbers. These numbers are either message sequence numbers or unique
+ identifiers.
+
+ IMAP4rev1 supports a single server. A mechanism for accessing
+ configuration information to support multiple IMAP4rev1 servers is
+ discussed in [ACAP].
+
+ IMAP4rev1 does not specify a means of posting mail; this function is
+ handled by a mail transfer protocol such as [SMTP].
+
+ IMAP4rev1 is designed to be upwards compatible from the [IMAP2] and
+ unpublished IMAP2bis protocols. In the course of the evolution of
+ IMAP4rev1, some aspects in the earlier protocol have become obsolete.
+ Obsolete commands, responses, and data formats which an IMAP4rev1
+ implementation may encounter when used with an earlier implementation
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/imap4/rfc2221.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group M. Gahrns
+Request for Comments: 2221 Microsoft
+Category: Standards Track October 1997
+
+
+ IMAP4 Login Referrals
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Copyright Notice
+
+ Copyright (C) The Internet Society (1997). All Rights Reserved.
+
+1. Abstract
+
+ When dealing with large amounts of users and many IMAP4 [RFC-2060]
+ servers, it is often necessary to move users from one IMAP4 server to
+ another. For example, hardware failures or organizational changes
+ may dictate such a move.
+
+ Login referrals allow clients to transparently connect to an
+ alternate IMAP4 server, if their home IMAP4 server has changed.
+
+ A referral mechanism can provide efficiencies over the alternative
+ 'proxy method', in which the local IMAP4 server contacts the remote
+ server on behalf of the client, and then transfers the data from the
+ remote server to itself, and then on to the client. The referral
+ mechanism's direct client connection to the remote server is often a
+ more efficient use of bandwidth, and does not require the local
+ server to impersonate the client when authenticating to the remote
+ server.
+
+2. Conventions used in this document
+
+ In examples, "C:" and "S:" indicate lines sent by the client and
+ server respectively.
+
+ A home server, is an IMAP4 server that contains the user's inbox.
+
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/imap4/rfc2195.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group J. Klensin
+Request for Comments: 2195 R. Catoe
+Category: Standards Track P. Krumviede
+Obsoletes: 2095 MCI
+ September 1997
+
+
+ IMAP/POP AUTHorize Extension for Simple Challenge/Response
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+Abstract
+
+ While IMAP4 supports a number of strong authentication mechanisms as
+ described in RFC 1731, it lacks any mechanism that neither passes
+ cleartext, reusable passwords across the network nor requires either
+ a significant security infrastructure or that the mail server update
+ a mail-system-wide user authentication file on each mail access.
+ This specification provides a simple challenge-response
+ authentication protocol that is suitable for use with IMAP4. Since
+ it utilizes Keyed-MD5 digests and does not require that the secret be
+ stored in the clear on the server, it may also constitute an
+ improvement on APOP for POP3 use as specified in RFC 1734.
+
+1. Introduction
+
+ Existing Proposed Standards specify an AUTHENTICATE mechanism for the
+ IMAP4 protocol [IMAP, IMAP-AUTH] and a parallel AUTH mechanism for
+ the POP3 protocol [POP3-AUTH]. The AUTHENTICATE mechanism is
+ intended to be extensible; the four methods specified in [IMAP-AUTH]
+ are all fairly powerful and require some security infrastructure to
+ support. The base POP3 specification [POP3] also contains a
+ lightweight challenge-response mechanism called APOP. APOP is
+ associated with most of the risks associated with such protocols: in
+ particular, it requires that both the client and server machines have
+ access to the shared secret in cleartext form. CRAM offers a method
+ for avoiding such cleartext storage while retaining the algorithmic
+ simplicity of APOP in using only MD5, though in a "keyed" method.
+
+
+ =======================================================================
+ ==james-project/project/server/src/site/resources/rfclist/imap4/rfc2086.txt
+ =======================================================================
+
+
+
+
+
+Network Working Group J. Myers
+Request for Comments: 2086 Carnegie Mellon
+Category: Standards Track January 1997
+
+
+ IMAP4 ACL extension
+
+Status of this Memo
+
+ This document specifies an Internet standards track protocol for the
+ Internet community, and requests discussion and suggestions for
+ improvements. Please refer to the current edition of the "Internet
+ Official Protocol Standards" (STD 1) for the standardization state
+ and status of this protocol. Distribution of this memo is unlimited.
+
+1. Abstract
+
+ The ACL extension of the Internet Message Access Protocol [IMAP4]
+ permits access control lists to be manipulated through the IMAP
+ protocol.
+
+Table of Contents
+
+ 1. Abstract............................................... 1
+ 2. Conventions Used in this Document...................... 1
+ 3. Introduction and Overview.............................. 2
+ 4. Commands............................................... 3
+ 4.1. SETACL................................................. 3
+ 4.2. DELETEACL.............................................. 4
+ 4.3. GETACL................................................. 4
+ 4.4. LISTRIGHTS............................................. 4
+ 4.5. MYRIGHTS............................................... 5
+ 5. Responses.............................................. 5
+ 5.1. ACL.................................................... 5
+ 5.2. LISTRIGHTS............................................. 6
+ 5.3. MYRIGHTS............................................... 6
+ 6. Formal Syntax.......................................... 6
[... 8583 lines stripped ...]