Contents |
 |
|
|
|
 |
|
| |
The design of the
flush(8) server and of the flush queue
introduce a few limitations that should not be an issue unless you
want to turn on fast ETRN service for every possible destination.
-
The
flush(8) daemon maintains per-destination logfiles
with queue file names. When a request to "deliver mail now" arrives,
Postfix will attempt to deliver all recipients in the queue files
that have mail for the destination in question. This does not
perform well when queue files have recipients in many different
domains.
-
The
flush(8) daemon maintains per-destination logfiles
only for destinations listed with $
fast_flush_domains. With other
destinations it not possible to trigger delivery with "sendmail
-qRdestination" or, with Postfix version 1.1 and later,
"postqueue -sdestination".
-
Up to and including early versions of Postfix version 2.1,
the "fast flush" service may not deliver some messages if the
request to "deliver mail now" is received while a
deferred queue
scan is already in progress. The reason is that the queue manager
does not ignore the volatile in-memory list of dead domains, and
the list of message delivery transports specified with the
defer_transports configuration parameter.
|
|
|
