If randmap could nest, then one could say
randmap:{smtp1,randmap:{smtp1,randmap:{smtp1,randmap:{smtp1,smtp2
and approximate the desired ratio with 15/16. But it does not nest,
because 'randmap' is like 'static' combined with multiple choice.
That's enough humor for now.
Wietse
On Tue, Feb 26, 2019 at 04:01:15PM +0100, Tom Sommer wrote:
> > # Picks smtp1 90% of the time, smtp2 10% of the time.
> > randmap:{smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp2}
>
> True, that is a way - although a litte bit of a workaround; setting 93%
> is a little bit of a mess :
Wietse:
> # Picks smtp1 90% of the time, smtp2 10% of the time.
> randmap:{smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp1,smtp2}
Tom Sommer:
> True, that is a way - although a litte bit of a workaround; setting 93%
> is a little bit of a mess :)
I didn't think that such a high level of pr
On 2019-02-26 15:51, Wietse Venema wrote:
Tom Sommer:
I have a feature request for a lookup table like randmap(), but with
the
option to control a percentage or a count of mails sent to the
transport.
Even if the percentage was just a "chance" of selection, it would be
nice.
So you could do :
Tom Sommer:
> I have a feature request for a lookup table like randmap(), but with the
> option to control a percentage or a count of mails sent to the
> transport.
>
> Even if the percentage was just a "chance" of selection, it would be
> nice.
>
> So you could do :
>
> sender_dependent_defa
I have a feature request for a lookup table like randmap(), but with the
option to control a percentage or a count of mails sent to the
transport.
Even if the percentage was just a "chance" of selection, it would be
nice.
So you could do :
sender_dependent_default_transport_maps = randmap:{
