David Wright wrote:
> So my guess was wrong. I found mutt's sole mention of mailname in
> /etc/Muttrc:
> 
>   # If Mutt is unable to determine your site's domain name correctly, you can
>   # set the default here. (better: fix /etc/mailname)
>   # 
>   # set hostname=cs.hmc.edu

That is from a Debian patch:

https://salsa.debian.org/mutt-team/mutt/-/blob/6fa73261/debian/patches/debian-specific/Muttrc.patch

> The manual, /usr/share/doc/mutt/manual.txt.gz, doesn't mention using
> mailname at all; the important part of hostname determination is given
> as:
> 
>   Its value is determined at startup as follows: the node's hostname is first
>   determined by the uname(3) function. The domain is then looked up using the
>   gethostname(2) and getaddrinfo(3) functions. If those calls are unable to
>   determine the domain, the full value returned by uname is used. Optionally,
>   Mutt can be compiled with a fixed domain name in which case a detected one 
> is
>   not used.
>  
>   Starting in Mutt 2.0, the operations described in the previous paragraph are
>   performed after the muttrc is processed, instead of beforehand. This way, if
>   the DNS operations are creating delays at startup, you can avoid those by
>   manually setting the value in your muttrc.
> 
> I don't know whether Debian compiles mutt to know about mailname.

It is Debian-specific, from a different patch than the
Muttrc update:

https://salsa.debian.org/mutt-team/mutt/-/blob/6fa73261/debian/patches/debian-specific/882690-use_fqdn_from_etc_mailname.patch

-- 
Todd

Attachment: signature.asc
Description: PGP signature

Reply via email to