Comcast no longer uses port 25 for outgoing emails. And even when changing to outgoing port 587 via my Thunderbird program, I kept receiving error message NB connect error 1460.
I thought it was a Thunderbird issue, it wasn't.
Thought it was a Comcast issue. It wasn't.
Couldn't figure out what was causing the problem until I found others experiencing the same problem online: https://getsatisfaction.com/mozilla_messaging/topics/outgoing_messages_not_going_anywhere_plain_timeout_or_nb_connect_error_1460
Apparently, Avast is still using port to 25 to send emails that it's scanned (?) ... even when we specifically say to use a different port. As a Comcast user and an Avast user the only way I can get my outgoing emails to send is by turning off Avast's outgoing scan function.
Avast tech people please check into this issue. I'd like to be able to scan my outgoing emails again.
Incoming emails are not an issue.