On Sat, 2023-09-30 at 23:22 +0200, Patrick Dupre wrote: > Sep 30 23:08:29 Sappho sendmail[88774]: My unqualified host name (Sappho) unknown; sleeping for retry > Sep 30 23:09:15 Sappho systemd[1]: sendmail.service: start operation timed out. Terminating. > Sep 30 23:09:15 Sappho systemd[1]: sendmail.service: Failed with result 'timeout'. > > I have in > /etc/hostname > Sappho > > in /etc/host.conf > multi on > > in /etc/hosts > # Loopback entries; do not change. > # For historical reasons, localhost precedes localhost.localdomain: > 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 > ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 > # See hosts(5) for proper format and other examples: > # 192.168.1.10 foo.mydomain.org foo > # 192.168.1.13 bar.mydomain.org bar > For what it's worth, the "do not change" instructions really refer to just the first two lines for localhost loopback addresses (127.0.0.1 and its IPv6 equivalent of ::1). Various servers required a hostname with at least one dot in it. Some have options that can be set to not require it, but the simplest solution is to give it one. Make sure that you apply the hostname to an IP that also applies to the name when a reverse lookup is done. Some things do checkups that require it work in both directions. e.g. in your hosts file, if your IP was 192.168.1.10 then you'd have a line in it like: 192.168.1.10 Sappho.localdomain Sappho Any lookups for Sappho.localdomain or Sappho would return 192.168.1.10, and any lookups against 192.168.1.10 would return Sappho.localdomain The first name listed after the IP will be returned in a reverse lookup, and other names listed after it will be aliases for that IP. It's usually best to avoid using 127.0.0.1 and localhost addresses when horsing around with servers, and essential if you want to be able to do things between different machines on your LAN. The .localdomain suffix is usually safe to use within Linux, it's a long established solution to this situation. Other suffixes are problematic, such as .home and sometimes .lan, as they're used by other dynamic addressing schemes (where IPs may change, and where lookups are sometimes done using other methods that a server might not try). Some routers use them with their DHCP server. Other suffixes such as .test and .invalid are around for testing things within a LAN, but you may find some servers refusing to do deal with mail with an .invalid domain name. -- uname -rsvp Linux 3.10.0-1160.99.1.el7.x86_64 #1 SMP Wed Sep 13 14:19:20 UTC 2023 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
