Your message dated Fri, 09 Mar 2018 09:22:42 -0500
with message-id <12673837.a0SURGFqhx@kitterma-e6430>
and subject line Re: Bug#892477: Acknowledgement (spf-milter-python: If
connection is IPv6, milter says "Void lookup limit of 2 exceeded")
has caused the Debian Bug report #892477,
regarding spf-milter-python: If connection is IPv6, milter says "Void lookup
limit of 2 exceeded"
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 ow...@bugs.debian.org
immediately.)
--
892477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892477
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spf-milter-python
Version: 0.8.18-2
Severity: grave
Tags: ipv6
Justification: causes non-serious data loss
Dear Maintainer,
I noted that when someone at mdh.se tries to send e-mail to us, and the
connection is from
an IPv6-address (almost all connections are these days), spf-milter-python will
reply "Void
lookup limit of 2 exceeded". The domain always passes all checks on both
mxtoolbox.com/spf.aspx and http://www.kitterman.com/spf/validate.html.
I even had a loop running for a day, using spfquery to log the results while
waiting for a
failing e-mail. When the mail-server responded "Void lookup limit of 2
exceeded", the data
in the diagnostic-log looked correct and had not failed.
I can reproduce this by telnetting my SMTP-gateway, and pretend to be sending
from mdh.se. If
I connect over an IPv6-connection I get a "Void lookup limit of 2 exceeded",
every time. If
I telnet the IPv4-address of the SMTP-gateway i get a soft-error (expected
result).
I have the same software on the other SMTP-gateway, and it has the same
behaviour.
-- System Information:
Debian Release: 9.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, 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 spf-milter-python depends on:
ii adduser 3.115
ii lsb-base 9.20161125
ii python 2.7.13-2
ii python-milter 1.0-2
ii python-spf 2.0.12t-3
spf-milter-python recommends no packages.
Versions of packages spf-milter-python suggests:
ii sendmail 8.15.2-8
-- Configuration Files:
/etc/spf-milter-python/spfmilter.cfg changed:
[milter]
socketname = /var/run/spf-milter-python/spfmiltersock
;umask = 0177
name = pyspffilter
;trusted_relay =
internal_connect =
127.0.0.1,192.168.0.0/16,10.0.0.0/8,IPv6:0:0:0:0:0:0:0:1,::1,0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1
;best_guess = v=spf1 a mx ptr ?all
;delegate = domain.com
untrapped_exception = CONTINUE
[spf]
access_file = /etc/mail/access.db
;access_file_nulls = false
;trusted_forwarder = careerbuilder.com
-- no debconf information
--- End Message ---
--- Begin Message ---
On Friday, March 09, 2018 03:59:04 PM Harald Hannelius wrote:
> Please close this bug. It turned out that the domain mhd.se must have
> AAAA-records for the included 'a:' hostnames in DNS, which they didn't. And
> by using cloud-based e-mail they are using IPv6 without actually knowing it.
> > $ host f-medby.ita.mdh.se
> > f-medby.ita.mdh.se has address 130.243.84.223
>
> $ host -t aaaa f-medby.ita.mdh.se # first void lookup
> f-medby.ita.mdh.se has no AAAA record
> $ host -t aaaa aaaa www.netigate.se # second void lookup
> www.netigate.se has no AAAA record
> $ host -t aaaa smtp.quicknet.se # third void lookup
> smtp.quicknet.se has no AAAA record
>
>
> Many thanks to Stuart D. Gathman for pointing this out to me.
Thanks for reporting back on it. Closing the bug.
Scott K
--- End Message ---
