ACL hit logging
2014-02-12 by Jim Klimov
Hello all,
I am trying to systematize the messages logged by milter-greylist
so that it would be easier to grep the logs for various causes of
connection permission or denial.
There are a couple of problems I've hit:
1) It seems that the rules are picky about the order of msg, log
and addheader actions - I only see headers actually added in
cases when addheader is the first (and often only) rule,
especially on the "continue" ACLs
2) If the system falls back to the default ACL like this:
acl greylist $score>=0 \
log "MGL-TEMPFAIL: %P{conninfo}: default greylisting action" \
msg "MGL-TEMPFAIL: default greylisting action for %P{conninfo}"
I see the "MGL-TEMPFAIL" entries in both cases of greylisting
as well as when the attempt is old enough to be passed through
(and this is logged on the next line in the log output).
Are there good tricks to verify that the delay timer set for
this particular tuple has expired, so I can log the accepted
messages as such, and then fall through to the default greylister?
Thanks,
//Jim