Comment by zappAtom
Ok, I just made some checks and for me synching with my existing account still works! Also with the new update! There are some remarks & bugs I still have for activeSync (see this thread:...
View ArticleComment by daywalker
please read my initial post. my account stopped syncing after update. and adding a new account doesn't work since then.
View ArticleComment by zappAtom
My (existing) account continues to work in 1.1.9.28 - so it seems to only affect new set ups, or?
View ArticleComment by shertell
Didn't work for me either. Last update from today from Jolla Care is that their devs have nothing new regarding this. This sucks big time.
View ArticleComment by daywalker
didn't work for me though. we don't have any server side restrictions...
View ArticleAnswer by tvicol for Can't add Microsoft Exchange account since 1.1.9.28 update
This worked for me: Go to Settings -> Device lock and change "Automatic locking" to 5 minutes. Than change number of tries to 5. Security code must have at least 6 numbers.
View ArticleComment by chris.adams
Further investigation showed a couple of issues - one related to SSLv3, but the other related to the cipher version which are supported by the base OS. In some cases (e.g., Windows Server 2003) there...
View ArticleComment by SlOrbA
@chris.adams Thanks for your effort and after reading the rfc7568 I'll actually start using my company Exchange only after TLSv1.1 or newer is available.
View ArticleComment by chris.adams
@late88 @shertell I understand completely, and thanks for your patience up to this point. I hope that in the future we're able to improve our level of protocol and server support to include legacy...
View ArticleComment by shertell
Unfortunately I have to change to another device too. Calendar is that important in daily life nowadays. This is a big dissapointment.
View ArticleComment by late88
I'm afraid I have to change back to android only because of this bug. It's a must have feature for me to cope with my work. Really sad :(
View ArticleComment by SlOrbA
I've been able to duplicate the effect with cURL, but with cURL I'm also able to override defaults with flags. I don't know if cURL project is using the same libraries and how Exchange client calls the...
View ArticleComment by chris.adams
I know very little about that so I cannot comment. We are looking into the possibility of providing an option in the account page to "Allow Insecure SSL Versions" but I can't give an ETA on when that...
View ArticleComment by SlOrbA
Can I make some Proxy configuration with a squid I own to circumvent this issue?
View ArticleComment by SlOrbA
@chris.adams can you provide workaround SSLv3/TLSv1 enablement method for those willing to solve the issue by them selves until either Jolla or the exchange operators provide the more permanent solution?
View ArticleComment by chris.adams
Right, apparently we upgraded our SSL stack to disallow SSLv3 by default, as that has a security issue. We will look into providing an option (opt-in) to allow a particular account to use insecure SSL,...
View ArticleComment by chris.adams
Thank you for this information! We will follow up on these leads and try to keep everyone informed as to our progress.
View ArticleComment by rudi10
I suggest you continue inspecting Sailfish's ssl-stack. I got a tcpdump when trying to create an Exchange account to company server. Excange responds to SSL Client Hello packet with FIN, ACK packet...
View Article