Purushotham Nayak:
> Thanks so much for the information! Also, tempfail does work correctly. But
> couple of questions though,
>
> 1. When default action is tempfail and the milter is unavailable, smtpd
> sends 451 (Requested action aborted: error in processing). Wonder if there
> is a way to
Combining milter restart with postfix reload sounds like a good suggestion.
Our milter restarts due on rare occasions due to upstream changes, but
combining it with postfix reload or postfix -> milter seems good solution.
Thanks very much for your input.
Thanks,
Purush
On Thu, May 11, 2017 at
> On May 11, 2017, at 12:16 PM, Purushotham Nayak
> wrote:
>
> 2. I noticed that when the milter application exits, it sends FIN to smtpd
> but smtpd keeps the connection open in the CLOSE_WAIT state. When the client
> sends something new and smptd tries to
Thanks so much for the information! Also, tempfail does work correctly. But
couple of questions though,
1. When default action is tempfail and the milter is unavailable, smtpd
sends 451 (Requested action aborted: error in processing). Wonder if there
is a way to send 421 (Service not available,
Purushotham Nayak:
> Hi All,
>
> I have a question about the correct way to restart a milter application.
>
> I'm using postfix 2.6.6 with a milter application that was built using
> sendmail's libmilter (8.14.7). The problem I'm having is when I need to
> restart the milter application (due to
Hi All,
I have a question about the correct way to restart a milter application.
I'm using postfix 2.6.6 with a milter application that was built using
sendmail's libmilter (8.14.7). The problem I'm having is when I need to
restart the milter application (due to a config change for example), I