I really do appreciate all your attempts to help but I realize this forum is not the appropriate place for the conversation. I was just hoping for a "quick" fix.
FYI, nothing suggested here has worked so far. If anyone has any further thoughts, I would appreciate it if you would contact me directly. As it stands now, I either abandon Comcast or Tbird, neither alternative being very appealing. Thanks again. On Jul 24, 8:41 pm, alanrf <[email protected]> wrote: > As I mentioned earlier, I am a Comcast customer. > > I have just tested (within the past 10 minutes) the following settings > for SMTP all successfully using smtp.comcast.net as the server: > > Port: 25 > Use secure connection: Never > > Port 465 > Use secure connection: SSL > > Port 587 > Use Secure connection: TLS > > These connections have worked for me without problems for the last 2+ > years (as I have reported in the main Thunderbird forum). The only > issue (as reported earlier) is likely to be the unsecured connection > if you you are not physically connected to the Comcast network (ie you > are using another service - airport, hotel, coffee shop etc). > > Apologies to the Thunderbird Webmail extension users for posting in > this forum about issues not related to the Webmail extensions. > > On Jul 24, 7:53 pm, KE4AVB <[email protected]> wrote: > > > Dave, May need to use TLS connection instead of the SSL. If Outlook > > setup is the same as Outlook Express there isn't a TLS settings. > > > Try these instructions: > > > Comcast > > > Comcast's instructions > > > Comcast's instructions state you should leave both "use secure > > authentication" and "use secure connection (SSL)" unchecked when > > configuring the POP account. Some users have enabled "secure > > authentication" and gotten it to sporadicly work. The SSL support > > seems to be reliable. Its recommended you use a secure connection > > (SSL) rather than secure authentication if you don't want to send the > > password in the clear when logging into the POP server. > > > Comcast documents two SMTP configurations, a unsecure connection > > using port 25 and a secure connection using "TLS if available" and > > port 587. If you get a error message that the SMTP server may be > > unavailable or refusing SMTP connections there is a undocumented > > configuration that several users have gotten to work. Use port 465 , > > set "use secure connection" to SSL, check the authentication required > > box and provide your full Comcast address as the username. > > > The Comcast spam filters limit messages to Comcast addresses to > > six recipients per second. This may occasionally cause new mail to you > > to be bounced, or prevent you from sending a message. When this > > problem occurs the sender will get a 4xx error message (temporary > > failure) and a link for instructions on how to solve the problem. [1] > > > Here is the link for help with the Comcast setup from the knowledge > > database. > > >http://kb.mozillazine.org/Creating_accounts_in_Thunderbird_for_popula... > > > Hope this will help you... > > > Eugene > > > On Jul 24, 11:05 am, Chris Clifton <[email protected]> wrote: > > > > Hmm, if the settings are the same, then it should work. Many ISPs won't > > > accept incoming SMTP traffic unless the sending computer is using their > > > Internet service, (i.e. you're logged into either their broadband or > > > dial-up service and have an IP address allocated by them) so if you were > > > trying to use the Comcast server when logged into another ISP this might > > > explain the problem. This would affect Outlook as well however. > > > It comes down to there must be some subtle difference between your > > > Outlook and Tbird settings. This isn't really a question for this forum, > > > perhaps the tbird users' forum could offer more help? > > > > Dave Helmich wrote: > > > > No. As I said, the SMTP settings shown under account sttings are > > > > identical to those which I can successfully use in Outlook. Tbird is > > > > outomagically downloading form the comcast pop so thos settings are > > > > OK. > > > > > When I try to send an email from Tbird, I get the message failed > > > > indicating that maybe the server was down or my settings were wrong. > > > > (Too bad this message can't be cut and pasted or contain more info > > > > about at which stage the failure occurred.) > > > > > On Jul 23, 9:53 am, Chris Clifton <[email protected]> wrote: > > > > >> By default, Thunderbird uses the same SMTP server for ALL email > > > >> accounts. Normally the default server is the one belonging to the first > > > >> account set up after installing Thunderbird. Are you sure that > > > >> Thunderbird is set up to use the Comcast SMTP server for your Comcast > > > >> account? In account settings there should be a drop down menu showing > > > >> which outgoing server is selected for each account (click on the > > > >> account > > > >> name in the list to see settings for individual accounts). The > > > >> currently > > > >> selected server will show, and available servers set up in TB will be > > > >> visible when the menu opens. If your Comcast SMTP server isn't in the > > > >> list you cvan add or edit outgoing servers in the "Outgoing Servers > > > >> (SMTP)" section of TB's account settings. > > > > >> Dave Helmich wrote: > > > > >>> Then perhaps you have the magic key to get me into their server. > > > >>> Unfortunately, I am not that geeky about this stuff. After MUCH > > > >>> screwing around, I was able to get in on Outlook so I know the > > > >>> password works and my SMTP settings are correct. > > > > >>> Is it possible that there is some setting in Tbird that is not being > > > >>> wiped away or being re-set without getting into config? I am really > > > >>> at a loss. The Comcast people are worthless. I have maybe ten years > > > >>> of email in Tbird and I am loath (for that and because I want to > > > >>> support Mozilla) to abandon it. > > > > >>> I would welcome any suggestions. I am going to play with this for no > > > >>> more than a week and then cancel my service if I can't use Tbird. > > > > >>> Thanks, > > > > >>> Dave > > > > >>> On Jul 23, 1:50 am, alanrf <[email protected]> wrote: > > > > >>>> These extensions are designed to work with Webmail services such as > > > >>>> Yahoo, Hotmail and GMail. They provide no functions at all for ISPs > > > >>>> like Comcast which offer completely freely available POP and SMTP > > > >>>> services. Very simply, you do not need these extensions for Comcast > > > >>>> (just to mention - I am a Comcast customer too). > > > > >>>> On Jul 22, 11:04 am, Dave Helmich <[email protected]> wrote: > > > > >>>>> I am having no joy in using the SMTP connection to my new Comcast > > > >>>>> email 'service'. Will this extension work with Comcast since I have > > > >>>>> access to their webmail service? > > > > >> -- > > > > -- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thunderbird Webmail Extension" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/thunderbird-webmail-extension?hl=en -~----------~----~----~----~------~----~------~--~---
