Correction in-line.
Wietse Venema:
> Calvin Browne:
> > Hi all - need someone to hit me with a clue bat.
> >
> > I have one particular address in a domain that is handled by
> > virtual_alias_domains through a virtual_alias_maps table. This address
> > gets redirected to an account on another smtp server. I would like to
> > rate limit the delivery perhaps by sending it over its own transport?
> >
> > Any clues/pointers appreciated.
> > mail_version = 2.2.10
>
> A workaround for Postfix < 2.5 is in
> http://www.postfix.org/QSHAPE_README.html#backlog:
>
> * In the transport map entry for the problem destination,
> specify a dead host as the primary nexthop.
>
> * In the master.cf entry for the transport specify the problem
> destination as the fallback_relay and specify a small
> smtp_connect_timeout value.
>
> /etc/postfix/main.cf:
> transport_maps = hash:/etc/postfix/transport
>
> /etc/postfix/transport:
> example.com slow:[dead.host]
Make that:
[email protected] slow:[dead.host]
Where [email protected] is the output from virtual aliasing.
> /etc/postfix/master.cf:
> # service type private unpriv chroot wakeup maxproc command
> slow unix - - n - 1 smtp
> -o fallback_relay=problem.example.com
> -o smtp_connect_timeout=10
> -o smtp_connection_cache_on_demand=no
>
> With recent Postfix versions, use a transport map and
> the _destination_rate_delay feature.
>
> /etc/postfix/main.cf:
> transport_maps = hash:/etc/postfix/transport
> slow_destination_rate_delay = 10
>
> /etc/postfix/transport:
> [email protected] slow:
>
> Wietse
>
>
