1

Topic: Logwatch question related to ClamAV installation OUTDATED!

==== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Linux/BSD distribution name and version: Ubuntu 14,04
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- Related log if you're reporting an issue: mail.log
====

Hello, I set up my mail server a few days ago and just began paying attention to the Logwatch emails and noticed the following:

--------------------- clam-update Begin ------------------------


Last ClamAV update process started at Sat Aug  6 23:25:22 2016

Last Status:
    WARNING: Your ClamAV installation is OUTDATED!
    WARNING: Local version: 0.98.7 Recommended version: 0.99.2
    DON'T PANIC! Read http://www.clamav.net/support/faq
    main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder: amishhammer)
    nonblock_connect: connect timing out (30 secs)
    Can't connect to port 80 of host db.local.clamav.net (IP: 128.199.133.36)
    Downloading daily-22041.cdiff [100%]
    daily.cld updated (version: 22041, sigs: 486552, f-level: 63, builder: neo)
    bytecode.cvd is up to date (version: 283, sigs: 53, f-level: 63, builder: neo)
    Database updated (4705395 signatures) from db.local.clamav.net (IP: 168.143.19.95)

---------------------- clam-update End -------------------------

Is this something I need to do anything about or is it something you take care of when you develop the next release?

I tried to make sense of the URL they direct me to (DON'T PANIC! Read http://www.clamav.net/support/faq) but it makes no sense at all (to me anyway) so I am hoping you can provide some insight.

Thank you.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: Logwatch question related to ClamAV installation OUTDATED!

rp wrote:

    WARNING: Local version: 0.98.7 Recommended version: 0.99.2

Try to upgrade clamav to the latest version with 'apt-get update && apt-get upgrade'.

3

Re: Logwatch question related to ClamAV installation OUTDATED!

Try to upgrade clamav to the latest version with 'apt-get update && apt-get upgrade'.

Yep, tried that and this is what I get:

Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  linux-headers-generic linux-headers-virtual linux-image-virtual
  linux-virtual
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.


Could it be that Ubuntu is not looking at all available repositories?


ubuntu@mail:~$ sudo apt-get update && sudo apt-get upgrade
Ign http://us-east-1.ec2.archive.ubuntu.com trusty InRelease
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates InRelease
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports InRelease
Hit http://us-east-1.ec2.archive.ubuntu.com trusty Release.gpg
Hit http://us-east-1.ec2.archive.ubuntu.com trusty Release
Hit http://security.ubuntu.com trusty-security InRelease
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/main Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/restricted Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/universe Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/multiverse Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/main amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/restricted amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/universe amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/multiverse amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/main Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/multiverse Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/restricted Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-updates/universe Translation-en
Hit http://security.ubuntu.com trusty-security/main Sources
Hit http://security.ubuntu.com trusty-security/universe Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/main Sources
Hit http://security.ubuntu.com trusty-security/main amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/restricted Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/universe Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/multiverse Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/main amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/restricted amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/universe amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/multiverse amd64 Packages
Hit http://security.ubuntu.com trusty-security/universe amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/main Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/multiverse Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/restricted Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty-backports/universe Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/main Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/restricted Sources
Hit http://security.ubuntu.com trusty-security/main Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/universe Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/multiverse Sources
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/main amd64 Packages
Hit http://security.ubuntu.com trusty-security/universe Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/restricted amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/universe amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/multiverse amd64 Packages
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/main Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/multiverse Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/restricted Translation-en
Hit http://us-east-1.ec2.archive.ubuntu.com trusty/universe Translation-en
Ign http://us-east-1.ec2.archive.ubuntu.com trusty/main Translation-en_US
Ign http://us-east-1.ec2.archive.ubuntu.com trusty/multiverse Translation-en_US
Ign http://us-east-1.ec2.archive.ubuntu.com trusty/restricted Translation-en_US
Ign http://us-east-1.ec2.archive.ubuntu.com trusty/universe Translation-en_US

4

Re: Logwatch question related to ClamAV installation OUTDATED!

OK, no update available for clamav package. It's safe to not upgrade the package, but you still need to keep 'freshclam' service running to update clamav virus signature database.