I don't think SORBS was your main problem. The other spamtrap list you are using went offline over 4 years ago:
http://www.dnsbl.com/2013/04/status-of-spamtraptrblspamcom-dead.html You are getting false positive results from that list and should definitely remove it. Even though your logs indicated "blocked using dnsbl.sorbs.net", the spamtrap list above contributed to that score and partly caused it to be blocked. As for using SORBS, they provide detailed return codes which you can use for weighting appropriately in postscreen: http://www.sorbs.net/general/using.shtml Regards, Alan On 9/21/2017 5:20 PM, Gao wrote: > After googling I found that SORBS is notorious. I removed it from my > list. > > Now a new question, for the record already in the cache, how can I > clear it out? > > Thanks in advance. > > Gao > > On 2017-09-21 01:43 PM, Gao wrote: >> I am playing around postscreen and I just saw this in my log: >> >> Sep 21 13:31:39 iota postfix/postscreen[5855]: CONNECT from >> [209.85.192.179]:52393 to [45.62.236.121]:25 >> Sep 21 13:31:40 iota postfix/dnsblog[5857]: addr 209.85.192.179 >> listed by domain dnsbl.sorbs.net as 127.0.0.6 >> Sep 21 13:31:40 iota postfix/dnsblog[5858]: addr 209.85.192.179 >> listed by domain spamtrap.trblspam.com as 185.53.179.6 >> Sep 21 13:31:45 iota postfix/postscreen[5855]: DNSBL rank 2 for >> [209.85.192.179]:52393 >> Sep 21 13:31:45 iota postfix/postscreen[5855]: NOQUEUE: reject: RCPT >> from [209.85.192.179]:52393: 550 5.7.1 Service unavailable; client >> [209.85.192.179] blocked using dnsbl.sorbs.net; >> from=<xx...@gmail.com>, to=<yy...@mydomain.com>, proto=ESMTP, >> helo=<mail-pf0-f179.google.com> >> Sep 21 13:31:45 iota postfix/postscreen[5855]: DISCONNECT >> [209.85.192.179]:52393 >> >> I know this is not the fault of postscreen. My question is which >> black list I should trust? In this case both dnsbl.sorbs.net and >> spamtrap.trblspam.com put Gmail's IP in their BL. >> >> Gao
