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

Switched from POP to IMAP, after clicking re-test, receiving message: thunderbird failed to find the settings for your email acount

  • 1 பதிலளி
  • 1 இந்த பிரச்சனை உள்ளது
  • 3 views
  • Last reply by brezz

Recently updated to win 10 (1st mistake?). Accidentally set up a POP instead of and IMAP. I followed the instructions to switch from POP to IMAP and delete the POP account. I created a new account using IMAP but server setting is still showing POP server. My ISP is Comcast. Ports are set to 993, 587 SSL/TLS. Thunderbird is set to default mail client. I am using Bitdefender Internet security 2015 for win 10. Bitdefender firewall rules are to set to allow Firefox and Thunderbird through Any network, any protocol. This is about as much info as I can provide. Please help. Windows mail app won't send and receive unless firewall is set to trusted, not the best option.

Thanks.

Recently updated to win 10 (1st mistake?). Accidentally set up a POP instead of and IMAP. I followed the instructions to switch from POP to IMAP and delete the POP account. I created a new account using IMAP but server setting is still showing POP server. My ISP is Comcast. Ports are set to 993, 587 SSL/TLS. Thunderbird is set to default mail client. I am using Bitdefender Internet security 2015 for win 10. Bitdefender firewall rules are to set to allow Firefox and Thunderbird through Any network, any protocol. This is about as much info as I can provide. Please help. Windows mail app won't send and receive unless firewall is set to trusted, not the best option. Thanks.

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Probably bad form responding to my own post. Found the answer in another community posting. Should have set port to 465 instead of 587 as per Comcast instructions.

Read this answer in context 👍 0

All Replies (1)

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Probably bad form responding to my own post. Found the answer in another community posting. Should have set port to 465 instead of 587 as per Comcast instructions.