https://bugzilla.novell.com/show_bug.cgi?id=824141 https://bugzilla.novell.com/show_bug.cgi?id=824141#c2 --- Comment #2 from Aaron Burgemeister <aburgemeister@gmail.com> 2013-06-12 12:10:05 UTC --- Any idea why Postfix is looking in /etc/hosts in the first place? Would binding 127.0.0.2 explicitly fix things? The test about "Does the machine have a network interface with IP address 127.0.0.2" seems to miss the entire point that every machine, per RFC, binds the entire class A 127.x.x.x network to the loopback (lo) address by default, as shown here: Code: ---------- me@mybox:~> ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever ---------- The /8 on the end of the IP address means that this answers for everything matching ONLY the first eight bits of the address. As a test, ping any IPv4 address starting with 127 and it will respond immediately and the statistics for 'lo' ('ip -s link') will increase accordingly. Because of this, as well as the proper function of 99% of applications out there, this feels like a bug in Postfix. I still agree that, like in SLE, the default to write the hostname to the loopback address is a bug because it was implemented to work around other products' bugs, but in the end fixing this is missing the point. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.