On Monday, August 28, 2023, mailbombbin <[email protected]> wrote:
> > > On Sunday, August 27, 2023, mailbombbin <[email protected]> wrote: > >> >>> >> This is an email address I made to collect exploding emails and post to >> the list with. >> >> I even made a tiny PGP key and set mutt up for IMAP! >> >> However, I don't seem able to connect to smtp.gmail.com on either the >> SSL port nor the TLS port, even over TOR or from public wifi, so I'm on a >> web interface still. >> >> Still remains to try from a different device. >> > > Via other means I found a different IP address that smtp.gmail.com can > resolve to than the ones it does here. When I use that IP address, I can > access the SSL and TLS ports. > > Meanwhile, the IP addresses my name servers give me do respond on the old > cleartext port, but they give a header line for mx.google.com rather than > smtp.gmail.com . Meanwhile, mx.google.com does not resolve for me. > > Below: > > ~ $ host smtp.google.com > smtp.google.com has address 142.251.165.26 > smtp.google.com has address 142.251.165.27 > smtp.google.com has address 142.250.112.26 > smtp.google.com has address 142.250.112.27 > smtp.google.com has address 142.251.4.26 > smtp.google.com has IPv6 address 2607:f8b0:4023:1407::1b > smtp.google.com has IPv6 address 2607:f8b0:4023:140d::1a > smtp.google.com has IPv6 address 2607:f8b0:4023:140d::1b > smtp.google.com has IPv6 address 2607:f8b0:4023:1402::1b > ~ $ host smtp.gmail.com > smtp.gmail.com has address 142.250.10.108 > smtp.gmail.com has IPv6 address 2607:f8b0:4024:c00::6c > ~ $ nc -v 172.217.204.108 587 > Connection to 172.217.204.108 587 port [tcp/submission] succeeded! > 220 smtp.gmail.com ESMTP j21-20020a9f3095000000b00799f82d909bsm1396295uab.26 > - gsmtp > HELO smtp > 250 smtp.gmail.com at your service > ^C > ~ $ nc -v 142.250.112.26 587 > nc: connect to 142.250.112.26 port 587 (tcp) failed: Connection timed out > ~ $ nc -v 142.250.112.26 25 > Connection to 142.250.112.26 25 port [tcp/smtp] succeeded! > 220 mx.google.com ESMTP z59-20020a25a141000000b00d437d7a207bsi2952087ybh.40 > - gsmtp > HELO smtp > 250 mx.google.com at your service > ^C > ~ $ nc -v 172.217.204.108 25 > Connection to 172.217.204.108 25 port [tcp/smtp] succeeded! > 220 smtp.gmail.com ESMTP x12-20020a05610223cc00b0044e9fdc54b6sm1494894vsr.29 > - gsmtp > HELO smtp > 250 smtp.gmail.com at your service > ^C > ~ $ nc -v mx.google.com 587 > nc: getaddrinfo for host "mx.google.com" port 587: No address associated > with hostname > > ----- > After writing the above I realized I was sometimes typing smtp.gmail.com > and sometimes smtp.google.com . The former is presently working for me. > The assertion something was wrong appears bogus right now. > ~ $ nc -v 142.250.10.108 587 Connection to 142.250.10.108 587 port [tcp/submission] succeeded! 220 smtp.gmail.com ESMTP p139-20020a254291000000b00d749efa85a1sm1890459yba.41 - gsmtp Slight quirk where the other IP says mx.google instead of SMTP.gmail
