Dear all, I need your help again about the spamc error. I tell you I'm not using procmail.
In my /etc/default/spamassassin I have this lines: ENABLED=1 OPTIONS="--create-prefs --socketpath -U amavis --max-children 5 --helper-home-dir" PIDFILE="/var/run/spamd.pid" If I define the listen IP and port: OPTIONS="--create-prefs --socketpath -U amavis --max-children 5 --helper-home-dir --listen-ip=localhost --port=783" The spamc connects OK to port TCP/783 but I can't use the amavis tag features I used before. This situation shows me that the problem is between amavisd-new and spamassassin. And I repeat: I've never open port TCP/783 from spamassassin before and the anti spam worked fine. Can you help me please ??? Thanks a lot Alejandro On Mon, May 4, 2009 at 4:53 PM, Theo Van Dinter <felic...@apache.org> wrote: > If you're using amavis, what is calling spamc? It sounds like > something changed your config somewhere. Did someone put in a > procmailrc entry? > > > On Mon, May 4, 2009 at 2:57 PM, Alejandro Cabrera Obed > <aco1...@gmail.com> wrote: > > Dear all, I use Postfix (version 2.3.8-2+etch1) + amavisd-new (version > > 2.4.2-6.1) + spamassassin (version 3.2.3-0.volatile1), and they are > Debian > > Etch packages. > > > > Spamassassin is invoked from amavisd-new, so port TCP/783 is never open. > > > > A pair of days ago, I notice that the messages are not being checked for > > spam, and I have this log messages in /var/log/mail.err time after time: > > > > May 4 15:55:04 mail spamc[18892]: connect to spamd on 127.0.0.1 failed, > > retrying (#1 of 3): Connection refused > > May 4 15:55:04 mail spamc[18893]: connect to spamd on 127.0.0.1 failed, > > retrying (#1 of 3): Connection refused > > May 4 15:55:04 mail spamc[18894]: connect to spamd on 127.0.0.1 failed, > > retrying (#1 of 3): Connection refused > > May 4 15:55:04 mail spamc[18881]: connection attempt to spamd aborted > after > > 3 retries > > > > I tried restarting all the mail services but I fail. > > > > What can be the problem, because this model has worked very well until > last > > week and nobody has change nothing except apt-get dist-upgrade from > Debian > > volatile repositories ??? > > > > Special thanks > > > > Alejandro > > >
