-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Giulio Ferro schrieb:
> Paul J Stevens wrote:
>> Run it twice to get rid of all deleted messages. If this deletes a lot
>> of messages you should probably also run
>>
>> OPTIMIZE_TABLE <tablename>;
>>
>> for - at least - dbmail_messages and dbmail_messageblks
>>
>> All of this will take a long time to run.
>>
>>   
> I've run
> dbmail-util -c -t -u -p -d -y
> twice and this is what came out:

Now, put it into a cronjob!

> 
> first time:
> ------------------------------------------------------------------------------------
> 
> Repairing DBMAIL messageblocks integrity...
> Ok. Found [0] unconnected messageblks.
> 
> Repairing DBMAIL physmessage integrity...
> Ok. Found [1] unconnected physmessagesOk. Orphaned physmessages deleted.

That happens - sometimes. Don't worry.

> 
> Deleting messages with DELETE status...
> Ok. [13051] messages deleted.

Okay.

> 
> Setting DELETE status for deleted messages...
> Ok. [10739] messages set for deletion.
> Re-calculating used quota for all users...
> Ok. Used quota updated for all users.

Okay.

[...]

> 
> Deleting messages with DELETE status...
> Ok. [10739] messages deleted.

Well, it corresponds to the values above, and it's fine.

> 
> Setting DELETE status for deleted messages...
> Ok. [0] messages set for deletion.
> Re-calculating used quota for all users...
> Ok. Used quota updated for all users.
> 

> Vacuuming and optimizing database...
> Ok. Database cleaned up.
> 
> Maintenance done. No errors found.
> ------------------------------------------------------------------------------------
> 
> 
> 
> the I did:
> optimize table dbmail_messages:
> ------------------------------------------------------------------------------------
> 
> +------------------------+----------+----------+----------+
> | Table                  | Op       | Msg_type | Msg_text |
> +------------------------+----------+----------+----------+
> | dbmail.dbmail_messages | optimize | status   | OK       |
> +------------------------+----------+----------+----------+
> 1 row in set (35.71 sec)
> ------------------------------------------------------------------------------------
> 
> 
> and
> optimize table dbmail_messageblks:
> ------------------------------------------------------------------------------------
> 
> +---------------------------+----------+----------+----------+
> | Table                     | Op       | Msg_type | Msg_text |
> +---------------------------+----------+----------+----------+
> | dbmail.dbmail_messageblks | optimize | status   | OK       |
> +---------------------------+----------+----------+----------+
> 1 row in set (14 min 46.35 sec)
> ------------------------------------------------------------------------------------
> 
> 
> 
> All of the above commands took no more than 25 minutes...
> 
> Unfortunately there are still a lot of rows in dbmail_messageblks:
> mysql> select count(*) from dbmail_messageblks;
> +----------+
> | count(*) |
> +----------+
> |   515261 |
> +----------+
> 1 row in set (1 min 11.88 sec)

Really? I don't think so. Here a sample of my "family-and-firends" mail
server:

mysql> select count(*) from dbmail_messageblks;
+----------+
| count(*) |
+----------+
|    18231 |
+----------+
1 row in set (8.11 sec)


I think, half a million rows are okay. How many users do you have?

Uwe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJJA3rJAAoJEEJXG7BUuynnOYYP/0bd4zQ1DV4zPr2Y1Erk4tU6
SajRw5XBAJVlnRT0km1m0kkE+Q4ZiRQxOA7F7NdIayH+CpdC1TR5a1uaI37EuuRC
f4n1iqRBVMSXJEIfRKmmX3o72AF/XENga3zy7/DuHez7nxtMHC8Sw2AEQwo9x8/N
Ke5BrkfIBltcj1JjiMK5SVZ1Bvmy9s79iDbFyIxP3skxtXvmh/FRq1qCvLXkl6NM
vrM+1BKS8Oy/xSgyE0S4mX22Lli8YbJZFTDyYGtBHaq9FkQIT8Bx8zOTyXFJ/C3o
iEBQCfndMJz5YifOojDwOP5dfx/V6IAJRA3JNR+3z/TxiRaiHPKDEpSS/xc1kUp8
LS2wOS3NwZFJiODZqoKETlUW1SdqeCZPKs5QwRpz8C0YBMfi57ZMUa1EPrfC0KQr
DlpSVBQ8c1/RuOqH9AaA2fxwLzK2kE6vSs1G3frWu3dybPLebjkoKmq41bhz2SWh
rNwamVFDTHlY/UytSJK/pIZSGLMlYHqFRpoOGH0qcZk4zNmu/KrrNZRs/DK0nRYl
VI3TGrAPBvmiQpxg6Ia0MWbrJfsGXVZd5wKpBC/6Yu9tJAfhlpNjsI/t9BRd/1q9
FO5pBLWL8NTfU+qN6+IVQfplXCoZen0BVGNtMeF6Pv38DtxZmuk9DzHg4LYAgvaP
LO4ASNOyICQDHvJQfQAl
=Iru5
-----END PGP SIGNATURE-----
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail

Reply via email to