On Mon, 2007-09-10 at 12:22 +0200, Michael Monnerie wrote: > Dear Devs, I still can see this happening: > > With -rc2: > > # dbmail-util -tubdpy > > > > Repairing DBMAIL messageblocks integrity... > > Ok. Found [0] unconnected messageblks. > > > > Repairing DBMAIL physmessage integrity... > > Ok. Found [91746] unconnected physmessages > > Looks like all or most messages are going to be deleted?
I'm fairly certain (though it's not my data that's potentially lost :) that this is simply the fix for the long-standing bug #305. Previously there was no check for abandonned physical messages, and that was added recently. If you run it through one time and allow it to remove those, the next run should find none. Try it on a copy of your data first if you want.... > With -rc1: > > # dbmail-util -tubdpy > > > > Repairing DBMAIL messageblocks integrity... > > Ok. Found [0] unconnected messageblks. > > > > Checking DBMAIL message integrity... > > Ok. Found [0] unconnected messages. > > Can anyone confirm this? > > mfg zmi > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org > https://mailman.fastxs.nl/mailman/listinfo/dbmail -- Jesse Norell Kentec Communications, Inc. [EMAIL PROTECTED] _______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
