Let’s take a look at the ways in which we resolve these errors in our customer’s server.
The issue we are going to discuss is related to a Cloudlinux server with cPanel/WHM using CageFS.
Several clients on the server started to complain that each mail they received was sending back an error to the sender as mentioned below:
[Company name] Failed email delivery message
One of our clients reported an issue regarding their emails on their servers, that clients are sending them emails which are being received, but, the sender was receiving the following error message afterward:
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
pipe to |/usr/local/cpanel/bin/autorespond user@user@emailaddress /home/user/.autorespond generated by user@emailaddress
The following text was generated during the delivery attempt:
pipe to |/usr/local/cpanel/bin/autorespond user@emailaddress /home/user/.autorespond
generated by user@emailaddress
[2020-06-30 14:22:31 +1000] info [autorespond] Failed to read response template /home/user/.autorespond/user@emailaddress: No such file or directory From: username Subject: Test Date: Tue, 30 Jun 2020 04:22:25 GMT To: username <user@emailaddress? Service: proxyexecd was not running on the server, so all the proxy commands like Sendmail (/etc/cagefs/proxy.commands) didn't work for users in the cage.
You can also check the status of the service and if the status is stopped you run the below command to start the process,
Step1: Check the status of the service.
/etc/init.d/proxyexecd status/systemctl status proxyexecd proxyexec is stopped
Step2: Start the service if stopped.
/etc/init.d/proxyexecd start/systemctl start proxyexecd
You can also try restarting the proxyexecd to resolve the issue.
Hope this could help you troubleshoot the error. For further assistance, feel free to Contact Us.
This fix has been tested on CloudLinux servers with CageFS enabled in production cPanel environments.
As part of our Technical support service, we can assist you in troubleshooting issues related to cPanel/WHM and CageFS.
Frequently Asked Questions (FAQs)
Why is my cPanel autoresponder not working?
cPanel autoresponders may stop working due to permission issues, missing template files, or CloudLinux CageFS restrictions. One common cause is the proxyexecd service not running, which prevents autoresponder scripts from executing correctly.
Does CloudLinux CageFS affect cPanel autoresponders?
Yes. CageFS isolates user environments, and if proxyexecd is not running, required proxy commands such as sendmail may fail. This can result in autoresponder errors even though emails are received successfully.
What does “Failed to read response template” error mean?
This error indicates that cPanel could not access the autoresponder template file inside the user’s home directory. It usually occurs due to CageFS restrictions, incorrect file paths, or the proxyexecd service being stopped.
How do I fix cPanel autoresponder errors caused by CageFS?
Check the status of the proxyexecd service and start or restart it if necessary. Once proxyexecd is running, CageFS users can execute autoresponder commands correctly, resolving the email bounce-back issue.
Is it safe to restart proxyexecd on a production server?
Yes. Restarting proxyexecd is safe and commonly required when proxy commands stop functioning under CageFS. It does not affect running services and is a recommended fix for autoresponder-related issues on CloudLinux servers.
Will this fix work on all CloudLinux cPanel servers?
This solution applies to CloudLinux servers running cPanel/WHM with CageFS enabled. While it resolves most autoresponder issues related to proxy execution, server configurations should always be verified before applying changes.
You can also check our solution to Email account migration from one cPanel server to another
Follow us for the latest updates: Facebook, Twitter, LinkedIn
Subscribe to get free blog content to your Inbox
-
Previous Post
Is your ESXi Root Account Locked?
