Louisvdw

That is the same setup we all have (WHMCS in a sub account) Did you setup the forwards like in 2) and 3) in the opening post? (a forward from the main domain to the sub domain and then a forward in the sub domain to the WHMCS pipe) What DepotMan is refering too is that he had to change the Pipe from "| php -q /home/username/public_html/whmcs/pipe/pipe.php" to "/home/username/public_html/whmcs/pipe/pipe.php" in order for cPanel to accept it. (username should be your username on the server)

@othellotech, Thanks for the feedback. I found the information in the wiki about that. I seems I only need to disable "Sequential Paid Invoice Numbering" and then it should be fine again. I've done that and will review it with the next received payment.

I have a strange problem. When an invoice is sent to a client it has a certain invoice number (e.g. 1194) When that client pays and payment is added to the invoice, the payment confirmation is sent out, but the invoice number on the confirmation and on the system then changes to something else than the original number (e.g 156) General->Invoice Settings show to following: Next Paid Invoice Number [157] Only change this if you need to regenerate an invoice number Invoice Starting # [ ] Enter to set the next invoice number, must be greater than last #1195 (Blank for no change) And Sequential Invoice Number Format is {NUMBER} and Invoice # Incrementation that is blank (Default = 1) It shows the Paid Invoice Number different than the Invoice Starting #. Why are the 2 numbers for this, why is it having 2 different values and more important how do I best fix it so that my clients are not confused by the 2 different Invoice Numbers? PS. I have been upgrading from my initial V3.6 or V3.8 up to the latest V4.5.1 as the new versions came out. Not sure if that has anything to do with this problem.

The Support Departments read the TO address for the email that they are setup with. CC or Forwards will not work for you unfortunately. You will have to do some magic to get those mails to show the correct To address, or setup multiple departments

Thanks tkron. It's basically the same as what I have, you just forward mail for the hole domain using MX Records. It should work very nicely.

That method will work for different servers and/or domains.

You do not have to use the POP method. You can try to use the mail pipe using forwards method outlined in the following thread: http://forum.whmcs.com/showthread.php?t=16860

Thanks RenatoMN. This is just what I needed.

Are you perhaps using CPanel with the X3 theme? 'Cause according to the wiki

Yes I have tried this. I currently have to departments (Sales & support) setup like this working 100%. The process described above is exactly what I did to make it work.

Did you go to your secure.mydomain.com account and created the forward for support@secure.mydomain.com --> | php -q /home/secure/public_html/pipe/pipe.php This is the part that actually pipe the email to WHMCS

rhee, a forward does not change to TO address when it forwards a mail. Your mail will be received at email@mydomain2.com saying that it is addressed to email@mydomain1.com There must be something else wrong. Do you get an error, or is your e-mail just not received by the support department?

Where can I find which field types are supported when defining a module? From the Template I can see there are text & yesno types. From the wiki I can see that these fields are supported most likely: * Text Box - text in the template * Tick Box - yesno in the template * Dropdown Menu - ??? * Textarea - ??? * ??? Can someone fill in the blanks and perhaps give an example of how to use them (for instance how to populate a Dropdown Menu if that is available) Thanks

@Pima - It's more of a want than a need @mycommon - By using a normal forward from the one account to the next where you setup your WHMCS, it's the account itself that has the access. The main account does not have access to the second, so you can't call the PIPE directly.

Pima, that is a cleaner option, but I wanted the separate IP and still use email piping. With my setup as it is now, I have different IPs & accounts AND using email piping (Not a CRON)

My support email is under my main domain as support@mydomain.co.za, but WHMCS is installed under a seperate account secure.mydomain.co.za (with it's own IP), so piping "| php -q /home/username/public_html/whmcs/pipe/pipe.php" from support@mydomain.co.za won't work. According to http://wiki.whmcs.com/Email_Piping) I'll have to use the CRON Piping method There is another (better) way Here is what to do to setup this scenario to work with Email Piping directly into WHMCS: We're going to use a normal forward from mydomain.co.za to get to secure.mydomain.co.za and then piping from secure.mydomain.co.za into WHMCS using to normal method of "| php -q /home/username/public_html/whmcs/pipe/pipe.php" 1) Login to your WHMCS admin (e.g. at secure.mydomain.co.za/admin) and setup your support department. (Configuration, Support Departments, Add New Dep./Edit existing Dep.) Make sure that the email address that you specify is the address from your main domain that you want to use, even though it is under a different account/domain. (e.g. support@mydomain.co.za) 2) Then setup a forward for the email address from your main domain that you specified in your Support Department in 1), to an email address on your WHMCS domain. (e.g. Forward support@mydomain.co.za --> support@secure.mydomain.co.za) 3) Next we will setup the email piping on the mail address on the WHMCS domain using the pipe command supplied by your WHMCS. (e.g. support@secure.mydomain.co.za --> | php -q /home/secure/public_html/pipe/pipe.php) All that is left to do is to test your setup. Send a mail to you support department (e.g. support@mydomain.co.za) from a separate address that is not a admin. When replying as an admin, the response will be sent to the client from the email you specified under you support department. My example use a sub domain for WHMCS, but you can use a completely separate domain as well, so long as you can send emails as the mail user from your main domain.