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.

Thunderbird 52.1.1 doesn't work on MacOS el capitan

  • 7 respostas
  • 2 têm este problema
  • 1 exibição
  • Última resposta de starswan

more options

I've upgraded to Thunderbird 52.1.1, and it now doesn't sync with my IMAP server (pretty standard SSL). I run my own IMAP server and it doesn't even seem to attempt the login. I've tried removing profiles etc but nothing fixes it. I'm running MacOS X El Capitan. It was working fine with 45.8.0 before the upgrade.

I've upgraded to Thunderbird 52.1.1, and it now doesn't sync with my IMAP server (pretty standard SSL). I run my own IMAP server and it doesn't even seem to attempt the login. I've tried removing profiles etc but nothing fixes it. I'm running MacOS X El Capitan. It was working fine with 45.8.0 before the upgrade.

Todas as respostas (7)

more options

Does it involve startcom ssl?

more options

I'm not sure - how can I find out? I've looked at the server cert files and they don't reveal anything useful. I don't think so.

Alterado por starswan em

more options

what type of imap server?

more options

Dovecot 2.2.9 on Ubuntu 14.04

Alterado por starswan em

more options

open Thunderbird error console and clear it. try and get mail. Any errors appearing in the console?

more options

Nothing in the error console other than:

downloadable font: download failed (font-family: "Lato" style:normal weight:normal stretch:normal src index:0): content blocked source: https://fonts.googleapis.com/css?family=Lato&subset=latin,latin-ext

it seems to be unable to connect to anything.

more options

Sorry, turns out we are using StartCom SSL certificate. No warning from Thunderbird, just never connected. I thought normally you got a dialog saying that the certificate wasn't trusted? I've definitely seen one in the past when using a self-signed certificate.

Alterado por starswan em