Your message dated Sat, 17 Aug 2019 20:09:37 -0400
with message-id <3507368.9YtVu9T9gX@l5580>
and subject line Re: postfix-policyd-spf-python fails to failover to a
different nameserver
has caused the Debian Bug report #925975,
regarding postfix-policyd-spf-python fails to failover to a different nameserver
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
925975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925975
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postfix-policyd-spf-python
Version: 2.0.1-1
Severity: important
Hello,
Package: postfix-policyd-spf-python
Version: 2.0.1-1
postfix-policyd-spf-python fails to properly failover to a secondary nameserver
in case one of the declared nameservers in /etc/resolv.conf is not responding.
All incoming email is rejected with:
defer_if_permit 4.7.24 Message deferred due to: SPF Temporary Error: DNS
Timeout. Please see http://www.openspf.net/Why?s=[snipped]
related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718547 but python-
dns is not installed, so I'm thinking that the underlying problem is actually
in postfix-policyd-spf-python. No difference with python-dns installed.
The problem goes away if I manually remove the non-responding nameserver from
/etc/resolv.conf
Thank you,
Demetris Demetriou
-- System Information:
Debian Release: 9.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages postfix-policyd-spf-python depends on:
ii adduser 3.115
pn postfix <none>
ii python3 3.5.3-1
pn python3-authres <none>
pn python3-spf <none>
postfix-policyd-spf-python recommends no packages.
postfix-policyd-spf-python suggests no packages.
--- End Message ---
--- Begin Message ---
On Fri, 29 Mar 2019 18:34:38 +0200 Demetris Demetriou <[email protected]>
wrote:
> Package: postfix-policyd-spf-python
> Version: 2.0.1-1
> Severity: important
>
> Hello,
>
> Package: postfix-policyd-spf-python
> Version: 2.0.1-1
>
>
> postfix-policyd-spf-python fails to properly failover to a secondary
nameserver
> in case one of the declared nameservers in /etc/resolv.conf is not
responding.
>
> All incoming email is rejected with:
> defer_if_permit 4.7.24 Message deferred due to: SPF Temporary Error: DNS
> Timeout. Please see http://www.openspf.net/Why?s=[snipped]
>
> related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718547 but
python-
> dns is not installed, so I'm thinking that the underlying problem is
actually
> in postfix-policyd-spf-python. No difference with python-dns installed.
>
> The problem goes away if I manually remove the non-responding nameserver
from
> /etc/resolv.conf
I have finally had a chance to really research this bug. I am unable to
reproduce it either with current versions of the packages or the versions in
stretch. I can reproduce getting the result you got, but only if there are no
working nameservers in resolv.conf. If there is a bad one and a good one, it
falls back correctly.
I'm going to close the bug because I don't think there is anything more to do.
The only think I can guess is that there was some temporary glitch where none
of the nameservers were working.
Scott K
--- End Message ---
