With Kabir's help I proved that the bug is actually somehow in Entourage. It doesn't happen on his side, and doesn't happen with Thunderbird. So we should be go for M2 shortly.
Good to hear. Once a stable release is out, I'll try it on my server and give some feedback at least. I plan to try it with HSQL and Cloudbase (now Derby), hardly a production ready rig, but it should do for what I need.
If you get out a stable release and have a nice list of things that need to be done, I'll at least check out the list and see if there's anything I think I can tackle without needing to spend two weeks reading the code.
At work, our Exchange servers just went down in flames, and I'm sure the IT guys are very upset, so there's certainly an opportunity here, though not until the system is more advanced than it currently is, but all in good time.
HSQL meaning Hypersonic? The problem is that Hypersonic stores everything in memory. That is simply not feasible for email! (or at least not with the sizes of mail that I get ;-) ) Yes I speak from experience ;-)
HEAD is pretty much what I will be calling M2. Right now I'm working on an install tool. I could use some help creating configurations for databases other than MySQL. (Though I want to discourage people from using HSQL because they won't like the result at all).
Yes, I realize that M2 isn't going to be an exchange replacement :-) Its way to early for that. The culmination of 2-3 man months of effort from maybe an average total of 1.5 persons is not going to wipe out Exchange. Mainly get the snowball rolling and start the initial momentum.
HSQLDB doesn't store everything in memory when CACHED tables are used. You can currently store up to 2GB per database. The limit is due to rise to 8GB in the next version due by April (this is a real date as it is tied with the release of OpenOffice.org 2.00). So you will be able to start with HSQLDB for smaller setups and let users move to whichever RDBMS they use in house for larger deployments.
Maintainer, HSQLDB Project
I dunno a whole big amount about HSQL's various config options, but what is in JBoss now crashed ever few days when I used it. MySQL, once I figured out the BLOB issues, works wonderfully (except for my hard drive which is spitting out bad blocks every few days but that is scheduled to be fixed tomorrow/friday). HSQL is a "nice to have" I guess for testing it out, but unless someone proves sufficently to my satisfaction that it can work stabilly and painlessly, I'll always put a disclaimer. Its not personal, just thus far HSQL hasn't held up well for me and one thing I pretty nearly always have to do for JBoss consulting customers is switch them off of it for JMS (for some reason this is often missed -- you'd be surpised at the number of large companies that inadvertantly use it in production).
It probably hit the 2GB limit :) The newer versions of HSQLDB (1.7.2 and 1.7.3) have a DEFRAG function which is not used in the JBoss configuration.
I had not investigated the JBoss usage pattern until very recently. I'm currently working with some real test data from a live JBoss instance and will make space management automatic in the next version. The upshot will be that you can use an embedded HSQLDB database in a production server without any crash.
In any case, people will use an RDBMS that fits their needs / policies, so we'll just try to make HSQLDB better in this usage scenario.
Cool. Once M2 is out, it'd be really helpful if you could help add a config for HSQL that makes sense. I'm hoping to put M2 out right after the first of the year. I'm working on GUI installation right now.