Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

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

  • 1 отговор
  • 1 има този проблем
  • 10 изгледи
  • Последен отговор от brezz

more options

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.

Прочетете този отговор в контекста 👍 0

Всички отговори (1)

more options

Избрано решение

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.