On 01-Jul-24 13:25, John R Levine wrote:
On Mon, 1 Jul 2024, Brian E Carpenter wrote:
So if the IETF was willing to send SMTP/IPv6 then, Gmail wasn't playing. Does
anybody have evidence that it actually worked?
Yeah, logs on my mail server show over 4000 messages delivered via IPv6
from the IETF to me from 2017, when the logs start, until this March.
Thanks. So here is my question: what is different? You received SMTP
from mail.ietf.org via its IPv6 address (2001:559:c4c7::100?), whereas
mx.google.com received via 50.223.129.194.
It seems to need explanation, since mx.google.com receives from
mail-sy4aus01on20700.outbound.protection.outlook.com via 2a01:111:f403:201e::700.
I'd hazard a guess that Google is using a reputation mechanism of some kind,
but it would be interesting to know for sure.
Another bit of archaeology: it used to work, back in 2013:
Received: from mail.ietf.org (mail.ietf.org. [2001:1890:126c::1:1e])
by mx.google.com with ESMTP id rz8si13854629pbc.87.2013.02.25.18.22.54;
Mon, 25 Feb 2013 18:22:55 -0800 (PST)
It seems to have switched to IPv4 by about 2015, but it seems pointless to
analyse in more detail. I remain a bit confused, because mail.ietf.org
still appears to be dual-stacked today, according to DNS.
I have to say that the implication that the people running the IETF's mail
system are incompetent fools is getting a little old.
I don't believe I have implied that, and I agree that some of the messages
have been strident, to say the least. I agree with whoever it was who said
that the high-order bit is that the mail gets through.
Brian
Regards,
John Levine, johnl@xxxxxxxxx, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly
