You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Larry Rosenman <le...@lerctr.org> on 2020/02/13 14:53:30 UTC
3.4.4: Lots of DNS no callback messages (FreeBSD)
Greetings,
I upgraded to SpamAssassin 3.4.4 last night, and ever since, I'm
seeing a ton of:
<22>1 2020-02-13T08:51:17.000000-06:00 thebighonker.lerctr.org spamd
26116 - - dns: no callback for id
62451/IN/TXT/d.1.0.0.0.5.0.0.0.0.0.0.0.0.0.0.c.6.0.6.1.0.0.0.1.c.1.0.0.1.6.2.bl.spamcop.net,
ignored, packet on next debug line
<22>1 2020-02-13T08:51:17.000000-06:00 thebighonker.lerctr.org spamd
26116 - - dns: no likely matching queries for id 62451
What do I need to do to figure out why thes are now failing. It seems
to happen for EVERY lookup.
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
Re: 3.4.4: Lots of DNS no callback messages (FreeBSD)
Posted by Henrik K <he...@hege.li>.
On Fri, Feb 14, 2020 at 11:25:40AM -0600, Larry Rosenman wrote:
>
> So these are PROBABLY because of ShortCircuit?
It's 100% from usage of Shortcircuit. Trunk/4.0 has all this fixed.
Re: 3.4.4: Lots of DNS no callback messages (FreeBSD)
Posted by Larry Rosenman <le...@lerctr.org>.
On 02/14/2020 3:56 am, Henrik K wrote:
> On Thu, Feb 13, 2020 at 08:53:30AM -0600, Larry Rosenman wrote:
>> Greetings,
>> I upgraded to SpamAssassin 3.4.4 last night, and ever since, I'm
>> seeing a
>> ton of:
>>
>> <22>1 2020-02-13T08:51:17.000000-06:00 thebighonker.lerctr.org spamd
>> 26116 -
>> - dns: no callback for id
>> 62451/IN/TXT/d.1.0.0.0.5.0.0.0.0.0.0.0.0.0.0.c.6.0.6.1.0.0.0.1.c.1.0.0.1.6.2.bl.spamcop.net,
>> ignored, packet on next debug line
>> <22>1 2020-02-13T08:51:17.000000-06:00 thebighonker.lerctr.org spamd
>> 26116 -
>> - dns: no likely matching queries for id 62451
>>
>> What do I need to do to figure out why thes are now failing. It seems
>> to
>> happen for EVERY lookup.
>
> Are you using lots of shortcircuiting?
>
> Have you changed rbl_timeout setting?
>
> Is it always IPv6 related like that?
>
> It's just seeing some stale DNS responses from previous scans, so
> either you
> are aborting scans with shortcircuiting or rbl_timeout is too small to
> wait
> for all responses, or generally you have some problem receiving DNS
> responses in time.
>
> Anyway it's just a cosmetic message, in trunk this stale "problem" is
> fixed.
> If you can't fix the DNS delays with higher rbl_timeout etc, feel free
> to
> change the code to dbg() in DnsResolver.pm.
>
> info("dns: no callback for id $id, ignored, packet on next debug
> line");
I do have short circuits in place, and it's ALL types of requests.
The DNS server is fine as it's local to the box and responsive.
So these are PROBABLY because of ShortCircuit?
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106
Re: 3.4.4: Lots of DNS no callback messages (FreeBSD)
Posted by Henrik K <he...@hege.li>.
On Thu, Feb 13, 2020 at 08:53:30AM -0600, Larry Rosenman wrote:
> Greetings,
> I upgraded to SpamAssassin 3.4.4 last night, and ever since, I'm seeing a
> ton of:
>
> <22>1 2020-02-13T08:51:17.000000-06:00 thebighonker.lerctr.org spamd 26116 -
> - dns: no callback for id 62451/IN/TXT/d.1.0.0.0.5.0.0.0.0.0.0.0.0.0.0.c.6.0.6.1.0.0.0.1.c.1.0.0.1.6.2.bl.spamcop.net,
> ignored, packet on next debug line
> <22>1 2020-02-13T08:51:17.000000-06:00 thebighonker.lerctr.org spamd 26116 -
> - dns: no likely matching queries for id 62451
>
> What do I need to do to figure out why thes are now failing. It seems to
> happen for EVERY lookup.
Are you using lots of shortcircuiting?
Have you changed rbl_timeout setting?
Is it always IPv6 related like that?
It's just seeing some stale DNS responses from previous scans, so either you
are aborting scans with shortcircuiting or rbl_timeout is too small to wait
for all responses, or generally you have some problem receiving DNS
responses in time.
Anyway it's just a cosmetic message, in trunk this stale "problem" is fixed.
If you can't fix the DNS delays with higher rbl_timeout etc, feel free to
change the code to dbg() in DnsResolver.pm.
info("dns: no callback for id $id, ignored, packet on next debug line");