I've just updated to 5.2-BETA today and have noticed that my spamd is
now rejecting all connections from spamc because they are not coming
from 127.0.0.1 any more. It's now using my public IP address of 82.x.x.x:
Nov 22 14:38:30 womble spamd[657]: unauthorized connection from
I've just updated to 5.2-BETA today and have noticed that my spamd is
now rejecting all connections from spamc because they are not coming
from 127.0.0.1 any more. It's now using my public IP address of 82.x.x.x:
Nov 22 14:38:30 womble spamd[657]: unauthorized connection from
I noticed the same thing yesterday when postgresql stopped working
properly because there wasn't an entry for my public IP in the
pg_hba.conf file.
If you telnet to 127.0.0.1 the system still believes you are
coming from your public IP. Bizarre that. Other IPs don't act
that way. My system has
Matt Smith wrote:
I've just updated to 5.2-BETA today and have noticed that my spamd is
now rejecting all connections from spamc because they are not coming
from 127.0.0.1 any more. It's now using my public IP address of 82.x.x.x:
Yes, same problem here: at first, amavis refused to accept mails
Steve Ames [EMAIL PROTECTED] writes:
If you telnet to 127.0.0.1 the system still believes you are
coming from your public IP. Bizarre that. Other IPs don't act
that way. My system has two public IPs and 127.0.0.1. If I
telnet to myself on either of the public IPs then I appear
from the
From: Christian Laursen [mailto:[EMAIL PROTECTED]
Steve Ames [EMAIL PROTECTED] writes:
If you telnet to 127.0.0.1 the system still believes you are
coming from your public IP. Bizarre that. Other IPs don't act
that way. My system has two public IPs and 127.0.0.1. If I
telnet to myself
