BCC order emails

-- HikaShop version -- : 6.1.1
-- Joomla version -- : 5.4
-- PHP version -- : 8.2.29
-- Browser(s) name and version -- : Firefox & Chrome

Hi, A long time ago you gave me this code

if($data->order_status=="Payment Received"){ $mail->bcc_email = 'xxxxxx@xxxx.com'; } (I have tried using another email address and it still does not work?)

to put in email, order notification. This has been working for years but for some reason has stopped working for over a week now?

Any solution or alternative way the 'order notification' email can be sent to an alternative address as well as the main email address?

Rgds

Hi,

The "order notification" email is the one sent to the user when you click on the "email" button of an order in the backend and then validate the sending in the popup.
The content of the BCC field is actually visible in the popup if you click on the "BCC" text in the popup.
Also, it could be that everything is still working fine in HikaShop but that the email is ending up in the spam folder of the BCC recipient. So, you can check the BCC value if you look at the emails in the Customers>Email history. That way, you can make sure whether the issue is before HikaShop sends the email or after.

How did you add this code to the email exactly ? Could you provide some screenshots to illustrate the modification and the result ?

Hi, Never got an email to say you had responded??

I'm now sure this is down to something wrong with outlook as I have added the same code but to a gmail and that works.

the code is in emails, order notification email, this then sends a duplicate email to another address just in case of sever outage or internet outage, I then can still work due to the orders being on my phone.

Worked ok for 9 years, I have my service provider on it and they also suspect its down to Outlook?

Rgds

Hi,

Outlook is infamous for being quite strict with its spam filtering policies, too strict even, so I'm not surprised that you're telling me that.

Our forum also send the emails automatically, and this is still working fine for everyone else. So it's likely to be something with outlook too.