[Dbmail] Fw: new message

2016-02-23 Thread colin
Hey! Open message co...@itnavigate.com.au ___ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

[Dbmail] database overhead

2016-02-23 Thread Admin Beckspaced
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 t

[Dbmail] Orphaned physmessages, partlists, mimeparts

2016-02-23 Thread Admin Beckspaced
hello again ;) on my production server with dbmail 3.0.2 a run of dbmail-util always reports the following: # dbmail-util -ay Repairing DBMAIL message integrity... Repairing DBMAIL physmessage integrity... Ok. Found [1] unconnected physmessages. Ok. Orphaned physmessages deleted. Repairing

Re: [Dbmail] database overhead

2016-02-23 Thread Andrea Brancatelli
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

Re: [Dbmail] database overhead

2016-02-23 Thread Reindl Harald
Am 23.02.2016 um 10:40 schrieb Andrea Brancatelli: 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

Re: [Dbmail] database overhead

2016-02-23 Thread Reindl Harald
Am 23.02.2016 um 10:40 schrieb Andrea Brancatelli: 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

Re: [Dbmail] database overhead

2016-02-23 Thread Andrea Brancatelli
You're right, but as... http://dev.mysql.com/doc/refman/5.7/en/innodb-multiple-tablespaces.html _"innodb_file_per_table is enabled by default in MySQL 5.6.6 and higher. You may consider disabling it if backward compatibility with MySQL 5.5 or 5.1"_ _---_ Andrea Brancatelli Schema31 S.p.a. Res