Whmcs admin notification mail is not working when a customer places a order

[vispl2014]

Hi,

 

Whmcs admin notification mail is not working when a customer places a order

 

Please give the suitable solution for the above issue.

 

Regards,

vispl

[brian!]

either...

 

"Setup > General Settings > Mail "

For field "BCC Messages" you can enter an email where all WHMCS emails will go.

 

or

 

"Setup > Administrator Roles > Select role your account use "

Scroll down and see if you've selected option "Account Emails (eg. Order Confirmations, Details Changes, Automatic Setup Notifications, etc...)"

[vispl2014]

Hi Brian,

 

Still it is not working..

 

Regards,

Vispl

Edited July 9, 2014 by vispl2014

[vispl2014]

Hi,

 

Setup > Administrator Roles >" already have full permission and "Setup > General Settings > Mail "

For field "BCC Messages" email id also already entered, but admin notification mail is not working when a customer places a order

 

please help me.

 

Regards,

Vispl

Edited July 9, 2014 by vispl2014

[brian!]

Hi,

 

you may have already done so, but have you checked to see whether these new order emails are arriving in the spam folder of the mailbox?

are all other whmcs admin emails getting through to the mailbox - tickets, cronjob, backups etc ? if none are getting through, then it could be the mail settings... but your question implies that everythign else is getting through apart from these new order emails.

 

it would be interesting to know whether whmcs is sending the emails... or if it just the mailbox not receiving them, perhaps being filtered by spamassassin or some other mail server filters.

 

in your system activity log (utilities -> logs -> activity log), there should be an entry for each new order you receive...

 

New Order Placed - Order ID: xx - User ID: xx

does your log have such entries?

 

i'd also be tempted to try the old "turn it off and turn it back on" trick on those three checkboxes in the red square - so untick them, save changes, tick them again and save changes once more... if there is a faulty setting in the db causing this, that might resolve it.