I would like to get some detailed insights on how the Delivery Failure Scenarios work. Let's say i have currently Delivery Logs which will give information about Success and Failed Deliveries. I do have Exclusion Logs also which will give Excluded Addresses information which can be due to (Duplicates, Quarantine and Blacklisting)
But one thing is not clear if we want to check if any Email address(s) is no longer valid and should not be targeted, how can we identify such information from the logs. We want to filter out only those recipients (using query filters either on Failure Type / Status / Reason etc.) and do a cleanup of the data in Campaign + other systems outside of Campaign (based on information that is exported and sent from Campaign).
In order to ease the filtering from nms:recipient, the emailInfo elements comes from a join with nms:address.
Please note that an email in nms:address doesn't mean being invalid; there could be whitelisted emails in nms:address, valid after soft bounces until being treated by the nighthly job in case there are valid after some attempts to be delivered, otherwise there are classified as hard bounces. So please the type + status+ message reason accordingly to the documentation.
But yes, the documentation could be improved a bit with more examples.
OK if you don't use the factory nms:recipient for default target schema/document, and you use a custom delivery mapping, you should define an element as emailInfo to link with the nms:address content so it eases querie (or ask your admin to do so). And normally the broadlogs tables content of your custom delivery mapping should be accessible for you, even if you are not allowed to access to the Administration node (very classical management of privileges, please see again with your admin if not the case). Regarding the nms:address access, perhaps your admin can create a view folder with reading rights only, it is what I do for sharing information with Campaign managers without granting too much privileges.