Basically, I had two questions, since I am integrating my MTA server with adobe, upon delivery I need to trace back the stats back to adobe for reporting.
1. With resp to failure reasons, like mail box full, not connected, refused, unreachable, what table should I refer to insert the values? Would it be directly 'nmsdeliverylogstats'? Any other tables I need to take care? Because the delivery success / failures I am inserting in 'nmsbroadlogrcp' table and they auto populate in 'nmsdeliverylogstats'.
2. Is it possible to import / create work-flow in a way to insert the entries in above 2-3 tables at the same time? Currently, my work-flow just inserts entries into 'nmsbroadlogrcp'. Any reference for example?
You need to update the failure reasons in the nms:broadLogMsg schema, linked to the nms:broadLogRcp schema with msg-id field. Below screenshot should help.
For your second question, the answer is yes. How exactly are you receiving the response from the custom MTA? API, files, or something else. Based on that you can build a mechanism to update all tables with proper linked items.