GWAVA blocking what it shouldn't

From GWAVA4

Set your log levels to Verbose or Diagnostic

See Logging for more information on how to change the logging levels. The logs should clearly identify what services were triggered and the cause.

Is the issue replicable?

If so, diagnosing the problem should be a simple matter of looking at the log and observing what events seem to be triggering that shouldn't be.

The Scanner/Engine log for the GWAVA component will clearly display for example if

• a virus is detected
• a message is oversized
• a text filter matches the content (and which text filter)
• a message contains attachments that are fingerprinted as a particular type.

etc.

If replicable, consider quarantining the message

The GWAVA QMS clearly lists the events that were triggered by this message in the Properties.