Hi Chad,
Your original recommendation was:
"Change your "mynetworks" line in /etc/postfix/main.cf to something like
this if you want to allow the whole 192.168.0.0/16 network to be able to
relay through it:
mynetworks = 127.0.0.0/8 [::1]/128 192.168.0.0/16
I did this, but find that, when I
There were two - one was 5209, the other 5211, both the same.
> -Original Message-
> From: Blueonyx On Behalf Of Michael
> Stauber via Blueonyx
> Sent: Monday, September 25, 2023 8:45 PM
> To: blueonyx@mail.blueonyx.it
> Subject: [BlueOnyx:26519] Re: No clamd server appears to be
Hi Darren,
That appears to have worked, however, my clamav-daemon.socket did not look like
that, it only had:
ListenStream=/run/clamav/clamd.ctl
ListenStream=7358
Was this by chance a BlueOnyx 5209R?
--
With best regards
Michael Stauber
___
Hi,
That appears to have worked, however, my clamav-daemon.socket did not look like
that, it only had:
ListenStream=/run/clamav/clamd.ctl
ListenStream=7358
For the listenstream parameters.
Thanks
> -Original Message-
> From: Blueonyx On Behalf Of Michael
> Stauber via Blueonyx
>
Hi Darren,
I believe I am having a problem caused by the change you've made
> here - the clamd process is constantly running at 100% cpu all
> the time. The maillog shows this repeated continuously:>
clamd[232355]: TCP: Cannot bind to [127.0.0.1]:7358: Address already in use
clamd[232355]:
Hi,
I believe I am having a problem caused by the change you've made here - the
clamd process is constantly running at 100% cpu all the time. The maillog shows
this repeated continuously:
Sep 25 02:32:48 intersys18 clamd[232355]: Received 0 file descriptor(s) from
systemd.
Sep 25 02:32:48
