"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).

[quote
 http://archives.neohapsis.com/archives/postfix/2011-11/0385.html]
> > >   I have heard about bizarre errors on FreeBSD (jail) systems where
> > > the user-land library was out of sync with kernel-land, resulting
> > > in data structure mis-matches and system calls returning
> > > nonsensical results.

> > Is it a clever idea to hardcode local interfaces on build machine
> > into a package that will then be redistributed to other machines?

No.

> > Sounds like postfix will have to do without official packages on
> > FreeBSD from now on.
> 
> I would find that unacceptable. If the problem is with FreeBSD as
> Wietse has indicated, then the problem should be rectified on the
> FreeBSD side of the equation.

Well, the problem is on both sides. On FreeBSD, one can have "systems"
without any interface -- and postfix assumes that every system
it is built on has some kind of interface.

So, maybe it's time to change that assumption for the postfix
built process, if possible ?

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