On 30 Sep 2017, at 07:18, Wietse Venema <wie...@porcupine.org> wrote: > It could be simple. Suppose there is a 'popular site' counter table > (the opposite of the 'dead site' list) which is indexed by some > idea of 'destination' and which is updated in real time as delivery > agents announce what they are doing. To determine if a next-hop has > reached its concurrency limit, compare the configured limit for the > transport with the appropriate 'popular site' count.
It's sort of a reverse greylist: instead of blocking a site until it passes the greylist criteria you exempt it based on similar criteria. -- Apple broke AppleScripting signatures in Mail.app, so no random signatures.
