I copied the IP of the first non-authoritative answer (there were only non-authoritative answers). I came into work yesterday and Thunderbird was unable to connect to the incoming Comcast mail server (though it could connect to outgoing smtp). My Thunderbird w/ Comcast email worked fine for 4+ years on 3 LTS versions of Ubuntu/ It was working fine on Friday Nov 16.
I also use Ubuntu 18.04 and Comcast email w/ Thunderbird and I am experiencing the same issue (though I had been using port 995). What's the best way to diagnose the cause of both ping and Thunderbird's inability to contact Comcast's POP3 mail server ""? Which basically states systemd-resolved doesn't support RRSIG and I was able to get some of the test results posted in that article on the Ubuntu 18.04 system I use. Nameserver part of my online research, I did find this article: # See man:rvice(8) for details about the supported modes of # replace this symlink by a static file or a different symlink. # Third party programs must not access this file directly, but only through the # Run "resolvectl status" to see details about the uplink DNS servers # internal DNS stub resolver of systemd-resolved. # This is a dynamic nf file for connecting local clients to the # This file is managed by man:systemd-resolved(8). Ping: : Name or service not I do DNS lookups on "", I get addresses nslookup
When I ping Comcast's mail server address, I get ping Thunderbird can connect to Comcast's IMAP servers just fine So, I did some research and experimentation and found the following: Thunderbird issues a "Failed to connect to server " message and I can't retrieve new mail. Both are 64-bit systems and both are running Thunderbird 60.2.1. One system is running Ubuntu 18.04 and the other Ubuntu 18.10. Hi! Starting on Monday, November 19, 2018, Thunderbird on two Ubuntu systems I use can't connect to Comcast's POP3 mail servers.
0 kommentar(er)
