Ok. I checked the source.
Looks like do_null_messages correctly finds all the NULL messages, and does set
MESSAGE_STATUS_ERROR on all these messages. But there's no code to actually
flush all those messages from the database. I suspect that somewhere in the
past, this was handled subtly different.
Aaron, Ilja: any reason why do_null_messages calls db_set_message_status to set
MESSAGE_STATUS_ERROR instead of MESSAGE_STATUS_PURGE?
Sri, you can safely delete all those rows from dbmail_messages:
DELETE FROM dbmail_messages WHERE status = 6;
Or better yet: set their status to '3' (PURGE) and run dbmail-util again.
Sri Gupta wrote:
On Tue, Mar 22, 2005 at 04:34:32PM +0100, Paul J Stevens wrote:
Heh, a faq :-)
Use the -y switch, the -r switch is non-functional.
well, first and foremost, if that's true, someone needs to fix the man page.
second.. dbmail-util -ay doesn't do anything differently..
Here's the output of two consecutive runs. all your help is appreciated.
-Sri
venus root # dbmail-util -ay
Opening connection to database...
Opening connection to authentication...
Ok. Connected.
Repairing DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.
Checking DBMAIL message integrity...
Ok. Found [0] unconnected messages.
Checking DBMAIL mailbox integrity...
Ok. Found [0] unconnected mailboxes.
Repairing DBMAIL for NULL messages...
Ok. Found [177498] NULL messages.
Checking DBMAIL for NULL physmessages...
Ok. Found [0] physmessages without messageblocks.
Repairing DBMAIL for incorrect is_header flags...
Ok. Found [0] incorrect is_header flags.
Deleting messages with PURGE status...
Ok. [71] messages deleted.
Setting DELETE status for deleted messages...
Ok. [12] 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. Errors were found and fixed.
Try running dbmail-util again to confirm that the errors were repaired.
venus root # dbmail-util -ay
Opening connection to database...
Opening connection to authentication...
Ok. Connected.
Repairing DBMAIL messageblocks integrity...
Ok. Found [0] unconnected messageblks.
Checking DBMAIL message integrity...
Ok. Found [0] unconnected messages.
Checking DBMAIL mailbox integrity...
Ok. Found [0] unconnected mailboxes.
Repairing DBMAIL for NULL messages...
Ok. Found [177498] NULL messages.
Checking DBMAIL for NULL physmessages...
Ok. Found [0] physmessages without messageblocks.
Repairing DBMAIL for incorrect is_header flags...
Ok. Found [0] incorrect is_header flags.
Deleting messages with PURGE status...
Ok. [12] messages deleted.
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. Errors were found and fixed.
Try running dbmail-util again to confirm that the errors were repaired.
venus root #
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens [EMAIL PROTECTED]
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands_______________________________________www.nfg.nl
