Thursday, November 20, 2008

Thunderbird Update

Mozilla has released a patch for their Thunderbird email client, bringing the latest version to 2.0.0.18. This version closes several security holes. (details)

If you don't have automatic updates turned on, do Help → Check for Updates from within Thunderbird.

The patch is so small I wasn't able to see its size in bytes. Download, automatic install and restart took less than a minute, so there's no reason to put it off.

4 comments:

Anonymous said...

My partner and I both received the update. Now we can only receive email, not send. And we are using different ISP's.

Any way out of this box?

Dave

bjkeefe said...

Several ways. If you're still having trouble, let me know, and I'll make some suggestions.

Anonymous said...

Yes, I'm still having the same problem. I suspect that I need to change port number and maybe some other stuff. The current port is 110. Our broad band carrier is Comcast.

Any assistance will be greatly appreciated.

Thanks,

Dave

bjkeefe said...

Sorry to hear that you're still having problems, Dave.

The first thing to be aware of is that port 110 is for incoming (POP) mail. For outgoing (SMTP) mail, the correct port is usually 25.

I see by a FAQ on the Comcast help page that they also support using port 587. However, another FAQ nearby indicates that port 25 is the default (and presumably supported).

I tried linking directly to the FAQs but that doesn't appear to work. So, to get to the FAQs, go to help.comcast.net and click the "Go" button under "Help With High-Speed Internet." On the next page, click the "Email" link. On the next page after that, click the "Thunderbird" link.

To check your settings in Tbird, do Tools→Account Settings. In the left pane of the new window that pops up, look down at the bottom for "Outgoing Server (SMTP)." Single-click that. The right pane should then show you what the current settings are. If something looks wrong, highlight the entry saying smtp.comcast.net and click the "Edit" button. (If you don't see an entry that says smtp.comcast.net, that's probably the problem right there.)

Another thing to be aware of, while you're there, is the "Secure Connection" setting. The Comcast FAQs indicates that this should be set to "No;" i.e., not TLS or SSL.

Assuming you have all the settings correct, try to send a message. If it still won't work, probably the next best thing to try is calling Comcast tech support. If sitting on hold on the phone doesn't appeal, you might look at help.comcast.net for other ways to contact them; e.g., live chat or email (which you could probably send through a form on their site, or through their webmail interface, and not through TBird).

If you're still having problems, and you've verified your outgoing settings, and you're not able or willing to deal with Comcast's tech support, which leads you back here, you might make a note of the exact error message you get when you try to send a message.

Good luck.

ShareThis