I'm a big fan of not writing code someone else already has done, or compiling software for my distro if there is already a package available, heck I'm a sysadmin, I demand stability foremost, after that I'll think about adding things like performance, and cool flashy things
Here's the regular process I go through when I'm installing ClamAV to a Debian/Ubuntu mailserver:-
- Run the command "apt-cache search clam-av"
- Figure out which of the 42-billion options I want (normally something like clamav, clamav-milter, and clamav-update, or whatever else they've call the three packages that provide a) the actual application, b) the milter for sendmail, and c) the automatic update scripts).
- Realise when the packages install and I try to start them that the "stable" packages are years out of date... so have to go and figure out how to get the newer packages.
- For ubuntu, edit /etc/apt/sources.list to add in the "backports" repository, for Debian, use the "volatile" repo.
- Pray those are running at least recent when I update...
- If necessary, rant, moan, carry on, when I discover even that package is ages out of date, so I need to compile from scratch... at this point, I generally decide to give up and use an out of date version, but I keep an eye on the packages, same as everything else on the mailserver...
One all the rigmarole above is done, it's just a matter of adding clamav-milter to sendmail, and then watching it for a day or two to make sure mail is still flowing cleanly. Hopefully at this point, no viruses will get through
I actually don't have any users on my mailserver who I'm terribly concerned will trigger a virus if they get the mail, I just want to bounce it at the MTA to save on the hassles of even having the darn things around