clamscan etc log perms, can't keep logs

The default script that runs clamscan over a goodly portion of the system on a daily basis is haveing cron send messages to /var/spool/mail/mail, so I changed perms on that file so kmail could fetch it from the local mail box and set kmail up to do that. I find I had about 125k worth of messages because the scripts I copied over from the old drive aren't quite compatible with this install. I have fought tooth and nail with the system and it blanket denial of my ability to read a log file unless I either play with the parent locations ownership and permissions, so much so that I create in my home dir, a log subdir so that all these utilities could both write a log file and I could read it. I am eventually going to have to create some logrotate entries to handle maintenance on these log files, but at least I can read them. Which is the preferred method of dealing with this, my way, or hacking up owners and permissions all over the /var/log tree? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>