1

We have various trigger sends definitions setup for transactional notifications. The TSD have now gone live and there has couple of errors under the same error code:

"messageErrorCode":180008,"messageErrorStatus":"Unable to queue Triggered Send request. There are no valid subscribers."

However I have checked all the attributes, their types and validations seems to be correct.The API requests doesn't even get through the Triggered data extensions or Triggered Send Definitions. The type of email addresses in the API requests are:

mail@xxxxxx.com
mail@yyyyyy.com.au
admin@zzzzz.com.au

I am guessing the List Detective in sfmc is filtering out these types of email addresses and it is a concern for business because these are transactional requests and cannot be ignored.

Has anyone been able to bypass/turn off the List Detective or is there a way to pass these requests in API to TSD?

1

Looks like I have more clarity around List Detective in API triggered sends.

Key Points:

  • List Detective cannot be accessed via UI in sfmc and cannot be turned off.
  • Only Salesforce support can alter the rules around List Detective and that includes which email domain will included/excluded in the process.
  • List Detective updates can be applied within the Business Unit level which means making changes to one BU won't effect other.
  • List Detective is mainly to ensure that the sender reputation is maintained which is the reason why it is restrictive around spams.

Note: The Trigger send error code 180008 doesn't explain about the list detection error.

  • Hi @brad, We have the same issue with one of our account. Around 600 emails were skipped from sending and all the subscribers are from different domains. Any idea, how do we get this rules altered, so SFMC will send email to all users? All these users are valid users actually – Praveen Kumar Bandi Nov 21 '17 at 2:41
  • Hey @PraveenKumarBandi, you'll need to raise a support ticket and mention the email addresses that are being blocked due to list detective. sfmc support will then update the list detective in the backend to allow those email addresses into the platform. for eg if admin@xxx.com is blocked then you can request sfmc to allow any emails coming as 'admin@' with any type of valid domain. – Brad Sapkota Nov 21 '17 at 2:52
  • Hey @brad, admin@xxx.com/sales@/info@ would allow bulk of the emails, but still, SFMC is excluding many other valid emails in every send. – Praveen Kumar Bandi Nov 21 '17 at 4:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.