- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
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 common for all associated deliveries by operator. Further, could we use nmsaddress table? Correct me here, As per my understanding there's no direct way to insert hard / soft bounce stats. Both hard / soft bounces total / percent is auto calculated by Adobe system based on the failure reasons. For example - softBounce = @unreachable + @mailBoxFull + @invalidDomain + @disabled + @notconnected + @refused The flow might be : 1. Upon delivery, entries go into nmsaddress table where we have a column (saddress) consisting of email address associated with a particular deliveryID. The column 'iquarantinereason' could indicate the different failure reasons. This table might have daily clean-up activity since I could only see data for following deliveryID in QA while its empty in prod. 2. After step 1, in the background Adobe system might have a job running that dumps data into nmsdeliverylogstats table. Here we have all the failure columns associated with domains (sdomain). Say our email delieries were to rohan@gmail.com, rohan@yahoo.in. 'nmsdeliverylogstats' table will get the associated domains from 'nmsaddress' table and dump into 'sdomain' column as gmail.com and yahoo.in. In case unknown user failure was recorded for rohan@gmail.com, gmail domain would have that count against other domains. 3. There are other tables like 'nmsdelivery' and 'nmsbroadlogmsg' of which we aren't that sure now. 'nmsbroadlogmsg' table does have failure reason and failure type columns but its associated to single operator based on msgID. Adding / updating this table doesn't look correct if rohan@gmail is failure while all others are success. Also here issue is most of our deliveries are associated with same msgID (operator base). Not sure how to filter.
Views
Replies
0 Likes
Total Likes