On Mon, Nov 30, 2015 at 07:00:08AM -0800, Quanah Gibson-Mount wrote:
> >I've always (since ~2001) used large recipient limits with filter
> >transports, this also improves efficiency, no need to scan the same
> >content multiple times.
>
> Hi Viktor,
>
> Thanks for the reply! I've been on vacation so catching up on email. It
> sounds like the better solution then is to add:
>
> -o default_destination_recipient_limit=50000000
>
> to the content filter definitions? ;)
That won't work. The recipient limits are used in queue manager,
not the transport.
<transport>_destination_recipient_limit
And this would be an unwise global default, and the number is much
too high. You get dimishing returns especially beyond whatever
you've set for the virtual expansion limits.
--
Viktor.
