Hey @renovatorstore,
I noticed that you have both @renovatorstore.com.au and @higoldharware.com.au as domains of those recipients. Do you happen to have any sort of dedicated sending domain setup?
I still suspect those info@ and service@ recipients aren’t receiving those opt-in notifications due to some misalignment and are blocked by your inbox/DNS.
I would strongly advise working alongside your own internal IT administrators to review your DNS security settings and domain setup just to rule these possibilities out. Just because, if it ultimately is a DNS/domain setup issue causing these blockers, it’s better to catch these sooner rather than later. Although the @market and @mavis recipients successfully opted in, if it turns out to be a backend issue, there’s a strong possibility that they may not receive the subsequent notifications from the flow.
I would also like to highlight, that just because two addresses were set up in a similar fashion, doesn’t mean backend DNS filters are going to trigger one-hundred percent of the time. They aren’t perfect. Oftentimes these filters are triggered based on a number of factors including frequency of the requests, level of suspicion, source, etc.
David