> Don't know, cause only mysql 3.x used. If system rebuild don't solve > problem > - I try switch to mysql 4. > Think this is possible, bacause size of "pop3d" process grow up fast, may > be > something wrong with "messages buffer".
Could well be. Are you using MyISAM or InnoDB tables? How often do you optimize/analyze the tables? > >How many users do you have? > About 10-12 users. We've got around 8 > >And on average how often does each user check their email? > Mail robots check mail every 5 min. > Users check mail every 10-15 min. About the same. > Our mail database size is about 700Mb now ... But as I remember this > problem > appear after 4 or 5 days after installing dbmail (~3 month ago). Our database is only around 80mb. 4 - 5 days after installing... Odd > All this time I'm just restart pop3 daemon automatically once per day, but > of course this is stupid solution :( Yes agreed. > Can you check please - what average size of your "pop3d" processes? Average size for our pop3d is around 1500k - 3000k Kept a close eye on them over the last few days they hardly change. Do you run dbmail-maintenance at all? Just had another thought, are you running a raised securelevel 'sysctl kern.securelevel'? It's a long shot but it could maybe conflict with the memory management within dbmail somewhere? (again I doubt it tho) S
