This is a bit interesting,
I have a couple of servers that show the following:
[root@testserver ~]# rpm -qa | grep clam
smeserver-clamav-1.2.0-21.el4.sme
warning: only V3 signatures can be verified, skipping V4 signature
clamav-db-0.93-2.el4.rf
clamd-0.93-2.el4.rf
clamav-0.93-2.el4.rf
None of them send e-mail notices that clam is out of date, However, freshclam gives the following:
[root@testserver ~]# freshclam
ClamAV update process started at Fri Jul 25 08:52:28 2008
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.93 Recommended version: 0.93.3
DON'T PANIC! Read http://www.clamav.net/support/faq
main.cld is up to date (version: 47, sigs: 312304, f-level: 31, builder: sven)
daily.cld is up to date (version: 7826, sigs: 59420, f-level: 33, builder: ccordes)
As you can see the database is up to date but scanning engine is not at the latest build. You will find that we run a week or two behind ClamAV on pushing the engine updates. If you think about the process a bit, this is only reasonable. After ClamAV releases their final package it needs to be packaged for SME.