- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi @rohanpat,
nms:broadLogMsg table is used to store further information related to delivery send-outs. By default it does not contain much information about success deliveries, since the @status column in nms:broadLogRcp table tells us that the message was successfully sent. It does contain further information about the error deliveries. If you see carefully, these two tables are linked on the @msgId field (primary key of nms:broadLogMsg). There can be multiple messages which failed but due to same reason (mailbox full, invalid domain, etc.). Only one entry in this table can be linked to multiple records in the nms:broadLogRcp table to tell us more about the reason of failure.
In your case, you can use this table to store more information about failure (or even successful) deliveries. The choice is yours.
However, the table nms:address only contains information about email addresses which are either quarantined or blacklisted due to x,y,z reason. This table is checked by the typology rules to filter out any recipients from the delivery target which are either quarantined or blacklisted. This table does not contain any delivery level information per recipient. Moreover, entries into this table would also be made automatically based on the error qualification for a particular email address in the nms:broadLogMsg table (not 100% sure though).
Delivery success or failure stats are calculated by the RecomputeStats method run on every delivery automatically at one or several points in time. But if you want your custom MTA feedback to reflect correctly you need to execute this method on your own (not sure if the automatic job that recomputes these stats for every delivery will take your MTA feedback into consideration, better be safe and do it yourself).
Let me know in case of further doubts, will try my best.
Thanks,
Ishan