Thanks @Milan_Vucetic and @DavidKangni  We are under the impression, we would need to do recompute on nms:delivery for everything to be in sync. Could you suggest what schema other than delivery could be a best practice? Like simply going with nms:broadlog or nms:broadlogmsg? Also any way to update ...

Hi @Milan_Vucetic,Actually we are not using Adobe MTAs for delivery. We have our custom MTAs, based on logs we filter out the delivery sends and with help of target flow, have the data inserted in resp tables. That's the reason we have use this route. Once entries are in place, we recompute the sche...

Anyone around?

Hi,For recomputing, we are using logic that works on entire nms:delivery schema. We came across following solution across the community but it doesn't seem to fix our problem either since the logic is similar and performing on entire nms:delivery schema,<queryDef schema="nms:delivery" operation="sel...

Hi, Have a query with resp to how I could deal with failure reasons at individual recipient level since I am using my custom MTA? Like from my custom MTA logs, I am able to figure out success and failures, but when I see the 'NmsBroadLogMsg' table, only one 'ibroadmsgId' per operator is mapped. So i...

Hi,My query is with resp to failure reasons corresponding to hard / soft bounce stats. Actually I am not directly using adobe MTA, but built my custom MTA through which deliveries are happening. From these logs, I am mapping success / failures and then dumping into 'NmsBroadLogRcp' and 'NmsBroadLogM...

Basically what tables do I need to refer. Since I have my custom MTA, so picking up those logs and what tables to dump? broadlogrcp - Delivery success / failure Instead of going via import work-flow route, I manually inserted new entry in nmsbroadlogmsg table with mailbox full error against soft bou...

Hi @kapil. Instead of going via import work-flow route, I manually inserted new entry in nmsbroadlogmsg table with mailbox full error against soft bounce event code, based on msgId, inserted similar kind of record in nmsbroadlogrcp with other details like success / failure and deliveryID. Now my exp...

Thanks @Ishan for the explanation. I did follow your steps but no luck. Instead of going via import work-flow route, I manually inserted new entry in nmsbroadlogmsg table with mailbox full error against soft bounce event code, based on msgId, inserted similar kind of record in nmsbroadlogrcp with ot...

Thanks @Ishan. To this, how could brodlogmsg table be useful since it just has the operator level info. Like say, I have 7 email domains in my delivery and 2 of them fail, how this could be differentiated in broadlogmsg table, we we just have operator who has scheduled delivery info with msgid been ...