Adam Roses Wight:
> I've started writing this feature to determine whether it's feasible
> with the current architecture, but no success yet, this doesn't seem
> to limit the number of jobs which are popped from the queue:
I just had to find out why it did not work (While it is possible
to impleme
On 06/21/2015 05:31 PM, Adam Roses Wight wrote:
Thanks for the feedback! Slowing down the SMTP delivery agent sure was easy...
there are a few things to clean up, but the patch below seems to be giving the
behavior I need.
Have a look at the following,
http://wiki.policyd.org/features#quotas
On Sat, Jun 20, 2015 at 07:18:34PM +, Viktor Dukhovni wrote:
> If there is to be a global rate delay, the transport process limit
> might as well be equal to 1. At which point to implement a rate
> delay, it suffices for each delivery to take a minimum amount of
> time, so an option along the
Adam Roses Wight:
> Attaching my WIP patch here...
>
> On Sat, Jun 20, 2015 at 04:37:11PM +, Adam Roses Wight wrote:
> > Many hosting providers limit the number of outbound SMTP connections over
> > time, and exceeding their threshold results in harsh consequences like
> > dropped connections
On Sat, Jun 20, 2015 at 04:48:24PM +, Adam Roses Wight wrote:
> Attaching my WIP patch here...
>
> On Sat, Jun 20, 2015 at 04:37:11PM +, Adam Roses Wight wrote:
> > Many hosting providers limit the number of outbound SMTP connections over
> > time, and exceeding their threshold results in
Attaching my WIP patch here...
On Sat, Jun 20, 2015 at 04:37:11PM +, Adam Roses Wight wrote:
> Many hosting providers limit the number of outbound SMTP connections over
> time, and exceeding their threshold results in harsh consequences like
> dropped connections and unpredictable delays until
