• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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