* John Levine: > In article <87sh5v7iut....@mid.deneb.enyo.de> you write: >>Is it expected that it is possible for the Internet at large to send >>email to t-mobile.com addresses? >> >>It looks like they have some far-ranging network blocks for some >>reason, at the TCP/IP level (connection attempts time out). > > Works fine for me from multiple networks. Perhaps you should try some > traceroutes and figure out where the route misconfiguration is.
Working 25/TCP traceroute: 9 us-nyc01b-ri2-ae8-0.aorta.net (84.116.133.97) 135.133 ms 130.678 ms 135.886 ms 10 lag-5.ear3.NewYork1.Level3.net (4.68.72.9) 131.931 ms 133.667 ms 134.765 ms 11 * * * 12 T-MOBILE-US.ear2.SanJose1.Level3.net (4.31.196.158) 228.278 ms 228.114 ms 223.949 ms 13 * * * 14 206.29.176.21 (206.29.176.21) 198.787 ms 192.135 ms 192.213 ms Failing 25/TCP traceroute: 10 lag-5.ear3.NewYork1.Level3.net (4.68.72.9) 129.220 ms 132.507 ms 129.524 ms 11 * * * 12 T-MOBILE-US.ear2.SanJose1.Level3.net (4.31.196.158) 226.211 ms 233.079 ms 229.527 ms 13 * * * 14 * * * (and so on) The curious thing is that in the working case, I get this SMTP error message: 554 5.7.1 You are not allowed to connect. Which is probably deliberate because I'm connecting from residential cable (and I think it's listed on the DUL). The other source address is not (it's business cable). So it's either a deliberate block or missing route on the T-Mobile network. Hard to tell which. _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
