On 2024-09-26, Dale <rdalek1...@gmail.com> wrote: > Grant Edwards wrote: > >> It looks like your network is broken. Try this: >> >> $ telnet smtp.gmail.com 587 >> Trying 209.85.145.109... >> Connected to smtp.gmail.com. >> Escape character is '^]'. >> 220 smtp.gmail.com ESMTP 8926c6da1cb9f-4d888860978sm58959173.69 - gsmtp >> >> Note: Port 587 is for plaintext connection and then shifting into TLS >> mode with the starttls command. When configuring msmtp: >> >> port 587 >> tls on >> tls-starttls on >> or >> port 465 >> tls on >> tls-starttls off >> >> Port 465 starts using TLS immediately >> >> [...]
> Which package do I need for that telnet? I see a few packages with that > name. Any of them should work. I use net-misc/netkit-telnetd. It will also install a telnet daemon, but it won't enbale it > I am connected through a VPN but Seamonkey works fine. I can check and > send email there, Do you mean can send email via Gmail's SMTP server using Seamonkey? How are the SMTP server settings configured in Seamonkey? Is it using Oauth2 or an app password? > hence this thread. I figure I got something set up wrong after a > Gmail change. Sort of stupid to make something so secure you can't > use it. It's like buying a computer and saying the only way to > secure it is to keep it turned off. :/ Well, that last part is true, as long as you keep it in a locked room. I just did a quick test, and sending via smtp.gmail.com using an app password worked fine from mutt. I don't have msmtp set up at the moment.
