- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
I would even say that Message Center has never been designed for handeling correctly the quarantine functionnality:
Marketing instance
Message Center 1 (RT1)
Message Center 2 (RT2)
I know that kind of configuration is quite old today but always used for lots of customers
RT1 have "badEmail@homail.com" in its quarantine table
RT2 have "wrongEmail@gmal.com" in its quarantine table
It means that if your API call with "badEmail@homail.com" lands on RT2 (due to load balancing): the email sending will proceed
Now, as you know, both of these addresses are consolidated on marketing instance... But then, it will only helps your standard "batch" sendings
It means that the only way to address the issue is to build a custom API that will query the nmsAddress schema from your marketing instance with a queryDef (don't forget to check the correct status in your "where" clause) to check if the email address in parameter exists... And that will proceed the pushEvent method to the Message Center load balancer
Problem of this kind of integration is that it implies a robust architecture: I would suggest to deploy a dedicated webserver process for soaprouter.jsp: too many connections could lead to make web process failing in memory...
Or you could even imagine to execute directly a stored proc on nmsAddress table directly from your API... But take really care about possible deadlocks
For that kind of tricky issue... Adobe addressed it by promoting the "one RT message center instance": no more synchronization issue about nmsAddress ^^
In the end, if you have a deliverability consulting package with Adobe... I'm quite sure that they will be happy to integrate your CSV file on RT instance(s)...