Roland de Lepper:
> Hi Wietse,
>
> Thanks for the reply.
>
> What about milter_default_action = quarantine ?
As documented, this leaves the message in the "hold" queue. If the
Milter should have done something with the message, then those
things will never happen. The message is now in the queue, and the
Milter is a before-queue feature.
If I may ask, is the archive connected over SMTP or over a
propietary protocol?
I think that "defer accepting mail while the archive is down" is
the safest option (i.e. leave it up to the sender to retry).
Everything else requires that the message is queued in Postfix while
the archive is down, for example as in this simplified picture:
network -> smtpd -> queue -> smtp -> smtpd+milter -> queue -> delivery agents
The part with "smtp -> smtpd+milter: would implement an SMTP-based
empty after-queue filter.
Wietse
> regards,
>
> Roland de Lepper
>
>
> On Wed, Oct 23, 2013 at 1:24 PM, Wietse Venema <wie...@porcupine.org> wrote:
>
> > Roland de Lepper:
> > > smtpd_milters = inet:81.x.x.x:8092 inet:217.x.x.x:8092
> > > milter_default_action = tempfail
> > > milter_connect_timeout = 10s
> > >
> > > This works perfectly without any problems. the question raised, what if
> > the
> > > connection between the mailserver and location B is down. Is the email
> >
> > As documented no mail is delivered after Milter failure. The Postfix
> > SMTP server will reply with an error status code (4xx) and the
> > client will have to send the message again.
> >
> > The bad alternative is "milter_default_action = accept", which means
> > that mail will be delivered but not archived.
> >
> > If you want both mail delivered AND mail archived, then you need
> > to use sender_bcc_maps or recipient_bcc_maps to add recipients for
> > archival purposes.
> >
> > Then, Postfix will do the retrying until the message is too old,
> > at which time it will be returned to the sender.
> >
> > Wietse
> >
