On Fri, Jun 12, 2015, at 09:33 PM, Noel Jones wrote:
> I don't intend to insult you, and apologize if you interpreted it
> that way. If you have a question, please ask it.
Thanks. Moving on.
Goal
I don't want to lose mail if the back-end server connection is offline
for an extended period of time.
I want the front-end -- for which Up-time/availability is not a concern
-- to hold it, assuming it's passed available restrictions, and then (re)submit
it to the back-end when then connection's back up.
Problem
That's my understanding of what a store & forward server provides.
With remote recipient verification in the loop, IIUC, it's a PRE-QUEUE
check. If the back-end is offline, the recipient verification, fails and the
email is deferred for subsequent re-delivery.
If the back-end downtime is greater that the sender's max resend
attempt interval -- a value that is out of my control, and I do not know what
is typical for the 'big senders' today -- then the email is lost.
Question
Is it possible to (re)configure postfix such that
(1) I use only remote recipient-verification, with policy == reject
unverified
(2) when the backend is down, if some set of resrictions have already
passed, accept the msg into a (separate?) queue, store indefinitely
(3) when backend is backup, reinject messages for continued processing
and eventual delivery
or, does the use remote recipient verification necessarily mean that messages
will be lost after a sender's redelivery schedule is exceeded?
Or, are there additional options I might consider to achieve the same goal?
