Jeff - just a follow up by way of explanation and to help raise your comfort levels!
OS X and OS X Server are special "Apple-flavoured" implementations of Unix.
To provide the "Server" functionality, Apple uses a number of open source software solutions.
Note that this is a simplistic and non-exhaustive list
For Web services - its Apache / PostgresSQL / PHP ( as opposed to Apache / MySQL / PHP )
For Mail Services - its Dovecot / Postfix / Amavis / Spamassassin / ClamAv
They have provided a "GUI" in the form of Server.app and a command line tool in the form of "serveradmin" to manage these services so that an average person can make changes to "some" things that will keep their "state" across OS system upgrades etc. Server.app and Serveradmin wrap a conglomeration of Shell, Perl and Ruby and Python scripts around these services and most of the time ( certainly since 10.8) they work reasonably well.
Apple maintains these "states" through .plist files and direct manipulation of the various config files.
The rule i've found is - anything that has a setting in server.app and or serveradmin should be set via those mechanisms.
Anything else is fair game!
But at the heart of it all - services like Mail are just Apple-wrapped implementations of open source software.
Why am I telling you this. Because there is a wealth of information on the interweb regarding these chunks of software, their configuration and troubleshooting. You just have to supply the "how does this fit in the OS X" context.
The first thing to do in your quest for that context is to make sure the "locate" database is up to date -
$ man locate #( for info on the command)
$ sudo /usr/libexec/locate.updatedb #( to update the locate database - I think its part of the weekly maintenance script??)
$ locate -i clam # ( the -i to ignore case)
might give you a list in part that looks like this ....
/Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/CommonEx tras/63-setup_clamav.sh
/Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/Promotio nExtras/63-setup_clamav.sh
...............................................
...............................................
/Library/Logs/Mail/clamav.log
/Library/Logs/Mail/clamav.log.0.bz2
/Library/Logs/Mail/clamav.log.1
/Library/Logs/Mail/clamav.log.2.bz2
/Library/Logs/Mail/clamav.log.3
/Library/Logs/Mail/clamav.log.4.bz2
/Library/Logs/Mail/clamav.log.5
/Library/Logs/Mail/clamav.log.6.bz2
/Library/Logs/Mail/clamav.log.7
/Library/Logs/Mail/freshclam.log
/Library/Logs/Mail/freshclam.log.0.bz2
/Library/Logs/Mail/freshclam.log.1
/Library/Logs/Mail/freshclam.log.2.bz2
/Library/Logs/Mail/freshclam.log.3
/Library/Logs/Mail/freshclam.log.4.bz2
/Library/Logs/Mail/freshclam.log.5
/Library/Logs/Mail/freshclam.log.6.bz2
/Library/Logs/Mail/freshclam.log.7
/Library/Server/Mail/Config/clamav
/Library/Server/Mail/Config/clamav/clamd.conf
/Library/Server/Mail/Config/clamav/freshclam.conf
/Library/Server/Mail/Data/scanner/clamav
/Library/Server/Mail/Data/scanner/clamav/db
/Library/Server/Migrated/private/etc/clamd.conf
/Library/Server/Migrated/private/etc/freshclam.conf
/Previous System/System/Library/LaunchDaemons/org.clamav.clamd.plist
/Previous System/System/Library/LaunchDaemons/org.clamav.freshclam-init.plist
/Previous System/System/Library/LaunchDaemons/org.clamav.freshclam.plist
$ cat /Applications/Server.app/Contents/ServerRoot/System/Library/ServerSetup/CommonEx tras/63-setup_clamav.sh ( print the file to terminal) use "less" instead of "cat" and you can go back and forth in the file with the B and F keys ( q to quit).
This file is just a shell script that sets up the ClamAV on the system when Server.app is installed. It shows the permissions and owners that should be on various files. How do you increase the log level to debug for clam so you can see whats going on ?
$ sudo serveradmin settings mail:postfix:virus_log_level = "debug"
www.krypted.com provides a whole bunch of info on OS X Server setup, log levels etc. - Why not have a look?
cheers
Gerry