"not" keyword no more accepted in compound ACLs ?
2009-06-13 by Benoit Branciard
In our current production milter-greylist config (a 20080319 snapshot - basically a 4.0 version plus SPF status selection), we have several "compound" ACLs with positive and/or negative tests, like these examples: acl blacklist from aw-fraud@... not domain /paypal/ msg "Phishing fraud refused" acl blacklist dnsrbl "SBL+XBL" spf pass spf self msg "Unauthorized client (XBL,badSPF), please use an official mail relay" These days I downloaded and built the 4.2.2 version, installed it, restarted, and got syntax errors on my (unmodified and previously accepted) greylist.conf: config error at line 203: syntax error Digging somewhat further, it appears that the new milter-greylist is choking on the "not" keyword of an ACL statement, excepted when it is applied to the first clause. So acl blacklist not clause1 clause2 is accepted, whereas acl blacklist clause2 not clause1 is considered invalid. I compiled and verified this behaviour is still present in today's CVS (4.3.2+). Did some of the new features broke the ACL parser ? -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve.