Re: [vserver] Spamc is hardcoded to 127.0.0.1 ???

From: ADNET Ghislain <gadnet_at_aqueos.com>
Date: Wed 05 Mar 2008 - 18:16:03 GMT
Message-ID: <47CEE363.5040400@aqueos.com>

Alejandro Facultad a écrit :
> Dear all, I have a vserver guest with localhost mapped to
> 192.168.0.100 (a private non-routable IP). I installed a complete mail
> server with Postfix+Courier+Amavisd-new+Spamassassin+.......
>
> This mail server works OK, except for this log I get from
> /var/log/mail.log:
>
> Mar 5 15:43:47 mail spamc[24544]: connect to spamd on 127.0.0.1
> failed, retrying (#1 of 3): Connection refused
> Mar 5 15:43:48 mail spamc[24544]: connect to spamd on 127.0.0.1
> failed, retrying (#2 of 3): Connection refused
> Mar 5 15:43:49 mail spamc[24544]: connect to spamd on 127.0.0.1
> failed, retrying (#3 of 3): Connection refused
> Mar 5 15:43:50 mail spamc[24544]: connection attempt to spamd aborted
> after 3 retries
>
> I change all ocurrencies of 127.0.0.1 by 192.168.0.100, but becausae
> spamc is a binary file I think it's hardcoded to 127.0.0.1.
>
> How can I solve that in order to use localhost=192.168.0.100 and
> eliminate the above log error ???
>
> Have you experienced this problem ???
>
> Special thanks
>
> Alejandro
man spamc

       -d host[,host2], --dest=host[,host2]
           In TCP/IP mode, connect to spamd server on given host (default:
           localhost). Several hosts can be specified if separated by
commas.

           If host resolves to multiple addresses, then spamc will fail-over
           to the other addresses, if the first one cannot be connected to.
           It will first try all addresses of one host before it tries the
           next one in the list. Note that this fail-over behaviour is
incom-
           patible with -x; if that switch is used, fail-over will not
occur.

;)

-- 
Cordialement,
Ghislain
 

Received on Wed Mar 5 18:30:42 2008
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Wed 05 Mar 2008 - 18:30:44 GMT by hypermail 2.1.8