On Sat, Nov 10, 2001 at 16:21, Philip Hazel wrote: > I have had a thought. If you do NOT set primary_hostname, Exim will call > the uname() function to find the name. If it then finds a name that is > not fully qualified (that is, if there is no '.' in the name), Exim will > call gethostbyname() in order to find the fully qualified name. (This is > all documented under 'primary_hostname'). The gethostbyname() may be > what is doing the DNS lookup. When you set primary_hostname explicitly, > it won't do this. > > Exim really expects to operate with a fully qualified host name, because > hosts on the Internet are supposed to have such names.
On Sat, Nov 10, 2001 at 18:09, Jö Fahlke wrote: > Mail is usually delivered acording to MX records in the DNS. But there > are simply no MX records in /etc/hosts, so exim has look up the name > via DNS. This behaviour can be tuned by the "gethostbyname" option to > the "smtp" transport, AFAIK. > > Of course, this is no explanation for the 'exim -bp' problem. This might be the explanation! As the meachanism Philip described is true for 'exim -bp' as well! However, setting primary_hostname causes another problem I have described earlier: any remote delivery fails. Bye, Steffen
