Did you manage to get the URL to work? Reason I ask is Adobe engineering
said the status page was only ever made available in an internal Adobe
release version and was never released in a GA release. I could never
get it to work, even after getting pipelined set up properly.It could
also be because ...
OK - I finally have an answer on how ACC determines a valid email. It
took way more effort than I expected but we got an answer:So I am
assuming that the first part of this response is the dataPolicy check
and the second is a regex against the XtkEmail_Characters option. e.g.
So another piece to this puzzle (provided by Support) is the option
value for the valid characters in an email address XtkEmail_Characters.
I tested this value and this Option value is definitely being used by
the mystery validation function to check for valid characters in the
email before the writ...
Hi David - I tried what you said and escaped the special characters in
the email, but the recipient write still fails. Here is my test code:var
email = "blah23\/firstname.lastname@example.org";var firstName = "Ford";var lastName =
"Prefect";var mobile = "0000888999"//RFC5322 email regexvar regexEmail =
Agree with Jean-Serge. Check that you have pasted the right public key
in that matches your production private key in the Legacy OAuth
connection you created for your production instance. This should be
different to the key pair you used for DEV.
Hi davidk23955130 - I just tested that code you highlighted above with
an invalid email address - "email@example.com" - it passes those
tests but you can't insert it into the recipient table. The email
addresses passes all RFC5322 tests I have thrown at it.Can anyone tell
us the exact data poli...