I'm going to try sending this from Yahoo to see whether it will getYahoo is OK: (from my final Gmail Inbox -- soyeomul@gmail.com)
through. Bendel seems to be having some issues. I don't know whether
Yahoo will mangle the terminal commands. I apologize in advance if it
does.
A message that I sent from my primary email address this morning was
stuck in the outgoing queue:
# mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
D9EDA819CA 2475 Wed Feb 18 07:08:40 greg@wooledge.org
(connect to
bendel.debian.org[2001:41b8:202:deb:216:36ff:fe40:4002]:25: Connection
timed out)
debian-user@lists.debian.org
-- 2 Kbytes in 1 Request.
# host bendel.debian.org
bendel.debian.org has address 82.195.75.100
bendel.debian.org has IPv6 address 2001:41b8:202:deb:216:36ff:fe40:4002
# ping 2001:41b8:202:deb:216:36ff:fe40:4002
PING 2001:41b8:202:deb:216:36ff:fe40:4002(2001:41b8:202:deb:216:36ff:fe40:4002)
56 data bytes
^C
--- 2001:41b8:202:deb:216:36ff:fe40:4002 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 1005ms
# ping 82.195.75.100
PING 82.195.75.100 (82.195.75.100) 56(84) bytes of data.
64 bytes from 82.195.75.100: icmp_seq=1 ttl=47 time=86.8 ms
64 bytes from 82.195.75.100: icmp_seq=2 ttl=47 time=86.7 ms
^C
--- 82.195.75.100 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 3ms
rtt min/avg/max/mdev = 86.717/86.773/86.830/0.299 ms
So, I configured Postfix to use only ipv4, and now:
# postqueue -f
# mailq
-Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient-------
D9EDA819CA* 2475 Wed Feb 18 07:08:40 greg@wooledge.org
(host bendel.debian.org[82.195.75.100] said: 450 4.7.25 Client host
rejected: cannot find your hostname, [199.231.184.176] (in reply to
RCPT TO command))
debian-user@lists.debian.org
-- 2 Kbytes in 1 Request.Below is mine. I am in South Korea:
However, I do have a working "reverse DNS" on this host. It was
configured last night (8-9 hours ago);
$ host 199.231.184.176
176.184.231.199.in-addr.arpa domain name pointer wooledge.org.
A message that I queued up the other day and which was being rejectedBendel's rule/status is normal. I think time will solve this problem.
for the same reason did manage to go through successfully after
that. I don't know what's going on with bendel, but I hope it gets
fixed.
However, I do have a working "reverse DNS" on this host. It was configured last night (8-9 hours ago);
$ host 199.231.184.176
176.184.231.199.in-addr.arpa domain name pointer wooledge.org.
;; ADDITIONAL SECTION:
greg.wooledge.org. 3600 IN A 209.142.155.49 remote.wooledge.org. 3600 IN A 199.231.184.176
[...]
You should correct this or find another secondary more available
$ dig +short @199.231.184.176 -x 199.231.184.176
;; communications error to 199.231.184.176#53: timed out
;; communications error to 199.231.184.176#53: timed out
;; communications error to 199.231.184.176#53: timed out
;; no servers could be reached
So your DNS do not resolve your IP. Perhaps you filter request from
outside ? Or your host/resolv.conf asks your ISP ?
On 2026-02-18, Michel Verdier wrote:
some wrong things
$ dig -x 199.231.184.176
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to ::1#53: timed out
;; communications error to 127.0.0.1#53: timed out
So it seems that you correctly set a reverse. But there is a timeout
during revolving. You should tell this to your provider.
On 18.02.2026 14:30 Greg Wooledge wrote:
# ping 2001:41b8:202:deb:216:36ff:fe40:4002
PING 2001:41b8:202:deb:216:36ff:fe40:4002(2001:41b8:202:deb:216:36ff:fe40:4002) 56 data bytes ^C
Currently it works for me. Please use traceroute and check whether that
is a local issue or at the remote side or during transit.
The registrar won't let me simply remove the second DNS server.
They want two. So, I guess the *least difficult* path is to run the secondary DNS on my non-static-addressed home system, the same way I
used to run it on my static-addressed home system in the past.
I don't think IPv6 works from this host at all. I tried a few other IPv6 addresses, and couldn't ping any of them. If I'm correct then disabling
IPv6 in Postfix (which I've already done) seems like the best solution
to that.
There are ,lots of places on the Internet that offer free DNS secondary service, so if my hosting provider didn't offer this service and I
didn't want to buy more hosting, I'd probably use one of those. Add
their server(s) and then remove the one that doesn't work anymore.
On 19.02.2026 13:20 Greg Wooledge wrote:
I don't think IPv6 works from this host at all. I tried a few other
IPv6 addresses, and couldn't ping any of them. If I'm correct then disabling IPv6 in Postfix (which I've already done) seems like the
best solution to that.
That is the worst solution.
Make sure IPv6 works or remove all GUA addresses from your system, so
no other application will try to use it and fail.
How did you set it up?
# cat /etc/network/interfaces
# This configuration file is auto-generated.
#
# WARNING: Do not edit this file, your changes will be lost.
# Please create/edit /etc/network/interfaces.head and
# /etc/network/interfaces.tail instead, their contents will be
# inserted at the beginning and at the end of this file, respectively.
#
# NOTE: it is NOT guaranteed that the contents of /etc/network/interfaces.tail
# will be at the very end of this file.
# Auto generated lo interface
auto lo
iface lo inet loopback
# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
up ifconfig venet0 up
up ifconfig venet0 127.0.0.2
up route add default dev venet0
down route del default dev venet0
down ifconfig venet0 down
iface venet0 inet6 manual
up route -A inet6 add default dev venet0
down route -A inet6 del default dev venet0
On 19.02.2026 15:10 Greg Wooledge wrote:
I didn't. I have no idea how IPv6 works, or is intended to work.
There are courses online by people who know.
I've never seen a system where it works.
Then it seems you are living behind the moon.
Millions of machines use
it every day and terabits per second of traffic flows.
In your case: Investigate how the route came there. Use tcpdump and
monitor for router advertisments. If there are some, check from which
mac address they are and investigate why that device send them out.
On Thu, Feb 19, 2026 at 16:29:11 +0100, Marco Moock wrote:
On 19.02.2026 15:10 Greg Wooledge wrote:
I didn't. I have no idea how IPv6 works, or is intended to work.
There are courses online by people who know.
I've never seen a system where it works.
Then it seems you are living behind the moon.
We call it the United States.
Millions of machines use
it every day and terabits per second of traffic flows.
Oh, I'm not saying it doesn't exist, or doesn't work well for billions
of people. Just that I've personally never had access to a system
where it works.
My home system gives:
hobbit:~$ ping 2001:41b8:202:deb:216:36ff:fe40:4002
ping: connect: Network is unreachable
And the VPS with the IPv6 route but no IPv6 address has already been
covered.
In your case: Investigate how the route came there. Use tcpdump and
monitor for router advertisments. If there are some, check from
which mac address they are and investigate why that device send
them out.
I have an alternative plan: don't touch it at all, so I don't break
anything, especially since I don't understand it.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 119:49:23 |
| Calls: | 125 |
| Calls today: | 125 |
| Files: | 489 |
| D/L today: |
859 files (365M bytes) |
| Messages: | 76,568 |
| Posted today: | 26 |