delete from messages; delete from messageblks; thanx this worked, now my pop respone is about 20x quicker
> > and, > > the debian package has problems when upgrading > the dbmail stop = ok > package upgrade > then dbmail start, this takes forever... > and this results in a half-configured status in the dpkg status file.. grrrr. I tracked this one down. Apparently dbmail-imapd/dbmail-pop3d won't start immediately after shutdown, when there were some clients connected. Has anyone noticed similar behaviour ? I think its when the daemon can't bind, yet fails to raise the appropriate error. For now I've made the startup procedure persistent. Hopefully that will work. Please, try upgrading. >> Did that, here my output: Setting up dbmail-mysql (1.1.20030726-3) ... Setting up dbmail (1.1.20030726-3) ... Installing new version of config file /etc/init.d/dbmail ... Restarting dbmail servers: stopping restarting done. !!! but no prompt i have to do CTRL-C resulting in: dpkg: error processing dbmail (--configure): subprocess post-installation script killed by signal (Interrupt) Errors were encountered while processing: dbmail E: Sub-process /usr/bin/dpkg returned an error code (1) => after this i do a /etc/init.d/dbmail restart and dbmail restarts, but still there is a half-configured line in the dpkg status file for dbmail... :-(
