Hai Florian, 

No, Thats is due my setup with the mailscanner antispam behind it.

Just give those sites a good read, and the adjust the config to your needs. 

Running a caching dns on that server helps dns queries. 
Extra to that, install fail2ban and add postfix-dnsbl.conf
With filter : 
failregex = NOQUEUE: reject: RCPT from (.*)\[<HOST>\]:([0-9]{4,5}:)? 550 5.7.1 
Service unavailable; client \[(.*)\] blocked 

And this all helpt my traffic down about 5-10%. Not much but still. 


Greetz, 

Louis




> -----Oorspronkelijk bericht-----
> Van: flo...@floppy.org [mailto:owner-postfix-us...@postfix.org] Namens
> Florian Piekert
> Verzonden: woensdag 16 november 2016 14:39
> Aan: L.P.H. van Belle; postfix-users@postfix.org
> Onderwerp: Re: regexp for allowing helo host
> 
> Am 16.11.2016 um 14:35 schrieb L.P.H. van Belle:
> 
> I have those entries in the master.cf, except it's having the "n" for
> chrooted as well (should be transparent)...
> 
> I assume it is due to the sheer NUMBER of dnsbl sites to query
> simultaneously?
> 
> > Ah yes,
> >
> > In master.cf  adust these.
> >
> > smtp      inet  n       -       -       -       1       postscreen
> > smtpd     pass  -       -       -       -       -       smtpd
> > dnsblog   unix  -       -       -       -       0       dnsblog
> >
> >
> >
> >> -----Oorspronkelijk bericht-----
> >> Van: flo...@floppy.org [mailto:owner-postfix-us...@postfix.org] Namens
> >> Florian Piekert
> >> Verzonden: woensdag 16 november 2016 14:27
> >> Aan: L.P.H. van Belle; postfix-users@postfix.org
> >> Onderwerp: Re: regexp for allowing helo host
> >>
> >> Am 16.11.2016 um 13:59 schrieb L.P.H. van Belle:
> >>
> >> After going from
> >> postscreen_dnsbl_sites =
> >>   zen.spamhaus.org*2,
> >>   bl.mailspike.net,
> >>   bl.spamcop.net,
> >>   b.barracudacentral.org,
> >>   swl.spamhaus.org*-2
> >> to
> >>> postscreen_dnsbl_sites =
> >>>         b.barracudacentral.org*4
> >>>         bad.psky.me*4
> >>>         zen.spamhaus.org*4
> >>>         dnsbl.cobion.com*2
> >>>         bl.spameatingmonkey.net*2
> >>>         fresh.spameatingmonkey.net*2
> >>>         dnsbl.anonmails.de*2
> >>>         dnsbl.kempt.net*1
> >>>         dnsbl.inps.de*2
> >>>         bl.spamcop.net*2
> >>>         dnsbl.sorbs.net*1
> >>>         spam.dnsbl.sorbs.net*2
> >>>         psbl.surriel.com*2
> >>>         bl.mailspike.net*2
> >>>         rep.mailspike.net=127.0.0.[13;14]*1
> >>>         bl.suomispam.net*2
> >>>         bl.blocklist.de*2
> >>>         ix.dnsbl.manitu.net*2
> >>>         dnsbl-2.uceprotect.net
> >>>         hostkarma.junkemailfilter.com=127.0.0.3
> >>>         hostkarma.junkemailfilter.com=127.0.0.[2;4]*2
> >>>         # whitelists
> >>>         swl.spamhaus.org*-4
> >>>         list.dnswl.org=127.0.[0..255].[2;3]*-1
> >>>         rep.mailspike.net=127.0.0.[17;18]*-1
> >>>         rep.mailspike.net=127.0.0.[19;20]*-2
> >>>         hostkarma.junkemailfilter.com=127.0.0.1*-1
> >>
> >> I am rewarded with
> >> Nov 16 14:20:35 blueberry postfix/postscreen[18461]: warning:
> >> psc_dnsbl_request: connect to private/dnsblog service: Resource
> >> temporarily
> >> unavailable
> >> Nov 16 14:20:35 blueberry postfix/postscreen[18461]: message repeated 7
> >> times: [ warning: psc_dnsbl_request: connect to private/dnsblog
> service:
> >> Resource temporarily unavailable]
> >>
> >> Any idea?!
> >>
> >> I stopped pf, removed the postscreen_cache.db file just in case,
> restarted
> >> pf. Still getting those messages...
> 
> 
> 
> --
> 
> Florian Piekert, PMP
> flo...@floppy.org
> 
> Spargelweg 5                                Telephone+Fax: +49-179-
> 3928582
> 38179 Schwülper-Walle/Germany
> 
> ==========================================================================
> =
> Note:  this message was  send by me *only* if the  eMail message contains
> a
> correct pgp signature corresponding to my address at  flo...@floppy.org.
> Do
> you need my  PGP  public key? Check out http://www.floppy.org or send me
> an
> email with  the subject "send pgp public key" to  this address of
> mine.Thx!
> 
> 


Reply via email to