There is something that puzzles me:
With Groupsgield 5.2 and VSAPI 2.0 messages that are submitted to the IS (by MAPI or SMTP)are placed in a VSAPI queue, so they are scanned first. But when proactive scanning is disabled or enabled but with the maximum of 30 messages in the queue, messages are submitted to the store and scanned on-access or by the background process,if enabled, therefore unscanned messages can be present in the IS.
Is this statement correct?
Now the product guide of Groupshield 6.0 tells me that each time a message is written to the store, it will be scanned first. Is 6.0 different than 5.2 in this way, or under heavy load, items will not be scanned till accessed, same as in 5.2? AFAIS there is no difference in proactive/backgound scan between the two products
paul
With Groupsgield 5.2 and VSAPI 2.0 messages that are submitted to the IS (by MAPI or SMTP)are placed in a VSAPI queue, so they are scanned first. But when proactive scanning is disabled or enabled but with the maximum of 30 messages in the queue, messages are submitted to the store and scanned on-access or by the background process,if enabled, therefore unscanned messages can be present in the IS.
Is this statement correct?
Now the product guide of Groupshield 6.0 tells me that each time a message is written to the store, it will be scanned first. Is 6.0 different than 5.2 in this way, or under heavy load, items will not be scanned till accessed, same as in 5.2? AFAIS there is no difference in proactive/backgound scan between the two products
paul