Local, system e-mails only delivered on reboot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[I posted a similar question a couple of months back, but mistakenly thought I had resolved the issue]

One of my F40 systems fails to deliver local, system-generated e-mails (logfiles and such) UNTIL it gets rebooted.

sendmail-8.18.1-1.fc40.x86_64 is installed for local e-mail handling.

On reboot, SOME of the accumulated messages--along with failure warning messages that have been generated--get delivered to local mailbox (/var/spool/mail/username). Other messages remain in the queue.

Today, I noted at the end of a dnf update, the following:

Reload daemon failed: Transport endpoint is not connected
Failed to start jobs: Transport endpoint is not connected

No indication of which daemon being referred to, so it's not clear if this is referring to the sendmail daemon.

Journalctl reports (after rebooting):

Jul 03 09:45:04 kestrel (sendmail)[1524]: sendmail.service: Referenced but unset
 environment variable evaluates to an empty string: SENDMAIL_OPTARG
Jul 03 09:45:04 kestrel sendmail[1525]: starting daemon (8.18.1): SMTP+queueing@
01:00:00
Jul 03 09:45:04 kestrel systemd[1]: sendmail.service: Can't open PID file /run/sendmail.pid (yet?) after start: No such file or directory

And then, a batch of these, corresponding to the undelivered e-mails:

Jul 03 09:45:07 kestrel sendmail[1526]: 45T7V2ou003307: to=<root@xxxxxxxxxxxxxxxxxxx>, delay=4+06:14:04, xdelay=00:00:00, mailer=esmtp, pri=9500566, relay=kestrel.mynetworksettings.com., dsn=4.4.1, stat=Deferred: Connection refused by kestrel.mynetworksettings.com.

Even so, SOME the queued messages were in fact delivered after the reboot completed. Others remain in the queue, for example:

# mailq
		/var/spool/mqueue (9 requests)
-----Q-ID----- --Size-- -----Q-Time----- ------------Sender/Recipient-----------
4627Lrpw008404     3884 Tue Jul  2 03:21 <root@xxxxxxxxxxxxxxxxxxx>
(Deferred: Connection refused by kestrel.mynetworksettings.co)
					 <tkevans@xxxxxxxxxxxxxxxxxxx>

I do not know where the bogus domain name "mynetworksettings.com" comes from, as the system has a proper hostname.

My other F40 systems do not have this issue, as local e-mail is delivered properly.

Suggestions for further digging?  Thanks.
--
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux