If these are incorrect, changing them with chmod or
chown may solve the problem. If the permissions and
ownership are correct, or if changing them back to the defaults does not solve
the problem, generate a new scan.db file:
cd 'pmx prefix'/var/counters
mv scan.db scan.db.broken
pmx-qdigest --earliest <YYYY-MM-DD hh:mm:ss>
Set <YYYY-MM-DD hh:mm:ss> to the time of the earliest message
to include in the digest. The quarantine scan will start from this point.
Once the pmx-qdigest command has completed, the
scan.db database should be regenerated. The next
quarantine digest will start with the last quarantine ID scanned during the
run (in this case, the most recent message in the quarantine).
The next time pmx-qdigest is run by the Scheduler, it
should complete normally.