Am 02.06.2016 um 17:32 schrieb John Hardin:
On Thu, 2 Jun 2016, Antony Stone wrote:On Thursday 02 June 2016 at 13:16:57, Martin Gregorie wrote: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.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).The problem I see with this, though, is that you have to know that URIBL_BLOCKED is something sinister, and needs to be flagged as a problem, to bother doing this.You get that if URIBL_BLOCKED hits on a ham and you look at the rule descriptions on that message
well, if people would look and doing a clean work they would configure their machines proper long before connect them to the internet :-)
sadly a large amount of servers is managed by people who don't look and care and a large amount of inbound spam is caused by that fact....
mailadmin is a fulltimejob with responsibility, but explain them somebody who can type "yum install spamassassin postfix" and from the moment on it accepts somehow mail he starts to call himself mailadmin
signature.asc
Description: OpenPGP digital signature
