Your message dated Wed, 4 Dec 2024 21:52:00 +0300
with message-id <06f7e1a8-11e9-4cd1-8c6e-cc5282946...@tls.msk.ru>
and subject line Re: IPv6 only relay_transport does not work
has caused the Debian Bug report #722251,
regarding IPv6 only relay_transport does not work
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.)
--
722251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postfix
Version: 2.10.1-2
Severity: normal
Hi,
using a relay transport like
relay_transport = relay:[ipv6only.example.com]
where ipv6only.example.com only has a AAAA record but no A record gives:
9EDCC1612: to=<a...@sigxcpu.org>, relay=none, delay=0.05, delays=0.03/0.02/0/0,
dsn=5.4.4, status=bounced (Host or domain name not found. Name service error
for name=ipv6only.example.com type=A: Host found but no data record of
requested type).
It seems like postfix isn't expecting a ipv6 only entry here.
Cheers,
-- Guido
-- System Information:
Debian Release: jessie/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing'), (50, 'unstable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages postfix depends on:
ii adduser 3.113+nmu3
ii cpio 2.11+dfsg-1
ii debconf [debconf-2.0] 1.5.51
ii dpkg 1.16.10
ii libc6 2.17-92+b1
ii libdb5.1 5.1.29-6
ii libsasl2-2 2.1.25.dfsg1-14
ii libsqlite3-0 3.7.17-1
ii libssl1.0.0 1.0.1e-3
ii lsb-base 4.1+Debian12
ii netbase 5.1
ii ssl-cert 1.0.33
Versions of packages postfix recommends:
ii python 2.7.5-4
Versions of packages postfix suggests:
ii bsd-mailx [mail-reader] 8.1.2-0.20111106cvs-1
pn dovecot-common <none>
ii emacs23 [mail-reader] 23.4+1-4.1
ii emacs24 [mail-reader] 24.3+1-1
ii icedove [mail-reader] 17.0.8-1
ii libsasl2-modules 2.1.25.dfsg1-14
ii mutt [mail-reader] 1.5.21-6.3
pn postfix-cdb <none>
pn postfix-doc <none>
pn postfix-ldap <none>
pn postfix-mysql <none>
pn postfix-pcre <none>
pn postfix-pgsql <none>
ii procmail 3.22-20
pn resolvconf <none>
pn sasl2-bin <none>
pn ufw <none>
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Mon, 9 Sep 2013 15:26:17 +0200 Guido Günther <a...@sigxcpu.org> wrote:
Package: postfix
Version: 2.10.1-2
Severity: normal
Hi,
using a relay transport like
relay_transport = relay:[ipv6only.example.com]
where ipv6only.example.com only has a AAAA record but no A record gives:
9EDCC1612: to=<a...@sigxcpu.org>, relay=none, delay=0.05, delays=0.03/0.02/0/0,
dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for
name=ipv6only.example.com type=A: Host found but no data record of requested type).
It seems like postfix isn't expecting a ipv6 only entry here.
Hi!
It's been more than 12 years ago. A lot has changed in postfix
and in other software since that time. And postfix these days
appears to work with v6-only hosts just fine.
Let's close this bug report now finally.
Feel free to re-open it if you think it is incorrect and the problem
still applies to current postfix.
Thanks, and sorry it took so long..
/mjt
--- End Message ---
