On Mon, 2009-05-04 at 15:57 -0300, Alejandro Cabrera Obed 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.
> May 4 15:55:04 mail spamc[18892]: connect to spamd on 127.0.0.1
> failed, retrying (#1 of 3): Connection refused
I'd start by carefully verifying your postfix and amavis configuration.
Then I'd track down the entire mail processing chain, and specifically
look out where spamc might be called -- cause it shouldn't...
> 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 ???
May I point at the above statement? :) "Nothing" isn't particularly
appropriate in that context, is it? Something clearly changed, and I'd
closely investigate these changes first, if they coincide with the error
appearing.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
