On Wed, 3 Dec 2008, SM wrote:
At 18:23 02-12-2008, Byung-Hee HWANG wrote:
Are you using FreeBSD or NetBSD? If so, i understand you. Unfortunately, SA
developers do not care about IPv6 yet. So here SA program at first do
action with 127.0.0.1 than ::1, i guess ;;
This was tested on a BSD
At 18:23 02-12-2008, Byung-Hee HWANG wrote:
Are you using FreeBSD or NetBSD? If so, i understand you.
Unfortunately, SA developers do not care about IPv6 yet. So here SA
program at first do action with 127.0.0.1 than ::1, i guess ;;
This was tested on a BSD system. SpamAssassin developers
Dan Mahoney, System Admin wrote:
On Mon, 1 Dec 2008, SM wrote:
At 23:01 30-11-2008, Dan Mahoney, System Admin wrote:
So then, you're saying the behavior for ipv4 and ipv6 is somehow
different?
If you start spamd without specifying the IP addresses to listen on,
spamd will listen on the
At 23:01 30-11-2008, Dan Mahoney, System Admin wrote:
So then, you're saying the behavior for ipv4 and ipv6 is somehow different?
If you start spamd without specifying the IP addresses to listen on,
spamd will listen on the 127.0.0.1 IP address only.
You should have the IO::Socket::INET6
On Mon, 1 Dec 2008, SM wrote:
At 23:01 30-11-2008, Dan Mahoney, System Admin wrote:
So then, you're saying the behavior for ipv4 and ipv6 is somehow different?
If you start spamd without specifying the IP addresses to listen on, spamd
will listen on the 127.0.0.1 IP address only.
And on
At 07:03 01-12-2008, Dan Mahoney, System Admin wrote:
And on an ip6 enabled system, where will spamc localhost try to
connect to first? 127.0.0.1 or ::1?
By default, spamc connects to 127.0.0.1. On a properly configured
network, it will try ::1, then 127.0.0.1.
Yes, but there's no way to
On Sun, 30 Nov 2008, SM wrote:
At 21:45 30-11-2008, Dan Mahoney, System Admin wrote:
Since getting my hosts natively speaking ipv6, I've been seeing a lot of
initial timeouts connecting to spamc, because I believe it's apparently
trying ipv6 first.
spamc: connect to spamd on
