Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
So I don't know why ClamAV is so difficult to maintain.
I won't bore you guys with all the details of the issues I was having, suffice it to say I uninstalled using apt several times, tried reinstallng from the repo several times trying to get it working and finally went to trying to install from source. After following the instructions to install from source based on the instructions on the clamav site. After installing and restarting I am now getting the following error when running freshclam:
Hi,
I've recently tried it with two different email server set-ups and can confirm that the steps given at /stretch/filtering-viruses-malware/—in combination with rspamd—which makes interesting reading, work well. However, I finally opted for a different setup, as posted recently in this topic.
It is now up and running for 24/7 use.
I definitely would not compile it from source.
After following the instructions to install from source based on the instructions on the clamav site. After installing and restarting I am now getting the following error when running freshclam
When you compile it from source, did you create the .deb package?
After following the instructions to install from source based on the instructions on the clamav site. After installing and restarting I am now getting the following error when running freshclam
When you compile it from source, did you create the .deb package?
No, per the instructions I downloaded the tar file, untared it, installed the needed OpenSSL libraries, configured make, and make installed, followed by a reboot (this is from my memory, so might have missed a step.)
That said, following the instructions above have me somewhat working. So heres to hoping.
sephstorm wrote:No, per the instructions I downloaded the tar file, untared it, installed the needed OpenSSL libraries, configured make, and make installed.
I understood. Then it is clear why dpkg indicates that
This will spit out lots of output; the options given mean it shouldn't prompt you about unsigned files. When it finishes you should find your .deb in the parent directory, so cd up one level and install like so (as root):