This macOS clamAV repo is now part of MacPorts. The details below this notice are deprecated. To install: sudo port install clamav-server sudo port load clamav-server macOS-clamAV. A simple macOS clamAV configuration with scheduled volume scans and on-access scans of user Downloads and Desktop directories.

1. Clamav Mac Dmg Software
2. Clamxav

Clamav Mac Dmg Software

• ClamXav for Mac scans your computer or selected files and folders for viruses to help keep it running smoothly. With clear controls and instructions, this program makes it easy to keep your data.
• ClamXAV keeps threats at bay and puts you firmly in charge of your Mac’s security. Scan a specific file or your entire hard drive. Set it to scan automatically or run instant checks on suspicious files. It’s entirely up to you. Silent and deadly. ClamXAV is light on processing but heavy on malware.

There are a number of solutions on the market for scanning a Mac for files that have become infected with a virus or macro-virus. Many of these have a negative return on investment. So customers can instead go the open source route to scan files and quarantine them. And customers can use Jamf Pro to enable doing so. This page is meant to provide a quick and dirty guide to doing so, along with how this might be packaged and potentially tracked with Jamf Pro. First, we’ll install and configure a free tool called clamav.There are a number of ways to install clam. For this example, just to get it done quickly, we’ll use homebrew which is simply brew with the install verb and clamav as the recipe to be brewed:This is going to place your configuration files in /usr/local/etc/clamav and these cannot be used as those supplied by default are simply sample configurations. Because the .sample files have a line that indicates they are an “Example” they cannot be used. So we’ll copy the sample configuration files for freshclam.conf and clamd.conf (the demonized version) and then remove the Example line using the following two lines:Next, we’ll need to update the virus definitions for clamav. This can be run without the fully qualified file path but we are going to go ahead and include it as some computers might have another version installed (e.g. via macOS Server):The initial scan should cover the full hard drive and can be run as clamscanYour routinely run jobs should be setup to a quarantine location. Because all users should be able to see their data that was quarantined we would write this to /Users/Shared/Quarantine. We can then use a standard clamscan to scan the system and then “move” quarantined items to that location and log those transactions to /Users/Shared/Quarantine/Quarantine.txt.You can then use an Extension Attribute to read the Quarantine.txt file:Every environment is different. When combined with standard mrt scans using the built-in malware removal tool for macOS, clamAV can provide a routine added protection to isolate and help you remediate infections.Finally, it seems like I have yet to discuss antivirus and malware without getting into the conversation about whether you need it or not. In this post I am in no way taking a side on that argument, and it’s worth mentioning that I’m also not using “antivirus” to exclusively reference viruses but instead including all forms of malware. Rather, I’m exploring options for scanning systems routinely.You can easily run this nightly and parse the quarantine.txt file prior to picking it up with the Extension Attribute routinely in order to provided an additional layer of defense against potential threats to the Mac. Putting all of this into a software package would be rudimentary, and could benefit many organizations without putting our coworkers through the performance hit that many a commercial antivirus solution brings with it.Note: A special thanks to Steven Thomas Smith for pointing out that clamdscan is multi-threaded!

ClamAV on Mac with Kerio MailServer

© May 2019 Anthony Lawrence

I downloaded ClamAV source from https://www.clamav.net. A simple ./configure; make; make install in the source directory was all that was required (thogh you do have to install the Xcode Tools from your install cd if you haven't already).

Well, gosh, that was easy. Now what?

Well, that depends on what you plan to do with it. If you only plan to scan files on your drives, there's nothing else you need.If you are planning to use the supplied 'clamav-milter' (see Sendmail Milters),you need to add the milter to your mail configuration (and you would have needed to run './configure --enable-milter' before compiling).See clamav-milter(link dead, sorry)for very basic instructions on adding this milter to sendmail.

In my case, I wanted to use it with Kerio Mailserver.

Kerio MailServer is able to work with several virus scanning engines. The preferred primary is McAfee, but (depending on your OS platform) other plugins can be used. As of version 6.1, they introduced the ability to do dual scanning, which allows each message to be scanned by two different AV products (one must be their McAfee option). Dual scanning can increase the chances of detecting viri.

Now with the 6.2 release (available in beta as I write this), ClamAV support has been added and can be used either as the stand-alone scanner or as the secondary to McAfee.

To use ClamAV with Kerio MailServer you need to get /usr/local/sbin/clamd running on the Mac (basically the same procedure applys to Linux) . That's going to requre editing (with sudo) two configuration files: /usr/local/etc/clamd.conf and /usr/local/etc/freshclam.conf

ClamAV forces you to at least comment out the 'Example' line from these files:

# Comment or remove the line below.
Example

For freshclam.conf that may be all you want or need to do, but at least this made you aware that the file exists and that you do have options to control freshclam. Freshclam is the program that updates Clamav's virus database, so you probably want to set it to run periodically with cron.

You'll need to do a little more with /usr/local/etc/clamd.conf. In addition to commenting out the 'Example', you need to set 'TCPSocket 3310' and you probably want to set 'TCPAddr 127.0.0.1' unless Kerio is running on a different machine than ClamAV.

With these set, you can start /usr/local/etc/clamd. After starting it, you should see it listening on port 3310:

$ sudo /usr/local/sbin/clamd
$ sudo lsof -i:3310
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
clamd 18975 root 0u IPv4 0x2f92e88 0t0 TCP localhost:dyna-access (LISTEN)

Of course you'll want clamd starting up on reboot. It would be best to handle that through Launchd but you could also just add it to /etc/rc if you want. Launchd gives you more control to restart if necessary.

Clamxav

Kerio automatically tests Clam with an EICAR file but you can send the same pattern to a local user if you aren't the trusting sort. I tested, and found the expected entry in the Kerio Security Log:

I'm glad to see this support added to Kerio. I think it would have been better if they had implemented milter support because that would allow even more options for Kerio users, but this is a welcome addition.

Got something to add? Send me email.