4:22 p.m.
Hello,
It seems that 09/09, the sendmail was working fine, but not on 09/16.
Now I get
systemctl start sendmail.service
Job for sendmail.service failed because a timeout was exceeded.
See "systemctl status sendmail.service" and "journalctl -xeu
sendmail.service" for details.
journalctl -xeu sendmail.service
Subject: A start job for unit sendmail.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sendmail.service has begun execution.
░░
░░ The job identifier is 13643.
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'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit sendmail.service has entered the 'failed' state with result
'timeout'.
Sep 30 23:09:15 Sappho systemd[1]: Failed to start sendmail.service - Sendmail Mail
Transport Agent.
░░ Subject: A start job for unit sendmail.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sendmail.service has finished with a failure.
░░
░░ The job identifier is 13643 and the job result is failed.
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
I do not see anything about sendmail in dmesg.
Something wrong now?
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
===========================================================================
4:45 p.m.
Am 30.09.2023 um 23:22 schrieb Patrick Dupre:
Hello,
It seems that 09/09, the sendmail was working fine, but not on 09/16.
Now I get
systemctl start sendmail.service
Job for sendmail.service failed because a timeout was exceeded.
See "systemctl status sendmail.service" and "journalctl -xeu
sendmail.service" for details.
journalctl -xeu sendmail.service
Subject: A start job for unit sendmail.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sendmail.service has begun execution.
░░
░░ The job identifier is 13643.
Sep 30 23:08:29 Sappho sendmail[88774]: My unqualified host name (Sappho) unknown;
sleeping for retry
https://users.fedoraproject.narkive.com/3QtoAqYk/fc3-problems-with-sendma...
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'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit sendmail.service has entered the 'failed' state with result
'timeout'.
Sep 30 23:09:15 Sappho systemd[1]: Failed to start sendmail.service - Sendmail Mail
Transport Agent.
░░ Subject: A start job for unit sendmail.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sendmail.service has finished with a failure.
░░
░░ The job identifier is 13643 and the job result is failed.
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
I do not see anything about sendmail in dmesg.
Something wrong now?
Sendmail requires a FQDN; see
https://www.sendmail.org/~ca/email/doc8.12/cf/m4/whoami.html
7:07 p.m.
On Sat, Sep 30, 2023 at 5:45 PM Alexander Dalloz <ad+lists(a)uni-x.org> wrote:
Am 30.09.2023 um 23:22 schrieb Patrick Dupre:
> Hello,
>
> It seems that 09/09, the sendmail was working fine, but not on 09/16.
>
> Now I get
>
> systemctl start sendmail.service
> Job for sendmail.service failed because a timeout was exceeded.
> See "systemctl status sendmail.service" and "journalctl -xeu
sendmail.service" for details.
>
> journalctl -xeu sendmail.service
>
> Subject: A start job for unit sendmail.service has begun execution
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ A start job for unit sendmail.service has begun execution.
> ░░
> ░░ The job identifier is 13643.
> Sep 30 23:08:29 Sappho sendmail[88774]: My unqualified host name (Sappho) unknown;
sleeping for retry
https://users.fedoraproject.narkive.com/3QtoAqYk/fc3-problems-with-sendma...
> 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'.
> ░░ Subject: Unit failed
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ The unit sendmail.service has entered the 'failed' state with result
'timeout'.
> Sep 30 23:09:15 Sappho systemd[1]: Failed to start sendmail.service - Sendmail Mail
Transport Agent.
> ░░ Subject: A start job for unit sendmail.service has failed
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ A start job for unit sendmail.service has finished with a failure.
> ░░
> ░░ The job identifier is 13643 and the job result is failed.
>
> 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
>
> I do not see anything about sendmail in dmesg.
>
> Something wrong now?
Sendmail requires a FQDN; see
https://www.sendmail.org/~ca/email/doc8.12/cf/m4/whoami.html
This is a sharp edge... A Fully Qualified Domain Name ends in a dot
('.'). The dot denotes the top of the DNS tree.
Systemd's hostnamectl strips the trailing dot when setting a hostname.
Jeff
8:21 p.m.
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.
4:54 p.m.
On Sat, Sep 30, 2023 at 11:22:47PM +0200, Patrick Dupre wrote:
Hello,
It seems that 09/09, the sendmail was working fine, but not on 09/16.
What was happenning in between these dates: software updates, your
changes?
Now I get
systemctl start sendmail.service
[ ... ]
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.
[ ... ]
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
I also run sendmail. The only config differences between your 3
files above and mine (apart from comments, and my hostname) is
in the first line of /etc/hosts:
yours:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
mine:
127.0.0.1 <my.hostname> localhost localhost.localdomain localhost4
localhost4.localdomain4
What does typing 'hostname -f' give on your computer? If it results in
an error, I'd try adding 'Sappho', which seems to be your hostname,
after '127.0.0.1' in the line above, and leave the rest unchanged. Then
again: 'hostname -f' - if that still gives errors, I'd either restart
sendmail, or whatever. Even better: I'd reboot ...
Good luck!
220
days inactive
221
days old
4 comments
5 participants
participants (5)
-
Alexander Dalloz -
Jeffrey Walton -
Patrick Dupre -
Tim -
Wolfgang Pfeiffer