BUG: Failure to handle unexpected output

[Alex Regan]

Hi,
I'm using amavisd-new-2.9.1 on fedora20 with Sophos SAVI and it's been 
working okay for a few days. I've now run into a problem where sophos 
thinks it has encountered an encrypted file (it's actually not 
encrypted), and writes output that apparently amavisd can't handle:

Mar  4 09:38:13 mail01 amavis[5352]: (05352-16) (!)run_av (Sophos-SSSP) 
FAILED - unexpected , output="FAIL 0212 
/var/spool/amavisd/tmp/amavis-20150304T092615-05352-fIDvvoCv/parts/p004\r\nFAIL 
0212 
/var/spool/amavisd/tmp/amavis-20150304T092615-05352-fIDvvoCv/parts/p002\r\nDONE 
FAIL 0212 File was encrypted\r\n"
Mar  4 09:38:13 mail01 amavis[5352]: (05352-16) (!)Sophos-SSSP 
av-scanner FAILED: CODE(0x546df48) unexpected , output="FAIL 0212 
/var/spool/amavisd/tmp/amavis-20150304T092615-05352-fIDvvoCv/parts/p004\r\nFAIL 
0212 
/var/spool/amavisd/tmp/amavis-20150304T092615-05352-fIDvvoCv/parts/p002\r\nDONE 
FAIL 0212 File was encrypted\r\n" at (eval 133) line 900.

I'll also have to contact Sophos and ask them why they think a file is 
encrypted when it's really not, but I wanted to see if this was 
something I should be concerned with and how to handle it.

In fact, is there a way to log or report or better indicate in the logs 
that an error has occurred? How can I control where the amavisd critical 
messages are stored?

Thanks,
Alex