Squat Failure Behavior Improvement?

[Lee]

Im running cyrus 2.2.10, and when i run squat -r -s, squat fails on 
certain messages or users because there is one corrupt message in the 
user's mailbox. This isnt a huge issue in itself because i can 
obviously remove the corrupt file or run reconstruct and then restart 
squat. The bigger issue, is that on a system with 1000s of users, if i 
plan to run squat as an automatic event in the future, i now have to 
worry that one corrupt message in even a single message will stop 
squatter in its tracks and i wont know it unless i'm constantly 
watching the logs for it.

Is there a reason squat is not designed to simply continue indexing 
after a message or user fails to be indexed? This seems like a pretty 
big problem for anyone running a large system where occasional file 
corruption is inevitable. Is there something i can do to fix this 
problem?

Thanks,
Lee

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html