Avatar

Level 6

Sorry but really a bad idea:
good practice is to target active users from the last 6 month (and 3, in the teddy bear world). In other term, to target people that, at least opened, your email. (actual good pratice is too target only clickers as the open tracking is less and less accurate. See my colleagues' answers for the technical explanation)

targetting people that provide no click/opening will lead to more SPAM/complaints & spamtrap and will lead to loss of ISP reputation: you'll send then less emails per hour).
With a such targetting politic there's 2 options:
1- using a dedicated pool of IPs and a dedicated subdomain that will always have a bad ISP reputation... But you won't have deliverability issue on your main sendings
2- calculate the max amount of targets and try to send the email when you recieve the most tracking activity of your users in order to mitigate the "bad points" from the main ISPs

Now if that's ok on your marketing project (the aboves are functionnal recommandations, not technical ones) and you still have green lights

You can do like this:
1- assign 2 different deliveryCode to your templates for email 1, 2, 3
2- for workflow on email 2, query your main audience, use a split activity and use this filter:
* TrackingLog doesn't exist such as
     > [delivery/@deliveryCode] equal to "xxxxx"
     > @date after DaysAgo(2)
* BroadLog exist such as
 > [delivery/@deliveryCode] equal to "xxxxx"
 > @eventDate after DaysAgo(2)
 > @Status equal sent
 
3- for workflow on email 3, query your main audience, use a split activity and use this filter:
 * TrackingLog doesn't exist such as
     > [delivery/@deliveryCode] in "xxxxx", "yyyyy"
     > @date after DaysAgo(4)
* BroadLog exist such as
 > [delivery/@deliveryCode] equal to "yyyyy"
 > @eventDate after DaysAgo(2)
 > @Status equal sent

If something is not clear, don't hesitate to ask