This tab says how VPOP3 handles its message store

The Delay while moving messages setting tells VPOP3 how quickly to import messages into the new database structure if it was upgraded from version 2.x or earlier. Usually this is OK to be left as it is, but if there is some special requirement to import the messages more quickly, you can decrease this number, but that will increase the load on the server.

Note that VPOP3 can read messages from either the old or new message stores, so it does not matter too much if some messages are still in the version 2 message store and other messages are in the new database store. However, during this time, the database backups will not contain all your data, so you should backup the VPOP3 directories as well (except for the pgsql folder tree)

If you have VPOP3 Enterprise, there is a 'Message Recycle Bin' which keeps deleted messages for a few days, in case they were deleted by mistake.

The default is 72 hours, but you can increase or decrease this number if necessary. If you set it to '0' the recycle bin functionality is disabled.

You can also use the Purge Recycle Bin button to trigger a purge of the recycle bin data. Note that clearing the recycle bin will not occur immediately, especially if there is a lot of data there.

The Recycle Bin Size section tells you how many messages are currently in the recycle bin.

To recover messages using the recycle bin, go to the Edit User -> Advanced tab for the relevant user.

Note that because the message data is stored in the database, purging the recycle bin will not free up disk space immediately. As with most enterprise database systems, PostgreSQL does not free up emptied space in the database files. This is for performance reasons. To free disk space, see the Freeing disk space topic. Note that VPOP3 will need to be closed down while this is done.