Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Namecheap hosting inability to retieve email

  • 2 respostas
  • 0 tem este problema
  • 1 exibição
  • Última resposta de Matt

more options

In the last couple of weeks I have been unable to retrieve my email using Thunderbird or outlook from Namecheap servers. They offer a solution specifically for thunderbird solution solution /setup they tell you to use server address for server part in client setup mine is https://premium288.web-hosting.com

none of this works diffrent machines clients all return a fail to find in various wording

so anyone else have a problem with namecheap?

In the last couple of weeks I have been unable to retrieve my email using Thunderbird or outlook from Namecheap servers. They offer a solution specifically for thunderbird [https://www.namecheap.com/support/knowledgebase/article.aspx/271/2186/cpanel-email-account-setup-in-thunderbird/?_ga=2.125804175.401066643.1697671825-1905463183.1697671825 solution] solution /setup they tell you to use server address for server part in client setup mine is https://premium288.web-hosting.com none of this works diffrent machines clients all return a fail to find in various wording so anyone else have a problem with namecheap?

Todas as respostas (2)

more options

Finally after several hours with diffrent "specialists" and stamping my feet and throwing a tantrum they found my ip was blocked and white listed it . The sky rained email!!!! But I kid you not I would have spent at least 2 hours online with them trying to get it working

more options

For what it is worth (not much) I did test your SSL security on the server as that was a real possibility (servers often have corporate SSL certificates that mismatch what they are hosting as) and that was all on the up and up, but the fact they do not support TLS V1.3 is something that should be at least raised with them as it is inherently more secure than older versions. There is also potential for connection initiated encryption downgrades that leave the servers "more" prone to denial of service attacks.

If you understand the stuff enough, knowing what blocklist they used to block your IP may help you in the future. A certain US based ISP keeps placing their own IP addresses into an SMTP blocklist because they are dynamically allocated and apparently should not send mail (even to their own SMTP server) They use a blocklist from spamhaus.

In a world of Microsoft Exchange servers which do not use any of the open source protocols by default, technicians for SMTP servers are, I think in short supply, so silly things keep getting done.