2
ClamAV stopped working
Problem reported by Patrick Mattson - 12/22/2021 at 5:26 PM
Submitted
I seem to have a problem with Clam AV since moving to 8025. I had an open ticket prior to the new version, they thought the new version might fix things.

Delivery logs are showing the following error: ClamD Checks error: No connection could be made because the target machine actively refused it 127.0.0.1:3310 | error

I checked my logs on December 18, was running Oct 2021 version, and this string was not there.

I tried to remove the two config files and restart the service, it created new config files, but still seeing the issue.

Is anyone else seeing this?

6 Replies

Reply to Thread
0
Zach Sylvester Replied
Employee Post
Hello Patrick, 

Thank you for posting to the community. 
I just did an upgrade from 7957 to 8025. After this, I tested clam av by sending an email and this is what I got. 
[2021.12.22] 17:49:50.172 [70501000] SpamCheck Processing Thread Started
[2021.12.22] 17:49:50.189 [70501000] Windows Defender Checks started.
[2021.12.22] 17:49:50.210 [70501000] Windows Defender Checks completed.
[2021.12.22] 17:49:50.217 [70501000] ClamD Checks started.
[2021.12.22] 17:49:50.266 [70501000] ClamD Checks completed.
[2021.12.22] 17:49:50.290 [70501000] Filetype Checks started.
[2021.12.22] 17:49:50.290 [70501000] Filetype Checks completed.
[2021.12.22] 17:49:50.300 [70501000] Spam Checks skipped: User authenticated
[2021.12.22] 17:49:50.300 [70501000] Spam Checks completed.
[2021.12.22] 17:49:50.300 [70501000] SpamCheck Processing Thread Completed
It appears that ClamAV is working as expected when you upgrade. I understand that you currently have a ticket open about ClamAV not working we will continue working with you to resolve the issue. If anyone else is having this issue please let us know and open a ticket with us so we can help you. 

Happy Holidays, 

Please note our office will be closed Thursday, December 23 in observance of Christmas. Please see the 'Business Hours and Holidays' link in my signature for more information. 
Zach Sylvester
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
Patrick Mattson Replied
Thanks Zach. Which log are you seeing those in?

I am not seeing Windows Defender referenced in the Delivery Logs.
0
Zach Sylvester Replied
Employee Post
Hey Patrick, 

This is in the spam checks log. You can locate this if you go to TroubleShooting->Logs You need to make sure that your spam checks are set to detailed. 
When you get an email you will see it populate with this information. Also to see the Defender logs you need to make sure that it's enabled by going to Settings->AntiVirus. Please let me know if you have any questions. 

Happy Holidays, 
Zach Sylvester
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
pjeski Replied
I just had ClamAV stop working on my server at work, but still working fine on the one at home. I looked at the conf files, and they had 8.3 paths (C:\PROGRA~2\SMARTE~1\...). That's bad form. I changed them all to quoted long file name paths ("C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Clam\...") and now both servers are working fine again.
0
Zach Sylvester Replied
Employee Post
Hey Pjeski, 

Thanks for letting us know your solution. May I ask which config file that was specifically? 

Kind Regards, 
Zach Sylvester
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
pjeski Replied
Fixing "C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Clam\etc\clamd.conf" is what got clam working again. I also fixed "C:\Program Files (x86)\SmarterTools\SmarterMail\Service\Clam\etc\freshclam.conf" for good measure.

Reply to Thread