***UNCHECKED*** Re: getting in subjects of received emails

[Nikolai Maziashvili]

Hi Conny,

I never meant to imply than freshclam not being installed causes 
UNCHECKED mark, but rather out of date clam DB and freshclam just being 
tool to update that DB.
Strangely on CentOS6 freshclam was installed out of the box and after 
updating DB UNCHECKED mark disappear from subject line.
But now, after reviewing ticket you mentioned (thank you for that) i 
understand why.
Now everything works properly.
Thank you again for feedback.

Regards,
Nikolai

On 10-12-2014 13:21, Cornelius Hald wrote:
> Hi,
> 
> from my experience there are at least two things that could lead to 
> this
> issue on CentOS7.
> 
> 1) Amavisd and clamav are not connected properly. See:
> https://issues.kolab.org/show_bug.cgi?id=3565
> 
> 2) Sometimes amavisd does not start properly after reboot. I actually
> don't know why. Try:
> systemctl restart amavisd
> 
> BTW FreshClam does not get installed automatically. Which is bad, but
> doesn't cause UNCHECKED messages. See:
> https://issues.kolab.org/show_bug.cgi?id=3996
> 
> Hope that helps!
> Conny
> 
> 
> On Tue, 2014-12-09 at 21:37 +0100, Nikolai Maziashvili wrote:
>> Hi everyone, i'm running fresh KOLAB33 on CentoOS7 machine and getting
>> ***UNCHECKED*** in subjects of received emails. I assumed that clamav 
>> db
>> was out of date and tried to refresh it by running freshclam, but to 
>> my
>> surprise it was not on the system???
>> Clamav is not the one responsible for spam checking? Or should i 
>> install
>> it manually (provided by clamav-update)? And if yes, should i keep
>> anything specific in my mind, regarding kolab, when editing freshclam
>> config file?
>> Thanks in advance,
>> Nikolai
>> _______________________________________________
>> users mailing list
>> users at lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users