[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postfix-users
Subject:    [pfx] Re: warn_if_reject and MILTER
From:       Wietse Venema via Postfix-users <postfix-users () postfix ! org>
Date:       2023-07-11 15:58:42
Message-ID: 4R0lsZ3HsmzJrP1 () spike ! porcupine ! org
[Download RAW message or body]

Wietse Venema via Postfix-users:
> Patrick Ben Koetter via Postfix-users:
> > Greetings,
> > 
> > I was wondering if there's something similar to warn_if_reject when it comes
> > to dry-run  / test-run MILTER applications in Postfix. The documentation on
> > warn_if_reject does not mention MILTERs, which usually means the feature isn't
> > there because otherwise it would be documented, and the per-Milter settings in
> > MILTER_README don't mention something I could use to warn_if_reject either.
> 
> Correct. warn_if_reject operates on smtpd_mumble_restrictions, and
> there is no "check_milter" action in smtpd_mumble_restrictions, for
> the same reason that there is no "check_smtp_syntax" action.
> 
> > Is that something worth to implement or should a dry-run test mode be left to
> > each individual MILTER implementation?
> 
> The Postfix Milter client currently does not implement an override
> mechanism; the 'default_action' is used only when the Milter fails
> to respond.
> 
> It should be possible to specify a 'warn_if_reject=yes' Milter
> attribute that overrides a specific Milter, and a corresponding
> milter_warn_if_reject main.cf configuration parameter that overrides
> all Milters. Much of the effort will be updating documentation.

However, after a Milter rejects  message, it may not expect to
receive further events for that message. Ditto for the underlying
libmilter implementation.

	Wietse
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-leave@postfix.org
[prev in list] [next in list] [prev in thread] [next in thread]