| Surely it would be much better, but as you say about the Norman | system, it | is be more complex to develop, and could be very OS dependent. norman runs on both Unix/WinTel platforms so it shouldn't be an issue, but yes, this approach would be application specific (frown) but if it's relatively easy to implement i don't see that being a problem.
| I agree, but perhaps the message texts could be optionally ignored. configuration issue - would work out great. | call as with java.lang.Process.waitFor(): i'm not saying it won't work, it's just a cludge to tie everything together. no matter what we still need to communicate with the vscan system - which is why using one with an open API is preferable. you mention doing a test to see what the cpu load might be - look also to the time constraint ... |> as for the file extension mailet, that would be rather easy; |> but i am not sure on it's overall usability as it would need |> to configured per mailbox. | Why per mailbox? as an ISP, the user is the one in control and needs to be able to decide herself to acept or refuse certain files. i cannot arbitrarily say that all attachments that match this mask will be deleted as i would loose business. _______________________ thanks, alan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
