• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

There was an error sending your message: sendmail returned error code 111

U

uy_info

Guest
Hi all,

When using webmail.<domain>.tld to create new message, using Squirrel, I get the following error:
"There was an error sending your message: sendmail returned error code 111"

this error shows up in /var/log/httpd/error_log as
qmail-inject: fatal: read error

My Server is:
Plesk version psa v8.3.0_build83080131.20 os_FedoraCore 7
Operating system Linux 2.6.23.15-80.fc7


Anybody any ideas? I did not find these forums to be useful but let's see if any tech-person replies.
 
any troubleshooting ideas?

anybody have a resource on PLesk / Qmail.. Howto troubleshoot?
 
SELinux

Problem was I coulndt reach qmail from php-apache aplications.

I checked for some permissions on executables. Then I remembered that iptables and SELinux are always ones to blame.

I am not sure why getenforce returns 1, because I dont remember enabling SELinux. Anyways setenforce 0 did the trick. I hope it does not open any other security holes.
 
Back
Top