#3298: Mutt's way to get the FQDN is broken
---------------------+----------------------
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: reopened
Priority: major | Milestone:
Component: mutt | Version: 1.5.20
Resolution: | Keywords:
---------------------+----------------------
Comment (by code@…):
I forgot to mention another case where, even when DNS is the configured
service, that the patch will do the right thing, whereas parsing
/etc/resolv.conf directly will not.
Say the search domain is what I said it was: search
local.domain.example.com example.com other.domain.example.com
Mutt will use local.domain.example.com as the domain. However, if via
DNS, the machine on which Mutt is running resolves to, say,
mailserver.example.com, then Mutt will (correctly) use the domain
example.com.
Reasons why the search domain might be configured that way include that
other servers (CIFS server, LDAP server, etc.) on which the mail server
depends are configured to be in local.domain.example.com, whereas for ease
of use the mail server itself is configured to be in example.com.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3298#comment:37>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
