On Tue, 2021-09-28 at 15:30 +0200, mau...@gmx.ch wrote:
> Hello
>
> never found the solutions for this..
>
The error messages aren't a lot of use without also knowing:
- what arguments are you using on the spamc command line?
- where is the spamd instance you're trying to connect to,
i.e. is
On 9/28/2021 9:30 AM, mau...@gmx.ch wrote:
Hello
never found the solutions for this….
Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II
*Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed, retrying
(#1 of 3): Connection refused*
*Sep 28 15:11:23 nmail
On 9/28/2021 9:30 AM, mau...@gmx.ch wrote:
Hello
never found the solutions for this….
Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II
*Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1
failed, retrying (#1 of 3): Connection refused*
*Sep 28 15:11:23 nmail
Hello
never found the solutions for this..
Sep 28 15:11:22 nmail spamd[3826]: prefork: child states: II
Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed,
retrying (#1 of 3): Connection refused
Sep 28 15:11:23 nmail spamc[4525]: connect to spamd on 127.0.0.1 failed,
We recently needed to downgrade an underpowered solaris host to SA2.64
I start spamd with a max of 32 processes and some people get lots of mail.
Users fire off spamc via their .procmailrc
I'm now seeing a lot of
[ID 702911 mail.error] connect(AF_INET) to spamd at 127.0.0.1 failed,
retrying
[EMAIL PROTECTED] wrote:
We recently needed to downgrade an underpowered solaris host to SA2.64
I start spamd with a max of 32 processes and some people get lots of
mail. Users fire off spamc via their .procmailrc
I'm now seeing a lot of
[ID 702911 mail.error] connect(AF_INET) to spamd at
We recently needed to downgrade an underpowered solaris host to SA2.64
I start spamd with a max of 32 processes and some people get lots of mail.
Users fire off spamc via their .procmailrc
I'm now seeing a lot of
[ID 702911 mail.error] connect(AF_INET) to spamd at 127.0.0.1 failed,
retrying
