Thunderbird connection log


I'm configuring Thunderbird under Windows 7 to connect via StartTLS. I would like to view a log of the connection in order to a) debug configuration settings, and b) make sure that it actually is connecting via TLS and accepting certificates correctly.

It appears that there is no native log in the application. Did I miss it?  

If there is no log, would a viable approach be with a packet sniffer - and which is the easiest to use?

Thanks much,
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dave BaldwinFixer of ProblemsCommented:
I don't see a log mentioned.  I just set up a 'secure' email on my Comcast account and it 'automatically' set it up for SSL/TLS.  Apparently Comcast POP3 is one of the 'known' email setups in Thunderbird although I could have chosen IMAP.  I'm pretty sure that it did work because my Avast anti-virus intercepted it and I had to accept the 'security exception' caused by the Avast self-signed certificate.
Dave BaldwinFixer of ProblemsCommented:
For packet inspection, I generally use Wireshark.

Open Wireshark, choose "capture options" from the menu, select the appropriate network interface and, presuming as IP of the distant mailserver, apply a capture filter of


That would limit the captured data to the conversation between your station and the mail server.

Capture the entire conversation when sending a test mail. Inspect the packets. If you could recognize text from your message in the lower pane, it's unencrypted. If it looks like completely junk, it's encrypted. If you see "SSL..." or "TLS..." as protocol in the packet list, the connection seems to be encrypted with SSL.

Right click on one of the packets and choosing "Follow TCP stream" will show the conversation concerning the stream the packet is part of.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
fredo783Author Commented:
This is a perfect solution. By using Wireshark I was able to determine that TLS was used and that connection was encrypted. Your tips on using Wireshark were very helpful. Thanks! (By the way, Wireshark is quite easy to use. )
You're welcome :)

Wireshark's ease of use depends on how familiar you're with such things as networks, TCP/IP, Ethernet, etc, I think. Maybe I've underestimated your skills - sorry for that ;-)

By the way, Wireshark is a basic tool for many network / data flow associated problems, and I use it regulary for such things. A good advice in such cases ... follow the data ...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Clients

From novice to tech pro — start learning today.