No database changes between 2.3.2 and 2.3.4. I plan on at least one very small chang for 2.3.5 (the mtime timestamp field on mailboxes will be replaced by a sequence). Also, the reported crashes in 2.3.4 are being worked on very actively. Until then, please do run dbmail in a keep-alive framework like daemontools, runit, or a simple shell wrapper like:
#!/bin/sh while [ 1 ]; do /usr/sbin/dbmail-imapd -D sleep 1 echo "crashed! restarting..."|logger -t dbmail-keepalive done dan wrote: > On Fri, 14 Nov 2008 14:48:01 +0100, Paul J Stevens <[EMAIL PROTECTED]> wrote: > >> Hi all, >> >> It is with great pleasure that I'm announcing the availability of DBMail >> version 2.3.4, the latest in the 'unstable' development series. > > Cool. Will update soon. Any caveats moving ( home server ... no I'm not > using in production ) from 2.3.2 to 2.3.4 ... ie are there any rolling > changes I need to apply to the DB from 2.3.3? > > Dan > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
