Probably you should do an optimize table on dbmail_messages and such. Consider it will take quite long time, and, even if it's not blocking, it will slow down the mysql server pretty much.
Furthermore take in consideration that on "first" run of dbmail-util the mail il flagged for deletion and on the subsequent run is actually deleted. In general it's pretty normal to have some spurious datas in the DB. Last consideration, if you're very concerned about disk space take in consideration enabling InnoDB Barracuda and do an ALTER TABLE Engine=InnoDB ROW_FORMAT=COMPRESSED; on the bigger tables - they will shrink down a lot. --- Andrea Brancatelli Schema31 S.p.a. Responsabile IT ROMA - BO - FI - PA ITALY Tel: +39. 06.98.358.472 Cell: +39 331.2488468 Fax: +39. 055.71.880.466 Società del Gruppo SC31 ITALIA Il 2016-02-23 09:48 Admin Beckspaced ha scritto: > hello there ;) > > i'm currently still runnning dbmail 3.0.2 on my production server. the > current dbmail database size, as reported by phpmyadmin, is about 1.8 GB > > i also run a daily script notifying users about their mailbox quota. this > quota script also scans through all users and reports back the current > mailbox size of each user and also calculates the total. today it reports a > total of 1150 MB > > so this means a database overhead of about 600 MB. is this overhead normal? > > yesterday i installed dbmail 3.1.17 on a development server. copied a > database backup from production. > run the mysql migration scripts 3_0_2-3_1_0.mysql and dbmail-util -ay > which seems to clean up lots of stuff: > > linux:~ # dbmail-util -ay > > Repairing DBMAIL message integrity... > > Repairing DBMAIL physmessage integrity... > Ok. Found [373] unconnected physmessages. > Ok. Orphaned physmessages deleted. > > Repairing DBMAIL partlists integrity... > Ok. Found [18] unconnected partlists. > Ok. Orphaned partlists deleted. > > Repairing DBMAIL mimeparts integrity... > Ok. Found [1156] unconnected mimeparts. > Ok. Orphaned mimeparts deleted. > > Repairing DBMAIL headernames integrity... > Ok. Found [273] unconnected headernames. > Ok. Orphaned headernames deleted. > > Repairing DBMAIL headervalues integrity... > Ok. Found [90075] unconnected headervalues. > Ok. Orphaned headervalues deleted. > > etc etc ... > > after the cleanup phpmyadmin reports 1.5 GB on the dbmail database > my dbmail quota script reports a total size of all mailboxes with 1182,16 MB > an overhead of about 300 MB with dbmail version 3.1.17 > > is this database overhead of approx. 20% of the database size normal? > or is this something i need to worry about?? > > thanks, greetings & all the best > becki > > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
