Marc Haber wrote: > On Sat, 11 Nov 2006 13:37:52 +0100, Renaud Allard <[EMAIL PROTECTED]> > wrote: >> Marc Haber wrote: >>> on November 7, I updated spamassassin on my personal Debian stable >>> system from (a backported) 3.1.5 to (also backported) 3.1.7. In Debian >>> terminology, a backport means that one takes a package from the >>> unstable or testing distribution and rebuilds it for use on stable. >>> >>> Since that backup, I have numerous spamassassin-related error messages >>> in my panic log: >>> >>> 2006-11-07 09:38:11 1GhMTD-0002Ym-He spam acl condition: warning - spamd >>> connection to 127.0.0.1, port 783 failed: Connection refused >>> 2006-11-07 09:38:11 1GhMTD-0002Ym-He spam acl condition: all spamd servers >>> failed >> Obviously, your spamd daemon is not listening on 127.0.0.1. > > I am not _that_ stupid, thanks for trying to help. > > The spamd is running, is processing mail, is logging that it is > processing mail, and all incoming mail has spamassassin headers that > clearly originate on the local system (an artificially created typo in > the report template shows up in incoming mail). > > Greetings > Marc >
Any chance that SA was trying a remote-update or DB rebuild or such around that $tod? It is (mostly) an interpreted-language animal, and may have simply been 'unable' to respond fast enough. For example - are these 'numerous' log entries showing any pattern of regulariy or spacing over time? Bill -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/