"postfix-current" broken on amd64 platform

[Kurt Jaeger]

Hi!

> > > > >   Postconf opens a socket to determine the mynetworks value (it
> > > > >   determines the local interfaces and their netmasks).
[...]
> Postfix does none of that. 

The fbsd postfix-current port during the post-install script does
something which fails on a jail-based build-cluster where the
jail itself has no network connectivity.

See this message for some analysis:

http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071419.html

And this message explains it:

http://lists.freebsd.org/pipermail/freebsd-ports/2011-November/071421.html

It says:
----------
It is a purposefully no-networking sandbox jail.
What networking activity postconf wants to run?
----------

> Can someone please explain what socket call is failing, and what
> the reasons for that might be? 

The reason is that postconf is called during post-install
and fails because the build jail is without any interface.

> I tend to believe that network-less build environments are not
> representative for the environment where an Internet MTA would run,
> but hey, what do I know.

The build environment seems to be network-less. It's not the
environment where the package will run.

-- 
pi at opsec.eu            +49 171 3101372                         9 years to go !