Alan,
I have been listening, and I certainly know your name.
Personally, I haven't used 2.0a3 since June. By my automated count, there
have been ~600 patches made to James since 2.0a3. I am bothered that there
have been critical fixes that have not been part of a Release Build. It is
my goal that when a defect is located in the future, that we can quickly put
out a fixed Release, as we just did to fix a resource leak impacting Oracle
users.
If you can demonstrate that James v2.1 provides a 250 return code to the
sender when using a JDBC spool and a failed database (and where the JDBC
driver is providing failure notification), then we have a serious defect to
fix. I cannot produce such an error.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
