"postfix-current" broken on amd64 platform

[Pav Lucistnik]

Wietse Venema píše v čt 17. 11. 2011 v 13:23 -0500:
> Wietse Venema:
> > Jase Thew:
> > > It can occur when IPv6 is enabled, but you don't have any IPv6 addresses 
> > > configured on any interfaces. (Yes, having an IPv6 enabled interface 
> > > with no addresses assigned is non-RFC3513 compliant, but it can and does 
> > > occur).
> ...
> > Thanks, this is very helpful. That code has not changed in 6 years,
> > so we are looking at an incompatible change in build environment.
> 
> Actually, a Postfix built-in default setting changed on 20110918.
> 
> It now enables IPv6 unless this is turned off in a configuration
> file.  I can fix that at compile time, and thereby not trigger
> the error on build systems with unexpected IPv6 configurations.

This is interesting.

The build jails are configured to have only IPv4 address on lo0,
but the host have both IPv4 and IPv6 configured on its lo0.

Changing the jail configuration is possible but if a reasonable
workaround can be made in postfix-current port I'd prefer not to touch
pointyhat configuration (unexpected consequences and all that...)

-- 
-- 
Pav Lucistnik <pav at oook.cz>
              <pav at FreeBSD.org>
MIPS: Meaningless Information Provided by Salesmen
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20111117/98d0ec10/attachment.pgp