|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Wietse Venema (wietse
porcupine.org)
Date: Fri Jul 23 2010 - 07:37:18 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mark Goodge:
> OK, I'm sure this is in the documentation somewhere, but my brain isn't
> working this morning and I need to get a fix for this fairly quickly, so
> I'm asking here instead :-)
>
> Anyway, I currently have a situation where mail is currently received by
> machine A, which then forwards it to machine B. (B is inside a firewall,
> A is the public-facing mail server and is the only external system which
> has access to B on port 25). Last night, the internal network on which B
> resides suffered a catastrophic failure and B is, therefore, not
> accepting mail from A. It's likely that it won't be accepting mail again
> until after the weekend.
>
> What I need to do is configure A so that mail destined for B is stored
> indefinitely (well, for a few days, at least) without generating NDRs or
> attempted delivery notifications, so that when B comes back online all
> the stored mail can be delivered and none of the senders will have
> received any bounces or delay notifications.
Consider temporarily increasing the bounce_queue_lifetime and
maximal_queue_lifetime.
This requires "postfix reload" as the life times are implemented
in the queue manager which normally runs forever.
Wietse
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]