You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mime4j-dev@james.apache.org by rd...@apache.org on 2009/03/01 22:50:40 UTC
svn commit: r749120 - /james/mime4j/trunk/src/site/xdoc/index.xml
Author: rdonkin
Date: Sun Mar 1 21:50:40 2009
New Revision: 749120
URL: http://svn.apache.org/viewvc?rev=749120&view=rev
Log:
MimeDefang is quite a different site now, concentrating on pushing it's commercial offerings. So opted to remove the link.
Modified:
james/mime4j/trunk/src/site/xdoc/index.xml
Modified: james/mime4j/trunk/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/james/mime4j/trunk/src/site/xdoc/index.xml?rev=749120&r1=749119&r2=749120&view=diff
==============================================================================
--- james/mime4j/trunk/src/site/xdoc/index.xml (original)
+++ james/mime4j/trunk/src/site/xdoc/index.xml Sun Mar 1 21:50:40 2009
@@ -51,8 +51,7 @@
<p> The parser has been designed to be extremely tolerant against
messages violating the standards. It has been tested using a
large corpus (>5000) of e-mail messages. As a benchmark
- the widely used perl <a
- href="http://www.mimedefang.org/node.php?id=48">MIME::Tools</a>
+ the widely used perl <code>MIME::Tools</code>
parser has been used. mime4j and MIME:Tools rarely differ
(<25 in those 5000). When they do (which only occurs
for illegally formatted spam messages) we think mime4j does a