Message379020
This is very likely caused by something janky my ISP (AT&T) is doing with IPv6, but the above named test fails for me because IPv6 addresses like `::1q` do not fail to resolve as the test expects.
I'm not sure what can or should be done about it, but as this is an annoying local failure, and I couldn't find another mention of it by searching bpo, I wanted to at least get it on record.
The test function's comment says:
"
# These are all malformed IP addresses and expected not to resolve to
# any result. But some ISPs, e.g. AWS, may successfully resolve these
# IPs.
"
So apparently, put AT&T in that bucket of ISPs that resolve those IPv6 addresses. |
|
| Date |
User |
Action |
Args |
| 2020-10-19 21:22:22 | barry | set | recipients:
+ barry |
| 2020-10-19 21:22:22 | barry | set | messageid: <[email protected]> |
| 2020-10-19 21:22:22 | barry | link | issue42092 messages |
| 2020-10-19 21:22:21 | barry | create | |
|