Post by Boris
I'm running a live version of Ubuntu 18.04 LTS along with it's default
Thunderbird 52.7.0, both 64-bit.
I've set up newsgroups just fine, but I can't seem to get the mail set
up, whether POP or IMAP.
When I enter my Comcast user name and email address, Thunderbird tells
me that "Configuration found in Mozilla ISP database".
I press "Done", and get "Configuration could not be verified - Is the
username of password wrong?" (No, it's correct.)
I press "Manual configuration", and all looks ok. Going back out to the
Mail window, I do see that even though my configuration could not be
Hmm...I press "Get Messages", and get "Failed to connect to server
mail.comcast.net". But, I can compose and send email successfully.
If I try setting up an email account I have with Yahoo, the
configuration is found in the Mozilla ISP database, but it cannot be
When I run Windows 7 or 10, I use the same settings when in Thunderbird,
and all is fine.
Any ideas as to why I can't get Thunderbird Mail to work in Ubuntu?
Flavor of SSL/TLS ? Port number ?
I've heard of this database idea, but didn't realize it
actually worked. No ones ever mentioned it. There was a
discussion long ago about "wouldn't it be neat if..."
and I guess that function is the result.
There is a logging feature, but it doesn't look like much fun.
They could have put this crap into about:config, instead of
making it out of shell environment variables.
If you compiled the product from source, you could also turn
on a "console" function, which opened a black terminal window
and dumped messages in it. But the messages themselves were
And you can't use Wireshark all that easily because of the
Back in the old days of PPP dialup, I don't know how many
times I consulted the verbatim recording the logger would
make of the "initial PPP conversation". You could see whether
it was using header compression or whether authentication
succeeded and so on. That was a great feature. Too bad more
Internet tools did not offer to collect a "decrypted"
recording of the conversation they were having, so Wireshark
would not be needed.
Occasionally you get lucky with Wireshark, and you see a tool
making references to the wrong internet address. But other than
that, it's not going to help all that much. I understand someone
knows how to break into the SSL/TLS on a host and decrypt it,
but I don't know how to do that.