I recently had to switch to using ClamAV 1.0.9 remotely for email scanning, pending building it (or a newer LTS version) to run directly on my Postfix mail-server machine.
Besides it being a bit slower over TCP, it has the following problem: it gives a "Broken Pipe" failure if the file to be scanned is too big. So far, this hasn't happened with actual email, but an unusually big attachment could cause it. In other words, using ClamAV over TCP severely limits it usefulness -- in a manner far, far worse than its longstanding (and wildly anachronistic) 32-bit file size limit. (How long has Linux supported 64-bit file sizes and offsets?) P.S. Does anyone know of some TCP-related configuration parameters (in the TCP stack or clamd itself) that might fix this Broken Pipe problem without causing something worse? (Obviously TCP per se can be used to transfer really big files, even well beyond 2**32 bytes.) On Mon, 10 Nov 2025 11:16:48 +0000 (GMT) Andrew C Aitchison via clamav-users <[email protected]> wrote: > On Mon, 10 Nov 2025, Massimo S. via clamav-users wrote: > > > version 0.103.10 is outdated, of course. > > But it's the last build that do not use Rust as development platform. > > > > And this is the last build available ported to AOS and eCS that are > > modern OS/2 distros. Since 30th September 2025 freshclam do not > > update anymore the signatures on these OSs. > > > > I'm asking to developers if it's possible to let v. 0.103.10 > > (OS/2-AOS-eCS) to let downlod signatures, since it's very hard > > (maybe impossible) to port latest ClamAV versions developed with > > Rust to this 32bit OS. > > > > Or possibly to public an updated signatures DB compatible with the 0.103.10 > > build. > > I doubt that it matters whether freshclam and clamav are the same version; > just use a modern freshclam to update your signatures. > > You don't even need to run freshclam on the OS/2-AOS-eCS machine, as > long as you have a networked file system, rsync or similar on both machines > though do remember to restart the daemon after each update. > > Alternatively configure clamdscan to use a remote scan daemon. > `man clamd` is not very clear, but set TCPAddr and TCPSocket in clamd.conf > on the OS/2 machine to point at your server (running current ClamAV). > https://lists.clamav.net/pipermail/clamav-users/2025-October/014349.html > > This is likely to work even if/when the signature format changes. > _______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
