I am hoping someone can assist me in getting piping working using email Mail Aliases.
My crons folder is outside my WHMCS root as per their docs on additional security steps.
My pipe.php file is set to permissions 755
I am using the correct path - proved by the fact crons are working as expected
As mentioned I do have crons running correctly but every attempt to setup email piping fails
I have tried every combination in the aliases destination string but receive errors ranging from
Permission denied Could not open input file:
Command died with status 1 -- Could not open input file
This is just one example of the aliases destination string I have tried
/usr/bin/php | php -q /home/mydomain/domains/my-sub-domain/whmcs_working/crons/pipe.php
Yes, it works fine for me, I have situation [cron outside public], all you need to do is create a mail alias.
VirtualMin, Edit Mail Alias, Tab Advanced Mode, Feed in program and use this:
php -q /home/user/crons/pipe.php
I’m going to weigh in on this old post. First of all, running piping is so much better than pop3 because you are instantly notified about new email. That can make the difference between a huge sale and a mediocre one, and the difference between slow customer service and perceived exceptional customer service. So I’m very much for piping instead of popping. Secondly the fact that WHMCS only supports cPanel and DirectAdmin should be taken with a pinch of salt. WHMCS has cPanel as a partner and are quick to not support other panels. Piping is a function of Postfix on Linux and Virtualmin does things in a stock way, so there should be no reason why it could not work.
As for the error itself:
“Command output: Could not open input file: php -q /home/mydomain/domains/my-sub-domain/whmcs_working/crons/pipe.php”
“Could not open input file” to me is a very simple and straightforward message. It simple can’t “open” / “FIND” the file. My guess it when piping the process can’t find the PHP executable. So I would change the pipe command to include the full path to PHP, e.g.: