> > Is keeping a message counter feasible, given the design of the code? > It's perfectly feasable and I've just done it when you enable debug to help > you (look in the CVS code I've just committed - mbox.c version 1.66). However > please don't enable debug all the time, and remember that enabling debug > now also leaves the temporary files around to aid (of course!) debugging. > > Look for the "Deal with email number %d" messages.
This is better than before, but the --debug option still generates an enormous amount of noise. Would it be possible to have a specific option that only explains which mailbox message the infected file is in? Trying to figure out which message is infected is certainly the next step once you've found an infected file, so I think this option would have a very broad appeal. Something like "clamscan -mbox -iN <files>" would be great. Is this possible/reasonable? Jeffrey Moskot System Administrator [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
