#3298: Mutt's way to get the FQDN is broken
---------------------+----------------------
Reporter: vinc17 | Owner: mutt-dev
Type: defect | Status: closed
Priority: major | Milestone:
Component: mutt | Version: 1.5.20
Resolution: fixed | Keywords:
---------------------+----------------------
Changes (by me):
* status: new => closed
* resolution: => fixed
Old description:
> It seems that Mutt gets the FQDN by reading /etc/resolv.conf, but this is
> incorrect when this file doesn't have the precedence (see
> /etc/nsswitch.conf). The consequence is that incorrect Message-Id's are
> generated.
>
> (There seems to be some problems with the BTS, that's why I submit
> another bug.)
New description:
It seems that Mutt gets the FQDN by reading /etc/resolv.conf, but this is
incorrect when this file doesn't have the precedence (see
/etc/nsswitch.conf). The consequence is that incorrect Message-Id's are
generated.
(There seems to be some problems with the BTS, that's why I submit another
bug.)
--
Comment:
See #3298.
Checking for the non-existence of getaddrinfo() is probably not necessary
at this point, because any systems lacking it are probably out of the
support window anyway.
Hinting from /etc/resolv.conf is still useful for the mobile/DHCP use case
where the DNS domain name is unlikely to resolve, but /etc/resolv.conf may
contain a useful value, but it should be the fallback to the DNS lookup
described in this ticket.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3298#comment:13>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
