Re: permit after all

2016-10-22 Thread Paul van der Vlis
Op 22-10-16 om 19:49 schreef L.P.H. van Belle: > paul, check if there are messages still in queue. I've cleaned the queue every minute using crontab, removing the mail from that specific recipient. > i had a comprimized account also and same as you it didnt stop. it did > after clearing up the q

Re: permit after all

2016-10-22 Thread L . P . H . van Belle
paul, check if there are messages still in queue.  i had a comprimized account also and same as you it didnt stop. it did after clearing up the queue list. the user in question has used its email and pass om a website which was   omprimized, at least thats what i think.  i my case i allow my

Re: permit after all

2016-10-22 Thread Bill Cole
On 22 Oct 2016, at 8:54, /dev/rob0 wrote: Should "closing 'permit' lines" be removed from live configurations? Of course not. That is how it works. If not specified as the OP did it, the ending value of any restriction stage is "permit". If not, mail would not be accepted at all. Not exac

Re: permit after all

2016-10-22 Thread /dev/rob0
> > reject_rbl_client bl.spamcop.net, This is an odd choice which can lead to a lot of woe. Spamcop is an automated list which often is too aggressive in blocking. > > > reject_rbl_client zen.spamhaus.org, > > > reject_rbl_client ix.dnsbl.manitu.net, I'm not per

permit after all WAS: Open relay

2016-10-22 Thread Geert Stappers
pipelining, > > reject_unauth_destination, > > check_policy_service unix:private/shadelist, > > reject_rbl_client bl.spamcop.net, > > reject_rbl_client zen.spamhaus.org, > > reject_rbl_client ix.dnsbl.manitu.net, > > permit > > permit after