Wietse Venema:
> Wietse Venema:
> > Mark Martinec:
> > > Trying to install postfix-2.9-20111219 from ports on FreeBSD 9.0
> > > (with an inet6-only kernel), the installation fails as before:
> > > 
> > > postfix-current$ make install
> > > ...
> > > Skipping /usr/local/share/doc/postfix/postfix-power.png...
> > > Skipping /usr/local/share/doc/postfix/scache.8.html...
> > > Skipping /usr/local/share/doc/postfix/tlsmgr.8.html...
> > > postfix: fatal: could not find any active network interfaces
> > > *** Error code 1
> > 
> > How do you want to proceed: wait until I have time to reproduce
> > your IPv6-only setup for which I have no specification, or spend
> > all of next year doing blind testing?
> 
> I'm assuming that you have "inet_protocols=ipv6" in main.cf, instead
> of the backwards-compatibility "inet_protocols=ipv4" workaround,
> because that would not work on your machine.

After I made "inet_protocols=all" the default on your request, I
received notice that Postfix no longer would build on freebsd.org
"build" systems, and that it would be removed from ports. These
build environments have IPv6 in the kernel but they have no IPv6
interfaces.  Basically, these are IPv4-only boxes with can IPv6
configuration that violates the RFCs.

These changes were made to avoid being kicked out of the ports:

20111117

        Workaround: don't use IPv6 at build time. File: conf/main.cf.

        Workaround: don't abort when IPv6 is present but busted.
        File: util/inet_proto.c.

Now, I can easily remove the first workaround. But that won't
prevent the post-install script from adding "inet_protocols=ipv4"
to main.cf when you upgrade Postfix.

To avoid all this, patch conf/main.cf and s/ipv4/ipv6/. Meanwhile
I'll see what it takes to add a question to the Postfix install
script. I hate to bug people with useless questions.

        Wietse

Reply via email to