search

whiteout-io / mail

[ABANDONED] Mail App with integrated OpenPGP encryption
https://whiteout.io
MIT License
545 stars 96 forks source link

Error message: Could not parse certificate list. #385

Closed deltaman closed 9 years ago

deltaman commented 9 years ago

Hi,

When creating a new account on the first time I get the error message: Could not parse certificate list.

When using IMAP with TLS(993), although this is working with Thunderbird.

Hugo

lenovouser commented 9 years ago

:+1: Same error here.

deltaman commented 9 years ago

I have also testen the Certificate chain with the app SSL Detective, that app showed me that there was an intermediate certificate was not trusted. I have installed the COMODO certificate and testes again. Although the SSL Detective app showed me that the certificate chain was trusted, whiteout mail is still gives me the same error.

deltaman commented 9 years ago

After updating to version 1.2.0, login seems to succeed for IMAP:993.

Now I am getting the same error for SMTP STARTTLS

felixhammerl commented 9 years ago

On the desktop: Please use the chrome app, as it supports native tls.

On iOS/Android: Starting with version 1.2.0, we use the native TLS stack for TLS connections, NOT STARTTLS.

The webapp and STARTTLS on iOS/Android default to using forge because of this bug:

https://github.com/MobileChromeApps/mobile-chrome-apps/issues/532 https://github.com/MobileChromeApps/mobile-chrome-apps/issues/269 https://code.google.com/p/chromium/issues/detail?id=467677

Problem is: Google does not seem to care about fixing its API...

deltaman commented 9 years ago

Does this mean that if I want to use this app that I have to change the server configuration? So that SMTP to work with TLS?

Op 7 jul. 2015 om 11:30 heeft Felix Hammerl notifications@github.com<mailto:notifications@github.com> het volgende geschreven:

On the desktop: Please use the chrome apphttps://chrome.google.com/webstore/detail/whiteout-mail/jjgghafhamholjigjoghcfcekhkonijg, as it supports native tls.

On iOS/Android: Starting with version 1.2.0, we use the native TLS stack for TLS connections, NOT STARTTLS.

The webapp and STARTTLS on iOS/Android default to using forgehttps://github.com/digitalbazaar/forge because of this bug:

MobileChromeApps/mobile-chrome-apps#532https://github.com/MobileChromeApps/mobile-chrome-apps/issues/532 MobileChromeApps/mobile-chrome-apps#269https://github.com/MobileChromeApps/mobile-chrome-apps/issues/269 https://code.google.com/p/chromium/issues/detail?id=467677

Problem is: Google does not seem to care about fixing its API...

— Reply to this email directly or view it on GitHubhttps://github.com/whiteout-io/mail-html5/issues/385#issuecomment-119136439.