CageFS and AutoResponders
-
In my case this did not help. We have multiple servers and we start facing issue from the last cpanel update 11.50.2.2 on all servers at the same time. Not just autoresponders but mail pipe is not working in general. our WHMCS system is not managing the ticket when mail is received because of this. 0 -
Is this post of any use to you? Re: Setting up email piping - WHMCS Forums 0 -
Yes that's how it is configured and it was working for long time without issue until today when cpanel updated to 11.50.2.2 and it just stop working. 0 -
Yes that's how it is configured and it was working for long time without issue until today when cpanel updated to 11.50.2.2 and it just stop working.
Same issues here, since 11.50.2.2 all of our servers fail autoresponders, unless they are outside cagefs yum clean all / yum update lve-wrappers no help0 -
I removed cageFS, installed it again. It worked for me. 0 -
yum clean all / yum update lve-wrappers no help
Please post the output from:rpm -qa | grep lve-wrappers
Also, check to see if running the "/usr/sbin/cagefsctl --update" command helps. Thank you.0 -
rpm -qa | grep lve-wrappers lve-wrappers-0.6-6.el6.cloudlinux.x86_64 Uninstall / Reinstall did not work either Working with Antom at CloudLinux # chmod 555 /bin # chmod 555 /usr/bin # cagefsctl --force-update This fixed the Auto responder and email piping issues for me. I still have issues with SFTP to accounts inside CageFS we are working on..... 0 -
Update to fix for me Reset permissions of /usr and /usr/bin to 755 Delete all old autoresponders - - example : /home/USER/.autoresponder.useremail@userdomain.com.data The Current autoresponders in "/home/USER/.autorespond/" folder work fine 0 -
I am happy to see the issue is now addressed. Thank you for updating this thread with the details of your correspondence with Cloud Linux. Thank you. 0 -
Tried all of the above, none worked. The email piping issue continues in varying ways. For tickets generated through email piping at whmcs, the users are getting 2 email responses ie. auto responder (set at whmcs) and a bounced back emails with mail delivery failure notice. WHMCS team when consulted mentions it as "cloud not exiting properly", while my server admin says, the piping is working (as emails are being piped through and tickets created), so the issue lies with php scripts. Trying to find a resolution. 0 -
WHMCS team when consulted mentions it as "cloud not exiting properly", while my server admin says, the piping is working (as emails are being piped through and tickets created), so the issue lies with php scripts.
We can take a closer look, but I will need additional information on how to direct your support request. Is your Cloud Linux license purchased directly from Cloud Linux or through cPanel? Thank you.0 -
Update: I can share my part of the experience, may be its useful. However, please bear in mind that I am an end user with very little know how of back end scripts. Problem: CloudLinux + Cpanel + probably some server configuration (which I don't know) causing bouncing of the emails send to support departments created within WHMCS - Piping done using forwarding. The error message (given at the bottom) indicates failure to locate pipe.php / its directory. Probable Reason: WHMCS suggests command for use in Cpanel Email Forwarding for piping : | php -q /home/username/public_html/whmcs/crons/pipe.php WHMCS clarifies use of only public_html/whmcs/crons/pipe.php at related location in Cpanel's. The earlier part i.e. | php -q /home/username/public_html/ and related piping is achieved through appropriate combination of WHMCS scripts with Cpanel. During past usage of whmc and cpanel, I noticed that once we put public_html/whmcs/crons/pipe.php in forwarding section of Cpanel, the remaining part including | php -q will automatically appear. However, recently | php -q part does not show up. (at least so in my case) WHMCS does not provide any guidelines on this | php -q / part, i.e where and how to insert it (or even inset it or leave it). The WHMCS staff during inspection in response to my support ticket on this, did not indicate the need of | php -q and I may highlight that I created a support ticket with WHMCS and followed it up. The WHMCS team however, insisted that it pertain to cloud not existing properly. Resolution: A cpanel post at email pipe fine but still generate and send bounce email back to sender helped me to know that editing of this can be achieved from /etc/valiases/yourdomain.com file directly Thats what I did, added php -q in valises. This is just my personal experience which if applies to some one else to make use of. I am closely watching the corn jobs (which also have similar path without php -q to see how does it go. ---------error message in bounced emails -- pipe to |/home/username/public_html/support/crons/pipe.php generated by abc@domainname local delivery failed The following text was generated during the delivery attempt: ------ pipe to |/home/username/public_html/support/crons/pipe.php generated by abc@domainname ------ cagefs_enter: /home/username/public_html/support/crons/pipe.php: No such file or directory 0 -
We can take a closer look, but I will need additional information on how to direct your support request. Is your Cloud Linux license purchased directly from Cloud Linux or through cPanel?
Thanks, Michael, it is resolved already.0 -
Hello, For me the uninstall method worked on one server so far. I first disabled and removed all directories associated with CageFS: /usr/sbin/cagefsctl --remove-all Uninstall it: yum remove cagefs yum clean all Install it back: yum install cagefs Go to WHM -> CageFS -> Initialize cagefsctl --force-update After that, I tried again to see if the autoresponse works, and it does (so far). I will try it on some other servers which are encountering the same problem. Will come back if I find anything different. P.S. Don't forget to enable CageFS for all the users after init from WHM. Hope this helps somebody. 0 -
Hello, A solution to this was to remove the eximmailtrap file: mv /etc/eximmailtrap /etc/eximmailtrap.bak service exim restart Regards. 0
Please sign in to leave a comment.
Comments
15 comments