Elliot Cater
Member
Hi
We're currently trying to rate limit the amount of mail we send to Hotmail/Live/Outlook addresses to improve our IP reputation.
We have created 2 delivery servers, one that has an hourly quota of 20 and domain policies as below:
The other none limited delivery server is identical apart from the server name and domain policies as below:
For some reason the sending is stalling to a halt. On manually running the "send-campaigns" command with the verbose parameter it becomes apparent that both delivery servers are just getting bogged down with the hotmail addresses in the list.
It seems the "processing" behaviour is to check all of the unsent subscribers against the domain policies and blacklists, every single time the send-campaign command is issued.
If you have a fairly strict quota on one delivery server and quite a high percentage of subscribers in a list being matched with the domain policy, you're very quickly going to end up in a situation where both servers are affected by the quota.
If there was some way to have the IF loop at SendCampaignsCommand:869 get another subscriber from the DB it might solve that but it would mean excessive DB querying...
The alternative that I can see is to change the processing quantity to a number higher than the amount of subscribers being matched by a deny policy. Not ideal at all tho!
Elliot
We're currently trying to rate limit the amount of mail we send to Hotmail/Live/Outlook addresses to improve our IP reputation.
We have created 2 delivery servers, one that has an hourly quota of 20 and domain policies as below:
![allowoutlook.png](http://advertisingyorkshire.net/images/caters/screenshots/allowoutlook.png)
The other none limited delivery server is identical apart from the server name and domain policies as below:
![denyoutlook.png](http://advertisingyorkshire.net/images/caters/screenshots/denyoutlook.png)
For some reason the sending is stalling to a halt. On manually running the "send-campaigns" command with the verbose parameter it becomes apparent that both delivery servers are just getting bogged down with the hotmail addresses in the list.
It seems the "processing" behaviour is to check all of the unsent subscribers against the domain policies and blacklists, every single time the send-campaign command is issued.
If you have a fairly strict quota on one delivery server and quite a high percentage of subscribers in a list being matched with the domain policy, you're very quickly going to end up in a situation where both servers are affected by the quota.
If there was some way to have the IF loop at SendCampaignsCommand:869 get another subscriber from the DB it might solve that but it would mean excessive DB querying...
The alternative that I can see is to change the processing quantity to a number higher than the amount of subscribers being matched by a deny policy. Not ideal at all tho!
Elliot
Last edited: