Comment 10 for bug 2046581

If adjustments to the wording are needed to add context, here are a few places to do so:

./libfreshclam/libfreshclam_internal.c:2454: logg("^Your ClamAV installation is OUTDATED!\n");
./libfreshclam/libfreshclam_internal.c:2664: logg("^Your ClamAV installation is OUTDATED!\n");
./libfreshclam/libfreshclam.c:562: logg("^Your ClamAV installation is OUTDATED!\n");

And from the HTML faq included with the package:

<h2 id="your-clamav-installation-is-outdated"><a class="header" href="#your-clamav-installation-is-outdated">Your ClamAV installation is OUTDATED</a></h2>
<p>This message does NOT indicate that you are unable to download the latest CVD update! You'll get this message whenever a new version of ClamAV is released. In order to detect all the latest viruses, it's not enough to keep your database up to date. You also need to run the latest version of the scanner.</p>

I suppose it's the all-caps words that catch the eye. The code stanzas that include these logg() calls are testing the version string against what it can query from DNS Update Info. In general this feels redundant with the Ubuntu packaging system, that should already flag to the user if their packages are out of date, and therefore are providing misleading information which could lead them to update to non-Ubuntu versions. On the other hand, clamav specifically needs the version updates in order to validly consume the streamed data, so flagging the discrepancy is not necessarily wrong. So I'm not sure whether the warning should be disabled (e.g. via the 'vwarning' configuration toggle) or to leave it but perhaps refine the wording.