how_to:recovering_messages_from_corrupted_database_into_fresh_database

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
how_to:recovering_messages_from_corrupted_database_into_fresh_database [2025/09/11 14:28] – [Recovering messages from corrupted database into fresh database] paulhow_to:recovering_messages_from_corrupted_database_into_fresh_database [2025/09/11 14:48] (current) paul
Line 46: Line 46:
   - delete the 'settings.dmp' file you created in the VPOP3\pgsql\bin folder   - delete the 'settings.dmp' file you created in the VPOP3\pgsql\bin folder
   - at a command prompt, go to the VPOP3\pgsql\bin folder and run: <code> dropdb -U postgres -p 5433 vpop3_old</code> \\ (default password is 'pgsqlpass')   - at a command prompt, go to the VPOP3\pgsql\bin folder and run: <code> dropdb -U postgres -p 5433 vpop3_old</code> \\ (default password is 'pgsqlpass')
 +
 +
 +
 +=====Older version of VPOP3=====
 +If you have a version of VPOP3 prior to v8.8, it may stop restoring a user's mailbox folder if it encounters a corrupted message, so one option is to use these steps on the 'vpop3_old' database
 +
 +[[repairing_corrupted_database#finding_the_problem_message]]
 +
 +to find and delete the problem messages. If you can't delete the problem messages, you could try marking them as deleted instead, which will make the message restore option skip those messages.
 +
 +In PSQL run this instead of deleting the message:
 +
 +  UPDATE messages.foldermessages SET deletedtime=now() WHERE msgdataid= <problem message id>;
how_to/recovering_messages_from_corrupted_database_into_fresh_database.txt · Last modified: 2025/09/11 14:48 by paul