Doug Tokarik
New Member
Mr Twisted,
I really dig the Domain Policies addition found within each Delivery Server page on the Admin version. However using it for the first time this week, I began by "deny"ing just one domain (aol.com). Everything was fine/working as it should. I went back and added 5 more domains to "deny" and noticed a couple days later that the campaign had stopped sending. Everything still looked correct as in it was not paused, it was not completed, there were no visible errors, but it was just stuck at 18,310 sent and no matter what we did we could not get the thing to resume sending past 18,310. So trial and error'ing shit, eventually I removed 4 of the 6 "denied" domains, and noticed this was the ticket. This is what it took to resume for some reason. Further testing; I added a 3rd domain to "deny" and sure enough, it froze it again. Moved it back to only deny 2 domains (aol.com and comcast.net) and back to resuming sending.
Is this an issue you are aware of or have seen anyone else notice and talk about it? Is it possibly just a bug? If so, hopefully bringing it to your attention helps. Please keep me posted what you find. Appreciate brutha!
I really dig the Domain Policies addition found within each Delivery Server page on the Admin version. However using it for the first time this week, I began by "deny"ing just one domain (aol.com). Everything was fine/working as it should. I went back and added 5 more domains to "deny" and noticed a couple days later that the campaign had stopped sending. Everything still looked correct as in it was not paused, it was not completed, there were no visible errors, but it was just stuck at 18,310 sent and no matter what we did we could not get the thing to resume sending past 18,310. So trial and error'ing shit, eventually I removed 4 of the 6 "denied" domains, and noticed this was the ticket. This is what it took to resume for some reason. Further testing; I added a 3rd domain to "deny" and sure enough, it froze it again. Moved it back to only deny 2 domains (aol.com and comcast.net) and back to resuming sending.
Is this an issue you are aware of or have seen anyone else notice and talk about it? Is it possibly just a bug? If so, hopefully bringing it to your attention helps. Please keep me posted what you find. Appreciate brutha!