Package: python3-spf-engine
Version: 2.9.0-4
Severity: normal
Dear Maintainer,
When policyd-spf from postfix-policyd-spf-python times out during
a DNS request a Python traceback is printed:
Sep 10 07:11:18 bilbo policyd-spf[21475]: File "/usr/bin/policyd-spf", line
11, in <module>#012 load_entry_point('spf-engine==2.9.0', 'console_scripts',
'policyd-spf')()
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/spf_engine/policyd_spf.py", line 102, in
main#012 peruser, peruserconfigData)
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/spf_engine/__init__.py", line 545, in
_spfcheck#012 res = heloquery.check()
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/spf.py", line 591, in check#012 spf =
self.dns_spf(self.d)
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/spf.py", line 1160, in dns_spf#012 a = [t
for t in self.dns_txt(domain) if RE_SPF.match(t)]
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/spf.py", line 1210, in dns_txt#012 dns_list
= self.dns(domainname, rr,ignore_void=ignore_void)
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/spf.py", line 1354, in dns#012 for k, v in
DNSLookup(name, qtype, self.strict, timeout):
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/spf.py", line 131, in DNSLookup_dnspython#012
answers = dns.resolver.query(name, qtype)
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/dns/resolver.py", line 1102, in query#012
lifetime)
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/dns/resolver.py", line 992, in query#012
timeout = self._compute_timeout(start, lifetime)
Sep 10 07:11:18 bilbo policyd-spf[21475]: File
"/usr/lib/python3/dist-packages/dns/resolver.py", line 799, in
_compute_timeout#012 raise Timeout(timeout=duration)
Sep 10 07:11:18 bilbo policyd-spf[21475]: dns.exception.Timeout: The DNS
operation timed out after 30.000346899032593 seconds
I would expect a warning to be logged but not a Python traceback. I am
guessing that spf_engine should be catching the exception.
Perhaps this should be minor instead of normal, but this makes
monitoring logs via logcheck much harder because the stack traces
dominate the logs.
Thanks...
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable'), (1,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages python3-spf-engine depends on:
ii python3 3.7.3-1
ii python3-authres 1.2.0-1
ii python3-spf 2.0.13-1
python3-spf-engine recommends no packages.
python3-spf-engine suggests no packages.
-- no debconf information
