Email Piping Help

[gunnston]

Very new to this whole piping thing, so I thought I'd ask for some help.  

 

I've been trying my hardest to get this email piping done correctly.  I've been on a few of the forum posts on here, but I really don't know where I'm going wrong.  

 

I'm totally new to this piping business and I could be totally wrong in my methods, so I'll just tell you what I've been going through (based on the topics I've read on the Blesta forum.)  

 

Firstly, I'm using a reseller VPS account with cPanel.

 

I've successfully gotten the perl module installed with a little help from my hosting.  

 

I'm I got to section where I can set up piping in Support > Department without getting an error when I click save.  

 

I seem to be stuck at this point.  I've attempted to copy + paste the "Piping Configuration" in cPanel > Forwarders > Advanced Settings > Pipe to a Program, but I get RTS's everytime I test it.  

 

There may (or may not) be something totally obvious that I'm not doing.  

 

I was hoping someone could either tell me what that is, or point me in the direction of a totally simple tutorial on how to do what I'm trying to do (a piping tutorial, etc.)  Please remember that I have very little knowledge on most of this.  I'm going mostly on what a search engine and the Blesta forums tell me.  : )

 

Thank you in advance.  

[gunnston]

Hey Mike,

 

Turns out your were right.  It was /user/local/bin/php -c 

 

There was another line they had me add:  /home/username/php.ini

 

the other two lines were the same (the "pipe.php" and the "index/1/")

 

Not sure if every hosting is like this but I hope it can help someone.  My hosting support was great for me.  Took a while, but got it done.  

[Michael]

In that advanced are you using /usr/local/bin/php instead of /usr/bin/php? cPanel uses the local bit.

Also is pipe.php got the hashbang and chmod'd 777. I've noticed when helping a customer that cPanel is playing up in their latest version and doesn't hashbang it.

 

#!/usr/local/bin/php before the <?php

[gunnston]

Hey Mike,

 

Thanks for the heads up.  I ended up going to my hosting support for some of the help.  The path is definitely the root of the problem.  They've changed it to what you had.  It's still not working but they're working on it.  

 

Thanks for the heads up.

 

I'll post the results just in case anyone else is having the same problem.