On Fri, 5 Jun 2015 20:05:02 -0400 (EDT)
[email protected] (Wietse Venema) wrote:

> Janos Dohanics:
> > em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
> > mtu 1500
> > options=209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
> > ether 00:16:3e:6f:18:c9 inet 199.102.77.98 netmask 0xfffffff8
> > broadcast 199.102.77.103 inet6 fe80::216:3eff:fe6f:18c9%em0
> > prefixlen 64 scopeid 0x2 inet 199.102.77.99 netmask 0xfffffff8
> > broadcast 199.102.77.103 inet 199.102.77.100 netmask 0xfffffff8
> > broadcast 199.102.77.103 inet 199.102.77.101 netmask 0xfffffff8
> > broadcast 199.102.77.103 inet 199.102.77.102 netmask 0xfffffff8
> > broadcast 199.102.77.103 nd6
> > options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> > # postconf inet_interfaces
> > inet_interfaces = 199.102.77.99, localhost
> > 
> > # postconf smtp_bind_address
> > smtp_bind_address =
> > 
> > And on the destination server, the mail log says:
> > 
> > Jun  5 19:23:52 barrida postfix/smtpd[57612]: connect from
> > smtpc.telissant.net[199.102.77.99]
> > 
> > Can you explain?
> 
> Perhaps your kernel picks a random IP address from five identically
> configured addresses. My FreeBSD9 box has netmasks of 0xffffffff
> on all IP address "aliases".
> 
> Perhaps you have smtp_bind_address in master.cf where it is typically
> used.

That's precisely the case... as I suspected, I was missing something.

Thank you all for your help.

-- 
Janos Dohanics

Reply via email to