On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote: > > > > > Therefore I agree that there could be better way of noticing admins > of a [URIBL_BLOCKED] issue. > There's one obvious way of doing this for very little cost & effort: use logwatch.
If you're a pukka sysadmin you'll be reading the nightly logwatch report as you drink your first coffee at work, so all that's needed is to create and install a logwatch service that scans /var/log/maillog for lines containing "URIBL_BLOCKED" - this involves a two line config file and a scanner (a few lines of Perl). Then install and forget - add it to the SA package: if URIBL blocks the sysadmin will know about it the next day. Martin
