At 05:39 PM 3/9/2005, manu@... wrote: >This means the default is broken. Any info with -l? OK, I did some more checking, the default is definitely broken with the regex ACL rules in place.. I commented out the acl debug requirement for the syslog message at the bottom of acl_filter, and added another debug for the "default" case. Without: Mar 9 17:58:58 xanadu milter-greylist: acl_filter hostname = "postfixprim.ofir.com" Mar 9 17:58:58 xanadu milter-greylist: acl_filter loop bottom with check==0 && match Mar 9 17:58:58 xanadu milter-greylist: Mail from=<>, rcpt=<xxxxxx@...>, addr=193.0.243.235 is matched by entry acl whitelist default With: Mar 9 17:57:33 xanadu milter-greylist: acl_filter hostname = "209-232-74-254.kingschools.com" Mar 9 17:57:33 xanadu milter-greylist: acl_filter using default. EXF_DEFAULT 4 retval 5 testmode 0 Mar 9 17:57:33 xanadu milter-greylist: j29MvW2X032628: addr 209.232.74.254 from <> to <xxxxxxxxx@...> delayed for 00:01:00 So it would appear that the regex domain acl's are clobbering the acl whitelist default somehow and it's falling into the default case.
Message
Re: [milter-greylist] 2.0b2 - domain acl's not working?
2005-03-09 by Matt Kettler
Attachments
- No local attachments were found for this message.