Hello List:
If you have (rogue) orphaned messages DBMA will 'rat them out' and serve
them up to the next crontab 'dbmail-util -d' firing squad.
DBMA finds and marks orphaned messages for deletion.
Get DbMail Administratior - DBMA V2.1.2 at
http://library.mobrien.com/dbmailadministrator/
untar it
(see README if you haven't done this before)
Open in browser.
Configure from the GUI.
Select "Update Delete Status" checkbox and press "Go".
All your "orphaned messages" are marked for deletion with
dbmail_messages.status = '001'.
Look for changes in the MAIN MENU statistics column: "Number of deletes
pending"
This 'Update Delete Status function' runs a scan of the database looking
for three basic problems.
1. messages marked delete by the client but status is still 000;
2. messages having no 'owner mailbox'** and
3. messages unattached to a user.
These are three issues which DBMA users have emailed me about. From DBMA
user feedback I deduce this is sometimes caused by mucking around in the
datatbase with an editor like MySQLCC, PHPMyAdmin or phpPgAdmin. There
may also be issues with some patched/migrated database schemas; and
surely there's the gremlins and quirks.
If DBMA finds some orphaned messages DBMA will, with gentle grace, set
their dbmail_messages.status to a mere 001 and their deleted_flag to a
certain "1" preparing them for the ultimacy of the maintenance cleanup.
Look at the "Number of deletes pending:" column of the DBMA statistics
(Main menu) to observe any changes after doing "Update Delete Status".
Why status 001?
You are the real 'administrator' and must be afforded a chance to review
what you have done.
If you don't like '001', go nuts, repeat the action and they will all be
set to '003', the final bell. The next crontab 'dbmail-util -d' removes
them from the database. (You may someday benefit from this two-step
flexibility.)
NOTE: The Update delete status function is not available to "Group
Administrators" under the RESTRICTGroupID constrict.
best...
Mike
