If MailScanner is set up to use spamassassin, then it normally wouldn't be using spamc. However, if spamd is not running, spamc can't connect to it.
spamc = client spamd = daemon On Fri, 10 Dec 2004, Andy Norris wrote: > > My understanding is that spamd should not be running when spamassassin is > used in conjunction with MailScanner as MailScanner uses spamassassin > directly, and not as a daemon? > > So is this a MailScanner issue, then? > > Thanks Mike, > Andy > > > At 01:44 pm 2004-12-10, you wrote: > >Is spamd running? > > > >On Fri, 10 Dec 2004, Andy Norris wrote: > > > > > > > > Sorry to bother again, but I feel we must be getting closer... > > > > > > This in the logs (/var/log/maillog) now...(!) > > > > > > Dec 10 13:44:40 tireswing spamc[22597]: connect() to spamd at 127.0.0.1 > > > failed, retrying (1/3): Connection refused > > > Dec 10 13:44:41 tireswing spamc[22597]: connect() to spamd at 127.0.0.1 > > > failed, retrying (2/3): Connection refused > > > Dec 10 13:44:42 tireswing spamc[22597]: connect() to spamd at 127.0.0.1 > > > failed, retrying (3/3): Connection refused > > > > > > Any hints what to look for here? This is getting very frustrating, as the > > > first few messages are scanned by SA, but after a while it starts to > > either > > > time out or refuse connection, then we're at virtually no spam filtering. > > > > > > >-- > >Mike Burger > >http://www.bubbanfriends.org > > > >Visit the Dog Pound II BBS > >telnet://dogpound2.citadel.org or http://dogpound2.citadel.org > > > >To be notified of updates to the web site, visit > >http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a > >message to: > > > >[EMAIL PROTECTED] > > > >with a message of: > > > >subscribe > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit http://www.bubbanfriends.org/mailman/listinfo/site-update, or send a message to: [EMAIL PROTECTED] with a message of: subscribe
