当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Thunderbird 52.1.1 doesn't work on MacOS el capitan

  • 7 件の返信
  • 2 人がこの問題に困っています
  • 9 回表示
  • 最後の返信者: 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.

すべての返信 (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.

この投稿は starswan により に変更されました

more options

what type of imap server?

more options

Dovecot 2.2.9 on Ubuntu 14.04

この投稿は starswan により に変更されました

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.

この投稿は starswan により に変更されました