On 20 Dec 2018, at 06:46, Kai Schaetzl wrote:
> Using Sorbs is dangerous, anyway, we abandoned it years ago. If you want
> to use it then use it in the way it is intended for weighted RBLs. e.g. do
> not use it as the sole source of blocking.
I keep parring down my list and am considering going
Stefan Bauer wrote on Wed, 19 Dec 2018 21:10:10 +0100:
> the threshold is at default, so 1.
This may not be part of your problem, but using a threshold of 1 and then
using this weighting scheme is nonsense:
postscreen_dnsbl_sites = zen.spamhaus.org*2 bl.spamcop.net*1
b.barracudacentral.org*1 dn
Stefan Bauer:
> the threshold is at default, so 1.
>
> but the dns timeout, Wietse mentioned, might be the real cause. gonna check
> manuals, if this is configurable.
postscreen will wait for DNS lookup results until the postscreen_greet_wait
timer expires.
postscreen_greet_wait = ${stress?{
the threshold is at default, so 1.
but the dns timeout, Wietse mentioned, might be the real cause. gonna check
manuals, if this is configurable.
Thank you.
Am Mittwoch, 19. Dezember 2018 schrieb Viktor Dukhovni <
postfix-us...@dukhovni.org>:
> On Wed, Dec 19, 2018 at 02:00:34PM +0100, Stefan Bau
On Wed, Dec 19, 2018 at 02:00:34PM +0100, Stefan Bauer wrote:
> Dec 19 13:04:36 mx1 postfix/postscreen[4770]: CONNECT from
> [209.85.166.196]:52168 to [public-ip]:25
> Dec 19 13:04:42 mx1 postfix/dnsblog[4774]: addr 209.85.166.196 listed by
> domain dnsbl.sorbs.net as 127.0.0.6
> Dec 19 13:04:42 m
On Wed, Dec 19, 2018 at 02:58:00PM +, Dominic Raferd wrote:
> This might help OP identify any non-default postscreen settings (kudos:
> Viktor) -
>
> LC_ALL=C join --check-order <(postconf -n) <(postconf -d | sed
> 's/=/(default:/; s/$/)/')|grep ^postscreen_
Thanks, but may be worth noting t
Stefan Bauer:
> Hi,
>
> Dec 19 13:04:36 mx1 postfix/postscreen[4770]: CONNECT from
> [209.85.166.196]:52168 to [public-ip]:25
> Dec 19 13:04:42 mx1 postfix/dnsblog[4774]: addr 209.85.166.196 listed by
> domain dnsbl.sorbs.net as 127.0.0.6
It took 6s for dnsblog to figure out that the client is li
On Wed, 19 Dec 2018 at 14:51, Matus UHLAR - fantomas
wrote:
> On 19.12.18 14:00, Stefan Bauer wrote:
> >Dec 19 13:04:36 mx1 postfix/postscreen[4770]: CONNECT from
> >[209.85.166.196]:52168 to [public-ip]:25
> >Dec 19 13:04:42 mx1 postfix/dnsblog[4774]: addr 209.85.166.196 listed by
> >domain dnsb
On 19.12.18 14:00, Stefan Bauer wrote:
Dec 19 13:04:36 mx1 postfix/postscreen[4770]: CONNECT from
[209.85.166.196]:52168 to [public-ip]:25
Dec 19 13:04:42 mx1 postfix/dnsblog[4774]: addr 209.85.166.196 listed by
domain dnsbl.sorbs.net as 127.0.0.6
Dec 19 13:04:42 mx1 postfix/postscreen[4770]: PAS
Hi, I don’t know the answer to your question but from this site
http://www.sorbs.net/using.shtml
it looks like the IP 209.85.166.196 seems to have tripped one of these :
new.spam.dnsbl.sorbs.net127.0.0.6
recent.spam.dnsbl.sorbs.net127.0.0.6
old.spam.dnsbl.sorbs.net127.0.0.6
Hai,
recent.spam.dnsbl.sorbs.net = 127.0.0.6
and you gave it 1 point.
whats the postscreen_dnsbl_threshold set at ?
I'll bet thats set higher than 1.
Greetz,
Louis
Van: cubew...@googlemail.com [mailto:owner-postfix-us...@postfix.org]
Namens Ste
11 matches
Mail list logo
