>> > It seems the tempfail is from the milter, not from Postfix. Postfix >> > is not in a position to know that the milter is not working as it >> > should, the milter is responding "normally". >> >> That's too bad. I'm surely oversimplifying things but I figured the milter >> would do something like pass a non-zero exit along, which postfix could then >> use to make a decision on the status. > > Postfix isn't executing the milter as a subprocess, they communicate over a > socket. If the milter returns a 4XX verdict, that's normal milter behaviour. > If the milter drops the connection, times out, ... that's a milter failure, > and *then* the Postfix milter_default_action kicks in.
I guess there is a missing feature to configure milter in test mode. In smtpd_xxx_restrictions if you use external policy daemon you can configure warn_if_reject,check_policy_service unix:private/policy, the same for proxy filtering with warn_if_reject, smtpd_proxy_filter=127.0.0.1:21111. I don't have seen similar feature for milter protocol Regards, Sébastien Worldline is a registered trade mark and trading name owned by Worldline through its holding company. This e-mail and the documents attached are confidential and intended solely for the addressee. If you receive this e-mail in error, you are not authorized to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Worldline therefore can accept no liability for any errors or their content. Although Worldline endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Worldline by email.
