On Sun, 2006-09-24 at 20:55 +0200, [EMAIL PROTECTED] wrote:

> ---------------------------------------------------------------------- 
>  paul - 01-Mar-06 22:50  
> ---------------------------------------------------------------------- 
> I've rephrased the report then.
> 
> dbmail-util -t currently doesn't test for unused physmessages. This is an
> omission.
> 
> all the db_icheck_... functions need some cleaning up and refactoring.

Paul I could easily just add physmessage icheck functions in the same
style as we have now (generating a huge list, then go through it
deleting entries). Or work on refactoring, which I've started on by
rewriting each function as an "icheck" / "ifix" pair. The first SELECTs
a count of bad stuff, the second DELETEs on the same WHERE clause.

Something I've been thinking about, though, is that I'd like to be able
to dump items as they are being deleted. Generating maybe an mbox format
file of all messages / physmessages / mailboxes dumped in a given
session would provide some peace-of-mind and an audit trail in case
something goes wrong.

I suppose an important question to ask is what an mbox formatted
physmessage or mailbox looks like...

Aaron

Reply via email to