Nikolai Lusan <[email protected]> wrote: >> One thing I did learn from this is that it would help if the PolicyD >> messages were easily distinguishable from Postfix messages ! > > I don't know what your setup is doing, but on my > system /var/log/mail.log has easily distinguishable log messages - they > have "cbpolicyd" prepended to them, with a timestamp and the hostname :)
PolicyD wasn't logging anything to syslog for this - though it does for quota updates. The only thing appearing in the mail logs was from Postfix. Interestingly, when I added warn_if_reject before the policy server restriction, I then started getting more info logged from PolicyD (I think, it's late now, and my eyes are going square from several hours staring at logs earlier in the day !). Actually, I think it's just that the helo module doesn't log anything to syslog - so when that module rejects the message, nothing is logged other than the reject line from Postfix. If the helo module passes the message, then the other modules (greylisting, quotas) do log stuff to syslog. it was a while before I thought to look in the separate cbpolicyd log. Silly me ! _______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
