No. Well designed ones won't do that to you. Scott K
On Friday, January 25, 2019 01:51:55 AM Matt Wong wrote: > This gets closer - and as far as I tested, it's not the name, but rather > the ip to wich inet_interfaces is set to. Default seems "all" - wich > includes the IPs of all interfaces + loopback - and it seems the error > is caused by some quirk that postfix doesn't want to deliever to any ip > it self is set to. It doesn't matter if you set interfaces to loopback > and send mail to the nic-IP or vise versa - as long as they different. > > As I scrolled through the docs - seems there is no config option to > override this behaviour like "ignore loopback" - so it seems this check > is hardcoded in the source. > > I also tried mini_sendmail - but as you have to override sendmail > yourself - it gets overridden by package update - but I guess this issue > can be said about just any package-based distribution. > > Matt > > Am 25.01.2019 um 01:05 schrieb Viktor Dukhovni: > > On Thu, Jan 24, 2019 at 05:15:58PM -0600, Noel Jones wrote: > >> On 1/24/2019 4:54 PM, Matt Wong wrote: > >>> Well, I got a bit further: When listing mailq postfix complains > >>> about "127.0.0.1 loop back to myself". > >> > >> Change the postfix "myhostname" parameter to something other than > >> what James uses. > > > > While that's necessary, it is typically not sufficient. One also > > needs to make sure that that destination IP address is not listed > > in "inet_interfaces". > > > > In this case, an explicit setting of "inet_interfaces" to just the > > public IP address of the machine would be required. > > > > main.cf: > > # Choose a non-loopback interface IP > > # > > inet_interfaces = 192.0.2.1 > > > > # Choose a name that is different from the name used in > > # the SMTP 220 greeting banner or EHLO response of the > > # non-Postfix loopback SMTP service. > > # > > myhostname = mail.example.com > > > > ...
