Danny Angus wrote:
Will james cope gracefully with the jdbc exceptions if/when these tables
are locked? (In particular, will delivery/spooling/processing be deferred--will I lose emails?)
Don't count on it. I would establish this by testing it, rather than rely on anyone else's opinion. James doesn't cope well with db's "going away" and coming back again, but if James doesn't think that the connections are bad it may just wait and retry until the operation suceeds. You won't be able to persist incoming mail during the outage, which is a risk.
If not, is it possible/advisable to suspend james' operation
programmatically?
If you're using cron to schedule your db admin use cron to stop & start James. SMTP allows for outages by mailservers without loss of messages, so the issue is really about whether your users can be cajoled into accepting any.
Thanks, Steve
Maybe it would be a good idea to implement some sort of nightly backup routine into James, especially if we are going to use an embedded database like derby or hsqldb. Then we have a self contained mail server that doesn't depend on external programs.
Steen
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
