On 2018-03-20 (04:56 MDT), Uwe Schindler wrote:
>
> why they not simply blocked the Hetzner recursive name servers instead of
> everything
I would have to assume bad behavior on Hetzner's part.
--
'And stars don't care what you wish, and magic don't make things
Hi Uwe!
On Fr, Mär 16, 2018 at 12:18:10 +0100, Uwe Schindler wrote:
Did you solve this problem in the meantime? Unfortunately this also
Yes, I was contaced by a key account manager of Spamhaus. I got a free
datafeed query service key.
Maybe you could contact Spamhaus to tell them about
; Sent: Tuesday, March 20, 2018 10:59 AM
> To: Uwe Schindler <uschind...@apache.org>
> Cc: users@spamassassin.apache.org; 'Alex Lasoriti' <lasor...@spamteq.com>
> Subject: Re: skipping nameserver '0.ns.spamhaus.org' because it is a CNAME
>
> Hi Uwe!
>
> On Fr, Mär
Hi Stephan,
> I see the problems as well in my postfix logs (I’m a Hetzner custom=r as
> well):
> warning: dnsblog_query: lookup error for DNS query
> 36.142.70.194.zen.spamha=s.org: Host or domain name not found. Name
> service error for name=36.142=2E70.194.zen.spamhaus.org type=A: Host not
>
Hi Alex!
On So, Jan 14, 2018 at 07:30:36 +, Alex Lasoriti wrote:
On 2018-01-14 17:20, Ian Zimmerman wrote:
I am getting these, too. With other news in the last few weeks, are
things falling apart at spamhaus?
Not that I am aware of :) The infrastructure keeps consolidating
and things
On 2018-01-14 19:30, Alex Lasoriti wrote:
> > things falling apart at spamhaus?
>
> Not that I am aware of :) The infrastructure keeps consolidating
> and things are getting stronger and stronger! What other news are you
> referring to ?
I probably had lodged in my memory (what remains of it)
On Sun, 2018-01-14 at 19:30 +, Alex Lasoriti wrote:
> On 2018-01-14 17:20, Ian Zimmerman wrote:
> >
> > On 2018-01-14 17:07, Per Jessen wrote:
> >
> > >
> > > AFAIK, bind does not accept NS records with CNAMEs, only A or
> > >
> > > records. It looks like spamhaus updated their
Thanks Alex. I was just looking for a good contact!
Regards,
KAM
On January 14, 2018 2:30:36 PM EST, Alex Lasoriti wrote:
>On 2018-01-14 17:20, Ian Zimmerman wrote:
>> On 2018-01-14 17:07, Per Jessen wrote:
>>
>> > AFAIK, bind does not accept NS records with CNAMEs, only
On 2018-01-14 17:20, Ian Zimmerman wrote:
> On 2018-01-14 17:07, Per Jessen wrote:
>
> > AFAIK, bind does not accept NS records with CNAMEs, only A or
> > records. It looks like spamhaus updated their nameserver config and
> > added cloudflare by way of CNAME.
Hi all,
this was a "sunday
On 14 Jan 2018, at 11:07 (-0500), Per Jessen wrote:
Chris wrote:
I started seeing this yesterday evening -
https://pastebin.com/Q01t63uf AFAICT it's happening on every message
that is processed by SA. This is:
spamassassin -V
SpamAssassin version 3.4.1
running on Perl version 5.22.1
Any
On 2018-01-14 17:07, Per Jessen wrote:
> AFAIK, bind does not accept NS records with CNAMEs, only A or
> records. It looks like spamhaus updated their nameserver config and
> added cloudflare by way of CNAME.
I am getting these, too. With other news in the last few weeks, are
things
Chris wrote:
> I started seeing this yesterday evening -
> https://pastebin.com/Q01t63uf AFAICT it's happening on every message
> that is processed by SA. This is:
>
> spamassassin -V
> SpamAssassin version 3.4.1
> running on Perl version 5.22.1
>
> Any ideas?
AFAIK, bind does not accept NS
On Sun, 2018-01-14 at 09:07 -0600, Chris wrote:
> I started seeing this yesterday evening
> - https://pastebin.com/Q01t63uf
>
I saw the same thing in last night's logwatch report and its being
reported in today's 'message' log. According to my logs it started here
at Jan 13 22:41:03 and is still
13 matches
Mail list logo