When I execute postconf -d mynetworks, it returns:
zimbra@zre-ldap002:~$ postconf -d mynetworks
mynetworks = 127.0.0.0/8 10.137.242.0/24 [::1]/128 [fc00:10:137:242::]/64
[fe80::%eth0]/64
Which Zimbra uses for mynetworks values throughout our application where
necessary (Amavis, SA, OpenDKIM, etc).
However, the SA folks noted:
Scoped address (...%eth0) is currently not useful and I believe
it is not recognized by NetAddr::IP. The reason is that the
information about a peer address coming from a socket
does not currently carry scope information, so something
like %eth0 at the end of an address never reaches an application.
For the time being just use non-scoped fe80::/10 .
So, does Postfix actually honor %eth0, is this a bug in postconf, or does
postfix just ignore it?
Thanks,
Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
