This shows you the differences between two versions of the page.
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] paul | how_to:recovering_messages_from_corrupted_database_into_fresh_database [2025/09/11 14:48] (current) – paul | ||
---|---|---|---|
Line 46: | Line 46: | ||
- delete the ' | - delete the ' | ||
- at a command prompt, go to the VPOP3\pgsql\bin folder and run: < | - at a command prompt, go to the VPOP3\pgsql\bin folder and run: < | ||
+ | |||
+ | |||
+ | |||
+ | =====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 ' | ||
+ | |||
+ | [[repairing_corrupted_database# | ||
+ | |||
+ | 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>; |