> > If this can be used to do individual files, well then > > sure - it would definately simplify things > > > but I do think there will sharring issues; James gfoes > > to process a mail but it's being scanned .... > > If you are doing this in a matcher, it is a synchronous process from the > perspective of the matcher. The matcher needs to get the > response in order > to effect changes in the message state. Other spooler threads won't be > accessing the message, either, because it is owned by the one calling the > matcher.
This is exactly what I would do (if I understtod correctly the matcher/mailet behaviour): inside a "HasAttachment" matcher, processed by the current spooler thread, I would invoke a mailet that: 1) creates a temporary work directory with some unique name; 2) copies the attachments into that directory; 3) starts the inline scanner on all files of that directory; 4) waits synchronously (waitFor()) the result (only this spooler thread would wait, isn't it?); 5a) if no firus is found just deletes the work directory and that's it (most of the times it will be this way); or 5b) if a virus is found ... does something - to think about. Perhaps all steps from (1) to (5a) should be done in a new matcher, and have the mailet just do (5b). Thanks, Vincenzo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
