Juan Miscaro:
> > Postfix doesn't have any per-user rate controls (some add-on policy services
> > can do per-user input rate limits), and output rate controls are limited to
> > what's available with
> > http://www.postfix.org/postconf.5.html#default_destination_rate_delay
> > which is a per-destination limit, not an overall limit.
>
> [...]
>
> > Maybe router or firewall based traffic shaping would help - at least you
> > could prevent SMTP from hogging all the bandwidth.
>
> That's an interesting option. How would Postfix react to saturated
> bandwidth? Will it simply defer messages and try again?
Postfix handles timeouts as required by the RFC.
But there is no reason why Postfix should time out when bandwidth
is limited. Just reduce main.cf:default_process_limit so you don't
try to run an insane number of email deliveries in parallel.
In your case, putting the mail "on hold" is an appropriate solution.
You can do this while mail arrives (header/body_checks or perhaps
smtpd_sender_restrictions) or after-the-fact with mailq|postsuper.
Wietse
