If we are looking for a specific "lost" message, it is a tedious job but using ultra edit helps as it can search and display multiple instances of what ever you are searching for.  This is no differant for any mail logs however and we have gotten good at it.  HOWEVER, when we have chronic "wolf criers", we end up charging for searching for, and resolving "lost mail" issues that are not caused by our systems (most).  This seems to slow down the requests!

My own experience with searching for specific addresses/messages has been that grep in linux is more efficient that anything else I've tried.  Migrating logs to a database and search was tedious, even with a custom script to do the bulk insert.  My vote would be for Logsat to include an option to log to a DB table but would not make it a top priority.

I have found a shareware program called 'search and replace'.  It's very fast at finding and listing any specific text in the logs, even multiple instances.  I use a file name mask to search by date range. Database queries are great but this is much faster and very easy.