I'm just wondering if anyone has a good suggestion for how to deal with
workstations, setup with a $relayhost for all outbound mail, which
occasionally get unplugged from the network or otherwise taken offline.
While this doesn't happen to our machines a lot, it does cause some
annoyance when a machine gets unplugged for a long time and a flood of
messages (and the resulting bounces) come through.

We don't mind getting the mail sent while the system is offline, but
(in cases where the sender is "root", which also forwards offsite), we
don't want to get all the bouncse. $notify_classes is set to the
default, but since most of the system messages (cron, etc.) come "from"
root, there's still a single bounce when a message can't be sent.

I could just set $maximal_queue_lifetime and $bounce_queue_lifetime to
really short values, but I'd rather preserve the original mail.

My other thought was to follow the suggestions in
http://www.postfix.org/STANDARD_CONFIGURATION_README.html#dialup

However, since there's no dialup script, I'd probably have to write a
cron job that flushes the queue every minute or two, which seems dumb.

I guess another approach would be to have a cron job that changes
$defer_transports and reloads Postfix if the network is down (and
reverses it when the network comes back up).

Anyone have a better / less kludgy approach to this problem? Am I just
thinking of it all wrong?

Disabling DNS lookups doesn't change anything, does it?

w

Reply via email to