Am 05.05.2011 04:11, schrieb Matthias Andree:
> Now, possible workarounds:
>
> - be sure that /etc/resolv.conf contains a "search" list where at least
> one of the listed domains has a direct localhost resolving to 127.0.0.1
> and/or ::1. Say, if you have "search example.com another.example", at
> least localhost.example.com or localhost.another.example must resolve IN
> DNS - /etc/hosts doesn't work here.
>
> - add "options ndots:0" to /etc/resolv.conf (if setting multiple
> options, check your manual - my resolver needs them all on only one
> options line, separated by blanks). Be wary of system configuration
> tools that rewrite /etc/resolv.conf, they might lose this option.
>
> - make sure to use a local "search" domain first in /etc/resolv.conf
> that has a localhost entry. For instance, if /etc/resolv.conf contains
> "search example.org", be sure there is a "localhost.example.org" DNS
> entry that resolves in class IN and type A to 127.0.0.1 and/or type AAAA
> to ::1.
Gee. None of that works without affecting other parts of the system. The
first and last don't work on current Postfix versions, and the middle
option breaks qualifying the very own hostname.
I'll withdraw these workaround proposals.
Postfix-specific workaround (dangerous, as it can cause misresolving):
/etc/postfix/main.cf:
smtp_dns_resolver_options=res_defnames # don't do this
See my other reply (to Wietse) in this thread for details.
Instead, ask your vendor to fix their resolver,
<http://sourceware.org/bugzilla/show_bug.cgi?id=12734>
