Jeremy Harris via Exim-users schreef op 2021-10-10 12:10:
On 09/10/2021 23:25, Oliver Heesakkers via Exim-users wrote:
I've done some more testing and have been reliably able to reproduce
the problem. The problem always occurs (in my test setup) when I have
av_scanner set up to a clamd TCP socket, regardless whether it's local
(127.0.01), remote, IPv4 or IPv6, they all SIGSEGV.
When I switch to a local clamd.sock, the problem vanishes.
Aha. This looks like a FreeBSD platform bug in Exim, hitting the
use of clamav/tcp.
If you need a fix for tcp use, are you in a position to compile exim?
--
Cheers,
Jeremy
I always compile my own Exim.
I moved some stuff around and found some RAM to use a local clamd, it's
been SIGSEGV free since then, so personally no, I no longer have a real
need. For the official Exim port though, it might be a good idea to get
a patch in before they update it (no, I'm not the maintainer).
--
Oliver
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
