On Thu, Jan 28, 2010 at 06:39:34PM +0100, Stefan Foerster wrote:
> > Only needed when restoring from backups, copying queue files, ... Not
> > needed when mounting a filesystem.
>
> I think the manpage for postsuper recommends executing it at least
> once before starting up Postfix. Can it do any harm in this specific
> scenario?
Not necessary unless you've disturbed the queue files. "postfix start"
already runs it once.
> One last thing: If the clocks are perfectly synchronized and the
> takeover didn't happen immediately but e.g. after 60 minutes
> (virtualized system, dynamic resource/node allocation), it could
> happen that the deferred queue holds a large number of messages which
> are due for a delivery retry. Or, to quote QSHAPE_README:
>
> ,----
> | When a host with lots of deferred mail is down for some time, it is
> | possible for the entire deferred queue to reach its retry time
> | simultaneously. This can lead to a very full active queue once the
> | host comes back up. The phenomenon can repeat approximately every
> | maximal_backoff_time seconds if the messages are again deferred after
> | a brief burst of congestion.
> `----
>
> If the node doesn't have to process any new incoming mail, will qmgr
> be able to handle six digit deferred queues?
So long as you just drain this queue, and don't take in any new mail,
the large deferred queue size is harmless. I'd recommend turning off
"smtpd" until the queue drains, and to let uncongested peer MX hosts
handle fresh mail.
--
Viktor.
P.S. Morgan Stanley is looking for a New York City based, Senior Unix
system/email administrator to architect and sustain our perimeter email
environment. If you are interested, please drop me a note.
