Roland de Lepper:
> The connection between Postfix and the archive is over SMTP.
>
> In my example with the smtpd_milter, will the email also go to the hold
> queue if only one archive connection is down?
Wietse:
> That depends on how the archive receive its mail. Does POSTFIX
> send the mail to the archive, or the MILTER?
Roland de Lepper:
> As stated in the manual of mailarchiva, it says:
> MailArchiva has an embedded Milter server that by default listens on port
> 8092. The instructions below configure Postfix to forward milter traffic to
> MailArchiva's milter server.
>
> So the MILTER sends the mail to the archive.
In that case, to archive all mail you need "milter_default_action
= tempfail". Since the Milter is a before-queue filter, Mail cannot
be delivered while the archive is unavailable.
If you want to deliver mail while the archive is down, use an
after-queue filtering approach, or an approach based on sender_bcc_maps
or recipient_bcc_maps.
Wietse
If the MILTER sends to the archive (I cannot verify that), then no
mail will be archived when the MILTER is unavailable.
Specifically:
1) With "milter_default_action = tempfail" mail is not archived
when the Milter or archive is unavailable. Mail is not delivered
to the recipient(s). The remote SMTP client receives a 4XX SMTP
reply code. The remote SMTP client retries until the MILTER becomes
available or until the mail is too old.
2) With "milter_default_action = accept" mail is not archived when
the Milter or archive is unavailable. Mail is delivered to the
recipient(s). The remote SMTP client receives a 2XX SMTP reply code.
3) With "milter_default_action = quarantine" mail is not archived
when the Milter or archive is unavailable. Mail is stored in the
"hold" queue. The remote SMTP client receives a 2XX SMTP reply code.
Obviously this option is the worst of all.
Wietse
