We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Windows 10 TB 38 suddenly stopped receiving emails from comcast.net

  • 4 replies
  • 2 have this problem
  • 2 views
  • Last reply by snaimon

more options

My wife and I share the computer. Don't know if there was a TB update 12-3. But starting sometime 12-3 aAfter 10 pm, TB fails to retrieve any emails from the comcast server. Initially TB was using PORT 110, I believe. [So-called] Comcast customer support suggested 495 or 995 -- or maybe both, sorry. None of those worked. I have installed Windows Live Mail and that works but on a different port.

I have no problems sending using TB at all, so it's the inbound port and the server is still mail.comcast.net.

Using Windows 10 - there was an article about Win 7. Moved to 10 about 2 months ago, so it's not Win 10. I bet it's Comcast closing a port. They claim they do not support TB. Swell.

Thanks for any help in advance.

Stan

My wife and I share the computer. Don't know if there was a TB update 12-3. But starting sometime 12-3 aAfter 10 pm, TB fails to retrieve any emails from the comcast server. Initially TB was using PORT 110, I believe. [So-called] Comcast customer support suggested 495 or 995 -- or maybe both, sorry. None of those worked. I have installed Windows Live Mail and that works but on a different port. I have no problems sending using TB at all, so it's the inbound port and the server is still mail.comcast.net. Using Windows 10 - there was an article about Win 7. Moved to 10 about 2 months ago, so it's not Win 10. I bet it's Comcast closing a port. They claim they do not support TB. Swell. Thanks for any help in advance. Stan

Chosen solution

Thank you very much; that fixed my TB problem.

The (notice in my original I said) "so-called" comcast customer care folks (3 different ones) with whom I spoke could not or did not point me to the link you provided.

I don't see where TB lets me use the imap access -- only pop3.

Indeed, I was using 110 and that has apparently been disabled. 995 works.

Read this answer in context 👍 0

All Replies (4)

more options

Please post your Troubleshooting Information. At the top right of the Thunderbird window, click the menu button , then select Help > Troubleshooting Information. Press the Copy text to clipboard button and paste the information into your reply.

more options

Application Basics

   Name: Thunderbird
   Version: 38.4.0
   User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
   Profile Folder: Show Folder
             (Local drive)
   Application Build ID: 20151119061742
   Enabled Plugins: about:plugins
   Build Configuration: about:buildconfig
   Memory Use: about:memory
 Mail and News Accounts
   account1:
     INCOMING: account1, , (none) Local Folders, plain, passwordCleartext
   account2:
     INCOMING: account2, , (pop3) mail.comcast.net:465, SSL, passwordCleartext
     OUTGOING: smtp.comcast.net:587, plain, passwordCleartext, true
   account3:
     INCOMING: account3, , (pop3) pop3.mindspring.com:465, plain, passwordCleartext
     OUTGOING: smtp.comcast.net:587, plain, passwordCleartext, true
 Crash Reports
   http://crash-stats.mozilla.com/report/index/bp-c977a0a0-b986-4372-9b58-0a8eb2150919 (9/19/2015)
 Extensions
   Lightning, 4.0.4.1, true, {e2fda1a4-762b-4020-b5ad-a41df1933103}
 Important Modified Preferences
   Name: Value
     accessibility.typeaheadfind.flashBar: 0
     browser.cache.disk.capacity: 358400
     browser.cache.disk.smart_size_cached_value: 358400
     browser.cache.disk.smart_size.first_run: false
     browser.cache.disk.smart_size.use_old_max: false
     browser.zoom.full: true
     dom.max_chrome_script_run_time: 0
     extensions.lastAppVersion: 38.4.0
     font.name.monospace.el: Consolas
     font.name.monospace.tr: Consolas
     font.name.monospace.x-baltic: Consolas
     font.name.monospace.x-central-euro: Consolas
     font.name.monospace.x-cyrillic: Consolas
     font.name.monospace.x-unicode: Consolas
     font.name.monospace.x-western: Consolas
     font.name.sans-serif.el: Calibri
     font.name.sans-serif.tr: Calibri
     font.name.sans-serif.x-baltic: Calibri
     font.name.sans-serif.x-central-euro: Calibri
     font.name.sans-serif.x-cyrillic: Calibri
     font.name.sans-serif.x-unicode: Calibri
     font.name.sans-serif.x-western: Calibri
     font.name.serif.el: Cambria
     font.name.serif.tr: Cambria
     font.name.serif.x-baltic: Cambria
     font.name.serif.x-central-euro: Cambria
     font.name.serif.x-cyrillic: Cambria
     font.name.serif.x-unicode: Cambria
     font.name.serif.x-western: Cambria
     font.size.fixed.el: 14
     font.size.fixed.tr: 14
     font.size.fixed.x-baltic: 14
     font.size.fixed.x-central-euro: 14
     font.size.fixed.x-cyrillic: 14
     font.size.fixed.x-unicode: 14
     font.size.fixed.x-western: 14
     font.size.variable.el: 17
     font.size.variable.tr: 17
     font.size.variable.x-baltic: 17
     font.size.variable.x-central-euro: 17
     font.size.variable.x-cyrillic: 17
     font.size.variable.x-unicode: 17
     font.size.variable.x-western: 17
     gfx.direct3d.last_used_feature_level_idx: 1
     mail.openMessageBehavior.version: 1
     mail.winsearch.firstRunDone: true
     mailnews.database.global.datastore.id: 221af57c-79a1-4ce4-b030-ed1ac592e8a
     network.cookie.prefsMigrated: true
     network.predictor.cleaned-up: true
     places.database.lastMaintenance: 1449253962
     places.history.expiration.transient_current_max_pages: 79613
     places.history.expiration.transient_optimal_database_size: 127377408
     plugin.importedState: true
     plugins.update.notifyUser: true
     print.print_printer: HP Deskjet 6940 series (Copy 1)
   .............

I have tried other ports. It was originally 110 and that did not work.

Stan

more options

It's possible Comcast only support SSL/TLS access now, which is a good thing.

Comcast support should be able to tell you the correct server settings. And you should be able to look up the correct settings on their support site.

There is no point trying different combinations of settings, simply use what Comcast require. And this isn't a secret. http://customer.xfinity.com/help-and-support/internet/email-client-programs-with-xfinity-email/

You need to turn on SSL/TLS for both, incoming and outgoing, and correct the port for incoming.

more options

Chosen Solution

Thank you very much; that fixed my TB problem.

The (notice in my original I said) "so-called" comcast customer care folks (3 different ones) with whom I spoke could not or did not point me to the link you provided.

I don't see where TB lets me use the imap access -- only pop3.

Indeed, I was using 110 and that has apparently been disabled. 995 works.