Piping issue with CloudLinux

[mwaraitch]

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

 

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.

 

-----------

 

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

Edited November 18, 2015 by mwaraitch

[mwaraitch]

Also Tired the Cron Piping Method and ended up with "No input file specified."

Edited November 18, 2015 by mwaraitch

[jeffdoyle79]

If you are still having issues I had the same problem, but it wasn't cloudlinux causing the issue. First check the path of your crons folder. I used the recommended security settings when I first setup my system and forgot... I noticed when I was going on to change the permissions... If indeed your crons folder is outside the default path shown on the support overview page then update it in the forwarder. Also make sure the file permission is 755. After some time I finally got mine to work. Good luck.