;s produced when something (such as monitoring
> software!) opens a TCP connection to the spamd port, then closes it again.
>
> --j.
>
> gable writes:
>> we have monitoring in place .. zabbix in this case .. The process isn't
>> dying, tailing the logs .. and checkin
? or some kind of keep-alive daemon checking to see if
> spamd is running?
>
> --j.
>
> gable writes:
>> gable wrote:
>> >
>> > Hiya
>> >
>> > Has anyone come across error like these before - spamassassin was
>> working
>> > pe
gable wrote:
>
> Hiya
>
> Has anyone come across error like these before - spamassassin was working
> perfect - but a couple of days ago - we got flooded with spam. Checking
> the logs ... errors like the one below come up 25,000 times :-) ... The
> only solution i'v
Hiya
Has anyone come across error like these before - spamassassin was working
perfect - but a couple of days ago - we got flooded with spam. Checking the
logs ... errors like the one below come up 25,000 times :-) ... The only
solution i've found to work is to keep restarting spamd on a crond ..
