Kim B. Heino:
> > However, you are looking for a solution BEFORE the mail queue,
> > that stops the verify daemon from sending probes.
>
> Yes, exactly.
>
> > Instead of per-domain quota, would not it be sufficient to impose
> > a global limit on the total number of pending verify requests for
> > information that is not already cached? Then use something like
> > "random drop" to keep the number within bounds.
>
> We have lot of different clients where we forward mail to. One global
> limit doesn't work: DDoS'ing one single client would affect all
> clients.
First, it is OK for you to code up something that works for your
specific use case.
However, I have to support the full range including sender probes.
So I would have to address things such as:
- The problem with external counters is that they aren't reset when
the verify daemon is restarted.
- The problem with per-domain in-memory counters is that they can
use up a lot of memory especially with sender domains.
Wietse
