We have a decision point at the start of our inbound email flow that contains the following code to allow emails that Bcc our email inbox, however the system disconnects the email. We use the same code for allowing emails that have our email address in the to and cc fields and they make it through. Is there a workaround that needs to be added for Bcc or is this just a symptom of Genesys cloud?
Contains(Lower(ToString(Email.Message.bcc))
I have read the post in the forum concerning email.message.bcc behaving differently and we have engaged with Genesys on the issue, to which they continuously refer to this post but a workaround/solution has not been proposed.
I am not specialist on mail server (protocol) but I started to read about this (BCC).
From what I understand, the fact that Email.Message.bbc is empty on an inbound email is by definition of email (not in Genesys Cloud but in email).
What I mean is that when you send an email with someone in BCC, the BCC field/info is not propagated to the recipients (by the originating email server).
So if you send an email with TO: address1, address2 - CC: address3 - BCC: my_address, none of the recipients will receive an email with BCC info/attribute.
When my_address receives this email, he will see the TO addresses, the CC addresses - but no BCC.
So how do I know I am in Bcc.
Because I receive the email and my address is not in the TO addresses nor in CC addresses.
Translating this to Architect, it would mean testing if the address does not appear in TO and in CC addresses.
Something like: FindFirst(Email.Message.to, MakeEmailAddress("myservice@company.com")) <0 and FindFirst(Email.Message.cc, MakeEmailAddress("myservice@company.com")) <0
As I don't know how you are segmenting the emails, note you can have the address appear both in TO and in CC.
Address in TO and in CC
Address in TO only
Address in CC only
Address not in TO and not in CC (-> BCC)