Patrick Ben Koetter:
> * Wietse Venema <postfix-users@postfix.org>:
> > Patrick Ben Koetter:
> > > I know I can put a transport to hold if I specify its name in
> > > $defer_transports. This requires "postfix reload" to put it to effect
> > > immediately and issuing the reload will requeue all mail - not what I
> > > want if
> > > I can avoid it.
> >
> > defer_transports is implemented by the queue manager. This is a
> > persistent process. It will not restart voluntarily.
> >
> > > Could I specify hold: in my transport map? AFAIK Postfix processes will
> > > not
> > > the map has changed and re-read it and the hold: would fade in quickly.
> >
> > Last time I looked, hold is not a message delivery transport.
> >
> > You may be surprised to learn that defer_transports is implemented
> > by sending mail to the retry(8) delivery agent (Postfix 2.4 and
> > later). If you specify retry: in a transport map then it will have
> > the same effect.
>
> Not quite - at least from what I learned from testing. It holds a message for
> a while, but then I observed Postfix releases the message after a short while.
> Is that time controlled by $transport_retry_time (?). If it is, can I set it
> to unlimited e.g. $transport_retry_time = 0. I didn't play with that yet...
The mail remains deferred until someone flushes the queue.
Wietse
