How to fix WHMCS Email Pipe Problem
In this article we discuss how to resolve the email piping issue in WHMCS. This is one of the key features of WHMCS for customer support.
WHMCS email pipe problem is a common issue especially after a new WHMCS installation. You can set up a cron job to pipe the emails into your WHMCS using the “Email forwarder” or “POP3 Import”
For email forwarders you add similar command to your cron job
| php -q /home/cpanel username/public_html/clients/pipe/pipe.php
In some cases when a client send an email to your support department (for example, [email protected]) they immediately receive a mail delivery failure report. This may be due to the permission issue to the pipe.php file and how you have set up your email piping in WHMC. The return email is something like following:
This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of itsrecipients. This is a permanent error. The following address(es) failed: pipe to |/home/username/public_html/clients/pipe/pipe.php generated by [email protected] local delivery failed The following text was generated during the delivery attempt: —— pipe to |/home/username/public_html/clients/pipe/pipe.php generated by [email protected] —— cagefs_enter: /home/username/public_html/clients/pipe/pipe.php: Permission denied —— This is a copy of the message, including all the headers. ——
The easiest way to resolve the issue is using the cPanel and change the permission of the pipe.php file (which is generally 644) to a lower security level that allows writing permission (permission 755). This will allow the sent emails to be write into the pipe.php and a ticket number be issued.