> James v2 is stable. In my view, such features and fixes that can be made
> within the stable code base without negatively impacting it ought to be
> made, especially if they are forward compatible with v3.
Come to think of it, my list isn't really that long:
* Update James to compile with GUMP against current Avalon CVS
* GeoMatcher
* RegexMatcher
* Index on repository name (looks like v2.1 only does it for MySQL)
* Thread isInterrupted() / InterruptedException changes
* FetchPOP changes (Received header and configuration options)
* DnsJava update
* Updates to Redirect, and rewrite other forwarding mailets as Redirect
subclasses.
* Fix Bounce method
All of these are pretty simple patches, except for some new matchers that I
have been working on, and the Redirect stuff. No real "development", per
se. I'm certainly open to discussion on them, and would defer some to James
v3 if people feel strongly about them.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
