-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: | On Wed, 30 Apr 2008, Alan Hodgson wrote: | |>> Tis a good question ... I don't know what causes it offhand, if the |>> resolver otherwise seems to work. It sounds familiar, though .. it |>> seems like you generally use 127.0.0.1 rather than "localhost" for |>> whatever the reason is. |>> |> |> If the lmtp process is running chroot it may be using different hosts and |> resolv.conf files than normal system processes. | | It doesn't seem to be running chroot (note the 5th field is "n"): | dbmail-lmtp unix - - n - - lmtp -o disable_dns_lookups=yes | | Any other ideas? |
Postfix by default uses dns via system library calls, what that returns will depend on resolv.conf. The behaviour of dig is not always representative of what the system libraries would return (for example dig does not use the search list of resolv.conf by default). disble_dns_lookups changes that behaviour and postfix uses getaddrinfo() which should also look in /etc/hosts, depending on the setting of /etc/nsswitch.conf or equivalent on your system. Postfix also has a parameter (from version 2.3) lmtp_host_lookup, which defaults to dns but can be set to native (to use nsswitch) or to dns, native. see http://www.postfix.org/postconf.5.html#lmtp_host_lookup http://www.postfix.org/postconf.5.html#smtp_host_lookup John -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFIG1Ymd4I3jTtt9EIRArGRAJ0VCXA/HdEYKXr24+N1YsFNS0CU8gCbBZKF l78jFMlGjhq/MrWQJB31oQ4= =9e3e -----END PGP SIGNATURE----- _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
