Milter-greylist

On Fri, Nov 12, 2004 at 04:51:08PM +0100, manu@... wrote:
> >       Of course not.  ACL would be interpreted the same way in normal or
> > in test mode with the exception of the default action.
> 
> Well my idea is to keep the test mode working as is so that configs
> don't get broken at upgrade time, but to deprecate it, because the ACL
> setup will allow the same setup with a much more cleaner config. 

	Yes.  Test mode will not be useful any more when ACL are used
by everybody.

> I was raising the concern of supporting the old syntax and test mode
> with the new scheme. You'll have to "emulate" ACL with the older
> keywords. The configuration parser will have to do this conversion while
> loading the config:
> 
> addr X          ->      acl whitelist addr X
> domain X        ->      acl whitelist domain X
> from X          ->      acl whitelist from X
> rcpt X          ->      acl whitelist rcpt X   if not testmode
> rcpt X          ->      acl greylist rcpt X    if testmode      

	Yep.  This is exactly how I intend to handle the current keywords.

> The result of using testmode and the acl keywords at the same time
> should probably be left unspecified: just don't do it, it's not
> supported with the new ACL syntax.

	Well, test mode could still be used to specify the default
b\ufffdhaviour.  In normal mode, the ACL can be implicitly terminated by:
acl greylist default
while test mode will change this implicit last rule to:
acl whitelist default

	IMO, we have to keep test mode until the current syntax is phased
out because the meaning of the rcpt keyword depends on it and we have to
handle the test mode to emulate rcpt with the ACL scheme.

		R\ufffdmy