top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

systemd/sendmail problem on Fedora?

+1 vote
438 views

I'm running Fedora-24(beta)/KDE, and sendmail/email (through KMail) is failing.
When I try to send email I get the warning "Failed to transmit message", and journalctl has the entry
"sendmail.service: PID file /run/sendmail.pid not readable (yet?)
after start: No such file or directory".

I've checked, and sendmail.pid is in place: 

$ sudo cat /run/sendmail.pid 
2829 
/usr/sbin/sendmail -bd -q1h

Googling for the journalctl entry, I see people have been encountering this problem for years. But I haven't seen any solution offered. Several of the comments suggest that it is a systemd problem.

please help?

posted May 25, 2016 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+3 votes
How to send a mail using sendmail utility in Linux?

How to send a mail using sendmail utility? Example would help?

+1 vote
Sendmail not presenting AUTH option after EHLO on CentOS

I have a CentOS 6.4 installation running Sendmail, and after some serious hair tear stare and compare I'm a bit stumped. When I connect to the server either with telnet or SSL, sendmail is not presenting the AUTH capability after an EHLO. Everything looks like it should be working, but no amount of tweaking is getting the AUTH capability advertised (and it doesn't work if you just try it anyway).

Here's the config bits from sendmail.mc--

 define(`confAUTH_OPTIONS', `A p')dnl
 define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
 TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl

Note: Also tried

 define(`confAUTH_OPTIONS', `A')dnl
 define(`confAUTH_MECHANISMS', `LOGIN PLAIN')dnl
 TRUST_AUTH_MECH(`LOGIN PLAIN')dnl

just to keep things simple.

saslauthd is running, and configured--/etc/sysconfig/saslauthd 

 SOCKETDIR=/var/run/saslauthd
 MECH=pam
 FLAGS=

/etc/sasl2/Sendmail.conf contains--
 pwcheck_method:saslauthd

/etc/pam.d/smtp contains--
 #%PAM-1.0
 auth include password-auth
 account include password-auth

But when I do "openssl s_client -starttls smtp -connect localhost:587" I don't get any AUTH capability--

ehlo localhost
250-pennzoil.gizmopartners.com Hello localhost [127.0.0.1], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-DELIVERBY
250 HELP
quit

All the certs are built, and if I connect via telnet, the server does advertise STARTTLS. So anyone able to point out the obvious or not so obvious config mistakes?

+2 votes
sendmail library using python?

I am looking for a python library that does mailing directly through "sendmail".

When I look into the docs, I see only an "smtlip" library but nothing that could serve with sendmail or postfix.

+1 vote
Fedora: What kind of secret does one need to use rsyslog on a systemd system?

What kind of secret voodoo does one need to use rsyslog on a systemd system? Is it even possible?

I have installed it, and I only get kernel boot messages in /var/log/messages.

I find journalctl to be fundamentally braindead, lacking features which we have taken for granted for decades in redhat/rhel/fedora/centos. (Seriously, whats the wisdom of keeping ALL logs around forever?, and in an easily corruptible format).

I found something on the fedora web site which said to just install rsyslog. Which seems to be obsolete or invalid.

0 votes
How to disable IPv6 configuration properly on Fedora Linux?

For some reason I have to temporarily deactivate IPv6 interface configuration on a F22 server box.

According to documentation (or at least as I understood) it could be done either by adding

IPV6INIT=no
IPV6_AUTOCONF=no
to /etc/sysconfig/network-scripts/ifcfg-eth0

or

NETWORKING_IPV6=no
IPV6_AUTOCONF=no
to /etc/sysconfig/network

I tried both, executed "nmcli c reload", "systemctl restart NetworkManager", even rebooted the system. No change in network configuration. In ifconfig I have a local link address as well as a global address as advertised by the router and autoconfig based on mac address.

All those options are documented in usr/share/doc/initscripts/sysconfig.txt, so I guess these are still valid options.

Now I am wondering what I may have overlooked or missed?

Any hint appreciated.

...