hutting
> > down Jun 11 19:38:22 cpollock spamassassin: spamd shutdown succeeded
> > Jun 11 19:53:33 cpollock spamc[26370]: connect(AF_INET) to spamd at
> > 127.0.0.1 failed, retrying (#2 of 3): Connection refused
>
> is it possible that you had some incoming mail that was tryi
llock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1
failed, retrying (#1 of 3): Connection refused
Jun 11 19:53:33 cpollock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1
failed, retrying (#2 of 3): Connection refused
is it possible that you had some incoming mail that was trying to
co
26370]: connect(AF_INET) to spamd at 127.0.0.1
failed, retrying (#1 of 3): Connection refused
Jun 11 19:53:33 cpollock spamc[26370]: connect(AF_INET) to spamd at 127.0.0.1
failed, retrying (#2 of 3): Connection refused
Prior to upgrading from .0.3 to .0.4 I ran #service spamassassin stop, and
also shut
proxy" on three mail servers. This
morning at 2am one of the three (but not the other two) started spewing
a lot of
spamc[8000]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1
of 3)
and did not identify any messages as spam until a user complained and I
restarted spamd a few min
I'm running spamassassin 3.0.3 as a "proxy" on three mail servers. This
morning at 2am one of the three (but not the other two) started spewing
a lot of
spamc[8000]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1
of 3)
and did not identify any messages as sp
