Yoda via Postfix-users: > What I'd like to understand: > > 1. Is sub-second default_destination_rate_delay safe to use under > sustained load on a queue that already has tens-to-hundreds of > active recipient destinations? Or is there a load-dependent > interaction with qmgr's per-destination scheduling state
As documented https://www.postfix.org/postconf.5.html#default_destination_rate_delay To enable the delay, specify a non-zero time value (an integral value plus an optional one-letter suffix that specifies the time unit). When I set the system-wide rate delay: # postconf default_destination_rate_delay=0.5s # postfix reload The queue manager logs a fatal error: May 4 14:02:01 wzv postfix/qmgr[2216906]: fatal: parameter default_destination_rate_delay: bad time value or unit: 0.5s For some reason this integer constaint is not enforced for smtp_destination_rate_delay, relay_destination_rate_delay, and so on, meaning that the parameter value may not be used. Investigating. Wietse _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
