https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6896
Bug ID: 6896
Summary: URL parser collects also invalid domain names,
resulting in warnings from a DNS resolver
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Hardware: All
OS: All
Status: NEW
Severity: minor
Priority: P2
Component: Libraries
Assignee: [email protected]
Reporter: [email protected]
Classification: Unclassified
Now that the DNS resolver is a bit more picky and chatty about
DNS errors, we can see occasional warnings like these in the log:
dns: new_dns_packet (host=patch-media-webrtc-trunk-src-modules-audio
_device-main-source-linux-latebindingsymboltable_linux.cc.
type=ANY class=IN)
failed: a label in a domain name is longer than 63 bytes
dns: new_dns_packet (domain=sintef..no. type=ANY class=IN) failed:
a domain name contains a null label
dns: new_dns_packet (domain=scientificadvances..co.in. type=A class=IN)
failed: a domain name contains a null label
dns: new_dns_packet (host=.appriver.com. type=A class=IN)
failed: a domain name contains a null label
dns: new_dns_packet (host=Www.masa\276E.COm. type=ANY class=IN)
failed: invalid name
at /usr/local/lib/perl5/site_perl/5.17.7/mach/Net/DNS/Question.pm
line 87.
dns: new_dns_packet (host=www.theasian.asia\303\243\302\200\302
\200\303\243\302\200\302\200\303\243\302\200\302\200ar.theasian.asia.
type=ANY class=IN) failed: invalid name
at /usr/local/lib/perl5/site_perl/5.17.7/mach/Net/DNS/Question.pm
line 80.
The following are similar, but they come from a SPF plugin,
or rather, from its underlying perl module:
dns: new_dns_packet (host=. type=SPF class=IN)
failed: a domain name contains a null label
dns: new_dns_packet (host=. type=TXT class=IN)
failed: a domain name contains a null label
dns: new_dns_packet (domain=. type=SPF class=IN)
failed: a domain name contains a null label
dns: new_dns_packet (domain=. type=TXT class=IN)
failed: a domain name contains a null label
Choices:
- demote the resolver warning into an 'info' debug level message
and not to bother with the cause;
- let the URL parser ignore such invalid domain names,
(or perhaps attempt to sanitize them???)
- those coming from the SPF plugin seem to find such invalid
domain names either in a HELO, or in some published
SPF record, and apparently do not bother checking for
valid syntax
--
You are receiving this mail because:
You are the assignee for the bug.
