Hi There, We are using dbmail 2.2.17 on debian squeeze connected to a mysql 5.1.49-3 server (replicated to another 5.1.49-3 server ). There is around 70GB in the dbmail_messageblks table. Each night (morning) at 3am we run "/usr/local/sbin/dbmail-util -ay" which results in a process that takes about 2 hours to complete (output below). During this time, however, messages queue in postfix and are not delivered until it is completed. As well as that, sometimes we get timed out pop3/imap connections.
I have some clients who complain that their messages do not get thru during this period (early birds!). Is this a normal process? Is there any changes or a different way of doing this so that the mail will continue to flow thru? Thanks Simon dbmail-util -ay output: # cat dbmail-util.log Repairing DBMAIL messageblocks integrity... Ok. Found [0] unconnected messageblks. Repairing DBMAIL physmessage integrity... Ok. Found [0] unconnected physmessages. Repairing DBMAIL message integrity... Ok. Found [0] unconnected messages. Repairing DBMAIL mailbox integrity... Repairing DBMAIL for NULL messages... Ok. Found [0] NULL messages. Checking DBMAIL for NULL physmessages... Ok. Found [0] physmessages without messageblocks. Deleting messages with DELETE status... Ok. [2049] messages deleted. Repairing DBMAIL for rfcsize field... Ok. Found [0] missing rfcsize values. Repairing DBMAIL for incorrect is_header flags... Ok. Found [0] incorrect is_header flags. Repairing DBMAIL for cached envelopes... Repairing DBMAIL for cached header values... Setting DELETE status for deleted messages... Ok. [5790] messages set for deletion. Re-calculating used quota for all users... Ok. Used quota updated for all users. Removing aliases with nonexistent delivery userid's... Ok. Found [0] dangling aliases. Vacuuming and optimizing database... Ok. Database cleaned up. _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
